Sales process automation: how do you put it in order? starting from criteria, not from tools
Automating a B2B funnel does not start with picking a platform. It starts with one question: what has to be true before an opportunity moves a stage forward. Below: how to write stage criteria, what should fire on its own when a stage changes, the minimum data a forecast needs, the exceptions to leave alone, and the order to build in and measure.
- 42 hoursthe average reply time to a web enquiry in an audit of 2,241 companies published in Harvard Business Review; the only stretch of a B2B funnel anyone has measured on a large sample
- 3 fieldsdecision maker, budget and decision date: the minimum at the qualification gate, without which a forecast is a sum of moods
- 14 daysthe usual threshold after which an opportunity with no movement drops out of the forecast until somebody actually moves it
- 30 and 90 dayswhen we measure the process after go-live, against metrics written down before the start
Short answer
Where do you start with sales process automation?
Start by writing down your funnel stages and the entry criterion for each one, in a form somebody can check without asking the rep what they meant. „The client is interested” is not a criterion. „Decision maker, budget and decision date are filled in” is one, because a rule can read it and two people will score it the same way.
Then describe what should happen on its own when a stage changes: which task is created, who gets reminded and when, which document is assembled, who gets notified. None of this needs an AI model. It needs rules somebody signed off on.
Build from the least contentious to the most: lead routing first, then follow-up after a proposal, then gates on stage changes, and the forecast last. A forecast calculated from fields nobody fills in yet is worse than a spreadsheet, because it looks credible.
How do you write a stage criterion two people will score the same way?
A criterion is decidable when you can check it from the CRM record alone, without asking the opportunity owner what they had in mind. If two reps look at the same opportunity and disagree, the criterion is a judgement call and no rule will defend it.
Take the stage names from how you sell today, not from a textbook. The condition goes in as one sentence, written on the side of fact rather than feeling. Below is the same stage list twice: once as it appears in the deck, once as a rule can read it.
| Stage | Judgement call | Criterion a rule can check |
|---|---|---|
| New lead | „looks legitimate” | company name, a named person and a contact channel are filled in, and the company fits the profile agreed at the workshop |
| Contacted | „we spoke” | the call is logged on the opportunity with a date and one sentence on what the client needs |
| Qualified | „the client is interested” | three fields are filled in: decision maker, budget and decision date |
| Proposal | „I sent something” | a document version is attached to the opportunity, with the date it went out |
| Negotiation | „we are closing” | an agreed amount and a decision date given by the client, not by the rep |
| Lost | „it did not work out” | a reason picked from a closed list of at most eight options |
The right-hand column doubles as the list of fields that have to exist in your CRM. If one of them does not, the criterion is a wish rather than a condition.
What should happen on its own when a stage changes?
A stage change is the best trigger in the whole funnel, because it is the one moment a rep touches the record anyway. Everything that is supposed to happen then happens without an extra click and without anyone having to remember it.
The scope is always the same and only the details move: a task with a due date, a reminder on the day promised to the client, a document assembled from opportunity fields, a notification for whoever has to get involved. None of it needs a model. A rule in the CRM or in n8n is enough.
- A task for the next step, due date counted from the stage change, assigned to the opportunity owner
- A reminder on the decision date the client gave, not seven days after the proposal went out
- A document assembled from opportunity fields: proposal, summary of agreements, order to sign
- A Slack or email notification for whoever prices the work, when an opportunity enters the proposal stage
- A history entry: who moved it, when, and with which fields filled in, so you can measure it later
- Moving a stage backwards is an event too: it clears the tasks from the previous step so no orphans are left
Which fields do you require at a stage gate so the forecast means something?
A forecast is not a separate module. It is the consequence of what you enforce at the gate. The field missing at qualification comes back a quarter later as the gap between a promise and a result. The list below is short on purpose: every extra field lowers the odds that anyone fills in the ones that matter.
Hold to one rule: a field goes on the list only when its absence changes a number in the forecast. Everything else can stay descriptive and nobody checks it.
| Field at the stage gate | Without it, the forecast | Who fills it in and when |
|---|---|---|
| Decision maker on the client side | quotes an amount nobody in the conversations so far actually signs off | the rep, after the first call |
| Budget or a range | shows the value somebody typed in when they created the opportunity | the rep, at qualification |
| Decision date given by the client | drops the opportunity into the wrong quarter and ruins the whole quarter | the rep, at qualification |
| Date of the last real movement | counts opportunities that are already dead | the automation, on every event on the opportunity |
| Loss reason from a closed list | gives you loose opinions instead of statistics | the rep, at close |
The date of the last movement is the only field a human never touches. That is exactly why it is the most reliable one, and why the 14-day threshold rests on it.
Which exceptions are not worth automating?
Every funnel has cases that break the process deliberately and rightly. Forcing them into a rule ends the same way every time: one exception path appears, then a second, and six months later nobody knows which version of the process is in force.
An explicit escape hatch works better. The rep ticks a special case, gives the reason in one sentence and moves on without a block. The automation does not judge it, it counts it. If the hatch shows up in one opportunity in four, it is not an exception. It is a missing stage.
- Large contracts run by the board, where decisions happen outside the CRM and at a different pace
- Long-standing clients who come back with an order without passing through qualification
- Tender work, where the deadlines come from the documentation rather than from your process
- Deals run jointly with a partner, where part of the history sits in somebody else's system
- One-off sales outside the core offer, which there is no point describing in stages
In what order do you build automations in the funnel?
Order matters more than the choice of tool. You begin with rules everybody agrees are obvious, with an effect visible in the same week. The forecast comes last, because it needs data nobody fills in at the start.
Below is the order we use when we wire a funnel together as part of B2B sales automation. Each step stands on its own and you can stop after any of them.
Lead routing
A form submission reaches the right rep in seconds, on a rule written in one sentence: region, industry or company size. Nobody argues about whose lead it is, because the team agreed the rule, not the system.
Follow-up after a proposal and after a meeting
The automation watches the date promised to the client and stops the sequence the moment a reply comes in. This is the one stretch of the funnel with a hard reference point: the audit of 2,241 companies published in Harvard Business Review found an average reply time of 42 hours.
Prompts and gates on stage changes
The automation checks the entry criterion and says what is missing. For the first two weeks it only flags, then it blocks. This is where the process actually changes and where most of the resistance sits, which is why it is not step one.
A forecast on one formula
Only once the fields are being filled in can you calculate pipeline value from stage, age and decision date. An opportunity with no movement for more than 14 days drops out of the forecast until it moves for real. The sales director signs off the formula.
Handover after a win
A win creates the project with its tasks, carries over the scope and the agreements, and triggers invoicing and client onboarding. It is the most commonly skipped stretch and usually the one that spoils the first weeks of the engagement.
How do you measure the process instead of the people?
A metric aimed at a person becomes a workaround inside a month. The rep stops creating opportunities they are unsure about, or moves them in bulk on a Friday. What you measure then is behaviour caused by the measurement, not sales.
Measure stretches of the process and where things are stuck. The four numbers below are enough for the first six months, and you read all of them out of the CRM without asking anybody anything.
- Median time in each stage, from entry to exit, counted separately for wins and losses
- Share of opportunities with no movement for more than 14 days, split by stage rather than by person
- Share of stage changes made without the required fields, which is the escape-hatch counter
- Gap between the forecast and the actual quarter, calculated on the same formula every month
Common mistakes
Five mistakes that break funnel automation
Starting with the forecast instead of routing and follow-up
The forecast is calculated from fields nobody fills in yet. Out comes a serious-looking number with no connection to the state of the funnel, and trust in the whole rollout is gone after the first quarter.
A stage criterion written as a feeling
Everybody reads „the client is interested” differently, so the stages stop meaning anything. The automation has nothing to check and becomes an expensive ornament in the CRM.
Enforcing a dozen fields at once
Reps type in whatever gets them through. You end up with a complete set of data that is completely untrue, and that is a worse position than an empty field.
Switching the block on from day one
The team learns the rule from an error message in the middle of a client call. The resistance created in the first week stays for the whole rollout.
Exceptions forced into the rule
A second and a third process path appear, each maintained by hand. Six months later nobody can say which version is in force, and the process goes back into a notebook.
Metrics pointed at people
People optimise the report rather than sales: opportunities created later, moved in bulk, closed without a reason. The data loses its value at exactly the point you start relying on it.
Checklist
Checklist before the first automation in your funnel
If any line is a no, start there rather than in the tool's configuration.
- Stages named the way you sell today, signed off by the sales team
- Every stage has an entry criterion written in one sentence and checkable from the CRM record
- The fields the forecast needs exist in the CRM, and there are at most five of them
- Agreed what happens on its own when a stage changes: task, reminder date, document, one notification
- The exception list written down, with an explicit escape hatch and a counter on it
- Build order set from routing and follow-up, with the forecast last
- Four process metrics written down before the start, each with the place it is read from
- The 30-day and 90-day measurement dates already in the calendar
Sources
Sources
- Oldroyd, McElheran, Elkington, „The Short Life of Online Sales Leads”, Harvard Business Review, 2011 (audit of 2,241 companies, average reply time 42 hours)
- HubSpot developer documentation: deals API, properties and webhooks
- n8n documentation: triggers, conditions and error handling in workflows
- JustAutomate, B2B sales automation: funnel stages, stage conditions and what the automation does
Let us write your stage criteria
Process first. Tools second.
On a free 30-minute consultation we take one stage of your funnel and try to write its entry criterion so that two people score it the same way. That is usually enough to see where the process comes apart. The process workshop costs EUR 3,500 net per week and ends with stages, conditions and a build order you can execute without us.
Book a free consultationFrequently asked questions
What is sales process automation?
It is moving the funnel out of people's heads and notebooks into a system: stages get entry criteria you can check without a conversation, and a stage change fires a task, a reminder, a document or a notification on its own. The rep still runs the client conversation. The automation keeps the record and the dates. No AI model is needed for this.
Where do you start with B2B funnel automation?
With lead routing and with follow-up after a proposal. Both rules are obvious to the whole team, both show an effect in the same week, and neither asks anyone to change a habit. Gates on stage changes come later, and the forecast comes last, once the fields are actually being filled in.
How do you write a criterion for moving between stages?
So that it can be checked from the CRM record alone. The test is simple: if two reps look at the same opportunity and disagree, the criterion is a judgement call. „The client is interested” fails that test. „Decision maker, budget and decision date are filled in” passes it.
How many fields should you require at the qualification stage?
Three to five, no more. Decision maker, budget and a decision date given by the client are the minimum without which a forecast is guesswork. Every extra field lowers the odds that anyone fills in the ones that actually matter, and data typed in carelessly is worse than an empty field.
Does sales automation require AI?
No. Stage criteria, tasks after a stage change, follow-ups, routing and the forecast formula are rules you describe once and that run the same way every time. You add an AI model later and for different work, for example answering questions about the state of the funnel in a plain sentence.
What do you do with exceptions the process does not cover?
Leave an explicit escape hatch: the rep ticks a special case, types the reason in one sentence and moves on without a block. The automation does not judge it, it counts how often it is used. If after a quarter the hatch shows up in one opportunity in four, that is not an exception, it is a missing stage.
How do you measure the effect of funnel automation?
On four numbers from the CRM: median time in each stage, the share of opportunities with no movement for more than 14 days, the share of stage changes made without the required fields, and the gap between the forecast and the quarter's result. All four describe stretches of the process, not people. The 30-day reading is for fixes, the verdict comes at 90 days.
How much does it cost to put a sales process in order?
The process workshop costs EUR 3,500 net per week and for a whole funnel usually runs 1 to 2 weeks. It ends with written stages, stage criteria, the field list and the build order. Implementation is quoted after the workshop, because only then do you know how many stages and systems are in scope.