Processes
Customer onboarding: how to standardize the start without making it rigid
The sale closed, the contract was signed and the customer is excited. The next two weeks define a good part of the relationship: whether they will feel they made a good deal or start to have doubts. In many companies, this period depends on who handled the account and on how busy that person was that day.
What onboarding is and why it tends to fail
Onboarding is everything that happens between the customer's "yes" and the moment they receive the first value from what they bought. It includes registration, contract, billing, access, gathering information, the first meeting and the handoff from sales to whoever will deliver.
It fails for three reasons that keep coming up:
- The handoff is informal. The salesperson knows everything that was agreed and tells operations in a message, when they remember. The customer ends up explaining everything again.
- Everyone does it differently. One sends the form before, another after, a third forgets the access. The customer notices the difference when comparing with the referral they received.
- The customer does not know what comes next. Silence after the signature is read as disorganization.
Standardizing is not making it rigid
The common fear is that a standard process makes service feel cold. The opposite happens when standardization is done well: it removes the work of remembering from people and leaves time for the part that needs a person.
The rule we use is to separate structure from content. The structure is the same for everyone: which steps exist, in what order, who is responsible, within what time. The content changes by customer: what was sold, the tone of the conversation, the particulars of their business.
The customer does not want improvised service. They want service that feels designed for them. That takes more process, not less.
The steps of an onboarding that works
The design changes from company to company, but these six steps appear in almost every service onboarding.
- Internal handoff. Sales records, in one place, what was sold, what was promised, who the contacts are and what the customer expects. Preferably in CRM fields, not in loose text.
- Welcome. On the day of signing, the customer receives a message saying who will look after them and what the next steps are, with dates.
- Formalization. Contract, registration and first charge. It is the most repetitive part and the first candidate to run on its own.
- Gathering information. A single form with everything operations needs. Asking little by little, by message, is what delays the start the most.
- Kickoff meeting. Alignment on goal, deadlines and way of working. Here the person makes the difference, and that is why the earlier steps were cleared out of the way.
- First delivery. A small, quick delivery that confirms the purchase decision.
For each step, define an owner, a deadline and the criterion for "done". It is the same format we describe in How to document a process people follow.
What to automate and what to leave to people
Onboarding has a lot of copying tasks: the same customer data goes into the contract, into finance, into the delivery system and into someone's spreadsheet. That kind of task is the natural candidate for automation.
It is usually worth automating:
- creating the customer record in the systems from the sale closed in the CRM;
- generating and sending the contract with the data already filled in;
- the first charge and the reminders, as we show in Payment reminder automation;
- sending the gathering form and the internal alert when it is answered;
- creating the tasks for each step for the owner, with a deadline.
It is usually worth leaving to a person:
- the kickoff meeting and any conversation about expectations;
- answers to questions that fall outside the standard;
- decisions about exceptions, such as a different deadline or a request outside the scope.
The logic is the same one that applies to AI agents in customer service: the machine handles the repetitive part and hands off to a person when the conversation calls for judgment.
How to measure whether it is working
Three metrics are enough to start:
- Time to first delivery: days between the signature and the first value the customer perceives.
- Stalled onboardings: how many customers have been in a step longer than planned, and in which one.
- Customer pending items: how many are waiting on something that depends on them, such as a document or an answer.
The third one tends to be a surprise. Much of the delay the company blames on itself is actually waiting for information from the customer, and is solved with a better form and an automatic reminder. More on choosing numbers in Process metrics.
An example to picture it
Imagine an accounting firm that takes on eight new customers a month. Today, each accountant asks for documents in their own way, by message, and the start of the work varies from three days to three weeks. With standardized onboarding, a closed sale triggers the contract, the charge and a single form. The accountant receives the task only when the documents have arrived, and the customer knows from day one the date of the kickoff meeting. The accountant's work did not change. What changed was everything around it.
Where to start
Take the last three customers who came on board and reconstruct, with the people involved, what happened in each one, day by day. The differences among the three show where the process depends on luck. Write the standard version on one page and run the next two customers through it before automating any step.
If you want to know how your operation stands on this and other processes, delpra™'s assessment takes 4 minutes and points out the priorities.
Written by the delpra™ teamProcesses, automation and AI so operations scale efficiently.