Customer funneling: moving people deliberately, not hopefully

2 days ago
3 min read

Introduction

Customer funneling is the practice of moving people deliberately from first contact to purchase, rather than leaving them to work it out. Most small businesses do it accidentally: something happens, then something else, and whether anybody advances depends on who happened to answer the phone.

The deliberate version is not complicated and it is not software. It is a short list of stages, a decision about what should happen at each one, and a named person responsible for making it happen. That is the whole discipline.

The word sounds mechanical, and the objection to it usually is too — that treating people as items in a process is impersonal. In practice the opposite holds: the businesses that decide in advance what happens next are the ones that stop leaving people waiting.

1. Customer funneling starts with the stages you actually have

The first step.

Not a template from an article — the stages your own records show, taken from enquiries, calendar and invoices. Usually four to six. Anything more cannot be maintained. Derive them from what already happens rather than what should.

2. Decide what advances somebody at each stage

The core decision.

For every stage, one thing that must happen for the person to move on. Written down. Vague stages produce vague responsibility. A quote sent, a visit booked, a question answered.

3. Name who does it

The accountability.

A stage with no owner is where people stop moving. In a business of three, this is still worth writing down. Ownership gaps cause more losses than technique gaps. One name per stage, not a team.

4. Set a time limit per stage

The mechanism that does the work.

Anything sitting longer than the limit gets attention, automatically. Most losses are things that quietly stopped rather than things that were refused. A date beside each name is enough. Two working days suits most stages.

5. Make the next step obvious to the buyer

The half that faces outward.

At every point the person should know what happens next and when. Uncertainty is where people go elsewhere. This costs a sentence each time. Give a date rather than a stage name.

6. Count how many are at each stage

The measurement.

A weekly count of people at each stage shows where the queue is building. It takes minutes from a spreadsheet. It is also the fastest way to spot a stage nobody owns.

7. Move people out as well as through

The neglected direction.

Somebody who is not going to buy should be marked as such and removed, not left to inflate the numbers. A clean list is what makes the counts usable. Say so honestly rather than leaving it ambiguous.

8. Do not add stages to fix a problem

The complexity warning.

When a stage is not working, the instinct is to add another before it. Usually the fix is to shorten the one that is failing. Removal beats addition almost every time.

9. Review it when something changes

The maintenance.

New service, new channel, new person answering enquiries — each is a reason to check the stages still describe reality. Twice a year, briefly. A process nobody revisits stops matching within a year.

Be careful about building the process around the tool. Choosing software first and then arranging your stages to suit its fields produces a funnel that describes the software, and those are the ones that get abandoned within a quarter.

Conclusion

Write down the stages your records actually show, then decide what moves somebody through each one.

Give every stage an owner and a time limit so nothing sits unnoticed, tell the buyer what happens next at each point, count how many people are at each stage weekly, mark and remove the ones who are not going to proceed, resist adding stages when the real fix is shortening an existing one, and revisit the whole thing twice a year.