How to unfuck your client onboarding with AI

Most marketing agency client onboarding is broken in the same place. You learn how a client talks, what they care about, the words they’d never use. Then that knowledge lives in your head, or one person’s head, and the moment they’re off the project the work stops sounding like the client.

I hit this hard a few years back, running an internal agency that produced content for some of the biggest names in their space. The bottleneck was never talent. It was voice. Getting a writer to sound like a specific client took weeks, and the knowledge never transferred. Scale one client, fine. Scale ten, and the whole thing falls over.

So I built a system to fix it. I’m not technical. I didn’t write code. I designed a flow and used AI to run it. Here’s the whole thing, the parts that matter, so you can build your own.

The core idea

A person’s voice feels unscalable. It feels like taste, instinct, the thing only a senior person “gets.” That feeling is the trap. Voice isn’t magic. It’s a set of rules nobody’s written down yet. Write the rules down, and you can hand them to anyone, including an AI.

That’s the entire move: turn an unscalable human act into a written spec, then build a loop that keeps the spec honest.

The flow

1. Structured intake. A deep interview, but not the usual brand-guidelines fluff. You’re hunting for the specific stuff: the words they overuse, the words they’d never say, the references they reach for, what they’re secretly insecure about, who they’re trying to impress. Tics and taboos. That’s where voice actually lives.

2. Sample harvest. Pull their real existing copy. Old posts, emails, scripts, anything in their actual words. This is ground truth. What people say about how they write and how they actually write are two different things, and the samples don’t lie.

3. Voice profile. Distil intake plus samples into one reusable spec. The rules that make them sound like them. This is the asset. Everything else is built on it.

4. System prompt. The profile becomes the operating instruction the AI writes from, every time. Not a clever one-off prompt you retype. A fixed instruction baked into the tool, so consistency is the default, not the exception.

5. Draft generation. Now you produce on-voice content at volume. The output sounds like the client because the rules are doing the work, not the writer’s memory.

6. The reliability loop. This is the part everyone skips, and it’s the only part that matters. A human reviews each draft against the profile and scores it. Every miss feeds back into the spec. The profile tightens with every cycle. After a few rounds the voice holds without you in the room.

Why the loop is everything

Anyone can write a good prompt once. The reason most “AI voice” attempts fail is they stop at the prompt and hope. Hope isn’t a system. The loop is what turns a lucky output into a reliable one. Miss, refine, repeat, until the spec is tight enough that a new team member can run it on day one and get it right.

That’s the difference between a trick and infrastructure. A trick works when you’re watching. Infrastructure works when you’re not.

What this actually unlocked

Onboarding went from weeks to hours. Voice stopped being a single point of failure. New people got up to speed fast because the knowledge lived in a spec, not in someone’s head. And the quality held at scale, which is the thing everyone promises and almost nobody delivers.

You can build a version of this for your own clients this week. You don’t need to code. You need to take the thing you think is magic and be willing to write down the rules.

I’m building in public from here. Next, I’m taking this same approach. a non-technical operator shipping real AI-enabled products and workflows. and building an actual software tool live, from zero. You’ll see the whole thing: what works, what breaks, what it costs. First build kicks off in the next issue.

Subscribe if you want to watch someone who can’t code ship real software anyway.