Workflow 010: The Onboarding Agent

If I had to onboard ten clients tomorrow, or ten new hires, nothing would fall through.

Not because we'd work faster. Because the moment someone pays, most of onboarding starts without anyone remembering to start it.

An onboarding agent fires on a confirmed payment and handles everything that has to happen next: creating the task list, drafting the contract, granting the right access, notifying the teams who need to know, and sending the welcome email. Mine runs off QuickBooks into Notion.

The part I want to be clear about: the onboarding call is still a person. On purpose.

What this replaces

The checklist that lives in someone's memory.

Every new client used to mean a scramble. Did we send the contract? Did they get access to the right page? Does the finance team know? Does recruitment know what this client needs?

Most of it happened. Some of it didn't. And the failure was never dramatic, it was small and embarrassing. A client given access to the wrong page. A contract sent two days late. Someone finding out about a new client from a passing comment.

Manual work at the start of a relationship is where things get lost, and it's the worst possible moment for that to happen.

Blueprint

Payment confirmed, everything else follows.

Trigger: a paid invoice in the accounting system. Inputs: the client record, the offer they bought, the contract template, the onboarding task list. Output: tasks created, contract drafted, access granted, teams notified, welcome email drafted.

What fires for a new client in my assistant business:

• A to-do appears on the team page to generate the full task list for this client
• The first draft of the contract gets written
• The client gets access to their own client page, with the correct permissions
• Finance is notified there's a new client to file
• Recruitment is notified, with what this client needs in an assistant
• The welcome email and expectations walkthrough goes out
• The deep dive call gets booked

Organize

What has to exist before any of this:

• A documented onboarding process, start to finish. Every step, in order, with owners
• One place tasks live, with templates per offer
• Contract templates
• Clear access levels, so the automation grants the right one
• Whoever needs notifying, named: finance, recruitment, delivery
• A payment system that can signal when an invoice is actually paid

The order matters. This workflow only works because the 90 day program was already mapped. Automation applied to a fuzzy process just produces fuzzy results faster.

Systematize

You are my onboarding agent. When a new client payment is confirmed,
run the onboarding sequence.

Client context you'll receive:
- Name and company
- What they bought
- Anything from the sales call

Do this, in order:

1. Create the onboarding task list in [TASK SYSTEM], using the template
   for the offer they bought. Assign owners and due dates.

2. Draft the contract from the template, filled in with their details
   and scope. Save as a draft for a human to review. Never send it.

3. Grant access: create their client page and give them the correct
   permission level. Double check the level before granting. Wrong
   access is worse than late access.

4. Notify the teams that need to know:
   - [FINANCE]: new client, what they bought, billing details
   - [RECRUITMENT / DELIVERY]: new client, what they need, timeline
   - [ANYONE ELSE]

5. Draft the welcome email: what happens next, what to expect, and the
   link to book the onboarding call. Save as a draft.

6. Report back: what you completed, what needs a human, and anything
   missing that blocked a step.

Rules:
- Never send anything directly to the client. Drafts only.
- If any information is missing, flag it instead of guessing.
- Do not schedule or run the onboarding call. That is a human's job.

How to set it up

1. Map your current onboarding, beginning to end, including the invisible internal steps.
2. Mark each step: repetitive with the same output every time, or needs a human.
3. Build the automation for the first group only.
4. Test on a real client with someone watching every step.
5. Keep the human steps human, and make sure the agent's job is to hand off cleanly to them.

Assign

Automated: task creation, contract drafting, access provisioning, internal notifications, the welcome email draft. All of it repetitive, all of it identical every time.

Human: the onboarding call. The welcome. The introductions to the team.

I could have automated the onboarding call. There was a point where I genuinely considered it, and the technology was there.

I chose not to, for two reasons.

The practical one: that call gets clients comfortable with the format they're about to live in. Their assistant will be remote, so the working relationship happens over video. The first call is where that becomes normal.

The real one: I like to keep human things human. Clients know we're AI first. They should also know they're being cared for by actual people who understand their business and give a damn about it.

The agent exists to support the person doing the onboarding, not to replace them. It clears the admin so the human shows up to the call with everything ready and nothing forgotten.

Rule of thumb from this build: automate what happens behind the relationship, never the relationship itself.

Same logic for hiring our own people. The paperwork, the access, the setup, all automatic. The welcome, the introductions, showing the team who just joined: still a person, every time.

Integrate

Onboarding is where several systems have to agree with each other:

• Payment confirmation is the trigger, so nothing starts until it's real
• The task list comes from the template for that specific offer
• Contract drafting reads from the templates skill
• Access provisioning depends on the client page structure existing
• Notifications land where each team already works, so nobody checks a new place
• The onboarding call, once it happens, gets processed by the meeting agent

The failure mode this fixes isn't slowness. It's the small stuff that quietly gets missed in the first week, when a client is deciding whether they made a good choice.

Tomorrow: the repurposing engine. How one video becomes a week of content.