Deal Stages for Service Businesses: Enquiry to Paid

Deal Stages for Service Businesses: Enquiry to Paid

Most service businesses don't lose deals because their pipeline stages are wrong - they lose deals because they have no stages at all. Enquiries live in an inbox, quotes in a folder, "hot leads" in someone's head, and the honest answer to "what's in the pipeline right now?" is a shrug. Deal stages fix that. They give every opportunity a clear place in a journey from first contact to paid invoice, so you can see what's where, what needs action, and what your pipeline is actually worth. But the stages have to be right - too few and they're useless, too many and they become admin nobody keeps up.

This guide lays out a practical set of deal stages for a service business, how to keep them useful, and why extending them through to "paid" matters.

What deal stages are for

A stage is a step an opportunity moves through, and each one should represent a real change in how likely the deal is to close. The value isn't the labels - it's that well-defined stages turn a vague pile of "people who might book" into a readable pipeline. At a glance you can see how many deals are at each step, which are stuck, and what the whole thing is worth. That readability is what makes a pipeline a management tool rather than a list.

A practical set of stages

Keep them simple and tied to events, not feelings. A solid default for most service businesses:

1. New Enquiry - someone got in touch.
2. Qualified - it's a genuine fit worth pursuing.
3. Quoted - an estimate has been sent.
4. Won - they've said yes.
5. Scheduled / Paid - the work is booked, delivered, and invoiced.

Five stages is plenty. Each maps to something that actually happened, so moving a deal forward is unambiguous - no debating whether a deal is "kind of" at the next step.

Keep the stages event-based

The test for a good stage: can you instantly say what has to happen for a deal to move to the next one? If not, you have the wrong stages or too many. Event-based stages ("quote sent," "client said yes") are objective - everyone places the same deal in the same stage. Feeling-based stages ("warming up," "very interested") are subjective, so different people sort the same deals differently and the pipeline stops meaning anything.

Stage vs status

A stage is where a deal is in its journey; a status is a condition on top of it (active, on hold, lost). A deal can sit in "Quoted" with a status of "awaiting decision." You don't strictly need both for a simple pipeline - clear stages plus a "lost, with a reason" option usually suffices - but the distinction helps when a deal stalls without actually moving backward. The important habit either way: mark lost deals lost, with a reason, so the pipeline stays honest.

Why "paid" belongs in the pipeline

For a service business, a deal isn't done when the client says yes - it's done when the work is delivered and the invoice is settled. Extending the pipeline through a final Scheduled/Paid stage means it reflects reality all the way to cash in the bank, and it connects selling to fulfilment and billing instead of treating "won" as the finish line. Plenty of "won" deals quietly die between yes and payment; a stage for it keeps them visible.

Stages are only as good as the discipline behind them

A pipeline with perfect stages that nobody updates is worse than no pipeline, because it looks authoritative while being wrong - you make decisions on a picture that's out of date. The discipline that makes stages work is small but non-negotiable: every deal gets placed when it arrives, moved when its trigger event happens, and marked lost (with a reason) when it dies. Done in the moment, this takes seconds per deal; left for a monthly cleanup, it becomes archaeology nobody has time for. The businesses that get real value from a pipeline aren't the ones with the cleverest stages - they're the ones who keep the board current, so a glance always reflects reality rather than last month's optimism. Simple stages you actually maintain beat sophisticated ones you don't.

How to set it up (step by step)

1. Define 5-6 event-based stages from enquiry to paid.
2. Write the trigger for each - what moves a deal forward.
3. Extend through delivery and payment, not just "won."
4. Mark lost deals lost, with a reason, so the pipeline is honest.
5. Review the board regularly - spot stuck deals and act.
6. Resist adding stages unless a real gap in visibility demands it.

Which numbers tell you it is working

• Conversion rate between stages - where deals fall out tells you what to fix.
• Time-in-stage - deals sitting too long flag stale opportunities.
• Won-to-paid gap - how many "won" deals stall before payment; the final stage makes this visible.

Setting it up in Tregovia

Add-on that matters:

• Sales Pipeline (EUR 10/month): pipelines with customisable stages shown as a Kanban board, so you drag deals from stage to stage, with activity logged on each deal.

Typical setup: base plan (EUR 47/month) + Sales Pipeline (EUR 10/month) = EUR 57/month, letting you define the stages that fit your service business and see the whole pipeline at a glance.

For a shorter buyer answer on stages, Kanban boards, stale deals, and forecasting, see the sales pipeline FAQ.

What Tregovia is not

Tregovia's Sales Pipeline gives you customisable, Kanban-style deal stages with logged activity - it is not a heavyweight enterprise CRM with automated lead scoring, territory management, or commission calculation. For a service business that wants a readable pipeline from enquiry to paid, customisable stages on a drag-and-drop board are exactly right; if you need complex sales-force automation, a specialist enterprise CRM goes further. The strength here is simplicity you'll actually keep up to date.

The bottom line

Deal stages don't win deals by themselves - but they make your pipeline readable, your forecast honest, and your stuck opportunities visible. Use five or six event-based stages from enquiry to paid, keep them objective so everyone sorts deals the same way, and extend them through delivery and payment so a "won" deal that never pays can't hide. Keep it simple enough that you actually update it, and the pipeline becomes the clearest picture you have of where your next revenue is coming from.

Frequently asked questions

What are deal stages?

Deal stages are the steps an opportunity moves through from first contact to won or lost - for a service business, typically something like enquiry, qualified, quoted, won, and then delivered/paid. Each stage represents a real change in how likely the deal is to close. Well-defined stages turn a vague list of "people who might book" into a readable pipeline where you can see exactly where everything stands.

What deal stages should a service business use?

Keep it simple and tied to real events, not feelings. A solid default: New Enquiry (someone got in touch), Qualified (it's a genuine fit), Quoted (estimate sent), Won (they said yes), and Scheduled/Paid (delivered and invoiced). Five or six stages is plenty for most service businesses - more than that and the pipeline becomes admin. Each stage should map to something that actually happened, so moving a deal forward is unambiguous.

How many stages is too many?

If you can't instantly say what has to happen for a deal to move to the next stage, you have too many - or the wrong ones. Overly granular pipelines (ten stages with fine distinctions) create busywork and inconsistency, because different people place the same deal differently. Fewer, event-based stages are more useful: they're faster to update and everyone agrees where a deal sits.

What's the difference between a stage and a status?

A stage is where a deal is in its journey (Quoted, Won); a status is a condition layered on top (active, on hold, lost). A deal in the "Quoted" stage might have a status of "awaiting client decision." You don't strictly need both for a simple pipeline - clear stages plus a "lost, with reason" option usually covers it - but the distinction helps when a deal stalls without moving backward.

Should 'paid' be a deal stage?

For a service business, extending the pipeline through to delivered-and-paid is often useful, because the deal isn't really "done" when they say yes - it's done when the work is delivered and the invoice is settled. Including a final Scheduled/Paid stage means your pipeline reflects reality through to cash in the bank, and it connects selling to fulfilment and billing rather than treating "won" as the finish line.

How does Tregovia handle deal stages?

The Sales Pipeline add-on (EUR 10/month) provides pipelines with customisable stages, shown as a Kanban board so you can move deals from one stage to the next, with activity logged on each deal. You can define the stages that fit your service business - enquiry through to won - and see the whole pipeline at a glance, on top of the base plan (EUR 47/month).