PeakKR

AI blog writing for clients

AI Blog Writing for Clients: Keep Each Voice Intact

Every agency that scales AI blog writing for clients hits the same wall around client number six. The posts are grammatically fine, the keyword is in the H1, the word count is right — and a plumbing company in Tulsa, a B2B SaaS, and a boutique law firm all sound like the same mildly enthusiastic consultant. One client notices. Then another. Then you're rewriting from scratch and your margin is gone.

The fix isn't a better model or a cleverer prompt. It's treating voice as a documented asset per client, built once and reused, the same way you'd treat a keyword map or a link prospect list.

Why AI drafts converge on the same voice

Models are trained to produce the statistically likely next sentence. Absent strong constraints, "likely" means the median internet blog post: 18-20 word sentences, three-item lists, transitional phrases like in today's fast-paced world, and a closing paragraph that restates the intro.

When you prompt with "write in a friendly, professional tone," you've given almost no constraint. Friendly and professional describes 80% of the training data. You've asked the model to be average, and it obliges.

The agencies that get this right do two things differently. They measure voice instead of describing it, and they feed examples instead of adjectives.

What "voice" actually breaks down into

Voice feels unquantifiable until you decompose it. Four components cover most of what a reader perceives:

Lexicon

The words this client uses and refuses. A commercial HVAC company says "equipment," never "units." A fintech says "customers," never "users." A trades client says "we'll come out and take a look," never "we'll conduct an assessment." Every client has 15-30 of these preferences, and getting them wrong is the single fastest way to make a post feel foreign.

Rhythm

Average sentence length and its variance. One of our reference clients averages 12.4 words per sentence with heavy fragment use. Another averages 24.1 with multi-clause sentences and semicolons. Those two read nothing alike even on identical topics. Run their existing posts through a readability tool and write the numbers down — it takes four minutes and does more for voice matching than a paragraph of adjectives.

Stance

Who the author is relative to the reader. Peer ("we've all botched a migration"), authority ("here's what the data shows"), or servant ("we'll handle this for you"). Also: does the client make claims or hedge? A law firm hedges on everything. A contractor says "this will fail within two years" without flinching.

Proof furniture

What the client reaches for when making a point. Case studies? Internal stats? Analogies from a specific industry? Customer quotes? A post that argues with a different kind of evidence than the client normally uses reads as inauthentic even when the words are right.

Build a voice profile in about 90 minutes

Do this once per client, at onboarding, and bill it as part of setup.

1. Pull 8-12 source pieces

Not their whole blog. Ask the client: "Which five pieces of writing best represent how you want to sound?" Then add three to five more from their site — ideally pages their sales team sends to prospects, plus any founder LinkedIn posts, which are usually the least sanitized version of their voice. If the client has a brand guide, read it, but weight it below the actual writing. Brand guides describe aspiration; the writing describes reality.

2. Measure before you describe

Record, for the sample set: average sentence length, Flesch reading ease, paragraph length in sentences, first-person plural vs. second-person ratio, contraction usage, and whether they use em dashes, semicolons, or neither. Fifteen minutes of counting gives you a spec no amount of vibes-based prompting will match.

3. Write the do/don't list

Twenty lines maximum, split in two columns. Example from a real roofing client profile:

4. Build a sample bank

Extract three paragraphs from the client's own work: one opening, one explanatory middle section, one closing or CTA. These go into every prompt verbatim as few-shot examples. In testing across our own client set, adding real sample paragraphs reduced first-draft editing time by roughly 40% compared to a prompt with voice described in prose only. The model imitates structure it can see far better than structure it's told about.

The prompt structure that holds up

Order matters. A reliable structure for AI blog writing for clients, in sequence:

  1. Role and audience — who's writing, who's reading, what the reader knows already.
  2. The measured spec — sentence length target, reading level, paragraph length, person/POV.
  3. Do/don't list — the banned-words list is the highest-leverage item here.
  4. Sample paragraphs — labeled as style reference, not content to reuse.
  5. The brief — primary keyword, search intent, required sections, internal links, factual constraints (service areas, licensing, guarantees, pricing you're allowed to state).
  6. Explicit outputs — H2/H3 outline, word range, meta title and description.

Topic selection lives upstream of all this. The brief is only as good as the opportunity behind it, which is why we pull most client topics from query data rather than brainstorming — Search Console is the cheapest topic research tool you already own. Storing the voice profile against the client record rather than in a doc somewhere is the difference between this surviving staff turnover and not; it's one of the reasons we built voice profiles directly into PeakKR's AI blog writer for agencies instead of leaving them in prompt files.

QA: catch drift before the client does

Voice erodes quietly. A junior editor "improves" a fragment into a full sentence, someone swaps in a stock transition, and eleven posts later the client emails: "these don't sound like us anymore."

Run a five-point check on every draft, 90 seconds:

Quarterly, re-sample: pull three recent published pos

Featured in this list? Grab your “Featured on PeakKR” badge and add it to your site — free.
Get your badge →

Frequently asked questions

How do you make AI write in a client's voice?

Build a voice profile from 8-12 of their best existing pieces: measure average sentence length, reading level, pronoun use, and recurring phrases, then write explicit do/don't rules and attach 2-3 full sample paragraphs as few-shot examples. Description alone isn't enough — the samples do most of the work.

How many sample articles do you need to capture a client's voice?

Eight to twelve pieces is the sweet spot. Fewer than six and you're copying one writer's mood on one day; more than fifteen and you're averaging across voices that have drifted over the years. Prioritize recent pieces the client has praised or that their sales team actually sends to prospects.

Should agencies disclose that blog posts are AI-assisted?

Put it in the contract, not in a footer on the post. Most clients care that a human edits, fact-checks, and signs off — write that into the scope so expectations are clear. Google's guidance targets content quality and helpfulness, not the drafting tool, so disclosure is a client-relationship decision rather than an SEO one.

How long should AI-assisted blog posts take to produce?

Once a voice profile exists, a 1,200-word post typically takes 35-50 minutes of human time: 10 for brief and outline, 5 for generation, 20-30 for editing, fact-checking, and internal linking. The first post for a new client takes two to three hours because you're building the profile alongside it.

Nick Quirk

Written by Nick Quirk

Founder of PeakKR

Nick Quirk is the founder of PeakKR, the agency workspace. He has spent decades running SEO and operations for marketing agencies, and writes about what holds up in real client work: technical audits, reporting, local campaigns, retainers and the systems behind them.

Run your agency on PeakKR

Client projects with phases, time tracking, technical SEO audits, client-ready reporting and AI briefs — the workspace this blog is written from.

Start free

Keep reading