Generative AI has made B2B content cheap to produce and expensive to trust. Buyers can tell when an article was generated from a prompt and never touched by someone who has done the work, and so can the AI assistants that now summarise the web for them. The teams winning with generative AI are not the ones producing the most; they are the ones whose content still sounds like people who know the subject.
Voice is not a tone setting. It is the accumulation of opinions, examples, vocabulary and judgement that make your content recognisably yours. This guide is about using generative AI for the parts of content work it does well while protecting the parts that carry the voice.
Where Generative AI Helps Without Costing You Anything
- Research and synthesis: summarising calls, reports and competitor content into a brief.
- Structure: proposing outlines, section orders and the questions a piece should answer.
- First drafts of the boring parts: definitions, background, step lists, metadata, alt text.
- Adaptation: turning one strong piece into a summary, a post, an email and a script.
- Editing passes: consistency, clarity, length, terminology checks against a style guide.
None of these is where the voice lives. Handing them to AI gives your writers time for the parts that are.
Where the Voice Lives, and Who Owns It
Three things make B2B content sound like a company that knows what it is doing, and generative AI cannot supply any of them on its own.
Opinions
A point of view on what works and what does not, stated plainly. Models hedge by default. Your subject-matter experts do not, and their opinions are the reason a buyer trusts you. Capture them in interviews, calls or voice notes, and make them the spine of the piece.
Specifics
Real examples, numbers with sources, the detail that only comes from having done the work. A model will produce plausible generalities; a practitioner produces the thing that happened last quarter. Insist on at least one specific per section.
Vocabulary
The words your team actually uses, including the ones it refuses to use. Write them down. A style guide with approved terms, banned phrases and examples of your sentences is the single most effective control on AI output.
A Workflow That Keeps the Voice
1. Brief from an expert, not from a keyword
Start every piece with fifteen minutes of a practitioner talking: what the reader gets wrong, what they should do instead, a story that proves it. Transcribe it. That transcript is the raw material the AI works from, and it contains the opinions and specifics a prompt never will.
2. Let AI structure and draft around the expert's material
Ask the model to outline and draft using the transcript, your style guide and two or three of your best published pieces as examples. Tell it what not to do: no hedging, no generic openers, no invented statistics. Treat the output as a first draft written by a capable junior who was not in the room.
3. A human rewrites the parts that matter
The opening, the argument, the examples, the conclusion. An editor who knows the subject rewrites those in the company's voice and cuts anything that sounds like everyone else. This step is not optional and it is where most AI content programmes fail by skipping it.
4. Check facts and claims before anything ships
Every number gets a source. Every product claim gets checked against what the product does. Generative models are confident about things that are not true, and B2B buyers remember the company that published them.
5. Measure trust, not volume
Track what content does for pipeline, which pieces AI assistants cite, and what sales hears from prospects, rather than how many articles shipped. Volume is easy now and no longer a signal.
The Content Types Where AI Should Do Less
Not every B2B piece carries the same amount of voice, and the workflow should flex with it. Some content is mostly information, and AI can carry most of the load with a light edit. Some content is entirely judgement, and AI should stay in the research and editing seats.
| Content type | AI share of the work | What the human must supply |
| Product documentation, how-to guides, glossary entries | High: draft, structure, consistency | Accuracy check against the product |
| Comparison and buyer's guides | Medium: research, tables, first draft | The recommendation and the reasons |
| Thought leadership and opinion pieces | Low: outline and editing only | The argument, the examples, the stance |
| Case studies | Medium: structure from interview notes | The customer's words and the real numbers |
| Sales enablement and objection handling | Low: formatting | What actually works in calls |
| Executive and founder content | Very low: transcription and tidying | Everything else |
Teams that apply one workflow to every type end up with documentation that reads like an opinion piece and opinion pieces that read like documentation. Matching the AI share to the content type is the simplest quality lever available.
Prompting for Voice, Not Just Output
The prompt is where most teams lose the voice, because they ask for an article and get the average of every article. A voice-preserving prompt has four parts, and it is worth building once as a template.
- The material: the expert transcript or notes, pasted in full, with an instruction to use only what is there and to mark anything it needs that is missing.
- The examples: two or three of your best pieces, with a note on what makes them yours.
- The rules: the style guide's banned phrases, terminology and sourcing rule, stated as constraints.
- The reader: who they are, what they already know, and what they should be able to do after reading.
Then ask for an outline first and approve it before the draft. A model that is told what not to do and given real material to work from produces something an editor can work with. A model asked to write about a topic produces something an editor has to replace.
Repurposing Without Dilution
Adaptation is where generative AI earns its keep, and where voice quietly drains away. A strong article becomes a summary, then a post, then an email, and by the fourth derivative the opinion has been sanded off. Two habits prevent it. First, repurpose from the expert material, not from the previous derivative, so each version keeps the specifics. Second, give each format its own rule for what must survive: the post keeps the opinion, the email keeps the example, the summary keeps the number. A derivative that carries none of the three is not worth publishing.
What This Looks Like in a Real Team
A B2B services firm with two writers and a dozen consultants moved from four articles a month to twelve without adding staff, and its consultants stopped complaining that the content did not sound like them. The change was not the model. It was a fifteen-minute recorded interview at the start of every piece, a style guide with forty banned phrases and twenty example sentences, and a rule that a consultant signs off the final draft. The writers became editors and interviewers. The AI did the structuring and the first draft. The voice came from the people who had done the work, which is the only place it can come from.
Guardrails Worth Writing Down
| Rule | Why |
| Every piece starts from expert input | Opinions and specifics cannot be generated |
| Style guide with banned phrases and example sentences | The most effective control on model output |
| No statistic without a source | Models invent plausible numbers |
| A named human editor signs off | Accountability for voice and accuracy |
| AI-assisted, never AI-published | Buyers and AI assistants both detect it |
INSIDEA
Ready to put AI to work in your business?
Practical automation and AI workflows built on top of your stack, not bolted on.
Content That Sounds Like Your Best People
INSIDEA runs content programmes for B2B companies where generative AI does the production work and the company's experts supply the voice. We build the style guide and the expert-interview workflow, connect content to HubSpot so its contribution to pipeline is visible, and optimise it so AI assistants cite it accurately. If your content has become faster and flatter at the same time, that is the fix.

