How Many Steps Does Your Quote-to-Cash Process Actually Take?

The quote to cash process is everything that happens between a customer saying they are interested and the money landing in your account: pricing it, getting the price approved, sending the quote, chasing the signature, turning the signed thing into an order, delivering or provisioning it, raising the invoice, and chasing that too. Most founders will tell you it is about six steps. Count it properly and it is rarely under twenty.

That gap is the whole point of this post. Not because twenty is bad, some of those steps are load-bearing, but because you cannot argue about a process you have never seen written down, and almost nobody has written this one down.

Why nobody knows the real number

Because no single person has ever done the whole thing.

Sales owns the front. Somebody in finance owns the invoice. Delivery owns the bit in the middle, and in a company under fifty people that is often whoever is least busy that week. Each of them can describe their own section accurately and confidently, and each of them has a slightly wrong idea of what happens either side of it. Ask the salesperson what happens after a contract is signed and you will get a shrug wearing a sentence.

The other reason is that the steps nobody counts are the ones that involve waiting or looking something up. Fetching last year's pricing to check what this client paid is a step. Waiting two days for a director to approve a fifteen percent discount is a step, and an expensive one. Neither shows up in any system as an event, so neither appears in any report, so neither gets discussed.

Count the waits, not the actions

Here is the counting method, and it takes an afternoon.

Take three deals that closed in the last quarter. One straightforward, one that dragged, one that involved a discount or a non-standard term. For each, work backwards from the invoice being paid and write down every point at which the thing changed hands or changed system. Not what people did. Where it sat.

You are counting two things. Handoffs, meaning the thing moved from one person to another. And waits, meaning the thing sat somewhere doing nothing while a human got round to it.

Actions are cheap. A person doing a task takes the time it takes. Waits are where the elapsed time lives, and elapsed time is what your cash flow actually feels. A quote-to-cash process made of eighteen fast actions and nine waits will take three weeks, and the three weeks will be almost entirely the waits.

Do it on paper. Do not open a diagramming tool yet.

The five places the extra steps hide

Approval. Every company has a discount threshold, and the threshold is usually a number one person keeps in their head. The approval step is invisible until you notice that four deals last quarter each sat still for three days waiting on the same inbox.

Re-entry. The customer's details get typed into the CRM by sales, into the quote document by whoever builds quotes, into the accounting system by finance, and into whatever tool actually delivers the thing. That is the same information keyed four times, and each keying is both a step and a chance to introduce an error that becomes another step later.

The signature loop. Sending a contract is one step. Getting it back is not. Between them sit the version the client's lawyer marked up, the clause you agreed to change on a call and forgot to change in the document, and the second signature nobody knew was required.

Handover to delivery. This is the biggest single gap in most small companies. Sales knows what was promised. Delivery knows what was scoped. The two are not the same document, and reconciling them is real work that appears on nobody's job description.

The invoice chase. Raising an invoice is quick. Establishing that the invoice went to the wrong email address, finding the right one, resending, and following up eleven days later is not quick, and it happens more often than anyone admits.

What the number is actually for

The number is not a target. A company that gets its quote-to-cash process from twenty-six steps to nineteen has not obviously improved anything, and treating step count as a score is how you end up removing a check that existed because somebody once shipped an unsigned deal.

What the number gives you is an argument with evidence behind it.

You can now ask whether the discount approval threshold should be higher, because you can show what the current one costs in elapsed days. You can ask whether sales should build quotes at all. You can put a real figure on how long your cash takes to arrive after somebody says yes, which is the figure that decides whether you can hire in March.

And you get one thing that matters more than any of that: a shared picture. When four people who each understood a quarter of the process look at the whole of it together, the conversation changes. Somebody always says "wait, why does it go back to me at that point?" That sentence is worth the afternoon.

If you want the picture to be something more durable than a photographed whiteboard, abi. Clone builds a working model of how your business actually runs, departments, roles, systems and the processes moving between them, with step counts you can turn on to see where the hands go. It is free to build your own, no card needed, and a first pass takes about ten minutes. Letting abi. interview your team is the paid part, because that is the part that costs us money each time. The map is not.

The honest limit of counting steps

Counting steps tells you where the time goes. It does not tell you which steps deserve to exist, and it is genuinely bad at telling you which ones are load-bearing.

Plenty of the slowest steps in a quote-to-cash process are slow because somebody is thinking. A director sitting on a discount request for two days may be doing exactly what you pay them for. Strip that out because it looked like a bottleneck and you will discover the reason for it about two quarters later, in a deal you should have walked away from.

So the map is the beginning of the judgement, not a substitute for it. Count the steps, then go through them one at a time and ask what each is protecting you from. Some are protecting you from nothing and have simply outlived the person who added them. Those are the ones to remove, and there will be fewer of them than you hoped.

Start with the deal that dragged. The straightforward one will tell you what your process does on a good day, which you already know. The one that dragged will tell you what it does under load, which is the only version that matters.