Your Copy Serves One Role. The Rest Just Object.
Most website copy is written for one buying role. Learn how to write for a specific role without turning the other decision-makers into silent objectors.
Most copy has an accent
Read your homepage out loud and you can usually hear who it was written for. "Ship faster with less overhead" is a practitioner's sentence. "Reduce operational risk and total cost of ownership" is a finance sentence. "Empower your team to do their best work" is a people-leader sentence. Each one carries an accent — a set of assumptions about what the reader cares about, what they fear, and what counts as proof.
The problem isn't that your copy has an accent. It has to. The problem is that most pages pick one accent by default, without deciding to, and then quietly ignore every other role that has to say yes.
This matters more now than it did two years ago. When an AI model refers a buyer to your site, it often sends the person who asked the question — which might be the practitioner researching options, not the economic buyer who signs. That person then has to relay what they found to the rest of the committee. If your page only speaks their language, the other roles get a secondhand summary with none of the reassurance they specifically needed.
Writing for a role is not writing for a persona
A persona is a fictional person: their goals, their day, their frustrations. Useful, but easy to over-invest in. A buying role is narrower and more actionable: it's the specific job someone does inside the decision.
The same person can occupy different roles across two purchases. What stays constant is what each role is scanning for.
| Role | Reads the page asking | Stops trusting when |
|---|---|---|
| Practitioner / end user | "Will this actually work for how I do the job?" | The copy is abstract, no specifics, no screenshots |
| Economic buyer | "What does this cost, and what's the risk if it fails?" | No pricing, no proof of outcomes, vague ROI |
| Technical evaluator | "Does this fit our stack and our security rules?" | No integration detail, no docs, no compliance info |
| Champion / internal seller | "Can I defend this choice to my boss?" | Nothing they can copy-paste into a pitch |
Most pages serve the practitioner well and the champion badly. The champion is the role that carries your case into the room you'll never be in — and they leave your site with adjectives instead of ammunition.
The silent objection is the expensive one
When a page speaks only to one role, the other roles don't argue with you. They can't — you're not in the conversation. They object silently, inside the buyer's own head or the internal Slack thread, and you never see it.
Analytics won't show you this. You'll see the page got traffic, the person spent a reasonable time, and then the deal went cold. The drop-off looks like disinterest. It was actually an unanswered question belonging to a role your copy never addressed.
This is the specific gap an [AI Focus Group](https://visibilityradar.ai) is built to surface. When you run several role-based personas across the same page, the practitioner persona often sails through while the finance persona stalls on the same sentence the practitioner loved. That divergence is the signal. It tells you the page isn't broadly weak — it's narrowly tuned, and you can see exactly which role falls off and where.
How to write for a role without alienating the rest
The wrong fix is to write for everyone. Copy that tries to reassure all four roles in one paragraph becomes mush — the classic "enterprise-grade platform that empowers teams to drive results at scale." That sentence has no accent because it has no reader.
The right fix is layering: one dominant voice, with explicit on-ramps for the others.
1. Choose the primary role deliberately
Decide which role your best deals start with. For most self-serve and mid-market products it's the practitioner. For enterprise it's often the economic buyer or the champion. Write the top of the page in that role's language and don't apologise for it.
2. Give every other role a labelled door
Below the primary pitch, name the other roles' questions plainly. A "For security teams" section. A pricing page that a finance reader can reach in one click. A short block a champion can lift verbatim into their internal pitch. You're not diluting the main message — you're adding side doors for people who arrive with a different job.
3. Match proof to the role, not to your pride
Different roles accept different evidence. Practitioners trust screenshots and specific workflows. Economic buyers trust numbers and named outcomes. Technical evaluators trust docs and integration lists. A testimonial from a happy user does nothing for a CFO who needs a cost argument. Put the right proof next to the right question.
4. Write the champion's talking points for them
The single most under-served role is the person selling you internally. Give them a crisp three-line summary of why-this-over-nothing and why-this-over-the-obvious-alternative. If they have to invent that argument themselves, half of them won't, and the deal dies in a room you can't reach.
The honest limit
Role-based persona testing tells you where a specific role's reasoning breaks. It doesn't tell you which role dominates your real pipeline — only your CRM and your sales calls know that. Use the persona work to find the *gaps*, then use real deal data to decide which gap is worth fixing first. A blocker that stops a role you rarely sell to isn't your priority, even if a persona flags it loudly.
Your next step
Open your highest-intent page and read it once as each of the four roles in the table above. Mark the first sentence where each role would want something the page doesn't give. If three of the four roles stall in the same paragraph while one glides through, you've found your accent — and the roles you've been letting object in silence.
See your brand's AI visibility score
Free scan — no signup, results in 60 seconds across 6 AI models.
Check My Brand →