Teams where every stage means something different
Ask three salespeople what qualified means and you get three answers. The pipeline looks full, but nobody can say what is actually real. Design replaces individual judgement with a shared definition.
One pipeline.
One meaning.
Pipeline and lifecycle design gives your marketing, sales, and service teams one shared set of stages, definitions, and handoff rules, from first enquiry to repeat business.
Who this design
is for.
Pipeline design pays for itself fastest when more than one person touches the customer journey, and the word pipeline currently means different things to each of them.
The founder who cannot forecast
Every quarter ends with a surprise. Deals everyone counted on quietly die, and the ones that close were not on anyone's list. Forecasting fails because the stages underneath it mean nothing.
Businesses where leads rot between teams
Marketing celebrates enquiry numbers while sales complains about quality, and good buyers wait days for a first call. The missing piece is not effort; it is an agreed lifecycle with a named owner at every step.
Anyone whose CRM pipeline is decoration
The CRM has stages, but deals sit wherever they were last left, and the real tracking happens in a spreadsheet or the sales head's notebook. When the system and reality diverge, the stages were never designed properly.
One lifecycle, defined.
Six stages from first touch to repeat business. Each with a plain-language definition and an exit condition, so nobody has to guess.
01
Subscriber or first touch
Someone you can reach who has raised no hand yet.
Moves on when: They engage: a reply, a download, an event, a call.
02
Lead or new enquiry
A hand raised: a form, a call, a WhatsApp message.
Moves on when: Owned by a named person and contacted within the agreed time.
03
Qualified
Worth a salesperson's time, on grounds everyone agreed in advance.
Moves on when: A real conversation has happened and a next step exists.
04
Opportunity or deal
A specific piece of business with a value, a need, and a timeline.
Moves on when: Progresses through deal stages, each with an entry condition.
05
Customer
The deal is closed and money has moved or is committed.
Moves on when: Handed to delivery with the promise, dates, and details attached.
06
Repeat and referral
A happy customer who is systematically asked for the next sale.
Moves on when: The loop continues, measured like every other stage.
These are the shapes, not the final words. Your stages get named in your business's language, and their count changes to fit how your buyers actually move.
The rules behind
every stage.
Four principles we refuse to compromise on, because pipelines that break them stop being believed.
01
Every stage has a written definition
One sentence, in plain language, that two people can read and agree on whether a record belongs there. If the team cannot apply a definition consistently, it gets rewritten until they can.
02
Entry conditions, not feelings
A deal enters a stage because something observable happened: a meeting held, a requirement documented, a proposal sent. Never because someone feels good about it.
03
Every handoff names a receiver
Marketing to sales, sales to service: each handoff says who receives the work, within how long, and with what information attached. A handoff without a receiver is where customers disappear.
04
The pipeline must be countable
If a report cannot be built from the stages, the stages are wrong. We test every design by building the reports the business actually needs from it before anything is final.
How the design happens.
Four moves. The argument in the middle is not a problem to avoid; it is the work itself.
01
Gather
We collect how each team talks about the journey today: the words, the spreadsheets, the gut rules. The disagreements between teams are the most valuable material we find.
02
Draft
One candidate lifecycle and pipeline, written in your business's language, with definitions and entry conditions for every stage. Short enough to argue about in one sitting.
03
Argue
Marketing, sales, and service in one room, working through real deals from last quarter against the draft. Wherever the draft fails a real deal, the draft changes. This session is the heart of the work.
04
Settle
The agreed version is written down, built into the CRM, and given a review date. The first monthly review tests the definitions against new deals and adjusts what reality disagrees with.
What you receive.
A working structure, not a framework deck. Everything below is written in your team's language and built into the system they use daily.
Discuss pipeline designOne lifecycle from first touch to repeat customer, with a written definition and entry condition for every stage
A deal pipeline whose stages mirror how your buyers actually decide, not a generic template
Handoff rules between teams: who receives the work, within how long, with what information
The definitions written into your CRM, so the system enforces what the team agreed
A monthly review agenda that keeps the definitions honest as the business changes
An honest word about pipeline design.
Every agency can draw you a funnel diagram. Here is what actually determines whether the design survives contact with your team.
The definitions are the product
The document matters less than the conversation that produces it. Teams that argue through the definitions together keep them; teams handed a finished framework quietly ignore it.
Fewer stages beat more
Every stage you add is a place a record can stall and a definition people can misremember. We push hard toward the fewest stages that still tell the truth about the work.
It will need revision
New products, new teams, and new markets all change the journey. The design includes a review rhythm because a pipeline that cannot change becomes fiction within a year.
Where pipelines
go wrong.
The four patterns behind CRMs that everyone has stopped believing.
Copying a template pipeline
A software demo's stages, installed unchanged. Your buyers do not move in generic steps, so the pipeline stops matching reality within weeks and everyone routes around it.
Stages that describe the seller, not the buyer
Proposal sent is something you did. Requirement agreed is something the buyer did. Buyer-side stages are observable and honest; seller-side stages invite optimism.
Designing without the people who use it
A pipeline designed by management alone gets compliance, not adoption. The salespeople who live in it daily must help write the definitions, or they will not trust them.
Letting dead deals linger
Without an exit rule, deals sit in late stages for months, inflating the pipeline and poisoning the forecast. Every design includes a clear rule for closing lost and moving on.
Common questions.
The things owners and team leads ask us most, answered the way we answer them on a call. Nothing here hides behind a click.
QHow many stages should a pipeline have?
Fewer than you think. Most growing businesses land between four and seven deal stages. The test is not the number; it is whether each stage has a clear entry condition and whether the team applies them the same way. We would rather merge two fuzzy stages than keep a tidy-looking diagram.
QWhat is the difference between a lifecycle and a pipeline?
The lifecycle covers the whole customer relationship: first touch, enquiry, qualification, customer, repeat business. The pipeline is the part where active deals move toward a close. Lifecycle stages belong to the company; pipeline stages belong to sales. Both need agreed definitions, and this engagement designs them together.
QOur sales team will resist definitions. How do you handle that?
By having them write the definitions. The argue session exists precisely so the people who use the pipeline shape it. Resistance usually comes from definitions imposed from above; when the team builds the rules from their own real deals, the rules get used.
QDoes this require HubSpot or any specific CRM?
The design itself is tool-independent: stages, definitions, and handoffs work on paper. It lands best inside a CRM that can enforce entry conditions and report from the stages, and HubSpot is the strongest home we know for that. If you run a different tool, the design still applies.
QHow is this different from the revenue process audit?
The audit finds where the current journey leaks. Pipeline and lifecycle design builds the shared structure the journey should run on. Many clients do the audit first and design second, but if you already know the stages are the problem, you can start here directly.
One pipeline every team trusts.
Tell us how a deal moves through your business today. The first conversation is free and genuinely useful, whether or not the design work follows.