Personalisation is a context problem, not a writing problem

Most AI-written outreach reads badly for one reason, and it isn’t the model’s fault. Ask a language model to “write a personalised connection message” with nothing behind that instruction but a name and a job title, and it will produce something fluent, plausible, and generic — because fluent and plausible is what you asked for, and generic is what you gave it the material to produce. The writing quality was never the bottleneck. The context was.

The wrong problem gets the attention

It’s tempting to chase better personalisation by chasing a better model, a cleverer prompt template, a longer set of style instructions. Those changes move the needle a little. They can’t fix a message built from three data points, because no amount of prompt engineering invents information the model was never given. A sentence that sounds personal but is built from a name, a title and a company is a trick, and most readers — especially the senior, frequently-pitched ones you actually want to reach — spot the trick within a sentence and a half.

You cannot write your way out of a context problem. You can only feed the model more of the right context.

What a genuinely personal message actually needs

A message that reads as personal, rather than personalised-sounding, is usually built from context on both sides of the conversation:

• Your own services, areas of expertise and relevant past work — what you can credibly say you’ve done
• The specific prospect’s role, seniority and what that role is typically accountable for
• Their company — industry, size, and anything about its situation that’s genuinely relevant
• Why this prospect and your services intersect, stated plainly rather than implied

That last point is the one templates skip. “We help companies like yours” is not personalisation, it’s a category. “We modernised the claims workflow for two logistics platforms your size” is personalisation, because it’s specific enough that the reader could ask a follow-up question about it and get a real answer.

Why a review step matters more than a better prompt

Feeding the model good context still doesn’t make the output safe to send blind. A model can connect facts that don’t actually connect, overstate a similarity, or draft a sentence that’s technically accurate but reads oddly to the specific person receiving it. That’s why AI-drafted messages exist to be reviewed, not auto-fired: a person reads the draft, regenerates it if the angle is off, edits the specific line that doesn’t land, and only then approves it to send. The AI’s job is to produce a strong first draft fast. A human’s job is still to decide it’s actually right for this one person.

Context beats volume every time

There’s a version of “personalisation at scale” that just means running the same weak-context prompt across a thousand names faster. That isn’t personalisation, it’s generic messaging with a mail-merge field, and prospects have gotten very good at recognising it in the first three words. The alternative isn’t slower — it’s the same automation, pointed at a richer input. Draft generation still runs on every qualified lead automatically; what changes is what it’s allowed to draw on before it writes anything.

Treat the prompt as a research brief, not a style guide

The practical shift is to stop treating the prompt as a style instruction — “write in a friendly, professional tone” — and start treating it as a research brief: here is what we do, here is who this person is, here is the specific reason those two things belong in the same sentence. Get that brief right and the tone mostly takes care of itself, because a message built from real, specific, relevant facts tends to read as personal without needing to be told to.

The writing was never the hard part. Knowing what to say, and to whom, always was.