Client Onboarding Process: A Step-by-Step Workflow for Agencies and Service Firms
By Kirill Stolbushkin
Short answer: A client onboarding process is the set of steps that takes a new client from signed contract to the first piece of delivered work. For most agencies, consultancies, and B2B service teams it runs in seven steps: confirm what was sold, hand off from sales to delivery, welcome and intake, internal setup, kickoff, first delivery, and a check-in. The steps are rarely the problem. They live in five places, and nobody owns the whole thing.
Ask a team how they onboard clients and you usually hear the same story. A form for intake, a checklist in a doc, emails to chase missing logins, and a spreadsheet to see who is where. Every new client takes a round of manual coordination, and the more clients you sign, the more often something gets missed. This guide lays out a process you can run the same way every time.
What client onboarding covers
Client onboarding starts when the contract is signed and ends when the client is getting value and the work has settled into its normal rhythm, between sales before it and account management after it.
This guide is for agencies, consultancies, accounting practices, IT service providers, and SaaS teams that run an implementation for each customer. It is not about regulatory identity checks on new customers, or about onboarding employees.
Why client onboarding breaks
The same few problems show up again and again:
Context gets lost at the handoff. Sales promised a launch date or a weekly report. Delivery finds out in month two.
Information arrives in drips. The client sends the brand files, then the logins a week later, then names a different decision-maker.
The checklist lives in someone's head. When that person is busy, onboarding slows. When they leave, it breaks.
Every client gets the same list. Steps that do not apply get skipped by hand, and sometimes steps that do apply get skipped too.
The same details get typed again and again. Client names, contacts, and billing details get retyped into three or four tools, and each copy is a chance to get something wrong. Collect them once and reuse them everywhere.
Nobody can see where a client is stuck. Waiting on the client looks exactly like waiting on your own team.
The fix is structure: one owner, one list of steps, and one place to see status.
The client onboarding process, step by step
Step 1: Confirm what was sold
Before anyone says welcome, make sure the basics are settled: signed contract or statement of work, scope, start date, billing terms, and any deposit or first invoice. If work waits for a deposit, make the process wait too, instead of relying on memory.
Step 2: Hand off from sales to delivery
Write a short handoff note so delivery does not have to rediscover what sales already knows:
What the client bought, in plain words, and what is explicitly out of scope.
Why they bought it and how they will judge success.
Any promises made during the sale: dates, reports, people, extras.
The client contacts, and who the real decision-maker is.
Risks or red flags sales noticed.
Step 3: Welcome the client and collect what you need
Send the welcome within a day of signature, and make it do real work. One message, one link, one deadline, covering everything you need to start:
An intake questionnaire about goals, audience, constraints, and past attempts.
Access requests: accounts, tools, systems, and who on the client side grants them.
Files and assets.
The named decision-maker and who signs off on deliverables.
Preferred communication channel and meeting times.
Step 4: Set up internally
While the client works on intake, set up your side: assign the team, create the project and its budget, prepare tools and folders, and draft the kickoff agenda. This runs in parallel with step 3, which is one of the easiest ways to shorten onboarding.
Step 5: Run the kickoff
The kickoff is where expectations get written down. Cover goals and success measures, scope boundaries, the timeline and first milestone, roles on both sides, how feedback and sign-off on deliverables will work, and the meeting and reporting cadence. End with a written recap and next actions with owners.
Step 6: Deliver something early
Pick a first deliverable the client can see within the first couple of weeks: a plan, an audit, a first draft, a configured workspace.
Step 7: Check in and close onboarding
Schedule a check-in a few weeks after kickoff. Ask what is working and what is unclear. Then close onboarding on purpose. Decide in advance what "onboarded" means, such as access complete, kickoff recap sent, and first deliverable accepted. Then the client moves to normal account management.
Fixed steps and conditional steps
The fastest way to stop missing steps is to separate the ones every client gets from the ones that depend on the engagement.
Fixed steps happen for everyone: contract confirmed, handoff note, welcome and intake, kickoff, first deliverable, check-in.
Conditional steps depend on the service or the client:
Paid media work needs ad account and billing access.
Website work needs domain, hosting, and analytics access.
A data or system migration needs an export from the old system and a test import.
An enterprise client may send a security questionnaire or a vendor form.
Write the conditions down as rules, such as "if the engagement includes paid media, request ad account access." The process picks them, so nobody has to remember.
Who owns client onboarding
Give onboarding one named owner per client, usually the account lead, project manager, or customer success manager. They do not do every step, but they own the flow and the status. Around them:
Sales: writes the handoff note and joins the handoff call.
Delivery lead: sets up the team and runs the kickoff.
Finance: confirms billing and the deposit.
Client decision-maker: completes intake, grants access, and signs off deliverables.
When a new client signs, notify the named owner directly, not a shared channel. A post in a channel means everyone assumes someone else picked it up. And end each stage with someone confirming it is done, so status is a fact rather than a guess.
If roles are fuzzy today, our guide to process ownership and RACI helps you settle them before the next client signs.
How it looks in different service businesses
Agencies: heavy on access and assets, such as brand files, ad accounts, and CMS logins. Conditional steps matter most here.
Consultancies and professional services: heavy on scope and stakeholders. Kickoff often includes discovery interviews. If you map client processes as part of the work, see process mapping for consultants.
B2B SaaS with implementation: heavy on data and configuration: admin setup, data import, training, and a first success milestone before handover to customer success.
How the client onboarding process maps to a flow chart
Client onboarding fits BPMN well because it has parallel work, waiting, and rules. The BPMN symbols cheat sheet explains each shape.
Message start event: the contract is signed.
Lanes: sales, account lead, delivery, finance, and the client, drawn as swimlanes so every handoff is visible.
Parallel gateway: client intake and internal setup run at the same time, and the kickoff waits for both.
Inclusive gateway: adds the conditional steps that apply to this engagement, such as ad access or a data migration.
Timer boundary events: a reminder to the client if intake misses its deadline, then an alert to the account lead.
End event: the client is onboarded, using your definition.
A checklist tells you what to do. A process model also shows the order, the owners, and what happens when something is late. We compare the two approaches in Vevos vs Process Street.
How to model and automate this in Vevos
Describe your onboarding the way you would brief a new account manager, and Vevos generates a BPMN 2.0 model with lanes, gateways, and timers, plus written process documentation you can share with the team. For example:
"When a contract is signed, sales writes a handoff note and the account lead sends the welcome with the intake form. While the client completes intake, the delivery lead sets up the project. If the engagement includes paid media, we also request ad account access. If intake is not done in five days, the client gets a reminder. When intake and setup are both done, we hold the kickoff, then deliver the first draft within two weeks and book a check-in."
Review the model with the people who run onboarding, fix what does not match, and save each change as a new version. Our guide to describing a process in plain English has tips for writing that first description.
Try it with the free AI process mapper, no account needed. You can start free on the Intro plan, with $9 and $29 plans for more models and room. When you want a working onboarding app, for example with an intake form, task tracking, and a status view, Conductor Agents, the Vevos agents that build apps from a model, can build and deploy one from your reviewed model, starting on Tempo at $199/month. See the pricing page.
A short client onboarding checklist
Contract, scope, start date, and billing confirmed.
Handoff note written and handoff call held.
Welcome sent with intake, access requests, and a deadline.
Conditional steps for this engagement added.
Team assigned and project set up.
Kickoff held and recap sent.
First deliverable shipped.
Check-in done and client marked as onboarded.
FAQ
What are the steps in a client onboarding process?
Confirm what was sold, hand off from sales to delivery, welcome the client and collect intake and access, set up internally, run the kickoff, deliver something early, and check in before closing onboarding. Intake and internal setup can run at the same time.
How long should client onboarding take?
It depends on the service and how quickly the client provides access and information. Define what "onboarded" means for you and track how long it takes to get there. Waiting on the client is usually the biggest delay, so one intake request with a deadline helps most.
What should a client onboarding checklist include?
Everything in the checklist above, plus conditional items for steps that only apply to certain services.
Who should own client onboarding?
One named person per client, usually the account lead, project manager, or customer success manager. Others do parts of the work, but one person owns the status and the next step.
How do you keep onboarding from becoming manual coordination as you sign more clients?
Send one intake request instead of many, write rules for the conditional steps, track status in a way that separates waiting on the client from waiting on your team, and give every client one owner.
Do I need a client portal or onboarding software?
Not necessarily. Map the process first: the steps, the owners, the conditions, and what "onboarded" means. Then pick a tool that fits that process, whether it is a portal, a project tool, or something you build. A tool chosen first tends to reshape your process around its features.
Related blog posts
- Work Order Process: From Maintenance Request to Close-Out, Step by Step — The work order process for facilities, property management, and field service teams: eight steps from maintenance request to close-out, how to set priorities and cost approvals, the exceptions that stall jobs, and how to draw it as a flowchart.
- Purchase Requisition Approval Process: Thresholds, Approval Chains, and Workflow — A practical guide to the purchase requisition approval process: the steps from request to approved requisition, how to set spend thresholds and approval chains, which duties to keep apart, and how to handle urgent and over-budget requests.
- Customer Support Escalation Process: How to Build a Ticket Escalation Workflow — How to design a customer support escalation process: support tiers, severity levels, clear triggers, handoffs that carry context, an escalation matrix, and how it all maps to a ticket escalation workflow.