How to cost contractor jobs and change orders on Starch

Ops & Supply2 roles covered3 Starch apps

Contractor job costing is the practice of tracking what a job actually costs — labor, materials, subcontractors, equipment — against what you estimated, and updating that number as work progresses and change orders land. It sounds straightforward until you're three weeks into a project and the change order log lives in one spreadsheet, the invoices are in QuickBooks, the crew hours are in a time-tracking app, and nobody has a current cost-to-complete figure. The result is that you find out a job lost money after it closes, not while you still have levers to pull. What this workflow looks like in practice varies — a GC running multi-trade projects has different data flows than a specialty sub or a facilities operator managing a vendor roster — but the core problem is the same: too much latency between when costs are incurred and when someone who can act on them sees them. On Starch, you end up with a live job cost view that pulls your actual spend from QuickBooks or your bank accounts, sits next to your original estimate and any approved change orders, and flags jobs where cost-to-complete is trending over budget. No manual export. No reconciliation sprint at month end. You see the number on the job, updated, when you open the dashboard — and if a job crosses your contingency threshold, you hear about it before the next site visit.

Ops & Supply2 roles covered3 Starch apps
Context

Why it matters

Why this is hard today

Margin on contractor work disappears fast when change orders aren't priced correctly or costs aren't tracked job by job. A 10% cost overrun on a $200K job is $20K you didn't plan on. Multiply that across four concurrent jobs and you have a cash problem, not a rounding error. Getting job costing right means you can see which project types are actually profitable, which subs consistently blow budgets, and where your estimates are systematically off — information that compounds into better bids over time.

Watch out for

Common pitfalls

Where this usually goes wrong

The most common mistakes: treating change orders as paperwork rather than margin events — logging them for the record but never checking whether the approved amount actually covered the scope. Running job costs against invoices only, ignoring committed costs like POs and signed sub agreements, so your cost-to-complete is always understated. Reconciling job costs monthly when most projects have a shorter cycle, so overruns surface too late to recover. And mixing overhead allocations inconsistently across jobs, which makes it impossible to compare project profitability in any meaningful way.

Toolkit

Starch apps used

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →
Pick your role

Choose your operator

A version of this guide tailored to your role — same recipe, different starting context.

Run cost contractor jobs and change orders on Starch

You're on the list! We'll be in touch soon.