Client onboarding used to be the part of my business I dreaded most. Not because I didn't like new clients — I did — but because the first week always felt like scrambling. Intake forms to review. Welcome emails to write. Contracts to customize. Project folders to set up. Initial audits to run. By the time I actually got to strategy work, I'd already burned eight hours on logistics.
Over the past six months I've automated most of that with Claude Code. The entire onboarding process now takes about 90 minutes of my time instead of a full day. The client experience is better, the deliverables are more consistent, and I can take on more projects without hiring another person. Here's exactly how I built it.
What Client Onboarding Actually Involves
Before I automated anything, I mapped out every task that happened between "client signs the contract" and "we start actual work." For my consulting practice, that list looked like this:
- Send welcome email with next steps and timeline
- Process intake form responses and extract key details
- Create project folder structure in Google Drive
- Generate custom contract from template with client-specific terms
- Set up project management board with initial tasks
- Run preliminary audit (technical SEO, analytics setup, competitor scan)
- Draft initial strategy brief based on intake responses
- Schedule kickoff call and send calendar invite with agenda
Most of this is repeatable. The welcome email follows the same structure every time. The project folder always has the same subfolders. The contract template only changes in a few specific fields. The audit scripts can run without human input. The only parts that need real judgment are reviewing the intake responses and shaping the strategy brief.
That realization was the key: I didn't need to automate everything, just the 70% that followed a predictable pattern.
The Three Scripts I Built
I broke the automation into three main workflows, each handled by a separate Claude Code script.
1. Intake Processing and Welcome Sequence
When a new client fills out my intake form (I use Tally), the responses get saved to a Google Sheet. A webhook pings a Claude Code script that reads the latest row, extracts the key details, and generates a personalized welcome email.
The script looks for things like industry, main goal, timeline, and budget tier. It uses those variables to customize the email copy — a SaaS client gets different messaging than a local service business. The email includes a branded PDF welcome guide (generated on the fly from a template), a link to book the kickoff call, and a checklist of what the client needs to prepare.
The same script also creates the project folder in Google Drive with a standardized structure: /Strategy, /Deliverables, /Reports, /Admin. It sets the right sharing permissions and adds the folder link to my internal CRM.
This part alone saves me about 45 minutes per client. The welcome email used to take 20 minutes to write because I'd overthink the tone. Now it's consistent, on-brand, and arrives within 10 minutes of the client submitting the form.
2. Contract Generation
I have a master contract template in Docusign with merge fields for client name, scope, deliverables, timeline, and payment terms. The Claude Code script pulls the relevant details from the intake form, maps them to the contract fields, and sends the document for signature.
The tricky part was handling scope variations. Not every client gets the same deliverables, so I built a simple rules engine: if the intake form says "SEO + content," include clauses A, B, and C. If it says "automation build," include clauses D and E. The script assembles the right combination and populates the template.
Once the contract is sent, the script logs it in my internal tracker and sets a reminder to follow up if it's not signed within 48 hours.
3. Initial Audit and Strategy Brief
This is the most valuable part of the automation. For every new client, I run a standard set of audits during the first week: technical SEO check, Google Analytics/Tag Manager review, competitor keyword analysis, and email/CRM setup assessment.
Each of these audits is now a Claude Code script. They pull data from the client's site, run the analysis, and output a structured JSON report. A second script takes all four reports, synthesizes them, and drafts a strategy brief with recommended priorities.
I still review and edit the brief before sending it — this is where the human judgment matters — but having a solid first draft cuts my prep time for the kickoff call from three hours to about 45 minutes.
How This Changed the Client Experience
The business outcome is obvious: I save 6+ hours per client onboarding. But the client-side impact has been just as meaningful.
Clients now get their welcome email and next steps within minutes instead of waiting a day for me to manually send it. The kickoff call happens faster because I'm not scrambling to prepare. The audit findings are more thorough because I'm running a consistent checklist every time instead of relying on memory.
One client told me it was the smoothest onboarding they'd experienced with any agency. That's not because I'm unusually good at onboarding — it's because the automation removes all the friction and delay that used to come from doing it manually.
What I Didn't Automate (and Why)
There are parts of onboarding I intentionally left manual:
- The kickoff call — this is the relationship foundation and needs to be live
- Strategy review — I still read every intake form response myself and shape the brief with context the script can't infer
- Pricing negotiation — edge cases still happen, and I want to handle those personally
- Scope clarification — if a client's needs don't fit a standard package, I talk it through before building the contract
The goal isn't to remove myself from the process. It's to remove the repetitive logistics so I can spend more time on the high-value conversations.
How to Build This for Your Own Business
If you're running a consulting practice, agency, or service business and want to automate onboarding, here's the roadmap I'd recommend:
- Document your current process — write down every task that happens between contract signing and project kickoff
- Identify the repeatable parts — anything that follows the same steps every time is a candidate for automation
- Start with the welcome email — it's the easiest win and gives you a template for how to structure the rest
- Automate the audit scripts next — these have the highest ROI because they're time-intensive and can run unattended
- Build the contract workflow last — this one has the most edge cases and legal sensitivity, so get comfortable with the simpler scripts first
The entire system took me about six days to build, spread over three weeks. Most of that time was writing the prompts and testing edge cases. Once it was live, the maintenance has been minimal — maybe an hour a month to tweak something based on client feedback.
If you want to see how this could work for your specific onboarding flow, I walk through it in detail on the Claude Code getting started guide. And if you're curious whether automation makes sense for your business model, the FAQ page covers the most common questions I get.
The tools are here. The only question is how much of your week you want to give back to yourself.