Writing9 min read
I automated client onboarding end to end
Eleven manual steps across six tools, reduced to one approval click. The full map, the parts that broke, and what I would not automate again.
- Automate
- Build

Client onboarding is the most automatable process in a service business, and almost nobody automates it. Not because it is hard — because it is scattered. The contract is in one tool, the invoice in another, the folder in a third, the project board in a fourth, the kickoff in a calendar and the welcome email in an inbox. No single tool owns it, so no single tool fixes it, so it stays manual forever.
I built the whole chain as one automation. Here is the map, and the parts that broke.
The eleven steps
Written out, the manual version was:
- Mark the deal closed
- Generate the agreement from the quote
- Send it for signature
- Chase the signature
- Raise the first invoice
- Create the Drive folder structure
- Create the project board from a template
- Add the client to the shared channel
- Book the kickoff call
- Write and send the welcome email
- Tell the delivery team it exists
Eleven steps, roughly 40 minutes, spread across two days because nobody does all eleven in one sitting. Multiply by however many clients you sign a month.
What the automation does
A closed deal is the only trigger. From there: the agreement is generated from the accepted quote and sent for signature; countersignature raises the invoice; the folder structure and project board are created from a template that varies by which package was actually bought; the channel is created and the team added; the kickoff is booked against real availability; and the welcome sequence goes out referencing what the client purchased rather than a generic hello.
One human approval sits in the middle — reviewing the agreement before it sends. That is deliberate. It is the one step where being wrong is expensive and being slow is not.
Three things that broke
Templates that assumed one package. The first version created the same folder structure for everyone. Real clients buy different things, and a delivery lead opening a folder full of irrelevant empty subfolders stops trusting the system immediately. Template selection had to become a branch, not a constant.
The signature webhook. It fired on sent, not on completed, which meant invoices were raised for contracts nobody had signed yet. This is the class of bug that makes people distrust automation permanently, and it is why I now run everything in parallel with the manual process for a week before switching over.
Timezones on the kickoff booking. Of course it was timezones. It is always timezones.
What I would not automate
The welcome email got worse, not better. The automated version was correct, personalised and completely dead — it read like a system had written it, because one had. Now it drafts and a human spends ninety seconds editing it before it sends.
That is the general rule I keep relearning: automate the assembly, keep the judgement. The moment the automation starts producing something a client reads and reacts to, put a person back in the loop.
The result
Forty minutes down to about four, and more importantly the two-day spread is gone. Everything happens within an hour of the deal closing, which is the part clients actually notice.