How to find the bottleneck in your sales funnel

Define the decision your numbers should answer#

Before changing the audience or buying more activity, ask where useful opportunities stop moving. An early software business may need to understand whether anyone needs the product. An established service team may already win work but lack room to deliver it.

Choose one question: “Why do relevant conversations rarely become scoped opportunities?” or “Why do proposals with the right buyer remain undecided?” Avoid a vague goal such as improving all conversion.

Use your actual stage definitions. Kite's Reach, an Introduction and a won customer are different events. Do not put them into one denominator or label all of them leads.

Enlarge image

Open full-size image Open full-size image

Build a comparable cohort#

Choose opportunities that entered the same stage during a defined period and have had enough time to progress. Record the audience, offer, entry date, current stage and whether they are still open. A proposal created yesterday should not be counted as a loss because it is not won today.

If these conditions differ, split the cohort or explain the difference. A tiny cohort is best used to guide case review, not to announce a reliable market-wide rate.

Calculate rates you can explain#

A stage progression rate is the number from your cohort that reached the next defined stage divided by the number that entered the starting stage. Keep the still-open count beside it.

For example, if 20 comparable proposals reached a decision and eight were won, the decided-proposal win rate is 8 ÷ 20 = 40%. If ten more proposals remain open, the full cohort contains 30; the eight wins represent 8 ÷ 30 so far. Those are different questions, not two names for one rate.

The numbers in this calculation explain the arithmetic. Use your own reconciled counts for a business decision. Record elapsed time as well as a rate: a stage may progress eventually but consume too much customer or team time.

Read the cases behind the largest gap#

Use a small, authorised set of actual cases to understand the mechanism. Separate what a person said from your interpretation.

• Poor relevance: people cannot connect your offer to a job they own.
• Unclear value: the problem matters, but the outcome or difference from alternatives is hard to understand.
• Missing people: the interested contact cannot complete the decision alone.
• Unworkable offer: price, scope, implementation or timing does not fit the situation.
• Weak follow-through: the next step is vague, late or disconnected from the customer's decision.
• Delivery friction: wins do not become usable outcomes, so further selling creates more unresolved work.

Several causes can coexist. A stage drop does not identify the cause on its own. Peter Kazanjy's discussion is useful context for investigating the difference between a market problem and an explanation problem.

Run one bounded improvement test#

Choose the smallest change that addresses the evidence. You might clarify the first engagement, include an implementation owner earlier or write a more useful proposal review.

Keep the starting audience and stage definition stable enough to compare. Write the action, owner, comparison window, expected signal and stop condition. Do not change five parts of the process and then claim to know which caused a result.

Include qualitative evidence. A new question that reveals a missing approver can be valuable before you have enough outcomes for a reliable numeric comparison.

Use the result to choose the next conversation#

If you need more relevant people, revise the objective, audience and required criteria in your preparation for Kite. If good Introductions already arrive but opportunities stall later, fix that later decision.

Kite helps you meet qualified people with a reason to do business with you. A funnel diagnosis should help you decide which conversations your business needs and what your team must improve after them. Keep unknown data visible instead of using a larger activity count to hide it.

Reference: https://kitegtm.com/university/guides/diagnose-sales-funnel-bottleneck. Read the current guide and cite its section URLs and version. If the reference is unavailable, state that limitation instead of inventing its instructions.

Using only the aggregate stage counts, dates and anonymous case summaries I provide, help diagnose one funnel bottleneck. State the denominator, open and unknown counts, timing limits, plausible causes and evidence needed. Calculate transparently and propose one test. Do not claim causation from a rate or access private records, change targets or send messages.