Client onboarding automation: taking on a new client with no step forgotten

The contract is signed, enthusiasm is high, and then whole days go by in which nobody asks for access to the accounts, the shared folder does not exist and the new client does not know who to write to. The first weeks decide whether the relationship starts with trust or with apologies. A system that automates the onboarding of new clients turns the list in the account manager’s head into a sequence of steps that start on their own and are visible.

It suits agencies, accounting practices, consultancies and software firms: anywhere onboarding means the same small things, done by different people, in a particular order.

The checklist, seen by the whole team

Everything rests on a list. For each type of service we write down the onboarding steps: who is responsible for each one, how soon and what it depends on. Some steps are done by the system (it creates the folder), others by a colleague (who phones for the kick-off conversation), others by the client (who grants access to the advertising account).

The list becomes a screen: every new client has a row, every step has a status. The manager sees at a glance where an onboarding has stalled and who it is waiting on. A simplified version can be shown to the client as well.

From the kick-off form to the welcome message

Automated messages do not take the place of a person. The kick-off conversation remains a real meeting; automation makes sure everyone comes to it with the data, the documents and the access ready.

Picture a marketing agency with three types of package. Once the quote is accepted, things connect like this:

• The kick-off form: billing details, contact people, objectives, existing accounts. The answers go into the CRM, and the company’s details can be pulled in by its tax identification code (CUI) from the public service run by ANAF, Romania’s tax authority, so that they are not mistyped.
• The contract: it is filled in from the template with the form data and the chosen package, then goes out for electronic signature.
• The folders: the standard folder structure is created, with permissions for the team and a space shared with the client.
• Access: the client receives the access requests with step-by-step instructions; the system comes back with a reminder where any are missing.
• The tasks: the project appears in the task manager with every step, divided among people, with deadlines calculated from the signing date.
• The welcome: a message introducing the team, the communication channels, the first stages and the link to the checklist.

Client onboarding automation: the order in which we build

We begin by retracing, step by step, a few recent onboardings together with the people who handled them. What usually comes to light is steps that only one colleague knows about: the ones that get forgotten when that colleague is on holiday.

Then we build in order of risk: first the list and the tasks, then the form and the contract, and the integrations with external accounts last.

• The step map: who, what, when, with what input data.
• The templates: contract, messages, folder structure, template project in the task manager.
• The workflow: built and tested end to end with a fictitious client.
• Measurement: the time from signing to the first deliverable and the steps left open past their deadline.

Existing automation tools or custom code

Automation platforms such as Make, Zapier or n8n connect well-known applications without conventional programming: when something happens in one place, actions start in others. For an onboarding with linear steps and widely used applications they are the natural choice: they are quick to build, and a colleague who is not a programmer can change them.

Custom code is justified in other situations: rules with many branches, applications with no connector, high volumes at which the platform subscription becomes expensive, or data that must not pass through a third-party service. n8n can be installed on your own server, which solves part of that last problem.

Often the solution is mixed: the main workflow in a platform, and the delicate step (generating the contract, for example) in a small service written by us and called through an API, that is, the interface programs use to communicate with each other. We tell you openly when you do not need code.

What cannot be automated in onboarding

Access to the client’s accounts is granted by the client, from their own account. The system can send the request and check whether access has come through, but it cannot skip that consent. Passwords are not sent by email and are not stored in the form: we use delegated access or a password manager.

The kick-off form collects personal data and sometimes commercially sensitive information. We settle who sees it, where it is kept and what is deleted when the engagement ends; the data processing clauses are for you to check with your lawyer or your data protection officer.

The contract template has its limits too: a negotiation with special clauses leaves the workflow and goes to a person, and the system has to allow that without getting stuck.

This is a typical project description: it shows how we usually approach this kind of work and does not present a project carried out for a particular client. Every real project starts from your company’s situation, and the stages, timescales and price are agreed after the initial discussion.