The Onboarding Sequence Nobody Follows

Ask three people in your business to describe how a new client gets set up and you will get three answers. All of them roughly right, none of them the same.

Onboarding is the process most likely to exist only as habit, and habit varies with who is busy that week.

Why inconsistency here is expensive

The first two weeks set what a client expects for the rest of the relationship. Somebody who is chased for information, told different things by different people, or left waiting for access has already decided what kind of company you are.

It is also the moment you are least likely to notice a problem, because everybody is busy starting the work rather than watching the experience.

What actually has to happen

The list is longer than most businesses realise once it is written down. Contract executed and filed. Payment terms set up. Folder structure created. Access granted to the right systems. Internal team briefed. Kickoff scheduled. Information collected from the client. Expectations set about what happens next and when.

Eight or nine steps, none difficult, all of them currently done from memory. Which is why one gets missed on roughly every third client.

Write it down before automating it

The documentation is worth more than the automation, and it takes an afternoon.

Write the sequence, then ask two people who do it whether that is what they actually do. The gaps between those answers are your inconsistency, and half of them are steps somebody added for a reason nobody now remembers.

Where AI runs it

Once the sequence exists, a signed contract triggers all of it without anybody remembering anything.

Folders created, tasks assigned to the right people, welcome sequence sent, kickoff proposed against real calendars, and the information request issued to the client with reminders that continue until it is complete.

AI does the parts that used to need a person to interpret. Reading the contract to pull out the terms that determine what happens next. Deciding which variant of the process applies to this client. Drafting the internal brief from what was agreed during the sale, so the delivery team starts informed rather than asking the salesperson.

That last one closes the most common gap in professional services, where everything the client explained during the sale has to be explained again to whoever delivers.

What to measure

• Days from signature to work starting. The headline.

• Steps completed against the defined sequence, sampled across recent clients.

• Client questions in the first two weeks. Volume here means expectations were not set.

• Days to collect the information you need to begin. Usually the longest stage and the one nobody owns.

The information request is the real bottleneck

Of the eight or nine steps, one reliably takes longer than the other eight combined: getting what you need from the client.

It looks like admin and it behaves like a wall. Work cannot start, the delivery team is idle or overloaded elsewhere, and the client does not perceive any urgency because from their side nothing has begun.

The failure is almost always in how the request was made. A paragraph in an email listing six things, with no indication of which are hard, no way to complete it in parts, and no visibility of what remains once they have sent some of it. Faced with that at the end of their own working day, most people send the easy items and intend to return to the rest.

Break it into individual items with a visible count remaining, make each one completable from a phone, and let reminders continue on their own. That single change tends to halve the elapsed time before anything else is touched.

Handling clients who go quiet

Some proportion of new clients disappear during onboarding. They signed, they were enthusiastic, and then nothing.

Usually it is not second thoughts. The person who signed has handed it to somebody who was not in the conversation, or an internal priority moved, or your request arrived during a bad fortnight. Silence gets read as a problem when it is almost always circumstance.

The response that works is persistent and low pressure. A short reminder on a schedule, escalating in channel rather than in tone, and after a defined period a direct message from a person asking whether the timing has changed. That last one recovers a surprising number and costs one minute.

What does not work is waiting for them to come back. A client who goes quiet in week one and is contacted in week four has already formed a view about how attentive you are.

Variants without chaos

The objection to a defined sequence is that clients differ. They do, and that is an argument for two or three named variants rather than for improvising every time.

Most businesses genuinely have a small number of shapes. A retainer starts differently from a project. A referred client needs less reassurance than one who arrived cold. An enterprise client has procurement steps a small one does not.

Name those variants, write each one down, and let the system pick based on what was sold. Everything outside them is an exception handled by a person, which is the correct use of a person.

What it should look like after ninety days

Three tests, run on the last five clients.

Could somebody who was not involved say exactly which steps ran and when, without asking anyone? Did every client receive the same set of things, allowing for variant? And did anybody on your team spend time chasing information rather than starting work?

If all three are clean, onboarding has stopped being a source of quiet damage. Most businesses find at least one of them uncomfortable the first time they look.

AI Optimize turns a signed contract into the whole sequence, running the same way every time. That work sits under Workflow Automation.