How much to charge for a client onboarding automation
How much to charge for a client onboarding automation comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is the value of the admin time every new customer costs the business today, times how many new customers they sign a year, plus any tool or assistant time the automation replaces. Your quote sits between the two. The job is usually what happens after a customer says yes: a welcome message, an intake form, records created in the CRM and the billing tool, a project folder, a kickoff booking and tasks assigned to the team.
I am not giving you a market dollar figure. A form that sends one welcome email and a system that onboards customers across five tools with branching steps by service type are different jobs. One number would be noise. Your rate and the client's numbers will get you a real one.
Claude Code writes the forms, the connections and the message sequence quickly. That speed is exactly why hourly billing undersells you. The slow part is getting the owner to write down what actually happens when a customer signs, because in most small businesses it lives in one person's head.
Calculate your floor and ceiling
Run this before you name a price. Every input is yours or the client's, so you can show the working in the proposal.
The client onboarding automation calculation
| Number | How to get it | Who supplies it |
|---|---|---|
| Floor | Your estimated hours for each line in the quote, plus a buffer you choose for edge cases and revisions, times your hourly rate | You |
| Time value per year | Admin hours per new customer, times new customers per year, times what an hour of that person costs | Client |
| Spend replaced | What they pay per year for an onboarding tool or for assistant time the automation takes over, if any | Client |
| Cost of a bad start | Only if they can point to real examples: a customer who asked for a refund or left after a missed step or a slow start | Client's own history, your judgment |
| Ceiling | Time value plus spend replaced, plus the bad-start line only if it is documented | Calculated |
If the floor is above the ceiling, the automation will not pay for itself. Say so and offer a smaller version, such as one intake form that creates the CRM record and sends the welcome message. If the ceiling is far above the floor, you have room to price on value. How far you move toward it depends on how solid their numbers are.
Find out what is at stake before you quote
Ask five questions on the first call: what happens, step by step, the day a customer signs, who does each step and how long it takes, how many new customers you sign in a month, which step gets forgotten most, and what customers ask in their first week that you answer again and again. Then ask them to walk you through the last customer they onboarded, in the actual tools. If the owner and the assistant describe different steps, you just found the real job.
Three kinds of onboarding clients and what to price against
| Client | What they need | Price against |
|---|---|---|
| Service business with a few customers a month | A signed customer gets a welcome, an intake form and a kickoff booking without the owner touching it | The owner's hours per new customer and the starts that slip when they are busy |
| Agency or consultancy | Each new client gets a folder, a shared channel, access requests, a project in the task tool and an invoice | Hours per new client across the team, plus any onboarding tool they pay for |
| Clinic, studio or membership business | New members or patients complete forms, agreements and payment details before the first visit | Front-desk hours per new customer and first visits lost to missing paperwork |
If they cannot tell you the steps or the hours, sell a paid discovery first and quote the build after. Paid discovery for AI projects covers how, and client discovery questions before you quote has more questions.
The CCC Onboarding Quote
Six parts of a client onboarding automation quote
| Part | What it prices | Question to ask the client |
|---|---|---|
| Process map | A written, step-by-step map of what happens when a customer signs, with branches by service type, signed off by the owner | If you were away for a month, what would your team need to know to onboard someone? |
| Intake | The form or forms that collect each detail once, with validation and file uploads, in a tool the client owns | Which details do you ask every customer for more than once today? |
| Connections | Creating the records, folders, projects, invoices and calendar bookings in each system | Which tools does a new customer need to exist in by the end of day one? |
| Messages | The welcome message and first-week sequence, in the owner's wording, sent in the right order | What do new customers always ask in their first week? |
| Checks and alerts | Checks that confirm each step ran and tell a named person when one fails or a customer stalls | Who should hear about it if a new customer has not finished intake after three days? |
| Handover and tuning window | A walkthrough, notes, and adjustments after the first few real customers go through | Who will own the process map once it is live? |
The process map is your anchor line. An automation built on a guessed process sends the wrong customer the wrong form, and the owner turns it off. Quote the map as its own line and explain that it is the difference between an automation that runs the business's real process and one that runs the process someone half remembered.
Checks and alerts is the line clients try to cut, and the one you should defend hardest. Onboarding fails quietly: a booking link breaks or a record is never created, and nobody notices until the customer complains. Build it so a failed step tells a named person the same day.
Agree who owns the accounts, the data and the wording
Put ownership in the proposal. The form tool, the CRM, the automation platform, the API keys and any hosting stay in the client's name, and they pay for those directly. Intake forms collect personal details, sometimes payment or health details, so the client decides what to collect and how long to keep it, and you build to that decision. You get access that ends on an agreed date. If the automation runs on your accounts and the client leaves, their new customers stop getting onboarded.
Then put responsibility in writing. The owner signs off the process map and the wording of every message. If they later add a service or change the steps, that is a change request, not a bug. Finally, define done: which service types are covered, which tools are connected, which messages go out and when, and which test customers went through end to end.
Always quote the tuning window
An onboarding automation meets reality with the first real customers. Someone skips a form field, a customer signs two services at once, a tool changes its connection, or the owner rewrites the welcome message after reading it in a real inbox. If you have not quoted for that, you fix it for free while the owner decides automation does not work for them.
Put a fixed tuning window in the first proposal, next to the build price. Say what it covers: fixing steps that break, adjusting the order and timing of messages, and reviewing the first few real customers with the owner. Say what it does not cover: new service types, new tools and new sequences. For ongoing work, offer a retainer. How to price a maintenance retainer covers the structure.
How to present the client onboarding automation quote
- Lead with the outcome in the owner's words. One line on what is at stake, such as every new customer booked into a kickoff with their details collected before anyone on the team opens their inbox, then the price.
- Offer three options. A starter with one service type, the intake form and the welcome message, a standard that adds the connections and failure alerts, and a full version with branches by service type, the first-week sequence and a longer tuning window. Make the middle one the clear best value.
- Show your calculation. Put their own hours, customer volume and tool spend in the proposal, and label any bad-start line as their example, not your forecast.
- Itemize it. Process map, intake, connections, messages, checks and alerts, then handover and the tuning window as their own lines. That gives the client a line to trim instead of a reason to say no.
- Take a deposit and tie the rest to milestones, with a test customer completing the whole flow as one of them. How much deposit to charge and how to structure milestone payments cover the schedule.
Skip hourly on the invoice, even though hours set your floor. Why I stopped charging hourly for AI builds explains why. If the client already runs n8n, see how much to charge for an n8n workflow. If onboarding is one piece of a wider automation job, see how much to charge for an AI automation.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a client onboarding automation?
Work out a floor from your estimated hours times your rate, and a ceiling from the admin hours it saves per new customer, times new customers per year, plus any tool or assistant time it replaces. Quote between the two and itemize each part.
Should I charge per new customer or a fixed price?
Charge a fixed price for the build, then a monthly retainer if the client wants ongoing changes and monitoring. Per-customer pricing ties your income to their sales, which you do not control.
What is included in a client onboarding automation?
Usually a mapped process, an intake form, records created in the client's tools, a welcome and first-week message sequence, checks that alert someone when a step fails, and a handover with a tuning window.
Who should own the accounts and data for an onboarding automation?
The client. The form tool, CRM, automation platform and API keys stay in their name, they decide what customer data to collect and keep, and your access ends on an agreed date.
Can Claude Code build a client onboarding automation?
Claude Code can write the forms, the connections between tools, the message sequence and the failure checks. You still own the process map, the owner's sign-off on wording, the data decisions and the testing with real customers.
Last reviewed by Duncan Rogoff on November 14, 2026


