Pricing
Pricing that doesn't need a decoder ring.
A flat platform fee plus a one-time implementation. No per-seat meter, no locked modules, no line item you discover at renewal. The number depends on your migration — so it comes on a walkthrough, not a landing page.
One fee for the platform. One project to get on it.
You pay a flat platform fee to run the system, and a one-time implementation to get your data and your people onto it. That is the whole shape of it.
- No per-seat meter. Every foreman, PM and clerk who needs the system gets it. You do not pay more for putting timecards in the field.
- No modules to unlock. Job cost, union payroll, certified reports, AIA-style billing, retention and field apps are one product — on every account.
- No usage tricks. Pay runs, jobs, invoices and reports are not metered events.
What actually moves the number.
Three things drive a quote, and none of them is how many people log in. They are how big your field is, how much history has to come across, and how many entities you keep books for.
A single-company sub moving one payroll and a year of open jobs is a different project from a multi-entity contractor bringing a decade of history. We price the work, not your seat count.
| Driver | What we look at |
|---|---|
| Field headcount | <25 / 25–100 / 100+ crew on payroll |
| Migration scope | Years of history and system(s) you run today |
| Companies / entities | Single company, multi-company, joint ventures |
Founding subs shape the product — and the terms.
We are onboarding a small number of founding subcontractors. They get direct influence over what gets built next, and their terms reflect the fact that they are helping prove the product on their own jobs.
That window closes as the cohort fills. Public, published pricing follows once the founding cohort completes.
What the implementation actually buys.
Implementation is the work, not a fee for the privilege of paying us:
- Data migration from whatever you run today — QuickBooks and spreadsheets, a payroll service, or a legacy construction ERP — with your open jobs, AP/AR and payroll history carried across.
- Onboarding by the team that built it — role by role, from foreman timecards to the payroll run to AR billing — not a login and a PDF.
- A parallel run against your existing books before anyone relies on the new numbers.
Why there's no number on this page.
Migration scope is the biggest variable, and it is different for every contractor. Putting a headline figure here would either overcharge the simple cases or lowball the hard ones. So the quote comes after a walkthrough, where we can see what you run today and scope the move honestly. No obligation, no sales engineer relay.
How buying this works.
No pressure sequence, no sales-engineer relay. Four steps, and the one that matters is the parallel run — you switch when you trust the numbers, not when a contract says so.
- 01
Walkthrough
45 minutes on your real workflows. Bring your controller and your owner.
- 02
Scoped proposal
We look at your current books and data, then quote a fixed implementation and a flat platform fee. No pressure sequence.
- 03
Parallel run
We stand the system up next to your current one and reconcile until the numbers match. You switch when you trust it — not when a contract says so.
- 04
Founding agreement
Plain paper: flat fee, no per-seat schedule, and your data is yours (standard SQL export) on the way in and on the way out.
Pricing questions, answered straight.
How long is the contract?
What does the contract look like?
What's extra?
Cloud or self-hosted — does it change the price?
When does pricing become public?
Get a real number for your operation.
Tell us your field size, what you run today, and how much history has to move. We come back with a scoped quote — not a range.
A walkthrough is 45 minutes on your real workflows.