Process Optimisation for Revenue Teams
Revenue process optimisation means finding the single stage where the most value is lost and fixing it in the system rather than in a document. Fixes ranked by durability: eliminate the step, automate it, enforce it with validation, then document it. Documentation is the weakest and the most commonly chosen.
- Find one bottleneck. A process improvement programme with six workstreams improves nothing measurably.
- Rank fixes by durability: eliminate, automate, enforce, document. Most teams start at the weakest.
- Measure stage duration, not just conversion. Slow stages and lossy stages need different fixes.
- A process that depends on someone remembering will decay within a quarter, every time.
- Removing a step is worth more than optimising it, and it is almost never the option considered first.
Find one bottleneck
The standard approach is a process improvement programme covering lead handoff, discovery quality, proposal turnaround, and forecast hygiene simultaneously. Six months later everything has been touched, several things are marginally better, and nobody can attribute any revenue change to any of it.
The alternative: find the single stage where the most value is being lost, fix it properly, measure the result, then move to the next one. Slower per initiative and far faster to compounding results, because you learn what worked.
Where to measure
Two different measurements, because two different things go wrong at a stage.
| Measure | Reveals | Fix direction |
|---|---|---|
| Stage conversion | Where deals die | Qualification, enablement, or exit criteria |
| Stage duration | Where deals wait | Handoffs, approvals, and dependencies |
| Rework rate | Where work gets redone | Upstream data or definition quality |
| Touch count to progress | Where effort concentrates | Automation candidates |
Most teams measure only the first. A stage with healthy conversion and a median duration of 23 days against a 6-day target is losing you a quarter of your cycle time, and no conversion report will ever surface it.
The four fix types, ranked by durability
- 011. Eliminate the step
The most durable fix and the least considered. Ask what would break if this step simply did not exist. A surprising number of approval gates, handoff forms, and required stages exist because of an incident nobody remembers, and removing them costs nothing and never decays.
- 022. Automate it
If the step must happen but requires no judgement, the system should do it. Routing, notification, data entry from a known source, stage progression from objective conditions. Durable, because automation does not forget when someone is busy.
- 033. Enforce it in the system
If the step requires human judgement, the system should make skipping it impossible — validation at stage change, required evidence, blocking approvals. Durable while the rule exists, and visible when someone changes it.
- 044. Document and train
The weakest fix and the most commonly chosen, because it is the cheapest to implement and produces an artefact that looks like progress. A documented process degrades continuously as people join, leave, and hit edge cases.
Work down that list in order for every fix. Only reach step four when the first three genuinely do not apply — and when you do, accept that you have chosen a fix that needs re-application every two quarters.
Worked example: the proposal bottleneck
A common pattern, and how the four fix types apply to the same problem.
Symptom: median 9 days between verbal agreement and proposal sent. Conversion from that stage is healthy, so nobody flagged it. Nine days is roughly 15% of the cycle spent producing a document.
| Fix type | Applied here | Durability |
|---|---|---|
| Eliminate | Do deals under $25K need a formal proposal at all, or would a summary email close them? | Permanent if it works |
| Automate | Generate the proposal from CRM fields; rep edits rather than assembles | High |
| Enforce | Block stage progression without a proposal record; alert the manager at day 3 | High while the rule stands |
| Document | Write a proposal SOP and train the team on it | Decays in about a quarter |
Most teams reach for the fourth row. The first row is usually available, frequently correct for a segment, and almost never asked.
Why documentation loses
Not because people are careless. A documented process depends on every person remembering it under pressure, in every edge case, indefinitely, including people who joined after the training. That is an unreasonable expectation of any team, and its failure is a design flaw rather than a discipline problem.
The test for any process you consider important: what happens in the system if someone skips it? If the answer is nothing, you do not have a process — you have a shared hope, and it will be honoured for about a quarter.
Not everything should be optimised
Three cases where the correct answer is to leave it alone:
- Low-volume, high-judgement steps. Optimising something that happens four times a quarter and requires real thinking each time produces overhead, not efficiency.
- Anything on an unproven motion. Instrumenting a sales process you may abandon in two quarters is expensive and usually wasted — the same argument as in RevOps strategy.
- Steps whose slowness is the customer's, not yours. Procurement and legal review are outside your control. Measure them separately so they do not contaminate your internal cycle metrics.
Measuring whether it worked
Commit to the metric and the date before you start. For a duration fix, the median for that stage, read four weeks after the change. For a conversion fix, stage conversion measured over a full cycle, because anything shorter is noise.
Then check for displacement, which almost nobody does. A stage that got faster because work moved to the stage before it has not improved anything — it has relocated the bottleneck, and the total cycle length is the number that tells you. Reviewing this properly is what the quarterly system review is for.
Want this diagnosed on your own numbers?
The RADAR™ Scan scores your revenue engine in 2 minutes — 12 questions, a 0–100 score, and your gate verdict. No email required.
Run your RADAR™ Scan→Questions this raises.
How do you optimise a revenue process?
What should you measure to find a process bottleneck?
Why does documenting a process not work?
What is the most durable type of process fix?
When should you not optimise a process?
Related guides.
Six steps from diagnosis to cadence — including the part most strategies skip, which is deciding what you will not do.
RevOps AgencyFour reviews, fixed agendas, named owners — the rhythm that stops a revenue system decaying back to entropy within two quarters.
RevOpsThe work a RevOps agency actually delivers, what it costs in 2026, and the honest comparison against hiring in-house or going fractional.
RevOps AgencyFirst we build your pipeline. Then we build the machine that scales it.
Every engagement starts with the RADAR™ Reveal — a 2-week audit with a scored report, gate verdict, and roadmap. Yours to keep, whatever you do next.