Where the Days Go Between "Yes" and "Invoice"

A customer says yes. When does the invoice go out? At a lot of companies between twenty and a hundred and fifty people, the honest answer is "eventually," and the gap between those two moments is where working capital goes to evaporate.

I have mapped this chain at enough businesses that it looks the same almost every time. The quote lives in a Word document someone copies from an older one. The approval, if there is one, lives in an email thread. The delivery details live in the head of whoever is doing the work. The invoice gets built later by re-typing what is in the quote, because the systems do not talk.

Nobody owns this gap, because it is not a department. It is the space between departments.

The three leaks

Approval waiting. A quote needs a signature, a discount sign-off, or a credit check, and it sits in someone's inbox until they get to it. The customer has already said yes; the delay is entirely internal. Nobody tracks it because it looks like a normal email, not like a stalled deal.

Re-keying. Every time data is typed from one system into another, you pay twice: once in the labor, and once in the errors that show up later as a wrong price on an invoice or a line item nobody agreed to. The re-keying is invisible in the org chart because it is just "what so-and-so does."

Delivery and invoice mismatch. What was quoted, what was delivered, and what was billed are three documents produced by three people at three times. When they disagree, the customer holds the whole payment over one disputed line, and you spend a week chasing a signature on a credit note.

The fix order

Fix these in order, because each one depends on the previous being clean.

1. Generate quotes from a template with real prices. Not a copy of last year's Word file. A system that pulls current pricing, applies your standard terms, and produces a consistent document every time. This kills most re-keying at the source, because the quote is now structured data, not prose.
2. Route approvals with a deadline. The approval goes to the right person automatically, and if it sits for two days it escalates or reminds. This is a small automation with an outsized effect, because approval waiting is the cheapest delay to remove and the most expensive one to notice late.
3. Hand the order off without re-typing. When a quote is accepted, the fulfillment record and the draft invoice are created from the quote's own data. The person doing the work sees what was promised; the person billing sees what was delivered. Nobody re-keys, so nothing drifts.

Why this is a cash conversation, not a software one

Every day you shave off the quote-to-cash cycle is a day your cash comes in earlier, and you did not have to sell anything more to get it. If you invoice thirty days after "yes" today and you can make it ten, you have effectively pulled twenty days of revenue forward, permanently, on every future deal. For a business doing, say, $10M a year, twenty days of that revenue is a meaningful pile of money sitting in your bank instead of your customers'.

That is the framing I would use with any vendor, including me. Do not buy this as a technology upgrade. Buy it as a cash-flow project with a software component. The measure of success is not "we implemented a quoting system." It is the number of days between yes and invoice, measured before and after, and the number should go down.

If you do not know what that number is today, that is your first task, and it is a free one: pull the last twenty accepted quotes, find the yes date and the invoice date for each, and average the gap. Write it down. Everything after that is easier to argue for.