Client onboarding automation with Make: what to automate after the client says yes, and what to keep personal (free blueprints)
Short answer
Automate the parts of onboarding that must happen every time and are easy to forget: a kickoff email that says what happens next, a first task with a due date, and an alert to whoever owns the client. Keep the kickoff call and the plan personal. Two free Make blueprints start onboarding from a quote marked "won" in Google Sheets or from a form webhook, for about 87 credits a month at the calculator's defaults (checked 2026-10-18).
What to automate when a client says yes: the kickoff email, the first task and the alert, from a quote sheet or a form. Two free Make blueprints.
Disclosure: links marked "paid link" pay us a commission from the vendor if you sign up. Your price is unchanged, and every file here works without them. How we choose tools →
The moment a client says yes is the moment a small business is busiest: the work has to be scheduled, the next quote is waiting, and the person who sold the job is already on another call. The client, meanwhile, has just committed money and hears nothing. Onboarding automation is not about replacing the welcome. It is about making sure the first reply never depends on someone having a free afternoon.
This guide covers what is worth automating in onboarding a client to a service business, what is not, the two ways an onboarding scenario can start, and what it costs on Make.
What to automate, and what to keep personal
| Step | Automate it? | Why |
|---|---|---|
| Thank-you and "what happens next" email | Yes | It must go out every time, within a day, and the wording rarely changes |
| A first task with a due date (the kickoff call) | Yes | It puts the next step on a list with a date, instead of in someone's head |
| An alert to the person who owns the client | Yes | The yes often arrives in someone else's inbox |
| Requests for access, files and logins | Partly | A checklist row can open by itself; someone still chases the answers |
| The kickoff call and the project plan | No | This is where the client decides they chose right; it needs a person |
The test is the same one we use for what to automate first: does it happen every time, are the steps the same, and does missing it cost a client? The first email and the first task pass all three. The call and the plan fail the second, because every client is different.
What to automate first for a client, and whyFour tests, the first six automations compared, and 27 free blueprints by problem
Two ways in: a quote marked "won", or a form
Onboarding has to start from something the business already does when a client says yes. In most small service businesses that is one of two things.
1. The quote sheet: someone types "won"
If quotes live in a Google Sheet, the status column is already the record of the decision. The kickoff blueprint searches that sheet every morning for rows marked "won", sends each client a short email with the next three steps, adds a "kickoff call" task due in two days to the onboarding list, moves the quote to "won - kicked off" so it never repeats, and sends you a Telegram message.
Quote marked "won" → kickoff email → onboarding task → alert
Mark a quote "won" in the sheet: the client gets an email saying what happens next, a kickoff task opens in the onboarding list, and you get an alert.
Get all 27 blueprints in one ZIP, by email
It reads the same five columns as the two quote follow-up blueprints (client, email, amount, sent_date, status), so one sheet carries a quote from "sent" to "followed up" to "won - kicked off".
Quoted, and no reply? When to follow up and what to writeA day-3 follow-up and a day-10 last email on the same quotes sheet
2. A form or another app sends a webhook
If the yes arrives through a signup form, a booking or a CRM, send it to a Make webhook. The welcome blueprint receives the name and email, sends the welcome email, opens a row in the same onboarding list and alerts the team, within seconds and only when a client actually signs.
New client → welcome email → onboarding checklist → alert
A client signs and hears nothing until someone is free. On signing, they get an email saying what comes next, a checklist opens and the team is alerted.
Set it up
- Copy both sheet templates from the kickoff page: the quotes sheet (A–E) and the onboarding list (date, name, email, task, due, status).
- Import the kickoff blueprint into Make. Connect Google Sheets, Gmail and Telegram, and point the search and the status update at the quotes sheet and the new row at the onboarding list.
- Rewrite the email in your own words: what happens next, by when, and who they will hear from. Put your name in the signature.
- Test with a quote row of your own address and the status "won". Run once and check the email, the new onboarding row, the status "won - kicked off" and the Telegram message.
- Run once more. Nothing should be sent, because the status has moved on.
- Schedule it for every morning and switch it on. If a form is the way in, import the welcome blueprint as well and send the form to its webhook.
What it costs
The kickoff scenario runs a search each morning, 31 credits in the longest month, plus 4 for each quote it kicks off: about 47 credits at 4 won quotes a month. The webhook welcome uses 4 credits per new client, about 40 at 10 clients. Together that is roughly 87 credits a month, inside Make's Free plan of 1,000 credits (checked 2026-10-18). Each is one active scenario, and the Free plan allows two (make.com/pricing, checked 2026-10-12); a business that already runs a lead alert and a quote follow-up needs a paid plan for a third.
Check what your scenarios cost togetherPick the onboarding automations and the ones you already run, see the credits and the plan
Both onboarding scenarios run on Make's free plan at small-business volume; this is our link: Sign up (one month of Core free) → paid link · we earn a commissionPaid link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.
What does not work
- A typed status is only as good as the typing. "Won", "won " and "WON" do not match "won". Use a dropdown in the status column.
- Once a day is not instant. A quote marked "won" in the afternoon gets its email the next morning. An hourly schedule fixes that for about 744 searches a month instead of 31.
- The automation opens one task. A checklist with owners and dates for access, files and invoices is still yours to build, and someone has to close it.
- An automatic email that sounds automatic. Write it as you would to one client; name the person they will hear from.
- Contracts and deposits. These blueprints do not send a contract for signature or an invoice. Add that step only when the tool you use for it can be called from Make.
What should a client onboarding email include?
A thank-you, the next three steps with dates, who the client will hear from, and an invitation to reply with anything you should know. Keep it short; the kickoff call does the rest.
Can I automate client onboarding with Google Sheets?
Yes. Keep quotes and the onboarding list in Google Sheets, and let a daily Make scenario pick quotes marked "won", send the kickoff email, add the first task and update the status.
Should onboarding start from the quote or from a form?
From wherever the yes is recorded first. If someone updates a quote sheet, start there; if clients sign up through a form or a booking page, send that to a webhook.
Does this work on Make's free plan?
At small-business volume, yes: about 87 credits a month for both onboarding scenarios at the calculator's defaults, inside the Free plan's 1,000 credits (checked 2026-10-18). The limit you meet first is two active scenarios.
What should not be automated in onboarding?
The kickoff call, the project plan and anything that depends on judgment about this client. Automate the reminders and the first message so the personal parts happen on time.
- Make — Pricing (Free: 1,000 credits a month, checked 2026-10-18; 2 active scenarios, checked 2026-10-12)
- Make Help Center — Schedule a scenario (daily, weekly, monthly; minimum interval depends on the plan; checked 2026-10-18)
- Make Apps Documentation — Google Sheets modules (Search Rows filters; Update a Row needs the row number; checked 2026-10-18)
- Gmail Help — Gmail sending limits (checked 2026-10-18)
- Make Help Center — Webhooks
Related guides
Next step
All automations →
BOOKING LOGBooking form → meetings sheet → confirmation email. Feeds the no-show reminder
A booking arrives and nobody confirms it. A Tally form writes the meeting to the sheet, emails the client a confirmation and pings you on Telegram.
ONE QUESTIONFeedback score → the same thank-you and review link for everyone; a low score also alerts you
Unhappy clients stay silent until the review. A one-question Tally form (0–10) sends everyone the same review link; a 6 or lower also pings Telegram.
QUOTE FOLLOW-UPQuote unanswered for 3 days → one follow-up, automatic
Every quote sent and unanswered within three days gets one short follow-up email, and the consultant gets an alert. Nothing to remember, nobody to chase.
Get one new Make automation each week
Get the full 27-blueprint pack (ZIP) by email, then one new automation a week. Every build on the site stays open and free without it.