Quick answer
To scale content production with AI without losing your voice, stop describing your style in adjectives. Feed the model three real samples of your own writing, have it extract countable rules from them, then store those rules in a settings field that loads automatically in every new session.
You can scale content production with AI and still sound like yourself. Most people who try find the opposite happens: output goes up, and everything starts reading like it was written by the same mildly enthusiastic stranger. The volume problem gets solved. A voice problem gets created in its place.
The usual fix is to tell the model to “sound warm but authoritative” and hope. That doesn’t work, and there is a mechanical reason why. What does work is showing the model your actual writing instead of describing it, then storing that evidence somewhere it loads automatically every time you open a new chat.
- Three real pieces that represent how you actually write
- A rule set describing your sentences, not your vibe
- A reusable prompt block that shows the model your patterns
- All of it stored where it loads on its own, every session
None of this needs a paid plan. Every layer runs on the free tier of ChatGPT, Claude, or Gemini. Budget about forty minutes to build it once, then two or three minutes per draft after that.
Will this work for you?
Why AI Drafts All Sound the Same
Ask a model to write something with no examples and no constraints, and it gives you the statistical middle of everything it has read. That middle is real writing — it’s just nobody’s writing in particular. It has no strong opinions, no odd sentence lengths, no favourite words. That is exactly what makes it feel machine-made.
The tells are consistent enough that readers spot them before they can explain them:
- Filler vocabulary that adds no information and no personality
- Every paragraph the same length, every sentence the same shape
- Contrast pairs used as a rhythm rather than as an argument
- Constant hedging, so nothing is ever actually claimed
Why Vague Adjectives Fail
Here is what most guides get wrong. They tell you to define your brand voice with adjectives — professional, friendly, confident — and stop there. The model has no way to turn “confident” into a sentence. It has read confident writing from ten thousand different authors, and it averages them.
The research community made this point long before AI writing tools existed. The Nielsen Norman Group’s four dimensions of tone of voice breaks tone into humour, formality, respectfulness, and enthusiasm — because “professional” on its own is too coarse to act on. A model needs the same decomposition, only more concrete still: sentence length, opening habits, punctuation you avoid.
✕ Describing your voice
Write in a professional yet approachable tone that reflects our brand's authoritative but human personality.
✓ Showing your voice
Sentences average 14 words. Open with a claim, never a question. No em-dashes. Say "we think" instead of "it could be argued".
The second version works because every line is testable. You can look at a draft and tell whether it complied. The first version is a feeling, and feelings do not survive translation into text. Getting this right is really an exercise in giving AI the right context rather than better adjectives.
How to Scale Content Production With AI
The Voiceprint Method is a three-stage system: capture three real samples of your writing, codify them into concrete rules, then carry those rules into persistent settings so every session starts on-voice. It is the approach we teach at PromptPeakAI to anyone who needs to scale content production with AI beyond a few pieces a month.
The Voiceprint Method: capture evidence, turn it into rules, then store the rules where they load automatically.
Most people who write about this stop at stage two. They explain how to describe your style, then leave you re-pasting that description into every conversation. Stage three is the part that turns a technique into a system, and it is also the part that decides whether this survives past week one.
Capture Three Real Samples of Your Writing
Pick three pieces you have already published or sent. Not three pieces you wish you had written, and not three pieces you admire from someone else. The model will copy whatever you give it, faithfully, including the parts you were hoping it would improve.
Choose three pieces that genuinely sound like you
Aim for 200 to 400 words each. Shorter than that and there aren’t enough patterns to detect. Much longer and the samples start crowding out the actual task later on.
- Range, not repetition. One long-form piece, one short post, one email works better than three blog intros.
- Real conditions. Something you wrote under normal deadline pressure, not your one heavily edited showpiece.
- Recent. Writing from four years ago encodes a voice you may have already moved on from.
- Clean. Strip client names, figures, and anything you would not want stored in a settings field.
You should now have three text files or three pasted blocks, each 200 to 400 words, that you would be comfortable putting your name on.
Codify Your Voice Into Concrete Rules
Now you ask the model to do the analysis you would struggle to do yourself. Reading your own writing for patterns is genuinely hard — you are too close to it. A model counting sentence lengths across three samples is both faster and more honest than your impression of how you write.
Run the extraction prompt on your samples
You are a copy editor analysing my writing style. I am giving you three samples of my own work. <sample_1> [paste sample 1] </sample_1> <sample_2> [paste sample 2] </sample_2> <sample_3> [paste sample 3] </sample_3> Analyse these and return a style rule sheet with exactly these five sections: 1. SENTENCE MECHANICS — average sentence length in words, longest and shortest, how much variation there is. 2. STRUCTURE — how I open a piece, how I close, typical paragraph length, whether I use lists. 3. VOCABULARY — words and phrases I use repeatedly; the register I write in; contractions or not. 4. PUNCTUATION AND FORMATTING — my habits with dashes, semicolons, questions, bold, and emphasis. 5. WHAT I NEVER DO — patterns absent from all three samples. Rules must be countable or checkable. Do not describe my tone with adjectives like "professional" or "engaging". If a pattern appears in only one sample, say so rather than presenting it as a rule.
Read what comes back before you accept it. The model will occasionally invent a pattern that isn’t there, or miss one that is. Delete anything you disagree with and add anything obvious it skipped. This edited sheet is your voiceprint, and it is worth ten minutes of care.
What the extraction step actually produces: countable rules, not adjectives.
One thing the rule sheet cannot do alone: rules describe, examples demonstrate. Keep your shortest sample attached alongside the rules, so the model has both the instruction and the proof. That pairing is ordinary few-shot prompting, and it is the single highest-return habit in this whole workflow.
Anthropic’s own prompting documentation recommends three to five examples for reliable results and suggests wrapping each one in labelled tags so the model can tell examples apart from instructions. That is why the extraction prompt above uses tags rather than dumping three blocks of text in a row. If you want a starting library of prompt structures like this, the free AI work templates cover the common professional formats.
You should now have a one-page rule sheet with roughly 10 to 20 specific, checkable rules, plus one short sample you are keeping attached to it.
Carry Your Rules Into Every Session
This is where the system either holds or quietly collapses. If your voiceprint lives in a note you paste manually, you will paste it for about a fortnight and then stop. Every major tool has a settings field that loads automatically instead, and all three of them are available without paying.
Store the rules where they load automatically
Anyone trying to scale content production with AI hits this wall in week two. The technique works; the discipline of re-pasting it does not. Moving the voiceprint from a document into a settings field is what turns forty minutes of setup into something that keeps paying out.
| Tool | Where the rules live | Availability |
|---|---|---|
| ChatGPT | Custom Instructions, under Personalization | All plans, including free |
| Claude | Project instructions, or account-wide instructions | Projects available on the free plan |
| Gemini | A custom Gem you create once | Free for all Gemini accounts |
Worth knowing before you write: OpenAI’s documentation puts a 1,500-character limit on Custom Instructions for Free and Go accounts, rising to 5,000 on Plus and above. If you are on free, that budget forces useful discipline — cut the explanation and keep only the rules.
The same voiceprint, stored three different ways. None of them require a paid plan.
Setting It Up in ChatGPT
Open Settings, go to Personalization, and check that customisation is switched on before you paste anything. The rules go in the field describing how you want responses written. Full detail on the field behaviour lives in our guide to ChatGPT Custom Instructions.
The ChatGPT Personalization screen with the Custom Instructions panel open, showing the response-style field with voice rules pasted in.
Crop to the settings modal only. Hide the account email, avatar, and the chat history sidebar.
File: chatgpt-custom-instructions-voice-rules.png · Alt: "Voice rules pasted into the ChatGPT Custom Instructions field"Setting It Up in Claude
Create a project for the brand or client, then paste the rule sheet into the project instructions and attach your sample as a project file. Because instructions are scoped per project, this is the cleanest option if you write in more than one voice. Our walkthrough of Claude Projects covers the rest of the setup.
A Claude project with custom instructions filled in and a writing sample attached as project knowledge.
Crop to the project settings panel. Hide the project list, organisation name, and any client names in file titles.
File: claude-project-voice-instructions.png · Alt: "Brand voice rules saved as Claude project instructions"Setting It Up in Gemini
Build a Gem, paste the rules as its instructions, and upload your sample during setup. Gems have been free for all Gemini accounts since early 2025, which makes this the lowest-friction option if you already work inside Google Workspace. The steps are in our guide to creating Gemini Gems.
Whichever tool you pick, the block you paste is the same. Here is the shape that works:
When you write anything for me, follow these rules. VOICE RULES - Average sentence length: [your number] words. Vary between [short] and [long]. - Open with [your opening habit]. Never open with a rhetorical question. - Paragraphs: [your number] sentences maximum. - Use contractions. Use first person. - Never use: [your banned words, comma separated]. - Never use em-dashes or semicolons. HOW TO WORK - Match the sample below for rhythm and word choice, not for topic. - If a rule and my request conflict, follow my request and tell me which rule you broke. - Do not add a summary paragraph at the end unless I ask for one. VOICE SAMPLE [paste your shortest sample here]
You should now be able to open a brand new chat, type a plain request with no style instructions at all, and get back something that reads like you wrote it.
With the voiceprint loading on its own, your per-piece prompt gets much shorter. You brief the substance and let the settings handle the sound:
Draft section [number] of a piece for [audience]. The point of this section: [the one thing the reader should take away]. What I already know that most people writing about this do not: [your actual insight]. Length: [word count]. Format: [prose / prose with one list / steps]. Do not restate the section heading before starting. Do not add a closing summary. Follow the voice rules already in your instructions. If something in this brief conflicts with them, follow the brief and tell me which rule you set aside.
Notice how little of that prompt is about style. That is the point of the whole exercise — style moved into storage, so the thing you type each time is the thinking.
Build Your Anti-Slop Constraint Block
The rule sheet tells the model what to do. A banned list tells it what to stop doing, and in practice the second one moves the needle faster. Models default to a small set of filler words and structural habits, and naming them explicitly removes most of the machine-made feeling in one pass.
Build your list from your own drafts rather than copying someone else’s. Read the last three things AI produced for you and write down every word that made you wince. That list will be more accurate than any generic version, and it will keep growing.
✕ Generic ban list
Avoid clichés, buzzwords, and overly formal corporate language. Keep it natural and human.
✓ Specific ban list
Never use: testament, landscape, robust, myriad, elevate, unlock, journey, tapestry. No sentence may begin with Moreover or Furthermore.
Structural bans matter as much as vocabulary ones. Banning em-dashes, three-item lists as a reflex, and the “it’s not X, it’s Y” construction changes the rhythm of the output more than any word swap will. We go deeper on this in our guide to negative constraints as a prompting technique.
Keep the list in the same settings field as your voice rules rather than pasting it per request. Here is the block to add underneath them:
NEVER USE THESE WORDS [list your ten worst offenders here, comma separated] NEVER USE THESE STRUCTURES - Em-dashes. Use a full stop or a comma instead. - The construction "it's not X, it's Y". - Three-item lists used for rhythm rather than because there are three things. - Opening a section with a rhetorical question. - Closing a section by summarising what you just said. IF YOU BREAK A RULE Say so in one line at the end, naming the rule. Do not silently comply by writing awkwardly around a banned word — rephrase the sentence properly instead.
Two cautions on ban lists.
- Keep it under about fifteen items. Past that, compliance drops and the model starts writing awkwardly to avoid words rather than writing naturally.
- Review it monthly. As models change, their tells change. A list built a year ago bans words the model no longer reaches for and misses the ones it does.
Is It Safe to Paste Client Work?
Your writing samples are the input to this whole system, which means you need to think about where they end up. The line that actually matters is not free versus paid — it is a consumer account versus a business or enterprise one.
On consumer plans, the default across the major tools is that your content may be used to improve models unless you opt out in settings. Business and enterprise accounts generally exclude your content by default. Both Claude’s published plan comparison and OpenAI’s plan documentation draw the line in exactly that place, and paying twenty dollars a month for a personal account does not move you across it.
Published work, your own blog posts, sent newsletters, public marketing copy.
Client emails, internal memos, proposals with named accounts or figures.
Anything under NDA, unreleased financials, personal data about staff or customers.
The practical answer for most people: choose published pieces as your samples. Published writing is already public, it usually represents your best voice anyway, and it removes the question entirely. If you do need to use internal work, anonymise before you paste, not after. Our fuller treatment of using AI safely with work data covers the settings side.
When the Voice Drifts Mid-Draft
Even with everything set up correctly, long drafts wander. The first few hundred words match your voice, and then somewhere around the middle it slides back toward the generic default. This is normal, it is predictable, and it has a fix.
| What you notice | Why it happens | What to do |
|---|---|---|
| Voice fades after 800 words | Early instructions lose weight as the draft grows | Generate section by section, not all at once |
| Banned words creep back in | The list is too long to hold reliably | Cut the list to your ten worst offenders |
| Output is stiff and over-formal | Rules present, sample missing | Attach a real writing sample alongside the rules |
| Every draft sounds identical | One sample dominating the pattern | Rotate which sample you attach |
| Rules ignored entirely | Settings field switched off | Check the customisation toggle is on |
Three questions that identify almost every drift problem before you start rewriting.
When drift shows up mid-draft, do not start a fresh chat and lose the work. Re-anchor in place instead — it takes one message and usually recovers the piece.
Stop. Before continuing, re-read the voice rules and the sample in your instructions. Then do two things: 1. Rewrite the last two sections so they follow those rules. Do not change the argument, only the sentences. 2. List which specific rules the drafted text broke. Continue from there, checking each new section against the rules before you write it.
If re-anchoring does not fix it, the problem is usually the rule sheet rather than the model. Vague rules produce vague compliance. Our guide to refining AI output diagnostically walks through isolating which instruction actually caused the gap.
What This System Cannot Do
Everything above solves one problem well: it lets you scale content production with AI while keeping your sentence-level signature intact. It is worth being clear about what it does not solve, because the gap is where scaled content usually goes wrong.
Four things this will not do for you.
- It will not give you something to say. Voice is how you sound. The argument, the opinion, and the original observation still have to come from you, and readers notice the difference between on-brand writing and writing with a point.
- It will not preserve your judgement. The model does not know which client detail is confidential, which claim needs legal review, or which joke lands badly with this audience.
- It will not survive without maintenance. Models change, your writing changes, and a voiceprint built once and never revisited slowly stops describing you.
- It will not make unedited output publishable. Expect a real editing pass. What changes is that the pass is now about substance rather than about tone repair.
Most professionals who scale content well use AI for the parts that are mechanical — structure, first drafts, format conversions — and keep the thinking on their side of the line. That division holds up. The shift toward context engineering is really this idea generalised: managing what the model knows beats rewording what you ask it.
Most professionals who scale content production with AI successfully treat the voiceprint as infrastructure rather than a trick. Build it once this week. Use it on the next three things you write, and adjust the rules where the output disagrees with your instinct. From there it compounds — the same profile powers repurposing one article into several pieces and keeps longer blog drafts sounding like a person wrote them.
Build your voiceprint this week
- Pick three pieces you already wrote and were happy with, 200 to 400 words each Run the extraction prompt and ask for countable rules, not adjectives Edit the rule sheet by hand — cut invented patterns, add the obvious misses Paste the rules plus your shortest sample into your tool's settings field Draft section by section on long pieces, and re-anchor the moment voice slips