Onboard a New Client Without a Week of Email
Onboarding a new client rarely involves much work. It involves a small amount of work spread across nine days, most of which is spent waiting for a reply to a message that could have been sent earlier. The elapsed time is a sequencing problem.
Quick answer (TLDR)
- Decide the complete ask before you send anything - a second request costs days, not minutes
- Build the destination first, so your first message points at something real
- Send one message, not a welcome followed by a list followed by a link
- Name the item that depends on a third party and tell them to start it first
- Check documents on arrival, while the client still has them to hand
Why the usual sequence costs a week
Watch a typical onboarding and the elapsed time is almost entirely waiting.
Day one: a welcome email. Day two: the client replies. Day three: you send the document list. Day six: two of the six documents arrive. Day seven: you ask about the other four. Day nine: three more arrive, one of them unusable. Day eleven: the corrected version. Day twelve: you realise you also need a signed engagement letter, which nobody mentioned because it lives in a different part of the process.
Total working time: perhaps ninety minutes across both sides. Total elapsed time: twelve days. Every gap is a round trip, and every round trip runs at the speed of whoever is slower to check messages that day.
The fix is not to work faster. It is to remove round trips. Each one you delete is worth roughly two days.
The six steps
1. Decide the whole ask before the first message
Before you contact the client, write down everything you will need: documents, decisions, access, information, signatures. All of it.
This is the step that gets skipped, and it is the expensive one. A second request arriving on day nine does not just cost the days it takes to fulfil - it costs credibility. The client now assumes there may be a third, and treats your requests as a stream rather than a task with an end.
If something genuinely cannot be known upfront, say so explicitly in the first message and say what it depends on. "Once I have seen the accounts I may need one more thing; I will tell you within a day." That is a different experience from a surprise.
2. Set up the destination before you contact them
Create the place the documents will live, and put the checklist in it, before you send anything.
The reason is not tidiness. It is that your first message can then contain a link to somewhere real, with the list already visible in it. The alternative - "I'll set you up and send details shortly" - is a round trip that exists purely because the preparation happened in the wrong order.
3. Send one message that contains everything
Welcome, scope, the full document list in plain language, the link, what happens next, and when.
Say the two things clients most often need permission for: that a phone photograph is fine, and roughly how long the whole thing should take them. A client who knows the task is twenty minutes will start it; a client who thinks it might be two hours will schedule it for a weekend that never arrives.
Name each document the way the client would name it, not the way your profession does. "Proof of address - a utility bill, council tax letter or bank statement from the last three months showing your name and address" removes a question that would otherwise cost two days.
4. Name the long-lead item explicitly
Almost every onboarding contains one item that depends on someone else: a reference, a certificate from a registry, a document held by a previous adviser, an official translation.
That item sets the real completion date, and clients almost always leave it until last because it looks like just another line on the list.
Say which one it is and say to start it first. This single sentence is frequently worth more than everything else on this page combined, because it moves the longest-duration task to the front instead of the back.
5. Review each item as it arrives
Open documents the day they land. Thirty seconds each. Say straight away if a page is missing, a statement covers the wrong months, or an image is cut off.
On the day they sent it, the client still has the document in front of them and re-doing it is trivial. A week later they have filed it, moved on, and the correction is a fresh task competing with everything else.
6. Close the loop and say what happens next
When the pack is complete, say so. Then say what you are doing next and by when.
Onboarding without a stated ending leaves the client uncertain whether more will be asked of them. That uncertainty is where the "just checking you have everything you need?" emails come from - which is a round trip you caused by not closing.
The realistic version
One day is achievable when the client is available and nothing depends on a third party. Often something does, and then the honest target is "one day of your time and theirs, plus however long the certificate takes."
That is still a different outcome from twelve days. The difference is not effort, it is that nothing is waiting on a message you have not sent yet.
A concrete example
A small consultancy onboarding new clients averaged around ten days from signed proposal to actually starting work. Nobody thought this was a problem until they measured where the time went: roughly seven of the ten days were spent waiting for replies.
They changed the sequence rather than the content. Everything the client needed went into a single first message pointing at a checklist that was already set up. The item requiring a third party was flagged as "start this today, it takes longest." Documents were reviewed on arrival rather than at the end.
The average came down to around three days, most of which was the third-party item. The work was identical; the waiting was not.
Where a client portal fits
We build one, so weigh this accordingly.
Droplana gives each client a private portal with a document checklist you set per client. The portal exists before you send the first message, so the welcome can point at it. The client opens one link with no account and no password, sees which items are outstanding, and can photograph paper documents straight from their phone. You comment on a specific file when something needs redoing rather than writing a fresh email about it, and the link stays the same for the life of the relationship, so it works at the annual review too.
What it does not do: it does not decide what to ask for, it does not write the message, and it will not make a client available who is busy. Steps 1, 3, 4 and 6 above are things you do, and no software substitutes for them. The portal removes round trips 2 and 5; the rest is sequencing discipline.
More on the request side in why clients don't send documents, and on the collection mechanics in how to collect documents from clients. The consultants page covers the same sequence for an engagement rather than a document pack.
The short version
Onboarding takes two weeks because it is a chain of round trips, not because it is a lot of work. Decide the entire ask first, build the destination before you write, put everything in one message, flag the long-lead item, review on arrival, and say when it is finished. Each deleted round trip is worth about two days.
Want the checklist ready before you send the welcome email? Try Droplana free - three clients, no card.