How to build a sales pipeline for a service business

1. Map the buying process before naming the stages

Start with one service and write down what normally happens between the first enquiry and a confirmed sale.

Does the customer need an assessment? A site visit? A written quote? Approval from someone else? A deposit before booking?

Use those steps to shape the pipeline.

A straightforward booking and a project requiring several assessments may need different processes. But you don’t need separate pipelines simply because two services have different names.

Create another pipeline when the steps are meaningfully different.

2. Give every stage a clear entry condition

Here’s a starting framework you can adapt:

These names aren’t compulsory. An assessment-based business might add “Site visit scheduled” or “Assessment completed.”

The important part is the evidence behind each move.

Preparing a quote internally doesn’t mean it has been sent. Following up doesn’t mean the customer has accepted. Interest alone doesn’t confirm a booking.

3. Keep follow-ups separate from stages

“Follow-up” tells your team that something needs doing. It doesn’t explain where the customer is in their decision.

You might need to follow up while clarifying a requirement, after sending a quote or while waiting for booking details.

Keep the opportunity in the stage that reflects its current position. Give the follow-up its own:

• Clear action.
• Responsible person.
• Due date.
• Relevant conversation context.

“Call the customer on Thursday to confirm the proposed service date” is more useful than “Follow up.”

4. Agree what won and lost mean

Choose the point at which your business considers the sale won.

That might require an accepted offer, a signed agreement or a required deposit. A confirmed booking may be the right point for your business, but define it explicitly.

Keep lost opportunities separate, with a reason where known. If the reason is unknown, record that rather than assuming it was price.

Remember that one customer can have several opportunities. Winning one job doesn’t mean every other purchase they’re considering is also won.

5. Use this template to define each stage

Before adding another column, complete these five lines:

Then test the definitions with your team. Would two people put the same opportunity in the same stage?

If not, clarify the condition before adding more complexity.

Putting the framework into Qonvera

Qonvera lets you create your own pipelines and stages, configure permitted movements between stages, and retain stage-change history.

Start with the process you’ve mapped. Create the stages that reflect it, then agree the conditions your team will use before making each move.

Permitting a transition is different from automatically executing it. Keep that distinction clear when configuring your workflow.

For your first review, choose a few open opportunities. Check whether each has an accurate stage, a responsible owner and a clear next action. Adjust the definitions where people are still guessing.