Confirm the deal and the date
Before anything else, write down what was sold and the date you promised to go live. Every step after this one hangs off that date. If nobody can name the go-live date, onboarding has not started yet.
Owner: You
Guide
Onboarding goes wrong in the same places every time: nobody owns it, the client is asked for things one at a time, and the go-live date moves because a small item sat unanswered for a week. Here is the process we see working, and a checklist you can copy.
Before anything else, write down what was sold and the date you promised to go live. Every step after this one hangs off that date. If nobody can name the go-live date, onboarding has not started yet.
Owner: You
One short message: who on your team does what, the kickoff date, the go-live date, and the two or three things you will need from them. Short enough that your contact can forward it internally without rewriting it.
Owner: You
Logins, brand files, contacts, billing details, approvals. Put every request in one list, each with a name next to it and a date it is due. Do not drip-feed requests over three weeks of email; that is what makes onboarding feel slow.
Owner: Shared
Thirty minutes. Walk the plan, confirm owners and dates, agree how you will communicate, and answer questions. End it by pointing everyone at the same list so there is one source of truth afterwards.
Owner: Shared
Your internal tasks stay yours, but the client should be able to see progress without asking. A visible list beats a weekly status email, and it stops the 'where are we?' thread before it starts.
Owner: You
Most onboardings stall on something small the client forgot. Decide up front how often overdue items get a nudge, and make the nudge automatic so it does not depend on someone remembering.
Owner: You
Confirm everything on the list is done, launch, and hand the account to whoever owns it day to day. A short recap of what was delivered and who to contact next closes the loop.
Owner: Shared
Onboarding lives in email. Requests get buried, nobody can tell what is still open, and the answer to "where are we?" takes someone twenty minutes to work out.
The client is asked to learn your software. Accounts, passwords and seat licences kill participation. Whatever you use, the client side should be one link.
Tracking every tiny task. You are managing a launch date, not timesheets. Track the milestones that move the date and leave the rest to your team.
Chasing by memory. If a reminder depends on a person remembering to send it, it will be late. Put it on a schedule.
It is the repeatable set of steps between signing a client and delivering what you sold: confirming scope and the go-live date, collecting what you need from them, doing the setup, and handing over. A good process is written down once and reused on every account.
It depends on the work, but the part you control is waiting time. Most delays come from requests sitting unanswered. Asking for everything in one list with dates, then chasing overdue items automatically, is usually what cuts the calendar time in half.
A go-live date, an owner on each side, the welcome note, the full list of what you need from the client with due dates, the kickoff call, a shared view of progress, scheduled reminders, and a handover at the end.
One named person on your side, even if several people do the work. Shared ownership is how dates slip. The client should also name one person who can answer questions and chase their own team.
Describe the rollout once. You get the steps, owners and dates on one board, a single link for your client with no login, and reminders that send themselves.