Implementation & support

Implementation by the people who built it.

No reseller, no offshore rollout team, no ticket robot. The people who wrote the system and reconciled it against fifty years of books are the people who move your data and answer your questions.

01Migration

Moving your books is what we do — at a smaller scale.

Migration is not a risk we manage around; it is the core competence. We moved fifty years of one contractor’s books and more than 3,300 jobs into this system and reconciled every number to the penny before anyone relied on it.

Your QuickBooks file, your payroll service export or your legacy construction ERP is a smaller version of a problem we have already solved. Open jobs, AP/AR balances and payroll history come across — not just a fresh empty database.

02Onboarding

Onboarding by role, not one generic training.

A foreman entering timecards and a payroll clerk running the weekly union cycle do not need the same session. So they do not get the same session.

  • Foremen — timecards from a phone: job, phase, workcode, RT/OT/DT, and daily reports.
  • Payroll — ratecards, fringe, garnishments, preflight checks and the print run.
  • AR & AP — progress billing with retention, and bulk payment runs with positive pay.
03Support model

A direct line to the building team.

When something is wrong at 6am on payroll Tuesday, you do not want a tier-one script. You reach the people who built the part that broke.

There is no tiered ticket queue between you and the engineers. That is only possible because the founding cohort is small — and it is a deliberate part of the founding offer.

04Walkthrough

What a walkthrough actually is.

A walkthrough is 45 minutes on your real workflows — your trades, your jobs, your payroll cadence. Not a slide deck, not a canned demo environment. You tell us what you run today and how big your field is; we show you the same work in this system.

05FAQ

Implementation questions.

How do you handle cutover?
A parallel run. The new system operates alongside your existing one and reconciles to it before anyone depends on the new numbers. You switch when the books agree, not on a calendar date.
What data can you actually migrate?
Open jobs and job history, AP/AR balances, vendor and customer records, and payroll history — from QuickBooks and spreadsheets, a payroll service, or a legacy construction ERP. Exactly what comes across is scoped on the walkthrough against what you run today.
How long does it take?
Honestly, it depends on migration scope — years of history and number of entities drive it more than headcount. We won't quote a fixed number sight-unseen; we scope it after seeing your current system, and we run in parallel so you are never forced to switch before you are ready.
Who runs the implementation?
The team that built the system and reconciled it against the reference contractor's fifty years of books. Not a reseller or a separate services vendor.

Meet the team that would run your migration.

Bring your current system and your field size. We will tell you honestly what the move looks like.

45 minutes on your real workflows.