How to Manage Multiple Pipelines for Different Services
Imagine a Tuesday morning. A £300 boiler call-out is listed as "In Progress" next to a £45,000 install that has been going on for six weeks, and a £150-a-month maintenance retainer has just been renewed. Your team is looking at one column to figure out who needs a site visit, who needs a proposal and who just needs an invoice. If you offer more than one service, there is a good chance every enquiry is arriving in the same pipeline.
Why does one pipeline stop working when you sell more than one service?
A single pipeline only works when opportunities follow roughly the same route. Once your services differ in timescale, decision-makers and follow-up, the stages stop describing anything real, and the numbers you pull from them stop being useful.
Different services follow different journeys.
A reactive job can go from enquiry to finished work in a day. A larger project might involve a site visit, a proposal, a revised scope, a bit of chasing and a signed contract over several weeks. Retainers have their own rhythm again, with onboarding and renewals that a one-off sale never has to think about.
Squeeze all three into one pipeline, and something gives. Either the stages get so vague they say almost nothing, or somebody builds a detailed process that suits a £20,000 project and looks faintly daft applied to a £250 call-out.
Then people quietly stop trusting the CRM. Updates get patchy, deals sit in stages that don't quite fit, and someone starts a spreadsheet "just for now". A few months later the owner is carrying half the pipeline around in their head again, which is more or less where they started.
A consultancy with audits and retainers
Take a small consultancy selling one-off audits and longer strategy retainers. Both run through the same five stages: enquiry, contacted, proposal sent, negotiating, and won.
Audits barely touch most of them. Someone might enquire on Tuesday morning, have a quick chat that afternoon and be ready to go ahead by Wednesday. Retainers are rarely that straightforward. There might be a few conversations, a proposal to work through, another person who needs to sign it off and, quite often, a change or two to the scope before everyone agrees on what the work actually looks like.
By Friday, the owner opens the CRM and sees six deals marked "negotiating". Two are £750 audits waiting on a simple yes or no. Four are five-figure retainers still being scoped. The system files them under the same heading, though commercially they're nowhere near each other.
So when the owner tries to work out which service converts better, where enquiries are going cold or what needs attention this week, the figures don't help much. Two different sales processes are being measured with one ruler.
Is it a pipeline problem or a software problem?
When a business tells us it has a pipeline problem, the pipeline is often innocent. What's usually missing is a clear picture of how each type of work gets from enquiry to sale.
Map what people actually do before you build anything.
Changing the software is the tempting fix. A new CRM gets discussed, automations get bolted on, and someone builds another dashboard. If the underlying journey is muddy, though, all you've achieved is faster muddle.
Start with what happens when someone enquires about each service. Who replies first? What do you need to know before you can quote? Does anyone have to visit the site? Is a proposal always needed? Who signs it off, and how long does that normally take? And what happens when the prospect goes quiet, which they will?
The answers should shape the pipeline. Do it the other way round, and the business ends up behaving according to whichever stages were set up on the day the CRM was installed.
Once you've done this, most service businesses find they have about three shapes of work, not ten. Reactive work moves fast: call-outs, repairs, and single-visit jobs. Something like enquiry, booked, completed, or paid is plenty, and there's no reason to push a £200 repair through seven stages. Project work needs more room, with a site visit, an estimate, a revised scope and sign-off from whoever holds the budget before anyone picks up a tool. Recurring work, such as maintenance contracts and monthly retainers, doesn't close and vanish. It onboards, renews, expands, and occasionally pauses.
Leave all three side by side in one pipeline, and it becomes very hard to see what's really going on.
What a hive can teach you about sales stages
A hive doesn't send every forager in the same direction. Bees adjust the dance depending on how far the food is, because a patch of flowers down the road and one two kilometres away call for different instructions.
A same-day repair and a six-week commercial deal are both revenue, but what happens next is completely different for each. Push them through one generic process, and the signal gets muddy for everybody reading it.
Five steps to set up multiple pipelines without creating chaos
Multiple pipelines earn their place when they reflect genuinely different buying journeys. Keep the structure simple, and make sure every opportunity has a next action and a named owner.
1. Map the real journey first.
Write down what happens from the moment someone enquires, one service at a time. If one journey runs enquiry, quote, booked, and completed, and another runs enquiry, discovery call, site survey, proposal, follow-up, and contract, you've probably found your reason for separate pipelines. Stages should exist because something actually happens there, not because they sound professional.
2. Build around buying journeys, not your service menu.
Ten services rarely need ten pipelines. Two can share one happily if customers buy them in roughly the same way. The useful number is how many genuinely different buying journeys you manage, which is usually smaller than the number of things you sell. It also stops the CRM turning into a maze of tabs nobody opens.
3. Split the opportunity and keep the customer whole.
A customer might buy a project today and come back six months later for ongoing support. That's one relationship with two opportunities attached, so there's no need for two customer records. Think of the customer record as the filing cabinet and the pipelines as the drawers. It matters most when you want to see what a client is worth over time, rather than treating every sale as a one-off.
4. Give each pipeline an owner.
Even if the same person manages everything, someone needs to know which enquiries are waiting for a reply, which proposals need chasing and what's been sitting still for too long. Without that, the slower deals slide behind the urgent work. The boiler that needs fixing today gets attention. The £30,000 proposal that needs a thoughtful follow-up on Thursday is much easier to forget, and it's worth a good deal more.
5. Review each pipeline against its own history.
A healthy conversion rate for emergency call-outs looks nothing like a healthy one for high-value projects. Sales cycles, commitment and reasons for saying no all differ. So rather than crowning a "best" pipeline, compare each one with itself. Are more enquiries becoming customers than three months ago? Are proposals waiting longer for an answer? Is one stage turning into a graveyard for otherwise promising deals?
Check the structure before you rebuild it.
Pull the last 20 enquiries your business received across all your services. For each one, ask three things. Did it end up in the right place? Did the stages it passed through reflect what actually happened? Could someone new to the business look at where it sits now and see what needs to happen next?
You'll probably spot the pattern fairly quickly. If the stages don't match reality, fix the structure. If they make sense but deals are still sitting untouched for three weeks, another pipeline won't help. That points to follow-up, ownership or sales behaviour, and it needs a different conversation.
Telling those two apart is a big part of what we do at Waggle Dance. We look at what people in the business actually do with an enquiry once it lands, rather than what the process says should happen, and then work out whether the fix belongs in the system, the process or the day-to-day habits.
Today's Deep Dive
FAQs
How many pipelines is too many?
If you’ve ended up with a separate pipeline for every service you offer, it’s worth asking whether you actually need them all. If two services are sold in much the same way, there’s no real benefit in splitting them just because the work looks different once the client says yes. A new pipeline makes sense when the sales journey changes, not simply because the service has a different name.
How do I know when a pipeline needs splitting?
Watch for stages people routinely skip, deals that stall at the same point every time, or a side spreadsheet that has quietly become the real record. Any of those suggests the pipeline no longer matches how at least one service is sold.
What's the biggest mistake when setting this up?
Copying the stages from the existing pipeline into a new one and changing the name. It feels like you've separated the services, but nothing meaningful has changed. If the second service follows a different buying journey, its stages need to reflect that; otherwise, you've got the same problem with an extra tab.
Can I run multiple pipelines in a spreadsheet, or do I need a CRM?
Two or three straightforward pipelines work fine in a well-organised spreadsheet, particularly if you're a solo operator with a modest number of enquiries. Trouble tends to start when several people are managing different opportunities at once. That's when a CRM starts earning its keep, thanks to ownership, reminders, automation and reporting rather than any fault in spreadsheets themselves.
Do I need to migrate my whole CRM to add a second pipeline?
Usually not. In most CRMs, you can add a second pipeline without disturbing what’s already there. There’s no need to move everything across at once either. Set up the new pipeline, put a few real opportunities through it and see how it works day to day. If the stages feel right, you can move the rest over as you go.
If you're not sure whether you have a structure problem or a behaviour problem, a Clarity Call is a sensible place to start. We'll look at how enquiries currently move through your business and where they get stuck.
