How to Develop Complete Funnel Stages With Proper Depth: The Exit-Criteria Method

Key Takeaways

• A stage is a state the buyer is in, not a task your team performed. Task-based stages tell you what you did; state-based stages tell you what is likely to happen, which is the only thing a forecast can be built on.
• Every stage needs an exit criterion that a second person could verify from the record without asking the rep. Without that, stage data is opinion and conversion rates are noise.
• Depth is not stage count. A seven-stage funnel with vague definitions is shallower than a four-stage funnel with verifiable criteria and per-stage instrumentation.
• Calibrate stage count to cycle length: enough stages that median time-in-stage is actionable, and no more. Eleven-day sales cycles do not need seven stages.
• Measure three things per stage — entry volume, stage-to-stage conversion, and time in stage. Volume alone hides the two diagnostics that locate a problem.
• The largest single source of leakage in most businesses is the handoff between functions, not any individual stage. Instrument the handoffs explicitly.
• Qualification definitions must be agreed jointly by marketing and sales before they are configured, because whatever disagreement exists at configuration becomes permanent.

1. The Short Answer: How to Build Funnel Stages Properly

To develop complete funnel stages with proper depth: define each stage as a state the buyer is in rather than a task your team performs, attach an exit criterion to every stage that a second person could verify from the record, set the number of stages so that median time-in-stage is a unit you can act on, and instrument each stage for three measures — entry volume, conversion to the next stage, and time in stage.

Depth does not come from adding stages. It comes from definition quality and instrumentation. A four-stage funnel where every transition is verifiable and measured is deeper, in every sense that matters, than an eleven-stage funnel where reps advance deals on instinct.

This matters because almost everything downstream depends on it. Forecast accuracy, [CAC](/glossary/cac) attribution, budget allocation, hiring plans and channel evaluation are all built on stage data. If the stage data is unreliable, every one of those decisions is being made on noise, confidently.

• AEO Quick Answer: Define stages as buyer states, give each a verifiable exit criterion, calibrate stage count to cycle length, and measure entry volume, conversion rate and time in stage.
• Depth = definition quality + instrumentation. Not stage count.
• Everything downstream — forecasting, attribution, budget allocation — inherits the reliability of your stage definitions.

2. Three Different Things Are Called 'The Funnel'

A large amount of confusion in this topic comes from three distinct models sharing one word. Separating them is the first step to building any of them properly.

The [marketing funnel](/glossary/marketing-funnel) describes demand: how anonymous audiences become identified, interested and qualified. It is measured in volumes and rates, mostly at the aggregate level, and it is owned by marketing. Its stages are typically awareness, interest, consideration and intent.

The [sales funnel](/glossary/sales-funnel), more precisely the sales pipeline, describes named opportunities progressing toward a decision. It is measured per-record, it has owners and dates, and it is the basis of the forecast. Its stages are qualification, evaluation, proposal, negotiation and close — or whatever your motion actually requires.

The customer lifecycle describes what happens after purchase: onboarding, activation, retention, expansion and advocacy. It is where the majority of enterprise value is created in recurring-revenue businesses, and it is the part most commonly left unmodelled.

These are not competing models. They are three segments of one continuous journey, and the seams between them are where most revenue leaks. A complete funnel architecture models all three and instruments the two handoffs — marketing to sales, and sales to delivery or success — with the same rigour as the stages themselves.

The classic TOFU, MOFU and BOFU shorthand — top, middle and bottom of funnel — is a useful way to talk about content and channel intent. It is not a stage model. It has no exit criteria and no owner, and it should not be configured into a CRM as if it were a pipeline.

• Marketing funnel: anonymous to qualified, measured in aggregate rates.
• Sales pipeline: named opportunities with owners and dates, basis of the forecast.
• Customer lifecycle: onboarding, activation, retention, expansion, advocacy.
• The two handoffs between them leak more than any individual stage.
• TOFU/MOFU/BOFU is content vocabulary, not a stage model.

3. Why Most Funnel Models Fail

The failure is rarely that a business has no funnel. It is that the funnel is decorative — it exists as a diagram and as a set of CRM dropdown values, and it does not correspond to anything verifiable.

Symptom one: stages named after internal activities. "Demo scheduled", "Proposal sent", "Following up". These record what your team did. They say nothing about whether the buyer is closer to deciding, which is why pipelines full of these stages produce forecasts that miss badly in both directions.

Symptom two: no exit criteria. Ask three reps what has to be true for a deal to move from stage two to stage three and you get three answers. Every conversion rate computed from that pipeline is measuring interpretation variance as much as buyer behaviour.

Symptom three: the graveyard stage. One stage holds forty per cent of open pipeline, and deals enter it and never leave. Usually it is a stage with a vague definition and no time-in-stage limit, and it functions as a place to put deals that are not really alive but that nobody wants to close as lost.

Symptom four: stage count copied from a template. Seven stages because a blog post said seven, applied to a motion that closes in eleven days. Reps advance deals through four stages in a single afternoon, which makes stage-to-stage conversion meaningless.

Symptom five: the funnel stops at the sale. Everything after closed-won is somebody else's diagram. In a recurring-revenue business this means the majority of lifetime value is unmodelled, and acquisition decisions are made on first-order revenue rather than on [LTV](/glossary/ltv).

Symptom six: unagreed qualification definitions. Marketing counts an [MQL](/glossary/mql) one way, sales counts it another, and the monthly meeting is spent reconciling numbers rather than fixing the problem the numbers describe.

• Stages named after your activities rather than the buyer's state.
• No exit criteria, so conversion rates measure interpretation variance.
• A graveyard stage holding dead deals nobody will mark lost.
• Stage count copied from a template rather than calibrated to cycle length.
• Funnel ends at closed-won, leaving most lifetime value unmodelled.
• Marketing and sales using different qualification definitions.

4. The Core Principle: Stages Are Buyer States

The single change that improves a funnel most is redefining every stage as a state the buyer is in, expressed in terms of what the buyer has done or confirmed — not what your team has done.

Compare two definitions of the same point in a process. Task-based: "Proposal sent." State-based: "Buyer has confirmed the problem is a priority this quarter, named the decision-maker, and agreed a decision date."

The first is satisfied by an email leaving your outbox. It is fully within your control, which is precisely why it predicts nothing — you can send a hundred proposals to people who will never buy, and your pipeline will look excellent. The second requires the buyer to have done something. It cannot be satisfied unilaterally, and that is what makes it predictive.

This is why buyer-state definitions produce better forecasts. Each stage transition is evidence about the buyer's actual progression rather than evidence about your team's activity level. When a stage-three deal has a seventy per cent historical close rate, that number means something only if entering stage three required the buyer to do something.

The practical test for any stage definition: could a deal satisfy this criterion without the buyer doing anything at all? If yes, rewrite it.

A second test, for the exit criterion: could a colleague who has never spoken to this buyer open the record and confirm the criterion is met? If they would have to ask the rep, the criterion is not verifiable and the stage data will not survive contact with a forecast review.

• Task-based stages are satisfied unilaterally, which is why they predict nothing.
• Buyer-state stages require buyer action, which is what makes them predictive.
• Test one: could this criterion be met without the buyer doing anything?
• Test two: could a colleague verify it from the record without asking the rep?

5. How Deep Should Your Funnel Be?

Depth is the question this guide exists to answer, and the answer has two parts that are frequently confused: the number of stages, and the richness of what you know about each one. Only the second is really depth.

For stage count, the calibration rule is straightforward. You want enough stages that the median time spent in each is a unit you can act on, and few enough that every stage transition represents a genuine change in probability.

In practice that means: for a transactional motion closing in under two weeks, three to four stages. For a considered purchase closing in one to three months, four to six. For a complex enterprise motion closing in six to eighteen months with procurement, security review and legal, six to nine — and in that case the additional stages are usually gates imposed by the buyer's process, which is exactly what they should be.

Two diagnostics tell you your stage count is wrong. If reps routinely advance deals through two or more stages on the same day, you have too many stages, and the intermediate ones are not real decision points. If a single stage holds a third or more of open pipeline and has a wide time-in-stage distribution, you have too few — that stage is concealing at least two distinct buyer states.

Real depth, though, is not stage count. It is how much you know about each stage. A stage is deeply modelled when you can state its entry criterion, its exit criterion, its median and distribution of time in stage, its conversion rate to the next stage, the segment-level variance in that rate, the most common reason for exit to lost, and the specific action that most improves its conversion.

You can have that depth on four stages. Most companies with eleven stages do not have it on any of them. Adding stages to a funnel with weak definitions is the modelling equivalent of adding decimal places to a bad measurement.

• Under two weeks to close: three to four stages. One to three months: four to six. Six to eighteen months: six to nine.
• Too many stages: reps advance through several in one day.
• Too few stages: one stage holds a third of pipeline with wide time-in-stage variance.
• Depth per stage: entry criterion, exit criterion, time distribution, conversion rate, segment variance, top loss reason, highest-leverage action.

6. The Complete Stage Architecture

What follows is a full-journey reference model. Very few businesses should implement all of it as discrete CRM stages — most should compress several of these into single stages. Use it as a checklist of states a buyer passes through, then decide which ones your business needs to distinguish.

Stage 0 — Problem unaware. The person has the problem you solve and does not know it is solvable, or does not frame it as a problem. No record exists. This stage is real, it is where category-creating demand generation operates, and it is measured through market-level indicators rather than per-record data.

Stage 1 — Problem aware. The person recognises a problem and begins looking for language to describe it. Search behaviour here is symptom-based rather than solution-based. Content that names the problem precisely performs disproportionately well, and this is where most durable organic authority is built.

Stage 2 — Solution aware. The person knows a category of solution exists and is learning how it works. They are comparing approaches, not vendors. This is where educational content, frameworks and diagnostic tools earn trust, and where a business that publishes genuinely useful material gains an advantage that is difficult to buy.

Stage 3 — Vendor aware / identified. The person becomes a known record: they submit a form, book a call, start a trial, or otherwise identify themselves. This is the first stage with reliable per-record data, and the first point at which the marketing funnel and the CRM meet.

Stage 4 — Qualified. The record has been assessed against a defined fit standard and meets it. This is where an MQL becomes an [SQL](/glossary/sql), and it is the most commonly disputed transition in the entire funnel because it is the point of handoff between two functions with different incentives.

Stage 5 — Active evaluation. The buyer has confirmed the problem is worth solving now, and is actively assessing options. Exit criterion should require confirmation of priority and timing, not merely a completed discovery call.

Stage 6 — Solution validated. The buyer accepts that your approach solves their problem. In software this often means a successful trial or proof of concept; in services, an agreed scope; in considered consumer purchases, a site visit or test.

Stage 7 — Commercial alignment. Price, terms and scope are agreed in principle. The remaining work is procedural. This is distinct from validation and should be a separate stage whenever your motion involves negotiation, because the failure modes are entirely different.

Stage 8 — Procedural close. Procurement, legal, security review, signature. In enterprise motions this stage has its own timeline that is largely outside your control, and modelling it separately is what prevents forecasts from slipping repeatedly by one quarter.

Stage 9 — Onboarding. The customer is implementing. Time-to-first-value is the governing metric, and this is where early churn is decided in almost every recurring-revenue business.

Stage 10 — Activated. The customer has achieved the outcome they bought. Define this concretely and per-product; "activated" without a specific milestone is not measurable.

Stage 11 — Retained and expanding. Ongoing value delivery, renewal, and expansion. In recurring-revenue businesses this is where the majority of lifetime value accrues.

Stage 12 — Advocacy. The customer refers, reviews or provides references. This stage feeds directly back into stages 1 and 2 for other buyers, which is why a complete funnel is better drawn as a loop than as a cone.

• Stages 0-2 are pre-identification: measured in aggregate, owned by marketing.
• Stages 3-4 are the handoff zone: the most disputed and most leak-prone transitions.
• Stages 5-8 are the pipeline: per-record, owned, forecastable.
• Stages 9-12 are the lifecycle: where most recurring-revenue value is created.
• Compress aggressively — most businesses need four to six CRM stages out of these thirteen states.

7. Writing Exit Criteria That Survive a Forecast Review

Exit criteria are the mechanism that turns a stage list into a funnel. A good criterion is specific, verifiable from the record, and requires buyer action. Here is the pattern applied to the pipeline stages.

Qualified. Weak: "Rep believes they are a fit." Strong: "Record meets the documented fit standard on company size, use case and budget range; a discovery conversation has taken place; and the buyer has confirmed they are exploring a change within a defined timeframe." Verifiable, because each element is recorded.

Active evaluation. Weak: "Demo completed." Strong: "Buyer has confirmed this problem is a priority in the current planning period, has identified who will make the decision, and has agreed to a next step with a date."

Solution validated. Weak: "They liked it." Strong: "Buyer has completed the evaluation step relevant to your product — trial, pilot, technical review, site visit — and has confirmed it meets their stated requirement, with any objections documented and addressed."

Commercial alignment. Weak: "Proposal sent." Strong: "Buyer has confirmed pricing and scope are acceptable in principle, and has named the remaining approvals required with expected timing."

Procedural close. Weak: "In legal." Strong: "Contract is with a named counterparty, with a stated expected turnaround, and the specific outstanding item is recorded."

Notice the shape shared by all the strong versions: something the buyer said or did, recorded in a field, with a date. That is what makes forecast reviews short. Instead of relitigating each deal's likelihood, the review checks whether the criteria are met, and the historical conversion rate for that stage does the probability work.

One discipline that makes this stick: require the exit criterion to be recorded in structured fields, not free-text notes. Notes are not queryable, and a criterion that cannot be queried cannot be audited or reported on.

8. Instrumenting Each Stage

A stage you cannot measure is a label. Three measures per stage are the minimum, and each answers a different diagnostic question.

Entry volume. How many records entered this stage in the period. Answers: is the problem upstream? Volume alone is the metric most teams report and the least useful in isolation, because it cannot distinguish a demand problem from a conversion problem.

Stage-to-stage conversion. What proportion of records that entered this stage reached the next one. This is the [funnel conversion rate](/glossary/funnel-conversion-rate) that locates leaks. Measure it cohort-based — following the records that entered in a period through to their outcome — rather than as a ratio of two period totals, which distorts badly whenever volume is changing or cycles are long.

Time in stage. Median, and the shape of the distribution. The median tells you velocity; the distribution tells you whether you have one process or two. A bimodal time-in-stage distribution almost always means two different buyer types are being run through one stage, and they should probably be separated.

Beyond the minimum, three further measures repay the effort. Exit-to-lost reason, captured as a structured field with a short controlled vocabulary — free text here produces nothing analysable. Stage-entry quality, meaning the eventual close rate of records entering this stage, segmented by source, which is how you evaluate channels honestly. And age of records currently in stage, which is how you find the graveyard before it consumes a quarter.

Segment every one of these by acquisition source, product and customer segment. Aggregate funnel metrics hide the variance that matters: a blended conversion rate of twenty per cent might be one source converting at forty and another at four, and the correct action in that case is a budget decision, not a sales-training decision. This is the point where funnel data starts informing [channel budget allocation](/guides/channel-budget-allocation-guide).

• Minimum per stage: entry volume, cohort-based stage-to-stage conversion, median and distribution of time in stage.
• Add: structured loss reasons, stage-entry quality by source, age of in-stage records.
• Use cohort-based conversion, not period ratios — period ratios distort when volume or cycle length changes.
• Bimodal time-in-stage means two buyer types sharing one stage.
• Always segment by source; blended rates hide the variance that determines the right action.

9. Diagnosing Leaks: A Repeatable Method

Once instrumented, the funnel becomes a diagnostic instrument. The method below isolates where revenue is actually lost, in order, and prevents the common error of optimising a stage that is not the constraint.

Step one: build the cohort table. Take all records entering the funnel in a period long enough for most to have resolved, and follow them stage by stage to outcome. You now have absolute counts and conversion rates for each transition.

Step two: find the largest absolute loss, not the lowest rate. A stage converting at fifteen per cent sounds alarming, but if only forty records enter it, fixing it recovers less than a stage converting at sixty per cent that four thousand records enter. Rank transitions by records lost, not by percentage.

Step three: check the handoffs first. In most businesses the largest single loss is at a handoff — marketing to sales, or SDR to closer — rather than inside any stage. Handoff losses are frequently mechanical: slow response, unclear ownership, records routed to the wrong person, or a definition mismatch causing records to be rejected. Mechanical problems are cheap to fix, which is why checking them first has the best return.

Step four: segment the leaking transition. Split it by source, segment, product and owner. A leak that disappears under segmentation was never a stage problem — it was a mix problem, and the answer is upstream in acquisition. A leak that persists uniformly across all segments is a genuine process problem at that stage.

Step five: examine time in stage at the leak. A stage with a high loss rate and a short time in stage suggests records arriving unqualified. A high loss rate with long time in stage suggests genuine indecision, which is usually a value or urgency problem rather than a qualification problem. The two require entirely different interventions.

Step six: read the loss reasons. With a controlled vocabulary, the top two reasons at the leaking stage usually point directly at the fix. Without one, this step produces nothing, which is why the structured field matters.

Step seven: change one thing and re-measure on a fresh cohort. Funnel changes take at least one full sales cycle to show a clean read. Changing three things at once, then reading the result before a cycle has elapsed, is how teams conclude that funnel work does not help.

This method is the backbone of the [funnel optimization](/solutions/funnel-optimization) engagements we run, and it is deliberately unglamorous. Most recovered revenue in this work comes from fixing handoff mechanics and qualification definitions, not from redesigning the sales process.

• Rank transitions by records lost, not by conversion percentage.
• Check handoffs before stages — mechanical failures are common and cheap to fix.
• Segment the leak: if it disappears under segmentation, the problem is acquisition mix, not process.
• Short time-in-stage plus high loss = unqualified arrivals. Long time plus high loss = value or urgency problem.
• Change one variable, then re-measure on a fresh cohort after a full sales cycle.

10. Getting Qualification Definitions Right

The marketing-to-sales handoff is the most contested transition in the funnel, and almost all of the contest traces to definitions written by one function and applied to another.

An MQL should be defined by fit and demonstrated interest together, never by a single action. "Downloaded a whitepaper" is not qualification; it is one behavioural signal, and on its own it produces a queue of records sales learns to ignore. A defensible MQL definition combines firmographic or demographic fit against your ideal customer profile with a behavioural threshold indicating active problem-solving.

An SQL is a record that sales has accepted, having assessed it against agreed criteria. The word doing the work is accepted. If sales cannot reject a record, the definition is not real and the handoff cannot be measured. Build an explicit rejection path with a required reason — the rejection reasons are among the most valuable data marketing can receive.

A product-qualified lead applies where a product-led motion exists: the record has used the product and hit a usage threshold that historically correlates with purchase. The threshold should be derived from your own conversion data, not adopted from an industry benchmark, because activation patterns are highly product-specific.

Three rules make these definitions durable. Write them jointly and sign them off jointly; a definition marketing wrote alone will be disputed the first month it is inconvenient. Attach a service-level agreement in both directions — marketing commits to volume and quality at a defined standard, sales commits to a response time and a disposition within a defined window. And review the definitions quarterly against actual close rates, because a qualification standard that is not recalibrated drifts steadily out of alignment with reality.

The measurable outcome of getting this right is the acceptance rate: the proportion of MQLs sales accepts as SQLs. Track it as a first-class metric. A falling acceptance rate is an early warning about lead quality that shows up months before it shows up in revenue. Our [lead scoring](/solutions/lead-scoring) work is largely about making this transition measurable.

• MQL = fit plus demonstrated interest. Never a single action.
• SQL requires that sales can actually reject records, with a required reason.
• PQL thresholds must be derived from your own conversion data, not borrowed benchmarks.
• Sign definitions off jointly, attach two-way SLAs, review quarterly against close rates.
• Track acceptance rate as an early warning on lead quality.

11. Stage Depth by Business Model

The correct architecture varies by how you sell. The following are the patterns we see work, with the specific consideration that decides each.

B2B SaaS with a sales-led motion. Five to six pipeline stages, with security review or procurement modelled separately if enterprise deals routinely pass through it. Buying-group tracking matters: model multiple contacts with roles, because single-threaded deals close at materially lower rates and you want that visible in the record. Lifecycle stages after close are essential, since renewal and expansion dominate lifetime value.

Product-led SaaS. The pipeline is short and the lifecycle is long. Most depth belongs in stages 9 to 11 — onboarding, activation and expansion — with activation defined as a specific in-product milestone. A heavy pre-sale pipeline model in a product-led business is usually modelling a process that barely exists. See our related work on [saas funnel optimization](/resource/blogs/saas-funnel-optimization).

D2C and e-commerce. Per-record pipeline stages are largely irrelevant; there is no opportunity object in a meaningful sense. Depth belongs in the aggregate funnel — session to product view to cart to checkout to purchase — and then in the lifecycle: first repeat purchase, second repeat, and cohort [retention](/glossary/retention) curves. The single most valuable stage boundary in D2C is first-to-second purchase, because it is the strongest available predictor of cohort value.

High-ticket services and consulting. Few, long stages, with a heavy emphasis on qualification depth and on a clearly separated commercial alignment stage. Scope and price negotiation is a distinct failure mode from solution validation, and merging them into one "proposal" stage conceals which one is actually losing deals.

Marketplaces. Two funnels running simultaneously, supply and demand, and they must be modelled separately and then jointly, because liquidity in one determines conversion in the other. Modelling only the demand side is the standard marketplace measurement error.

Education and EdTech. High volume, short windows, hard intake deadlines. Depth belongs in speed-to-lead and early-stage contact rates rather than in late-stage nuance. Model counsellor capacity explicitly against intake dates, because the binding constraint is usually capacity rather than demand.

Real estate and considered high-value consumer purchases. Long, low-intensity nurture measured in months or years, with a many-to-many relationship between buyers and inventory. Stage models built around a single opportunity per contact fit badly; model interest per property alongside buyer-level readiness.

12. Common Mistakes, and What to Do Instead

Adding stages to add rigour. More stages with the same weak definitions produce more places for deals to sit, not more insight. Instead, improve exit criteria on the stages you have before adding any.

Letting probability be assigned per deal by the rep. Rep-assigned percentages encode optimism, not evidence. Instead, derive stage probability from your own historical close rates by stage and segment, and let the criteria determine the stage.

Allowing skipped stages without a rule. If deals routinely jump from stage two to stage five, either your stages are wrong or your data is. Instead, either permit skipping explicitly for a defined motion, or enforce sequence — but decide, rather than leaving it ambiguous.

Never closing anything as lost. Pipeline that only grows is not a pipeline; it is a list. Instead, set a maximum age per stage, and require a disposition when it is exceeded.

Measuring the funnel only in aggregate. Blended rates hide the variance that determines what to do. Instead, segment every rate by source, segment and product as a default, not as a special analysis.

Treating the funnel as fixed. Buyer behaviour, channel mix and product all change. Instead, review stage definitions and conversion benchmarks quarterly, and expect to recalibrate at least annually.

Modelling only the pre-sale funnel. In recurring-revenue businesses this ignores where most value is created and leads directly to over-investing in acquisition of customers who do not retain. Instead, extend the model through activation, retention and expansion, and evaluate acquisition sources on lifetime value rather than on first-order revenue.

13. A Thirty-Day Implementation Sequence

Building this does not require a quarter-long project. A focused month is usually enough to get to a funnel that produces trustworthy data, after which improvement is continuous.

Days one to five: document the current reality. Map every distinct revenue motion. Interview reps about what actually happens, including the exceptions. Pull the last two quarters of closed deals and reconstruct their real paths. Expect to find at least one motion nobody had modelled.

Days six to ten: draft stage definitions and exit criteria. Write them as buyer states. Apply both tests — could this be satisfied without the buyer doing anything, and could a colleague verify it from the record. Circulate for challenge, specifically to the reps who will use them.

Days eleven to fifteen: agree qualification definitions jointly between marketing and sales, with two-way SLAs and a rejection path with required reasons. Get explicit sign-off. This is the step most likely to be skipped and most likely to cause the whole model to fail later.

Days sixteen to twenty: configure. Stages, required fields for each exit criterion, structured loss reasons, and routing rules. Keep automation minimal at this point; automating an unvalidated process encodes its errors.

Days twenty-one to twenty-five: build the three core reports — cohort conversion by stage, time in stage with distribution, and stage-entry quality by source. If your CRM cannot produce cohort-based conversion natively, this is the moment you discover it, and the point at which a warehouse becomes worth planning. Your CRM's data model determines how easily this goes, which is why [CRM selection](/guides/choose-best-crm-guide) and funnel design are the same project.

Days twenty-six to thirty: train on the criteria, not on the software. Run a live pipeline review using the new definitions and re-stage the existing pipeline against them. Expect the pipeline to shrink — often substantially. That is the model working correctly, and it is worth saying so in advance, because an unexpected pipeline drop is otherwise read as a crisis rather than as the removal of deals that were never real.

14. A Worked Example (Illustrative Model)

The following figures are an illustrative model built to demonstrate the arithmetic. They are not client results. Substitute your own numbers.

A B2B services business generates 2,000 identified leads in a quarter. 600 are accepted as qualified. 300 reach active evaluation. 120 reach commercial alignment. 60 close. Blended conversion from lead to customer is 3%.

Reading the transitions by absolute loss: identified to qualified loses 1,400 records; qualified to evaluation loses 300; evaluation to commercial alignment loses 180; commercial alignment to close loses 60. The largest absolute loss is at the first transition by a wide margin, and it is also the transition most teams ignore because a 30% acceptance rate does not look alarming in isolation.

Segmenting that first transition by source changes the picture entirely. Suppose paid search contributes 1,200 leads at a 20% acceptance rate, while referral contributes 300 leads at a 70% acceptance rate. The blended 30% is an artefact of mix. The problem is not the qualification process; it is that one channel is delivering volume that does not meet the fit standard.

The correct action follows directly, and it is not a sales-process change. It is an acquisition change: tighten targeting or offer on the underperforming channel, or reallocate budget toward the channel producing qualified volume — a decision that belongs in your [marketing mix plan](/guides/marketing-mix-plan-guide). Note that a team measuring only blended conversion would likely have run a sales-training programme instead, and seen no improvement.

This is the general shape of most funnel findings. The number that looks like a sales problem is frequently a mix problem, and only segmentation distinguishes them.

15. Putting It Together

A complete funnel with proper depth is not an elaborate diagram. It is a small number of stages, each defined as a buyer state, each with an exit criterion a colleague could verify from the record, each instrumented for volume, conversion and time, and each segmented by source.

Build it in that order. Definitions first, because instrumentation of undefined stages produces precise measurements of nothing. Instrumentation second, because diagnosis without measurement is guesswork. Optimisation last, and one variable at a time.

The return on this work is rarely a single dramatic improvement. It is that every subsequent decision — which channel to fund, which segment to target, where to add headcount, what to forecast — is made against data that reflects reality. That compounds in a way that individual conversion-rate wins do not.

If you want the funnel architecture reviewed against your actual pipeline data before you rebuild it, that is the diagnostic our RevOps team runs first in every [sales funnel](/solutions/sales-funnel) engagement.