Answers, grouped by who's asking.

Nightly. Field timecards captured during the day post to the cost ledger overnight, so you see burdened cost against budget within the week — not reconstructed at closeout months later. More on job costing →

Raw wages understate true cost, so every labor dollar is loaded with its burden — Labor OH, payroll burden and spread — and carried to the job automatically. The number you see is fully-burdened, not base wages. How burden flows →

Native. The GL, AP and AR are one system with job cost — there is no nightly export-and-reconcile loop between a job-cost tool and a separate general ledger. More on accounting →

Yes. Access is role- and project-scoped: a foreman signs in to his crew’s timecards and daily reports on his jobs, and nothing else — not payroll, not another PM’s budgets. More on field operations →

Yes. Ratecards carry union locals, classifications and effective dates, so a rate that changes mid-period applies from its effective date without re-keying hours or hand-patching the run. More on union payroll →

Yes — the reference contractor runs roughly 500 paychecks a week through it, with fringe, garnishments and preflight checks before the print run. The full pay cycle →

The real public-works shelf — Public Works, Certified Job List, Prevailing Wage Jobs, Employment Utilization, Local Hire, and apprentice reports like Lone Apprentice and 500 Hour, among others. Agency formats are confirmed on the walkthrough. The report shelf →

AB 889 makes fringe annualization mandatory and bans frontloading from January 1, 2026, with a 10-day DLSE records deadline. Burdened union labor is native here, which is exactly where systems that stop at the pay run struggle. We walk through annualization operationally on a call. On AB 889 →

Open jobs and history, AP/AR balances, vendor and customer records, and payroll history — from QuickBooks and spreadsheets, a payroll service, or a legacy construction ERP. Exact scope is set against what you run today. More on implementation →

As a parallel run. The new system operates alongside your current one and reconciles to it before you depend on the new numbers — the same way the original rebuild was proven penny-exact against fifty years of books. The cutover approach →

Your choice: managed cloud, or self-hosted on your own infrastructure. Access is role- and project-scoped, and a draft/submit document workflow gives you an audit trail on every financial record. More on security →

Not today, and we will not claim a badge we have not earned. A formal SOC 2 attestation is on the roadmap for the productized offering; when it exists it will be a real report you can read. How we state the roadmap →

No. There is a flat platform fee and a one-time implementation — no per-seat meter and no modules to unlock. Every foreman, PM and clerk who needs the system gets it. How pricing works →

Because migration scope is the biggest variable and it differs for every contractor. A headline number would overcharge the simple cases or lowball the hard ones, so the quote comes after a walkthrough. Public pricing follows as the founding cohort completes. More on pricing →

One real, honest reference — a 90-year union wall-and-ceiling subcontractor in Southern California whose operation this system runs. No invented logos or star ratings; you can talk to the reference on a call. The reference →

One native system covers the whole back office — job cost, union and certified payroll, AIA-style billing and field apps — with no per-seat meter and a modern web and mobile interface. Spreadsheets miss job cost, payroll-layer tools stop at the pay run, and legacy ERPs price by the seat. The full comparison →