How to Onboard a New Client: Process and Checklist

To onboard a new client you turn the signature into a record the same day, ask once for everything you need to start (contacts, access, materials, billing details), hold a short kick-off that fixes scope, dates and who speaks to whom, then deliver one small visible piece of work within the first two weeks. Everything the client has to read lives in one place instead of a thread of forwarded emails. Run this way, the gap between "yes" and the first real delivery tends to be days rather than the three or four weeks it stretches to while everybody waits for a file nobody asked for clearly.

If the weeks after a signature currently feel like a slow exchange of messages asking for the same things twice, by the end of this guide you will have a fixed sequence, a reusable checklist and a first delivery planned before the kick-off ends. The subject is the client's journey from accepting to receiving something, not how you set up your own internal system.

What you need before you start

• The accepted quote or signed contract, with its date. It is the document every later question goes back to. If signatures still arrive as scanned paper, the faster route is in the guide on how to get a quote signed online.
• A client record that already exists, not one created in a hurry after the first invoice bounces back. Moving a whole book across at once is a different job, covered in how to import a customer list into a CRM.
• One named owner. Not "the account team". A person, written down, who the client can name after the kick-off.
• A reusable checklist, the same for everyone, saved somewhere you can duplicate it. Onboarding invented fresh each time is how a step gets skipped.
• A single place for documents and updates, so nobody hunts through an inbox for something you sent three weeks ago.
• The name of whoever approves things on the client side. Often it is not the person who signed, and finding that out in week three costs a revision round.

Agree what you collect and from whom before the first email goes out.

What you collect	Who usually has it	When you need it
Billing details, order reference, invoicing address	the administration contact	before the first invoice
Logins, accounts, physical access	technical contact or outgoing supplier	day one of the work
Brand files, price lists, photos, existing material	the operational contact	before the first delivery
Who approves, and in how many days	the person who signed	at the kick-off
The contact for when something is urgent	the person who signed	at the kick-off

How to onboard a new client, step by step

1. Confirm acceptance the same day it arrives. A short reply saying what happens next, who the owner is and when the kick-off will be. It costs two minutes and closes the silence between signing and starting, which is when a client is most likely to wonder whether they chose well. They end the day knowing a name, a date and a next step.

2. Turn the accepted quote into a client record and a job. Carry over the amount, the agreed lines and the promised delivery date without retyping them: how that side is organised is on the page about projects and jobs. Nothing sold then sits outside the system while people are already spending hours on it.

3. Send one welcome message with one list of requests. Numbered, with everything you need and a date by which you need it. Three separate emails over a fortnight produce three partial answers. Say plainly what happens if something is missing, for example that the start slips by the same number of days. You get one thread the client can work through in a sitting.

4. Open the client's private area and put the documents in it. Contract, plan, contacts, the material they have sent: in one place both sides can reach, so "what did we agree" is answered by a link rather than by archaeology in an inbox. Flusia has a client portal for this, and the setup is in how to set up a client portal. The client now has somewhere to look before they have something to ask.

5. Run a kick-off of forty five minutes with a fixed agenda. Five points, always the same: what we deliver and what we do not, the dates, who talks to whom, how approvals work, how we handle things that come up. Write the answers down during the call. A page of decisions goes out within the hour and becomes the reference both sides use.

6. Put the first two weeks on a plan the client can see. Not the whole project, just two or three dated items, including what you need from them and when. They can then tell at a glance whether anything is waiting on their side.

7. Deliver something small within the first ten working days. A first draft, a configured account, a report on what you found, an inspection carried out. It cannot usually be the main deliverable. It has to be real and visible, so the client has seen you work before they see your first invoice.

8. Close onboarding explicitly. Say when it ends: "from Monday we move to the normal rhythm, a check-in every second Tuesday, requests through the portal". Onboarding that fades out without being declared over leaves both sides unsure whose turn it is.

The client onboarding checklist

The sequence above, condensed into something you copy for every new client. Tick it, date it, keep it on the client record.

1. Acceptance confirmed in writing, same day
2. Client record complete: legal name, billing details, contacts with roles
3. Job opened, with amount, scope and promised date carried over from the quote
4. Owner assigned and communicated to the client by name
5. Request list sent, with a deadline for the material
6. Access and credentials received, stored where more than one person can reach them
7. Private area opened, with contract, plan and contacts in it
8. Kick-off held, notes sent within the hour
9. Approval route agreed: who signs off, in how many days
10. First two weeks planned and visible to the client
11. First deliverable sent within ten working days
12. Invoicing schedule confirmed with the administration contact
13. Onboarding declared closed, with the date the normal rhythm starts

The reason to write them down is not bureaucracy: the step people skip is never the same one twice.

Onboarding for a one-off project

The engagement is short, so onboarding cannot take a fifth of it. Compress: the kick-off invitation and the request list go out in the same message, and the plan covers the whole project rather than two weeks. What matters most here is the approval route. On a six week project, two approvals of ten days each eat a third of the calendar and nobody planned for it. Agree at the kick-off how long an approval takes and who gives it, then put those dates in the plan with their own deadline.

The second thing to fix early is the edge of the scope. Mid-project requests are normal and often reasonable, but each one either becomes a visible line on the job or becomes a gift. Keeping sold lines and added ones apart from day one is what lets you have that conversation with a number in hand: the mechanics are in how to manage client jobs.

Onboarding for an ongoing service

For a monthly fee or a maintenance contract the purpose is different. You are not preparing one delivery, you are setting a rhythm that has to survive twelve months and at least one change of contact on their side.

Fix three things in the first fortnight. The cadence: which day the report arrives, how often you meet, how long a routine request takes to answer. The channel: one route for requests, so a message sent to a personal phone on a Saturday is not the one that gets lost. The boundary: what the fee covers and what is billed separately, stated while it is still neutral information rather than a dispute.

Then automate what repeats: the reminder for the monthly report, the task that opens on the first working day, the follow-up when material has not arrived after five days. Setting these once beats remembering them every month, and the patterns to start from are in the guide to automatic workflows.

Onboarding a client with several people involved

Above a certain size the client is not one person. Someone signed, someone will use the work, someone pays, and often someone was against hiring you. Treating the signatory as the whole company is how a project reaches month two with an unhappy stakeholder nobody has spoken to.

Map them at the kick-off, with one line each on what they care about, and ask "who else needs to see this before it counts as approved". A design agency taking on a rebrand, a maintenance firm covering four sites, an accountancy practice picking up a new company: in all three the signatory is rarely the person you speak to weekly. Then give each name a role, informed or consulted or decides, which is what tells you who to copy and who not to.

Alternative method: onboarding without a shared space

If you have no private area for clients yet, a reduced version can be running tomorrow. Two email templates, one with the numbered request list and one for the kick-off notes. A folder per client with the same four subfolders for everyone: contract, materials received, deliveries, notes. One shared file listing every client in onboarding with their stage and the date of the next step.

It costs nothing to start, and the limit is worth knowing first: material arrives as attachments across several threads, two people end up holding different versions of the same file, and the client cannot check anything without asking you.

Common mistakes

Asking for things as you need them. Four requests over three weeks, each blocking work, each sending the client off to find somebody internally. One consolidated list with a deadline is faster for both sides and makes a delay visible as a delay rather than as a mystery.

Leaving onboarding without an owner. When the salesperson has finished and the delivery team has not started, the days in between belong to nobody. The record needs a name on it from the day of acceptance, even if that name changes a week later.

Letting the client wait in silence. Two weeks of nothing after a signature is when a new client rereads the quote and starts wondering. Three lines saying "we are waiting on the access, everything else is ready" beat a polished deliverable ten days later.

How long it takes, and what comes next

Building the checklist and the two templates takes an afternoon, once. After that, onboarding one client costs roughly ninety minutes of your own time across two weeks: forty five for the kick-off, the rest for the request list, the notes and the record. The elapsed time is mostly not yours, it is how long the client takes to send what you asked for, which is why the request goes out on day one and not on day six.

After five or six clients, look at one figure: the days between acceptance and first delivery. Above three weeks, the bottleneck is almost always the material you are waiting for. The natural next step is the running phase, where work is tracked with its hours, costs and margin rather than just its deadlines: that side is in the guide to client jobs and work orders.

Frequently asked questions

How long should onboarding a new client take? For a project, acceptance to first delivery in about two weeks is a reasonable target for most service businesses. For an ongoing service, count the first full cycle, so roughly a month: the rhythm is only established once the first report or routine request has been through the whole loop.

What should you do straight after a client signs? Reply the same day with three things: who their point of contact is, when the kick-off will be, and what you need from them. Everything else can wait a day. Those three cannot: they are what turns a signature into a start.

Do you need software to onboard clients properly? No. A written checklist, two email templates and a tidy folder per client will carry a business taking on a few clients a month. A shared system starts to pay when several of your people answer the same client question, when material arrives as attachments nobody can find later, or when you are retyping the same amounts from quote to job.

Who should own onboarding, sales or delivery? Whoever is named on the record: the name matters more than the department. A common arrangement is that the person who sold stays visible through the kick-off and hands over explicitly during it, so the client sees the handover happen instead of discovering later that their contact has changed.