Straight answers

No, and we'd be suspicious of anyone who told you to switch general ledgers mid-year. QuickBooks Online stays your book of record and your accountant keeps working the way they already do.

Site OS is where the cost gets read, coded, argued about, approved, released and billed to your client. That's the work QuickBooks was never built for. A browser bridge then fills the matching QuickBooks bill form. It fills fields only; it never clicks Save.

You correct it, and the correction becomes history the next match learns from, so the same vendor lands in the same cost class next time.

More importantly, the system is built to decline rather than guess. If two of your jobs sit on the same street and the invoice doesn't carry a house number, the cost is left unassigned and flagged for a person. A blank field costs you thirty seconds. A confident wrong answer bills the wrong client, and on cost-plus that's a trust problem, not a bookkeeping one.

Per project, from a configuration that matches what your contract actually says: percentage or fixed, with the cost categories your agreement excludes handled explicitly rather than remembered. Costs roll into the client billing with the fee applied the same way every month, which means the number you send and the number in your contract don't drift apart.

Yes. Share links and portal views are scoped to the sections you pick. You decide whether a client sees the cost detail, the documents behind each line, progress photos, the schedule, or only the billing summary. Views are logged, so "I never got that" has an answer.

All four California statutory waivers: conditional and unconditional, on progress payment and on final payment.

Which one you're offered is driven by whether the vendor has actually been paid (the payment record decides that, not whoever is filling in the form) and by whether the invoice completes their billing on the job, read from the contract total against billed-to-date plus retention and "final" language on the document itself. The reasoning is shown in plain language before anything is sent.

Certificates, general liability and workers' comp expiry are held per vendor and per job, so an expired policy surfaces before the sub is back on site rather than after. It reflects the documents in your account, and it isn't a substitute for obtaining a current certificate, and nothing about it is a guarantee against a carrier cancelling mid-job.

Yes. There's a searchable licence lookup covering every licensed contractor in the state, built in, so vetting a new sub doesn't mean leaving the system for a government website.

No. Vendors receive release requests and documents by email. Clients reach their project portal through an emailed link rather than a password they'll have forgotten by the next billing. That matters more than it sounds. A portal your client can't get into is a portal that generates phone calls.

That's the assumption it was built under. The field surfaces (daily logs, time entry, receipt capture) are the light ones, and the phone layout gives a superintendent the same destinations an admin gets on a desktop rather than a stripped-down subset of them.

Access is a named profile, plus per-project assignment, plus per-user overrides. Finance, company cards, executive review and business development are each gated separately, so a superintendent with full access to their three jobs still can't open the card statement.

Every table carries an organization column with row-level security policies enforced by Postgres itself. The isolation doesn't depend on the application remembering to filter, which is the failure mode that actually matters in shared systems.

Yes. Bills, invoices, documents and photos export on request in a machine-readable format, during your subscription and for 90 days after it ends. Leaving should be a task, not a negotiation.

Row-level changes are captured append-only, so you can see who changed what and when, and put a bad edit back. Unusual bursts of activity raise an alert rather than waiting to be noticed.

$500 a month, flat, covering up to 15 active jobs with unlimited users and every module included. Additional active jobs are $25 each. Closed jobs stay readable and don't count. Full pricing.

Yes. Imports run in batches so you can check a slice before committing the rest, and there are merge tools for the duplicate vendors and jobs every real migration turns up. Cost classes and vendor-to-class mappings come along too, which is what makes the automatic coding useful in week one instead of month three.

Most offices are coding live bills the same week they import. The honest constraint isn't the software. It's how quickly your team stops emailing invoices to each other out of habit.

A person who built it, reachable through the same list you joined rather than a ticket queue.