One record per job, from booked to billed.

From $25,000, with most V1 systems landing between $25,000 and $65,000 depending on how much of the workflow it covers and how many systems it has to talk to. The comparison that matters isn't build cost against a subscription — it's build cost against what the manual coordination is costing you now. Scope and price are fixed in writing before any code exists.

Not automatically, and I'll say so on the call. If your workflow matches how those platforms are designed to work, they're cheaper, faster and genuinely the right buy. Custom makes sense when your real process breaks them — job stages they can't model, pay rules they won't handle, reporting they won't produce, or per-seat pricing that punishes you for hiring.

There's no headcount threshold — the trigger is friction, not size. A six-person crew losing ten hours a week to double entry has a stronger case than a thirty-person company whose off-the-shelf tool genuinely fits. The clearest tell is people keeping a spreadsheet alongside the software you already pay for.

Yes. It's built mobile-first so crews see assigned jobs, update status, capture photos and add notes from a phone. For canyon and rural job sites, key screens can be built offline-capable so they queue up and sync when signal returns instead of failing outright — that's a scoping decision, since offline support is real engineering.

It gets migrated as part of the build, not treated as an afterthought. Spreadsheets, an export from your current platform or a database — the customer list, job history and open work come across. What exactly comes over is agreed during scoping so nothing gets discovered on launch day.

Six to twelve weeks from signed scope. The date holds because the V1 feature list and an explicit out-of-scope section are written down first, so nothing gets quietly added. You see working features weekly, and your office manager and one crew lead should use it before launch — they find things nobody else would.