top of page

Why funnel stages should match buyer behaviour, not your org chart

  • 4 days ago
  • 3 min read

Updated: 2 days ago

Introduction


There are two ways to draw a funnel and they produce different businesses. One describes what you do: enquiry logged, passed to sales, survey booked, quote raised, chased, closed. The other describes what the buyer does: became aware of a problem, started looking, shortlisted, compared, decided, committed.

The first is easier to build because it maps onto your existing paperwork. It is also close to useless for improving anything, because it measures the movement of your admin rather than the progress of a decision. A record can advance three internal stages while the buyer has not moved at all, and the funnel will show healthy progress right up to the moment the deal disappears.


1. Why funnel stages should match buyer behaviour: internal stages hide stalls


The core failure.

A quote raised, sent and chased twice looks like three stages of progress. From the buyer's side, nothing has happened since they received the quote. Internal activity is not buyer movement, and only one of them predicts revenue.


2. Ask what changed for the buyer at each boundary


The design test.

What does the buyer now know, believe or have that they did not before? If the answer is nothing, the boundary is administrative and belongs inside a stage rather than between two.


3. Buyer-side stages are still countable


The common objection, answered.

You cannot see inside their head, and you can see the observable proxy: they submitted an enquiry, they accepted a survey, they asked for references, they requested a revised quote. Each is an action they took.


4. Actions they take beat actions you take


The ranking rule.

"We sent a proposal" is your action. "They opened it and came back with questions" is theirs. Where both are available, build the boundary on theirs, because that is the one that carries information.


5. This exposes the stages where you are doing all the work


An uncomfortable but useful finding.

If three consecutive boundaries are all things you did, that portion of the funnel is you pushing a buyer who has stopped moving. Recognising it early is worth more than the chasing.


6. Different buyer types move differently


Where one funnel becomes two.

A referral arrives already trusting you and skips comparison entirely. A cold enquirer does not. Forcing both through the same stages makes the referral funnel look inexplicably efficient and tells you nothing.


7. Long gaps between buyer actions are the real signal


What to watch.

Time since the buyer last did anything, rather than time since you last did anything. A deal where you have sent four follow-ups and received nothing is not progressing, whatever the stage says.


8. Talk to buyers to get the stages right


The research that takes an afternoon.

Ask five recent customers what they did, in order, from first noticing the problem. Their sequence will contain steps you did not know existed, and one of them is usually where you are being eliminated.


9. Keep your internal process, but keep it separate


Both are needed.

Your workflow still needs managing. Track it as a checklist attached to a stage, not as the stages themselves, so the funnel keeps measuring the sale and the checklist keeps managing the work.

Be careful about over-correcting into stages so buyer-centric that nobody can populate them. A stage has to be both a real change for the buyer and observable by you, and one without the other is not usable.


Conclusion


Build every boundary on something the buyer did, because internal activity is not progress.

Test each boundary by asking what changed for the buyer, use observable actions as the proxy for their internal state, prefer their actions over yours where both exist, treat a run of boundaries that are all your actions as a warning, separate funnels for buyer types that genuinely behave differently, watch time since their last action rather than yours, ask five recent customers to describe their own sequence, and keep your internal workflow as a checklist rather than as the stages.


Related reading


 
 
 

Comments


bottom of page