Revenue doesn’t disappear. It leaks. And it leaks in the same places in almost every service business: the gap between an accepted quote and a scheduled job, the gap between a completed job and a sent invoice, and the gap between a sent invoice and a collected payment. Fix those three gaps and you have a tighter operation.

Start With the Map

Before you fix anything, map your current job workflow on paper. Every stage a job moves through from first contact to final payment. Include every step, even the ones that feel too obvious to write down.

Most service business workflows look something like: inquiry → quote → quote accepted → scheduled → dispatched → in progress → completed → invoiced → paid.

The stages aren’t the problem. The handoffs are.

The Handoffs Where Revenue Leaks

Quote accepted → scheduled. An accepted quote that doesn’t get booked is a job that exists on paper but not on the calendar. This leak happens when the quoting and scheduling functions live in different places — one person sends the quote, a different person does the scheduling, and the hand-off between them is an email or a phone call that sometimes gets missed.

The fix: the moment a quote is accepted, booking the job should be the next required action in the system. Not a reminder. Not a notification. A required step that can’t be skipped.

Completed → invoiced. This is the most expensive leak in most service businesses. The job is done. The customer is satisfied. And then the invoice sits — because someone forgot, or because the invoicing step requires manual data entry from the job notes, or because the tech completed the job at 7 PM and no one processed it until two days later.

Every day between job completion and invoice sent increases the chance the payment gets delayed or the customer disputes something they’ve already moved on from.

The fix: invoice generation should be automatic at job completion. Not manual. Automatic.

Invoiced → paid. Invoices that don’t have a clear payment method and a clear deadline get paid slowly. Invoices that arrive by email with a PDF attachment get paid slower than invoices with an embedded payment link. Invoices with no follow-up after 7 days get paid whenever the customer gets around to it.

The fix: every invoice should have an embedded payment link, a clear due date, and an automated reminder sequence that fires if payment isn’t received.

How to Map Your Current Leaks

Pull the last 30 completed jobs. For each one, calculate: days from quote accepted to job scheduled, days from job completed to invoice sent, and days from invoice sent to payment received.

Average those numbers. The averages tell you where your biggest leaks are. If your average time from completion to invoice is 4 days, that’s your most urgent fix. If your average time to payment is 22 days, your invoice and follow-up process needs work.

Building the Workflow

Whatever system you use, the aim is the same: one job record that carries a job from inquiry to payment. When the job is marked complete, the invoice is created from the job record, goes out the same day with a payment link, and a reminder fires at day 7 if it’s unpaid. Configure it once, and every job moves through the same stages, regardless of who is handling it.

That consistency is the real operational win. Not the software — the consistency the software enforces.

For how a job moves through those stages, read how a job should flow from first call to final payment. The quote-to-job gap goes deeper on the first leak, and invoicing software for service businesses covers the second and third.

Frequently Asked Questions

What’s the right number of stages in a job workflow?

As many as necessary to reflect how a job actually moves through your operation — no more. Many service businesses work well with six to eight stages. More than 10 usually means you’re tracking intermediate steps that don’t need to be formal stages.

Should every job type follow the same workflow?

Standard jobs should follow the same workflow. Complex jobs or project-based work may need a separate workflow with additional stages for milestones, approvals, or multi-visit scheduling.

How do I handle jobs that get cancelled partway through?

Every workflow should have a clear cancellation stage that records: when the job was cancelled, at what stage, and why. This data is useful for identifying patterns — if 30% of your cancellations happen after scheduling but before dispatch, something in that window is creating friction.

What happens to the quote data when a job is created from it?

In a connected system, the accepted quote flows directly into the job record. Line items, pricing, customer details — they don’t need to be re-entered. The job is created from the quote, not rebuilt from scratch.

Co-authored by Brandon Sheriff and OLIVER, the field service and job management platform from Intelligent Analytics and Data Management.