How We Automated Our Client Onboarding
Eight to ten hours. That is what it cost us, in staff time, every time a new client signed.
Not in one place. Spread across four people, three tools, and a week of back-and-forth. Each individual step looked manageable. The total was not.
We fixed it. Here is exactly what we changed — and the thing we almost got wrong before we touched a single tool.
What the Old Process Looked Like
When a client signed with us, the work started immediately. And all of it was manual.
Someone drafted the welcome email. Someone else created the client folder in Google Drive — usually from memory, occasionally missing a subfolder. The contract went out through one platform. The CRM record was created in another. The invoicing profile was set up in a third. None of these systems talked to each other.
Scheduling the kickoff call alone took three or four email exchanges. The internal team briefing happened in a Slack message that sometimes got missed. By the time the client was fully set up and the kickoff call was confirmed, we had touched the process across four people over the course of several days.
The total time was 8–10 hours per new client. At ten new clients a month, that is a full working week of admin. Every month.
Why We Did Not Just Automate It Immediately
The temptation was to automate the process as it existed. Connect the tools, build the triggers, move on.
We did not do that. Before touching any automation tool, we mapped every step on paper and asked one question about each: does this step need to exist in its current form?
Two steps did not survive that question.
The first was our internal team briefing. It existed as a Slack message because we had always done it that way. When we looked at what information it contained, we realised it was duplicating what was already in the CRM record — which nobody was reading before the briefing. We removed the briefing step entirely and fixed the CRM template so it contained everything the team needed.
The second was a document request we sent to every new client asking for information we had already collected during the sales process. It existed because the sales handoff to delivery had never been properly designed. We fixed the handoff. The document request disappeared.
That is two steps removed before a single line of automation was written. If we had automated the old process, we would have automated both of those steps too — and made them faster and more reliable. That would have been the wrong outcome.
What the New Process Looks Like
A client signs the contract. That single event now triggers everything.
Within two minutes:
- The client folder is created automatically using a consistent template
- The CRM record is populated with all details from the sales process
- A personalised welcome email sequence is queued and sent
- The invoicing profile is created in the accounting system
- A kickoff call invitation is sent with a scheduling link
- The project workspace is set up from a standard template
Our account manager receives one notification. Everything is already done. The first human interaction with the new client is the kickoff call itself.
Total admin time: under 30 minutes, most of which is the account manager reviewing the setup before the call.
The Tools We Used
We use Make.com to orchestrate the sequence. The trigger is a webhook fired when a contract is marked as signed. From there, Make.com handles the calls to each system in order.
We chose this approach because it sits outside any single platform. If we replace our CRM or switch project management tools, the orchestration layer stays intact and we update one connection — not the entire process.
The tool choice followed the process design. Not the other way around.
What We Got Back
The obvious return was time. Eight to ten hours per client, recovered permanently.
The less obvious return was consistency. Every client now gets the same onboarding experience regardless of who is handling the account, what else is happening that week, or whether someone is on leave. The folder structure is always the same. The welcome email goes out within minutes of signing. The kickoff invite arrives before the client has finished reading the contract.
For a business where the first impression shapes the entire relationship, that consistency has value that is hard to put on a spreadsheet but easy to feel in client feedback.
Three Questions to Audit Your Own Onboarding
Before you open any automation tool, do this first.
Map every step in your current onboarding process. Then ask:
- Does this step exist because it adds value, or because it has always existed? Steps that survive only on habit are candidates for removal, not automation.
- Is any information being collected twice? Duplicate data collection almost always means a handoff was never properly designed.
- Which step causes the most delays when the responsible person is unavailable? That is your highest-priority automation candidate.
Fix what should not exist. Then automate what remains.
Curious whether your onboarding process is automation-ready? [Book a free 30-minute discovery call → kriyaflowai.com/discovery]