Make your AI
sound like you.
Three ways to stop getting the average agent's email back, and start getting yours.
Voice is not just language.
It is judgment expressed through language.
Left alone, AI predicts the average. Ask it for an email and it writes the email the average agent would write, because that is what it was trained on.
It does not sound like you because you have not given it a specific human pattern to work from. That is a structural problem, not a prompting problem.
Today is three ways to give it your pattern. Each one goes deeper than the last.
From a one-off fix to a system that holds.
Mimic a Sample
Hand it one thing you wrote and ask it to match your patterns for a single email.
Beginner · The one-offReusable Voice Reference
Give it several examples and have it derive rules you can reuse across every draft.
Intermediate · RepeatableThe Operating System
Mission, decision rules, and canonical voice working together so the output is authored, not generated.
Full build · DurableGive it a sample. Ask it to mimic.
Here is an email I wrote that sounds like me: [PASTE EMAIL] Study the sentence length, word choice, structure, pacing, and how I give advice. Now draft an email about [TOPIC] using those characteristics. Do not copy sentences or facts from the example. Use it only as a voice reference. Before writing, ask me any questions you need about the audience, situation, and desired outcome.
Several examples. Let it find the pattern.
I'm going to give you several examples of my communication. Identify the recurring patterns in: - How I begin - How I organize information - How I explain trade-offs - Sentence length and rhythm - Words and phrases I naturally use - Language I avoid - How I establish authority - How my written and spoken voices differ Separate your conclusions into: 1. Written voice rules 2. Spoken voice rules 3. Language to avoid 4. Questions you should ask before drafting Every rule must be supported by evidence from my examples. Do not invent personality traits or make my voice more polished than it is. Keep your full output to 8,000 characters or fewer so it fits in a saved instructions field.
Two documents. Three layers.
Your Mission Statement and your Canonical Voice Reference build something the first two methods cannot: a system that knows how you decide, not just how you sound.
Asked to write an email, it does not start with word choice.
It moves through the sequence first. Only then does it draft.
- 1Who is receiving this?
- 2What is happening?
- 3What outcome matters?
- 4What would this person genuinely advise?
- 5What trade-offs need to be explained?
- 6Written or spoken channel?
- 7What language or behavior is prohibited?
- 8What information is missing?
- Only then should it draft.
After it drafts, it checks its own work.
Review this draft against my Mission Statement, Decision Rules, and Canonical Voice Reference. Check: - Does the advice reflect how I actually think? - Did you preserve my intent? - Does this fit my written or spoken voice? - Did you add hype, urgency, assumptions, or invented specificity? - Are there phrases I would not naturally use? - Is anything missing that should be clarified before this is sent? Revise only where the draft violates one of those standards. Do not polish it merely to make it sound more impressive.
The first method imitates the surface. The third teaches it the connection.
That chain is what makes the output feel authored instead of generated. Method one borrows your voice for an hour. Method three gives the tool your judgment to keep.
Start with one email today.
Build the system this month.
Use Method 1 tonight on the next email you have to send. Feel the difference between the average agent's draft and yours.
Then, when you are ready to stop rebuilding your voice in every new chat, we build the operating system together.
Authorship is the competitive advantage.