Measure first, understand the real process second, compare third, and only then decide what to fix. Most improvement programmes start at the end — picking fixes before anyone has measured the gap.
When a sales organisation decides it needs to improve, the conversation usually starts with solutions. A new CRM. A new sales methodology. More training. Another hire. Everyone has a favourite fix, and the discussion becomes a debate between them.
The problem is that none of those fixes has been tested against a measured gap. The team is choosing medicine before diagnosing the illness.
Measure, Analyze, Benchmark, Map is the sequence AuditSales uses to avoid that. Four steps, in a specific order, and the order is the point.
1. Measure
The goal: define the metrics that matter and make sure they can actually be measured.
This starts with the four speed metrics — lead response, qualification, time to quote and time to close — and extends to conversion rates between stages and activity levels. For each one, the questions are simple: can we calculate it from data we already hold, and do we trust that data?
Often the first finding is that something important cannot be measured, because a timestamp is missing or a stage is not used consistently. That is a finding in itself, and fixing the instrumentation is frequently the first recommendation.
The output: a baseline for each metric, and a list of what cannot yet be measured.
2. Analyze
The goal: understand the process, the team and the tools as they actually work — not as the process document says they work.
This is the step most programmes skip, and it is the one that explains the numbers. Measuring tells you that time to quote is two weeks. Analysis tells you why: perhaps quotes need a manager’s approval, and the manager only reviews them on Thursdays.
Practical ways to do it:
- Trace real deals from first touch to outcome and note every wait.
- Shadow the team for a few hours and watch where time goes.
- Interview people at each hand-off — marketing, sales development, account executives, operations — about what they receive and what they wish they received.
- Map the stack: which tools are used, which are ignored, and where data is re-typed by hand.
The output: a picture of the real process, with the causes behind each number.
3. Benchmark
The goal: locate the gap.
Compare your baseline against best-in-class performance to see how far you are from what is possible. But also compare against your own best performers. Your fastest reps, your best quarter and your highest-converting lead source show what your own organisation can already achieve. Internal benchmarks are often more persuasive than external ones, because nobody can argue they are unrealistic.
The output: the size of each gap, and which gap matters most — your binding constraint.
4. Map
The goal: a roadmap, split in two.
- Quick wins — changes that can be made in days or weeks with little risk. Removing an approval step. Templating a quote. Routing leads out of a shared inbox.
- Strategic moves — larger changes that take longer and need investment. Automating the first touch. Redefining stages. Rebuilding lead scoring.
Quick wins build credibility and momentum while the strategic moves are underway. They also often reveal that a gap was smaller than it looked once the obvious friction is gone.
The output: a sequenced plan, with the binding constraint addressed first.
Why the ordering matters
Most improvement programmes start at Map. Someone picks a fix, and the organisation implements it. Sometimes it works. Often it improves a stage that was already performing well, while the real constraint sits untouched somewhere else. Months later, the metrics that matter have not moved, and the conclusion is that the fix did not work — when the real problem was that it was never aimed at the gap.
Starting at Measure feels slower. It is almost always faster, because it means the first thing you fix is the thing that matters.
Doing it yourself
A focused version of this can be run internally in a few weeks. The disciplines that matter most: resist proposing solutions until Analyze is done, trace individual deals rather than relying only on averages, and be honest about what the data cannot tell you.
Where to go next
The sales process audit walks through this sequence in practice. Audit before you automate explains why diagnosis comes before any automation. And AuditSales runs this sequence as an engagement.