How do I onboard a new client without losing a day to admin?

Onboarding eats your day because every step waits on you. The proposal gets signed, so you send the invoice. The invoice gets paid, so you send the welcome email with the right scheduling link and set up the client’s folder. Then you chase the logins and files you still need. A checklist tells you what comes next, but you still do each step by hand. With AI, each event can start the next step: a signature drafts the invoice, a payment drafts the welcome email and builds the folder, and a chaser drafts a nudge for whatever the client still owes. You approve, and the only wait left is the client.

Why does signing a new client turn into a day of admin?

Signing a new client is exciting. You’ve done the calls, you’ve sent the proposal, and somebody finally said yes. You’re happy to onboard them because it’s a new client, and that’s the whole point. But onboarding itself is a very boring task, because it’s always the same.

You always have to take the signed proposal and send an invoice. Once the invoice is paid, you send the welcome email with the right scheduling link for whatever they bought. You set up whatever client files and folders you keep for them. Then you ask for everything you need from them to actually start the work, whether that’s copy, photos, a questionnaire, or logins to their accounts. You’re doing the same steps, every time, for every single client. The only things that really change are the client’s name and the package they’re on.

It’s not done in one sitting either. Every step waits on the client doing something first. You can’t send the invoice until the proposal is signed, you can’t send the welcome email until the invoice is paid, and you can’t start the work until they’ve sent you what you asked for. So onboarding ends up spread across days, and you’re the one who has to notice each moment and get the next step out. With one client that’s manageable. With a few signing in the same week, you’re keeping track of who signed, who paid and who’s sent what, on top of the client work you already have.

None of these steps are hard. They’re just yours, and they land on you whenever the client decides to move. There’s a way to stop doing them by hand, but first here’s where the time actually goes.

Where does the onboarding time actually go?

A lot of onboarding is waiting. You’re waiting for the proposal to be signed, the invoice to be paid, and for the client to send over everything you asked for. Once you do get the thing you were waiting on, you want to be sending the next thing quickly. The onboarding process is different for every business, but it always has to be timely.

So there are two costs here. The first one is your hours. One survey of advice firms put onboarding at around 15 hours per client, and 54% of that time isn’t even spent with the client. It’s the admin around them. Your business might have less paperwork than an advice firm, but the shape is the same. More than half of onboarding is you preparing, sending and checking things, and not you talking to the person who just paid you.

The second cost is the gap between steps, and this one is harder to see. Right after somebody buys is when they’re most likely to second-guess it. Gartner surveyed over 3,400 software buyers and found 60% of them regretted a purchase, and 49% said an immediate response from the company they bought from would help. That’s software and not services, but the principle carries over. A client who signs on Monday, pays on Tuesday, and then hears nothing until Thursday because you were buried in other client work has two days to wonder if they made the right call. They’re probably not going to tell you that either.

Then there’s the wait you can’t control. Duda surveyed 120 agencies and found that clients cause about 87% of content-collection delays. Only 2.68% of those agencies collect all the content they need in one day, 37.5% take six to ten days, and 23.21% take more than eleven. So even the fastest version of you is going to wait on the client for as long as they take. The real problem is when you add your own delay on top of theirs, because you didn’t see that they paid, or you forgot to ask for something the first time and now you’re asking again.

Sources: Advice Efficiency Survey 2025 (IFA Magazine) · 2024 Global Tech Trends Survey (Gartner Digital Markets) · Ask any agency what their biggest website building challenge is (Duda)

Measure yours in 3 minutes: the free Task Audit scores how much of your recurring work could run without you.

Why isn’t an onboarding checklist enough?

Everyone says to build a checklist and make a process for your onboarding. Which is true, you definitely should. If you read my earlier issue on what to automate first, I said you should never automate a process that’s broken, and onboarding is no different. A checklist is how you make sure every client gets the same experience. Nobody forgets the scheduling link, the folders get set up the same way every time, and if you have somebody on your team, they can run it without coming to you to ask how.

But a checklist only tells you what the next step is. It doesn’t tell you when. Somebody still has to notice that the proposal got signed, open the invoice tool, fill it in and send it. Somebody still has to see the payment come through, find the right welcome email, pick the right scheduling link and set up the folder. And somebody still has to keep track of what the client hasn’t sent yet and write the follow-up. The checklist makes all of that consistent, but it’s still a person doing every step, just in the right order.

So you can take it one step further. Every step in onboarding has a trigger. The proposal gets signed, the invoice gets paid, a file shows up in the client’s folder. What happens after each trigger is the same every time; only the client details changing. Back in that same issue, I called onboarding a good first automation for this exact reason. The signed proposal already has the client’s name, email and package on it, which is everything the invoice and the welcome email need. Moving that information from one place to the next is boring data entry and monitoring, and that’s the kind of work AI handles well. So instead of you watching for each trigger and then doing the step, AI can watch for it and get the step ready, and you check the result before it goes out.

What happens when the signature runs the onboarding?

The whole onboarding comes down to three Claude Code skills, hooked up to the tools you already use, like your Gmail, your client folders, your document signer and your invoicing tool. There are three instead of one because each one waits for a different thing.

Firstly, an invoice skill is for when the proposal gets signed. It reads the signed proposal, builds the invoice and the invoice email from your template, and saves them in the client’s folder. The proposal already has the client’s name, their package and the price on it, so the invoice gets filled in from that, with the email drafted right next to it, ready for you to review and send.

Next, the welcome skill, for when the invoice gets paid. It reads the proposal and sets up the client’s folder, with subfolders for client files like access, brand, copy and photos. It also writes a client overview file with who they are, what we promised, what they owe, how they talk, and the last time we were in touch. Then it drafts the welcome email from your template with the right scheduling link for their package, so a client who bought the package with a 90-minute strategy workshop gets the link for that workshop. That same email asks for everything they owe in one go. Everything the client owes is in that one email because it shows we’re prepared and professional, and you’re not spamming them with a bunch of different emails. Give them everything they need right away, just after they pay.

Finally, a chase/nudge skill is for everything after that. For every client, it reads the proposal to see what they owe, checks their folder for what’s arrived, and works out what’s missing. Then it drafts a nudge email from your template for only what’s missing and gives you one line per client. So if a client has sent their website copy and nothing else, the nudge thanks them for the copy and lists what’s still missing, like their logins, their branding, and their photos. You can also give it due dates, so it only nudges when somebody’s actually late.

You can set it up such that nothing in any of the three skills sends on its own. The invoice, the welcome email and the nudge are all drafts until you approve them. If you connect Claude Code to Gmail, those drafts can go straight into your drafts folder, and all you have to do is read them and click send. You can also set them to run on a schedule, like a check every morning that sees a proposal got signed and drafts the invoice, or sees an invoice got paid and gets the welcome email ready.

So everything on your side, all the onboarding content and requirements, goes out in minutes instead of hours. Claude Code helps you run the whole onboarding, so the only part you spend time on is reading and approving the emails. The only time onboarding takes is however long the client decides to take.

If you want to see all three skills get built from scratch, the full walkthrough comes out this Tuesday on my YouTube channel: https://www.youtube.com/@Jonathan-Probert

What should your first ask to a new client include?

My first client onboarding took 12 days. Some of that was waiting on her, but a lot of it was me, because I didn’t have a good process yet and everything was kind of all over the place. I had the contract, then the invoice, and then I had to gather everything I needed from her. I sent her a questionnaire for everything I needed, and she had it back to me the same day. But then I realized I needed a list of all the accounts she was using so I could connect them to AI.

That list ended up being the slow part. She gave me access to everything the next day, but getting it all connected took another week. Some accounts needed verification codes that only worked with her live on a call. One connection broke and had to be redone on another call. And a couple of the tools she used didn’t have a way to connect at all. She signed on June 4th, and everything was connected on June 16th.

So even when the client is on top of it, the gap was still in what I hadn’t asked for yet. If the account list had gone out in the same email as the questionnaire, the logins and codes would have started days earlier. That’s why the welcome email asks for everything in one go, with logins first. They’re the thing most likely to need the client live on a call, so they’re the thing you want started earliest.

It’s also what makes the chase skill work. It reads the signed proposal to see what the client owes, so it can only chase what’s written down. If your proposal and your welcome email list every file, every login and every questionnaire you’ll need, the chase skill has a complete list to check against, and it nudges for exactly what’s missing. If something only lives in your head, nothing is going to chase it, and you end up realizing halfway through setup that you need one more thing from the client, exactly like I did.

Which parts of onboarding should stay yours?

Even with all three skills, I check everything before it goes out, because AI can get stuff wrong. With the welcome email, we’re using a template that gets filled in, so there’s not much room for it to go wrong. The nudge is different. It’s fully custom to what the client actually sent us, so AI has to figure out what they still need to provide and write a new email from that. What if it somehow assumes the copy and the brand workbook were both done, even though the brand workbook isn’t actually there? Then the client gets an email thanking them for something they never sent. So the step where I approve the draft stays, and the same goes for the invoice and the welcome email. We just want to make sure they’re fully correct before they get sent out, to save our reputation.

The relationship stays yours too. The skills handle the admin around the client: the invoice, the folders, and the emails asking for what you need. They don’t run your kickoff call, and they shouldn’t. That first call is one of the moments your client is actually paying you for, and the whole point of handing off the admin is that you show up to it prepared instead of behind.

If your service does require logins, you also need to be careful here. The welcome email asks for access, but the passwords themselves shouldn’t end up sitting in your AI’s files, where they can get pulled into a document or an email without you catching it. In your welcome email, you should be sending them a link to a service for securely sharing passwords. And some things still need a person. Verification codes that only work with the client on a call, or a tool that doesn’t connect to anything, are going to be on you. The chase skill can tell you they’re still open, but it can’t close them.

If you’ve got a five to ten person firm, maybe you have a client experience person, somebody who’s in charge of onboarding everybody and making sure that experience is good. With these three skills, they’re no longer the person sending everything and setting everything up. They’re able to onboard more people, and all they really need to do is be the one approving the different emails. They can spend that time answering client questions, and maybe even helping out in other parts of the business.

What AI can’t change is how fast your client moves. What it can change is that you’re never the one they’re waiting on. If you want to start this week, write down every step in your onboarding from signed proposal to first working session, and every single thing you ask a new client to send you. That one list is your checklist, and it’s also everything the skills need to start getting the steps ready for you.

And if you’d rather I just look at your business directly, I do a free discovery call.

Frequently asked questions

Why does signing a new client turn into a day of admin? Because onboarding is the same steps every time, and each one waits on the client doing something first. You send the invoice once the proposal is signed, then the welcome email with the right scheduling link once it’s paid, then set up their folders and ask for everything you need. It ends up spread across days, and you’re the one who has to notice each moment.

Where does the onboarding time actually go? Into your hours and into the gaps between steps. One survey of advice firms put onboarding at around 15 hours per client, with 54% of that not spent with the client. In a Gartner survey of software buyers, 60% regretted a purchase and 49% said an immediate response would help. Clients also cause about 87% of content-collection delays, so the goal is to stop adding your own delay on top of theirs.

Why isn’t an onboarding checklist enough? A checklist makes onboarding consistent, so nobody forgets the scheduling link and anyone on your team can run it. But it only tells you what the next step is, not when. Someone still has to notice the signature or the payment and do each step by hand. Every step already has a trigger, so AI can watch for it and get the step ready for you to check.

What happens when the signature runs the onboarding? Three Claude Code skills handle it. An invoice skill drafts the invoice and invoice email when the proposal is signed. A welcome skill sets up the client’s folder, writes a client overview file and drafts the welcome email with the right scheduling link when the invoice is paid. A chase skill checks what the client has sent and drafts a nudge for only what’s missing. Everything stays a draft until you approve it.

What should your first ask to a new client include? Everything the client owes, in one email, with logins first. Logins are the thing most likely to need the client live on a call, so you want them started earliest. The chase skill reads the signed proposal to see what the client owes, so it can only chase what’s written down.

Which parts of onboarding should stay yours? Approving every email before it goes out, because AI can get things wrong, especially on a nudge that’s written fresh for each client. The kickoff call and the relationship stay yours too. Passwords shouldn’t sit in your AI’s files, so send clients a link to a secure password-sharing service, and verification codes that need the client live are still on you.

Photo by Mina Rad on Unsplash