The client said yes three weeks ago. Why have they not ordered yet?
Between the signature and the first order sits a process nobody times. It is the most expensive stretch in the company, and the only one that appears in no report.
The deal went well. Sales closed it, the client is happy, the CRM row is green. And then nothing happens for twenty days — because the company search is missing, because the ID arrived unreadable, because the credit-limit request is sitting on the desk of someone who is on holiday this week.
Nobody measures that stretch. Sales moved on to the next deal, admin believes it is fast, and the client — who still has their previous supplier in the meantime — slowly stops being in a hurry. This article times those twenty days one by one, shows which of them are pure waiting, and what putting them back is worth.
1 · The twenty days nobody looks at
Here is the same client on two tracks: how they come aboard today in a company that works well but by hand, and how they come aboard when the process has a system behind it. Same scale. Tap a day to see what happens in it — and what it costs.
How they come aboard today — 21 calendar days
d1 · The yes, and the document request — Sales sends an email listing what is needed: company search, ID of the legal representative, bank details, credit limit if any. The list is the one they have, and it is not always the current one. (day one already spent on a list)
d2 · Waiting — The email reached someone who does not handle it and has to forward it. Meanwhile it is Friday. (day lost)
d3 · Waiting — Weekend. The calendar count keeps running when nobody is working, and it is the count the client sees. (day lost)
d6 · Documents arrive, most of them — Two files out of four. The company search is eleven months old and the ID is a crooked photo of a screen. Nobody notices immediately: the person who will have to use them notices, days later. (the error enters now, surfaces later)
d8 · Waiting in a queue — The file sits in a shared folder with nine others. There is no queue, there is an order of arrival everyone interprets. (day lost)
d10 · Manual verification — Somebody opens the companies register, eyeballs the VAT number, looks for beneficial owners. Twenty minutes of real work, after eight days of waiting. (20 minutes after 8 days)
d11 · A document is missing — The client is written to again for an up-to-date search and a readable photo. For them it is the second time they are asked the same thing, and it is the moment they start thinking we are disorganised. (the second request costs credibility)
d14 · Waiting — The client replies when they can: they have a business to run and this file is not their priority. They have still bought nothing from us. (day lost)
d16 · Credit limit request — The amount is over threshold, so it needs approval. The approver does not have the file in front of them: they have an email summarising the file. (a decision made on a summary)
d19 · Waiting for approval — The approver is travelling. There is no second approver, because it was never defined who that would be. (day lost)
d21 · Client active — The record is keyed into the ERP by hand, copying from the files. The client can order. Three weeks have passed since the yes. (first order possible on day 21)
With the process governed — 2 days
d1 · A link, not an email — On the yes the client receives a link. The form asks only what THEIR case requires: the VAT number is verified as they type it, an unreadable document is refused on the spot, the company search is fetched by the system instead of requested. Ten minutes, and they do it when it suits them. (no second request)
d2 · Checks automatic, decision human — Companies register, beneficial owners, sanctions lists: the checks run and produce a score. Below the threshold the account opens itself; above it, a person receives the WHOLE file, not a summary. A credit limit over threshold stays a human decision, but one taken in two minutes on complete data. (first order possible on day 2)
The number that makes it arguable
Of eleven marked days, five are pure waiting: nobody works on them and the file ages on its own. Nobody is being lazy — the process has nowhere to live, so it lives in people's inboxes, and an inbox has no queue, no state and no deadline.
2 · Why it is not a people problem
The instinctive fix is putting somebody in charge of chasing files. It works for a few months and then breaks, because the problem is not missing attention: it is a missing place.
The file does not exist as an object. What exists is four emails, two files on a shared drive and a CRM row saying “onboarding” for three weeks without saying where it got to. If somebody asks how far along we are, answering means opening three different places.
No state, therefore no deadline. A state exists to trigger something: if “documents requested” lasts more than three days, somebody has to know. Without states there are no thresholds, and without thresholds the delay is discovered when the client points it out.
Verification depends on who does it. One colleague reads the whole company search, another checks only the VAT number. Neither is wrong: what is missing is a definition of what “verified” means, and until it exists the quality of the check is a property of the person.
The client sees nothing. They do not know if something is missing, nor how far from the end they are, and the only way to find out is to phone — which generates more work for the company already struggling to keep up with them.
3 · What actually changes, in order of return
You do not need to build it all at once. These four pieces, in this order, cover most of the gap between the two tracks — and the first two stand up in a few weeks.
A form that validates as it is filled. The VAT number is checked by checksum and against the companies register the moment it is typed; an unreadable document is refused there and then, not three days later. This is the piece that removes the second request to the client, which is the one that costs credibility.
The file as an object with a state. One row saying where we are, for how long, and whose move it is. Thresholds do the rest: if a step exceeds the time it was given, it lights up — before the client notices.
Checks that run themselves, decisions that stay human. Companies register, beneficial owners, sanctions lists: these are lookups, and lookups are a machine's job. Judgement on an over-threshold credit limit stays with a person, who now decides on a complete file rather than an emailed summary.
Visibility for the client. A page telling them where their file is and what is missing. It removes the chasing calls, and turns waiting into explained waiting — which is a completely different thing from twenty days of silence.
4 · What putting those days back is worth
This is not a cost saving: it is margin the company has already sold and not yet collected. It is worth working out on your own numbers, because it is the figure that makes arguable an investment that otherwise looks like an organisational whim.
And there is a line the sum does not include because it cannot be measured: the clients who go cold during those three weeks. They do not leave with a no — the previous supplier simply still serves them, the urgency passes, and the first order comes in smaller than it would have been. It is a real loss that appears in no report, and I suspect it is larger than the deferred margin.
Let us time your onboarding
In the half-hour audit we do exactly what you have just read: we take the last client who came aboard and reconstruct their days, one by one, up to the first order. All it needs is somebody who remembers the dates — and they usually do, because they were frustrating.
At the end you have two numbers of your own: how many days it really takes and how many of those are pure waiting. From there the rest is a decision with data under it, not an impression. And if the numbers say your process is already fast, I will tell you and we part with one more fact each.
Why do weeks pass between a client signing and their first order?
Because that part of the process has nowhere to live: it lives in people's inboxes, and an inbox has no queue, no status and no deadline. The company search, the document that arrived unreadable, the credit request sitting on somebody's desk. In the case reconstructed in the article it is twenty-one calendar days, and part of that is pure waiting: nobody is working on it, the file simply ages.
What should you automate first in client onboarding?
The form that validates as it is filled in. The VAT number checked the moment it is typed, the unreadable document rejected immediately rather than three days later: it removes the second request to the client, which is the one that costs credibility. Right after comes visibility — a page telling the client where their file stands and what is missing, turning twenty days of silence into an explained wait.
How do you measure the time from signature to first order?
In calendar days, not working days: the customer counts weekends too. Take the last client you onboarded and reconstruct the dates one by one up to the first order, separating days when someone worked from pure waiting. You need two numbers: how many days it really takes, and how many of those are nobody's work. The second is the one you can act on.
Why put a deadline on the states of a case?
A state exists to trigger something. If «documents requested» lasts more than three days, someone has to know: without states there are no thresholds, and without thresholds the delay surfaces when the client points it out — the worst possible moment, once the enthusiasm of signing has worn off.