Your sales figures show what you won, not what you lost

You know roughly how many enquiries came in. You know how many contracts were signed. What you cannot see clearly is everything that happened in between. A call was not returned for four days. A proposal went out and nobody checked whether it had been read. Marketing passed on a list of names with no context, and the salesperson spent a week working out who they were. Each moment costs a little. Together, they can decide whether the pipeline is thinner than the marketing spend suggests.

This is the problem process mapping is designed to solve. The aim is to see the route from first contact to signed contract as a sequence of steps. Each step has a person responsible, a time it takes and a share of people who move on to the next one. Once the route is on paper, the gaps stop being a feeling. They become specific points you can examine.

Many owners assume the problem is lead quality. Sometimes it is. Often the leads are reasonable and the route is what breaks. That makes a better first question than "why are we getting so few good enquiries?" The more useful question is what happens to the enquiries you already have.

The same logic applies whether you sell equipment, components, professional services or project work. The steps differ, but the method is the same. Follow a sample of enquiries through the business, and write down what happens at each point.

Map the route from first contact to signed contract

Start by agreeing the start and end points. The start is the first contact a buyer makes. That might be a web form, a phone call, a trade show lead or a referral from a distributor. The end is the point you count as a win: a signed contract, a purchase order or, for repeat business, the next order. Write both down. A map that starts in the wrong place will miss the first leaks.

Next, list the steps in order. A typical route for a manufacturer or professional services firm might look like this:

  • First response to the enquiry
  • Qualification: the need, the budget range, the decision-maker and the timing
  • First call, meeting or site visit
  • Scope, quote or proposal
  • Decision, with a named next step and a date
  • Order or contract signed, then handover to delivery
  • Repeat order or renewal

For each step, record who owns it, the target time, the actual time, what triggers the next step and the share of people who move on. Keep the record in a shared document or spreadsheet rather than in one person's head. You will use the same fields later, when you measure the changes.

Suppose a manufacturer receives 120 enquiries a month. This is an illustration only, not a benchmark. Sixty of them pass the qualification check and get a call. Thirty of those calls lead to a proposal. Nine proposals are signed. The steepest drop is between proposal and signed contract, with 21 of 30 proposals not converting. That is the first place to look, although only a check of the reasons will show why.

Draw the route on one page. Use a simple grid with the steps across the top and the teams down the side, such as marketing, sales, operations and finance. Place each step in the column of the team that does it. Handovers between teams are where delays often hide, so draw those clearly.

Find the leaks: where value drops out

A leak is any point where a qualified enquiry slows down, stalls or disappears without a reason you would accept. Most leaks fall into a small number of types. Check the map against this list:

  • Slow follow-up: the first reply takes days rather than hours, and the buyer loses momentum.
  • Unclear handover: marketing passes on contacts with no context, or sales receives an enquiry it cannot match to an existing account.
  • Missing answers on the website: the buyer cannot find the information needed for the next step, so they may leave before they enquire.
  • Stalled proposals: there is no agreed next date, no named decision-maker, and no one asks whether the proposal was read.
  • Unowned steps: a task belongs to nobody in particular, so it happens late or not at all.

Each leak needs evidence before it gets a fix. Check the timestamps in your CRM, the email log and the proposal tracker. Ask the sales team which deals went quiet and why. Sometimes the answer is price. Often it is a missing piece of information, or a delay nobody had noticed.

Be careful with the first guess. A slow team is not always the cause. A long approval process on the client side, a change in their budget or a new supplier shortlist can all produce the same pattern. The map helps you tell them apart, because you record the reason each deal left the route, not only the fact that it left.

Website gaps are a content problem as much as a sales problem. If the answers a buyer needs are missing or hard to find, the fix belongs on the page, not in the sales team's follow-up. That side of the work is covered by conversion rate optimisation, and it can run alongside the sales fixes rather than waiting for them.

Prioritise fixes by value and effort

A list of leaks is only useful if you know which to fix first. Score each one on three points, using a scale of 1 to 5. Value is how much revenue the leak affects each month. Effort is how much time, money and change in habit the fix needs. Confidence is how sure you are that the leak is real and that the fix will work.

A simple method is to rank by value multiplied by confidence, then divide by effort. A high-value leak that is cheap to fix and well evidenced should go to the top. A high-value leak that needs a new system and a long project can wait until the quick fixes have been tested. Low-value leaks can be left alone, however untidy they look on the map.

Put a money figure on value wherever you can. Suppose the proposal stage above loses 21 of 30 proposals a month. If a better follow-up routine moved three more of those proposals to a signed contract, and each contract averaged £8,000, the illustration gives £24,000 of extra revenue a month. This is an illustration, not a forecast. The real figure depends on your win rate, your contract values and how many of those three would have been won anyway.

Fix one or two leaks at a time, not all of them. Give each fix a single owner, a start date and a short description of what will change. A fix without an owner is an idea, not a plan.

Write down why you chose each fix. At the review, you will be able to see what you expected, what happened and whether the choice was sound. That record is worth more than a long debate in the meeting room.

Measure before and after, with the same definitions

Before you change anything, measure the current route over a fair period. For a business with a steady flow of enquiries, several weeks of baseline data is usually enough to show a pattern. A shorter run can mislead. One large order, or a quiet fortnight over the holidays, can distort the picture.

Use the same definitions before and after the change. If you alter what counts as a qualified enquiry halfway through, you will not know whether the route improved or the counting changed. Write the definitions down and keep them fixed for the test.

Track the measures that match the steps on your map:

  • Time from enquiry to first reply, both the median and the slowest tenth
  • Share of enquiries that become qualified
  • Share of qualified enquiries that reach a proposal
  • Days from proposal to decision
  • Share of proposals that are signed
  • Average value of a signed contract

Change one thing at a time where you can. If the follow-up routine and the proposal template both change in the same month, the result will not tell you which one helped. Where the business is large enough, compare a sales team, region or product line that uses the new routine with one that does not. Where it is not, compare the same measures before and after, and say clearly that the comparison is rough.

Look at the trend over several weeks rather than the result for a single month. Write a short note on what changed, what you expected and what happened. That note is the most useful record you will keep, because it turns each test into a lesson for the next one.

Start with one route and one fix this month

Choose one route to map first, such as enquiries for a single product line or a single sales region. A narrow route gives you a clear picture quickly. It also avoids a long project that never finishes. If the wider pipeline numbers are not agreed yet, how to plan pipeline for manufacturing sales covers the groundwork to do first.

Next, sit down with the people who run each step. Draw the map together on one page. Ask the sales and marketing teams to describe the same route, then compare their versions. Where they differ, you will often find the first leak.

Then pull the numbers for the last six weeks from the CRM, the inbox and the proposal log. Fill in the baseline for each step. Where a number is missing, that is a finding in itself. The business does not know what happens at that step, and the first fix may be to start recording it.

Score the leaks, choose the top one and give it an owner and a date for the first change. Agree the measure you will use to judge the result. Then leave the change alone long enough for the result to show.

At the end of the test period, hold a short review. Decide whether to keep the change, adjust it or drop it, and then choose the next leak. Repeated over a few quarters, this habit makes the route easier to manage and to forecast. It also means the next fix is based on evidence rather than the loudest opinion in the room.

Find out where your enquiries are being lost

If you want an outside view of the route from first enquiry to signed contract, book a discovery call. We will look at the steps with you, agree which leak to examine first and set out what to measure.

Book a discovery call

Questions and answers

What is process mapping in a sales context?

Process mapping is a step-by-step record of how a buyer moves from first contact to signed contract. For each step it shows who owns the task, how long it takes and what share of people move on. Once the route is on paper, delays and drop-off points can be measured and examined, rather than guessed at.

How do I find where revenue leaks?

Follow a sample of recent enquiries through the business and note what happened at each step. Look for slow replies, stalled proposals, information lost in handover and questions buyers could not get answered. Check the CRM timestamps, and ask the people involved why deals went quiet. Compare the evidence with your conversion figures to see which drop-off is largest.

Who should be involved in mapping the sales process?

Include the people who touch each step: marketing, sales, the people who prepare quotes, operations or delivery, and finance where pricing or payment terms matter. Ask each group to describe the route as they see it. Differences between their descriptions often show where handovers are failing. One person should own the final map and keep it up to date.

How do I decide which fix to make first?

Score each leak for the revenue it affects each month, your confidence that it is real, and the effort the fix needs. Rank by value times confidence, divided by effort. Start with one or two fixes that have a clear owner and a measure. Record why you chose them, so the review can show whether the choice worked.