They signed. Everybody was pleased.
Three weeks later they are finally set up and working properly. In between: an account created here, a login sent there, documents chased twice, a form filled in that asked for things they had already sent, and one thing that got missed and surfaced in week four.
The selling took a week. The starting took three. And the second one is the bit the customer will remember when they describe you to somebody else.
Where the three weeks go
Onboarding is the most system-heavy process in most businesses, because it is the one moment when every system needs to learn about the same person at once.
- Details, collected more than once. They gave you their information when they enquired, again on the contract, and again on the setup form. Three times, because none of those three places talk to each other.
- Documents, chased. Identification, insurance, a signed authority, whatever your trade requires. Somebody asks, waits, asks again, and holds the mental list of who owes what.
- Accounts, created by hand. Your job system, your accounting package, your portal, your scheduling tool. Each one a separate person doing a separate manual creation.
- Access, sent piecemeal. Logins arriving in separate emails over days, some of which go to spam and get resent.
- The internal handover. Sales knows things that operations needs and passes them on in a conversation, which means whatever was not said is now lost.
- The thing nobody owns. One step sits between two people’s jobs. It gets done late or not at all, and surfaces as a problem a month later.
The cost is not the admin hours
Count the hours by all means. They are real. But three other costs are larger.
Revenue starts late. Whatever they signed for is not running yet, so nothing is being delivered or billed. Multiply the delay by what a customer is worth per week and you have a number that dwarfs the admin.
First impressions are load-bearing. The onboarding is the first time they experience how you actually operate, rather than how you sell. A chaotic three weeks teaches them something about you that a good sales conversation cannot undo.
The thing that gets missed. Every manual onboarding has a step that occasionally does not happen — a permission not granted, a document never collected, a system where they were never created. It is not discovered on day one. It is discovered on the day it matters.
Why this stays manual longer than anything else
Two honest reasons, and it is worth knowing them before assuming it is neglect.
First, it feels like a one-off. Every new customer feels bespoke while you are in it, so it never quite gets treated as a repeatable process even when it is the ninetieth time.
Second, it genuinely crosses the most boundaries. Onboarding touches sales, operations, finance and whatever compliance your trade has. Processes that cross departments have no single owner, and a process with no owner does not get improved. It gets endured, and everybody assumes somebody else finds it as annoying as they do.
What an Onboarding Engine does with it
The shape: new customer, documents, accounts, running.
One intake that collects everything once. A checklist that exists in the system rather than in someone’s head, so what is outstanding is a fact anybody can look up rather than a thing somebody remembers. Chasing that happens on a schedule without a person deciding to do it. Accounts created from the details already held rather than re-typed. And a visible state — which stage this customer is at, what is blocking them, how long they have been waiting.
The gates stay yours. Approving the customer, checking their documents are genuinely acceptable, deciding an exception is fine — all human. What goes is the collecting, the re-typing, the remembering and the chasing.
What I saw doing this from the other side
At Pantheon I delivered platform training to customers’ development teams, which meant meeting a lot of organisations at exactly this stage — after the decision, before things worked.
The pattern I would hand you: the customers who struggled later were almost always the ones whose start was messy, and not because the mess caused the problems. It was that a chaotic onboarding meant nobody had a complete picture of what that customer actually had, so every later question started with an investigation.
The setup is not admin you get through before the real relationship starts. It is where the record of the relationship gets created, and a bad one costs you for as long as they stay.
Audit your own, this month
- Take your last five new customers. Write the date they committed and the date they were genuinely up and running.
- Write the gap. Then ask each internal person involved what they were waiting on.
- Count how many times the customer supplied the same information. Ask them if you dare — it is the most useful uncomfortable question available.
- List every account or access that has to be created. Mark who creates each and whether anything verifies it happened.
- Find the step with no owner. There is one. Ask two people who does it and see whether the answers match.
If your gap is a day or two, nobody re-supplies anything, and every step has a name against it — you have a working onboarding, and it is rarer than you think.
What to do next
Measure the gap on your last five customers, and ask how many times each supplied the same information. Those two numbers describe your onboarding more honestly than any process document.
If your checklist lives in someone’s head, the difference between a checklist and an engine is where to look next.
If you want the whole picture instead of one workflow: tell us what’s still manual. You get a map of every point where your business stops and waits for a person, what that costs you in hours, and which of those an engine would take over first. Free, yours to keep, and useful even if you never hire us — including on the days the honest answer is that you should not build anything yet.
Common questions
Our onboarding genuinely is different for every customer. Does this still apply?
The steps vary; the skeleton rarely does. Nearly every onboarding is collect information, verify documents, create access, hand over internally, confirm running — with different content in each box. Build the skeleton and let the contents vary. If the honest answer is that two customers share nothing at all, you are doing bespoke projects rather than onboarding, and that is a different process.
How do we handle customers who are slow to send documents?
Separate your delay from theirs before you fix anything, because they need opposite treatments. Track the two clocks separately — time waiting on us, time waiting on them. Most businesses discover their own delay is bigger than they assumed. For the customer side, scheduled chasing that happens without anyone deciding to do it outperforms a person who feels awkward about nagging.
Is it worth automating if we only onboard a few customers a month?
For hours saved, frequently not. For the step that gets missed, sometimes yes — and that is the honest way to weigh it. Low volume is exactly where manual processes drift, because nobody does it often enough to build the habit. If your risk is a compliance step being skipped rather than time, the value is in the checklist existing outside somebody’s memory, and that is cheap to build.
What about the internal handover from sales to operations?
That is where most of the loss is, and it is the least automated part of any onboarding. Everything the salesperson learned lives in their head and their inbox, and gets passed on in a conversation. Anything not said in that conversation is gone. Capturing it at the point of sale, in a structure, is unglamorous and pays for itself faster than anything else here.