How should you onboard a new customer?

Onboarding is the least designed part of most service businesses because it falls between two people's jobs — the person who won the work has moved on and the person delivering has not started. That gap is where a customer who has just committed money sits with nothing happening, and it is where the doubt that produces early cancellations and anxious phone calls forms.

The same-day written confirmation is the single most effective element and it is not administrative. It restates what was agreed, what it costs, what happens next and by when, which does three things at once: it catches misunderstandings while they are cheap, it demonstrates that the business is organised, and it gives the customer something to show anyone else who needs to know. Sent the same day, it also arrives while the decision still feels good.

Naming a person is the second element and it matters more in small businesses than large ones, because the customer chose you partly for access. A named contact with a direct route removes the uncertainty about who to ask, which is what produces the low-grade anxiety that makes new customers call to check on things. Where the contact will change — from sales to delivery — say so and introduce the second person rather than letting the customer discover the handover by writing to someone who no longer handles it.

Setting the next visible event is what closes the gap. Even where real work cannot start for a fortnight, something should be scheduled inside the first few days: a call, a site visit, a document to review, a form to complete. It provides a reason for contact and a marker of progress, and it converts a silent fortnight into a period with a known shape.

What to collect at this point should be limited to what is genuinely needed to begin, for the same reason a long enquiry form is a poor idea. Onboarding is frequently used as an opportunity to gather everything the business might eventually want, which front-loads friction onto a customer who has just paid. Collect what is needed to start, and ask for the rest when it becomes relevant.

One thing to say explicitly that most businesses leave implicit: what the customer needs to do, and by when. Delays in service work are frequently caused by the customer — access not arranged, information not supplied, a decision not made — and a customer who was never told what was required does not experience the resulting delay as their own. Stating it plainly at the outset is not a defensive move; it is the difference between a shared timeline and a supplier who appears to be slow.