Client onboarding is everything between "yes" and the client getting the first thing of value from you. It is not a formality: the gap between signing and first value is where doubt lives, and a client who spends three weeks chasing you for a kick-off date has already learned how the rest of the engagement will feel.
It is also the cheapest thing to fix in most small firms, because the failures are not skill failures. They are a missing checklist, an unassigned owner, and a week lost waiting for a document nobody asked for clearly.
What client onboarding has to accomplish
- Confirm the scope in writing, in the client's words, so both sides are agreeing to the same thing rather than to a proposal read at different times.
- Collect what you need to start: access, brand assets, data, the name of the person who can approve things.
- Name the people — your lead, their lead, and who to contact when each is away.
- Set the rhythm: how often you meet, how you report, where questions go, and expected response times in both directions.
- Handle the commercial mechanics: purchase order, invoicing schedule, payment terms, billing contact.
- Cover compliance where it applies — identity checks, data processing agreement, confidentiality, sector-specific requirements.
- Deliver something small and real in the first week or two. The first delivery is what converts a signature into confidence.
- Book the first review before it is needed, so the relationship has a checkpoint that does not depend on someone remembering.
Ask for everything you need in one request, not in five as you discover each gap. A single well-structured intake — with the reason each item is needed — gets a faster and more complete response than a trickle of follow-ups, and it makes you look like someone who has done this before.
A thirty-day sequence that works
- Same day as signature: a welcome message naming your lead, what happens next, and when the kick-off will be. Silence in the first 48 hours is the most common early mistake.
- Within three days: send the intake request and book the kick-off. Booking before the intake returns removes a dependency that otherwise costs a week.
- Kick-off: agree scope, success criteria, the rhythm, and the escalation path. Write it up the same day and send it — the write-up is the artefact, the meeting is not.
- Week one or two: deliver the first small thing. Choose it for speed and visibility, not for importance.
- Set up billing properly before the first invoice, not after it bounces around their accounts department.
- Day thirty: a short review. Is the rhythm right, is the scope still what both sides think, is anything blocked. Fixing a mismatch at day thirty is cheap; at day ninety it is a renegotiation.
- Close the onboarding explicitly, so both sides know the engagement is now in its normal state and the checklist is done.
Standardise the path, personalise the words
The same checklist should run for every client — that is what makes onboarding reliable, and what lets someone else pick it up when the account lead is on holiday. What should never be standardised is the language: a welcome message that reads as a template teaches the client that they are one of many, at precisely the moment you want the opposite impression. Keep the steps fixed and write the two or three sentences that are actually about them.
Ettex CRM is where the relationship side lives: contact profiles with phones, emails, addresses and custom fields for the details each engagement needs, groups and tags to separate clients still onboarding from clients running normally, notes and activity logging so the kick-off call and the chase for access sit on one screen, a visual pipeline you can use for the onboarding stages themselves, and change history showing who did what and when — which is what makes a handover possible. The intake request fits Ettex Forms, where a single form collects everything with file uploads for assets and lands timestamped in a shared inbox; the scope write-up belongs in Ettex Docs; the contract goes through Ettex Signature; and the billing schedule sits in Ettex Invoices with a status on every invoice.
The honest limitation: Ettex has no onboarding automation. There are no sequences that send the welcome message on day zero and the reminder on day three, no task templates that spawn a checklist when a deal is marked won, and no client portal where the client watches their own progress. The pipeline, the forms and the documents are there; the cadence is something you run rather than something that runs itself.
Where onboarding goes wrong
- A gap between signature and first contact, which is when buyer's remorse does its work.
- Requirements requested piecemeal, turning one week into four.
- No named owner on your side, so every client question is routed by whoever happens to see it.
- Scope agreed in a meeting and never written down, which resurfaces as a dispute in month three.
- First value delayed until everything is ready, when a small early delivery would have bought months of patience.
- Billing set up late, so the first invoice arrives as a surprise to someone who has never heard of you.
- Onboarding that never formally ends, leaving both sides unsure whether the relationship has actually started.
Frequently asked
What is client onboarding?
The process between a client signing and receiving their first real value: confirming scope, collecting what you need, naming the people, agreeing the rhythm, setting up billing, and delivering something early.
How long should client onboarding take?
Aim for first value within two weeks and a formal close by day thirty. The exact length matters less than the client always knowing what happens next and when.
What should be in a client onboarding checklist?
Welcome message, intake request, kick-off booking, scope write-up, access and assets, named contacts and escalation path, billing setup, compliance items, first delivery, and a day-thirty review.
Who should own client onboarding?
One named person on your side, with a named backup. Shared ownership is the most reliable way to produce a client who has been contacted by nobody.
How do you avoid overwhelming a new client?
Ask once, in a structured intake, with a short reason next to each item. One complete request is less work for them than five follow-ups, even though it looks longer.
Should onboarding be the same for every client?
The steps should be; the wording should not. A fixed path makes it reliable and transferable, while templated-sounding messages undo the goodwill the process is meant to build.
Client onboarding is a scheduling problem dressed up as a relationship problem. Contact them the same day, ask once, deliver something small early, and review at thirty days — the rest is doing it the same way every time.