How should a contractor workflow run from lead to invoice?
Straight answer up front. Then the details.
The short answer
Ten stages, and every one of them needs a named owner: lead, qualification, estimate, approval, schedule, field work, change or exception, completion, invoice, follow-up. The stages aren't the hard part — the handoffs between them are. That's where jobs stall, details vanish and money leaks.
Your workflow won't match this map exactly, and it shouldn't. The point is that someone owns every handoff — and it can't all be you.
The map
Here's the full path a job travels, with the question each handoff has to answer. Read it against your own operation and mark every stage where the honest owner is "the owner" or "whoever notices."
Lead to invoice — owners and handoffs
- Lead comes inOwner: Whoever answers — but one named personHandoff risk: the call gets answered but never recorded. Capture who, where, what, when.
- QualificationOwner: Office or ownerDecision: is this our kind of work? Unqualified leads that linger clog everything downstream.
- EstimateOwner: Estimator or ownerMeasure it: how long from site visit to estimate sent? Slow estimates lose sold work.
- ApprovalOwner: OfficeHandoff risk: the customer says yes by text and nobody moves it forward. Approval needs one channel.
- ScheduleOwner: Dispatcher / schedulerThe sold-to-scheduled handoff is the most commonly unowned step in small operations.
- Field workOwner: Crew leadThe crew needs the estimate, the scope, the site details — without calling the office for them.
- Change / exceptionOwner: Crew lead escalates, office recordsExceptions are normal. Unrecorded exceptions are how approved work goes unbilled.
- CompletionOwner: Crew leadDecision: what counts as done? Photos, sign-off, punch list — defined once, not per job.
- InvoiceOwner: OfficeMeasure it: days from completion to invoice sent. This number is pure cash flow.
- Follow-upOwner: OfficeReviews, warranty, repeat work. The cheapest lead source you have — and the most skipped stage.
Every handoff needs five things
For each arrow on the map, define:
- An owner — one name, not a role shared by everyone
- A trigger — what event moves the job to the next stage
- A status anyone can see without asking
- An exception path — what happens when it doesn't go to plan
- A measurement — one number that tells you the handoff is healthy
Exceptions are where money leaks
The happy path — lead, estimate, job, invoice — mostly runs itself. What separates smooth operations from chaotic ones is what happens when the customer changes the scope mid-job, when a part doesn't show, when rain moves the schedule. If exceptions get handled by phone calls and memory, they leak: unbilled change orders, forgotten follow-ups, crews standing around. A workflow isn't real until its exceptions have a path.
Your version won't match this — that's the point
A service plumber and a remodeler run genuinely different workflows, and neither should force their operation into a generic map. Use this one as a mirror, not a mold: walk one real job through your version, stage by stage, and write down every place it moved because you personally pushed it. Those are your bottlenecks — and they're exactly what the Systems Audit measures.
ACS guidance — written from operator experience building systems for contractors, not from vendor marketing. Last reviewed August 10, 2026.
Our approach
We design systems around your business.
Built from inside the operation—not from the sidelines. The people doing the work help shape the system.
- Listen
- Map
- Build
- Test
- Refine
Worked with Connor
He Helped Me Believe
Robert shares how working with Connor helped him believe in himself, gain clarity around his purpose and begin turning his mission into something real.
Watch Robert’s storyWhere to go from here
Not sure which side you’re on?
Walk through the Systems Audit and we’ll point you in the right direction — even if the answer is a tool you already have.
Take the Systems Audit- About two minutes
- No sales call required