How to Give an AI Assistant Your Brand Voice

Give an AI assistant your brand voice by supplying real writing samples, turning their recurring choices into clear instructions, and testing those instructions on a new topic. Include the business facts and evidence behind the writing so the assistant can preserve your judgment as well as your phrasing.

For this exercise, think of brand voice as the choices you want to recognize across your work: how you explain a problem, address a reader, support a claim, and finish a thought. “Warm, smart, and authentic” might describe your intention. It does not tell an assistant which sentence you would keep.

The goal is a short, usable brief with examples you trust. Follow these five steps, then keep the brief beside the drafts you actually review.

Which real writing samples should you supply?

Choose pieces you would be happy to publish again in your current voice. Start with three to five examples as a manageable editorial exercise, not a scientifically established minimum. Include different jobs: explaining something, disagreeing with a common assumption, and inviting a reader to take a next step.

A popular post is not automatically your best voice sample. You might like its topic while disliking the exaggerated opening you wrote under pressure. Pick the writing choices you want repeated, then annotate why.

For each sample, supply:

• The text: enough of the complete piece to show how the argument develops.
• The reader: who it was written for and what they needed.
• The useful choices: specific sentences, transitions, or explanations worth preserving.
• The exceptions: a joke, format, or phrase that should not become a universal rule.
• The factual boundary: which details belong only to that particular story.

Anthropic's prompting guidance recommends relevant, varied examples and clear separation between examples and instructions. You can use plain labels such as “Sample A” and “What to preserve” to make that separation readable.

If you have little published work, create a starting sample yourself. Answer a customer question as you would in a thoughtful email. Explain why you recommend one choice over another. Read it aloud and edit the parts you would never say. Remove private customer details before sharing it.

Keep outside inspiration in a separate section. Another creator's post can help identify an audience question, but it should not become evidence of your personal voice or experience. The guide to turning outlier posts into original content ideas explains how to make that distinction during research.

Try this first request:

Read the labeled samples below. Identify writing choices that recur across them, and cite the sample that supports each observation. Separate recurring choices from one-off devices. Do not draft a new post or save instructions yet. Treat anecdotes and results as facts about their original context only.

Read the analysis as a proposal. If the assistant finds a pattern you dislike, say so. Your old writing is evidence to examine, not a contract requiring you to keep every habit.

How do you extract useful voice rules without copying a formula?

Turn each accepted observation into a rule someone could apply while editing. Pair it with an example and an exception. Avoid rules so broad that any polished business post would satisfy them.

Here is an illustrative translation for a fictional consultant who helps small service businesses improve client onboarding:

Vague preference	Usable editing instruction	Boundary
Be practical	Name a decision the reader can make before introducing a framework	Do not force every post into a checklist
Sound confident	State the recommendation and explain the reason	Preserve uncertainty when the evidence is incomplete
Be conversational	Address one reader and use familiar words	Keep necessary technical terms and explain them
Avoid hard selling	Describe who the offer helps and the next step	Do not hide a genuine invitation behind a vague closing question

Those are sample rules for this fictional business, not a template every entrepreneur should adopt. A researcher, designer, and fitness coach may need very different ways to explain uncertainty or show their work.

Use a before-and-after pair to make a rule concrete. For the consultant, compare these invented lines:

Too broad: “Transform your onboarding with a seamless process that delights every client.”

Closer to the intended voice: “Before the first client meeting, agree on the decision you need to leave with.”

The revision names an action and avoids promising a universal result. It does not establish that every post should begin with “Before.” Tell the assistant which choice matters, or you risk preserving the sentence pattern instead of the reasoning.

Keep the first brief short enough to review in one sitting. Ask for a handful of rules supported by the samples, plus any unresolved contradictions. “Use short sentences” and “explain the tradeoff fully” can coexist if the brief makes clarity the priority rather than imposing a rigid sentence length.

A useful follow-up prompt is:

Convert the observations I approved into a concise voice brief. For each rule, include the writing behavior, a supporting example, and when the rule should not apply. Do not invent catchphrases, personal opinions, or a mandatory hook formula. Show disagreements between samples for me to resolve.

What business context belongs beside your voice rules?

Keep style guidance separate from business facts. A voice rule describes how to explain something. A business brief establishes what you can truthfully say, who it serves, and what you want this particular piece to accomplish.

For each drafting task, provide the intended reader, their immediate question, your position, the supporting material, and the desired next step. Add current offer details only when they matter. A helpful educational post may end with something the reader can try without buying anything.

A compact brief can use these fields:

1. Reader and situation: an independent consultant preparing a first client meeting.
2. Question: what should be agreed before writing the agenda?
3. Position: agree on the decision the meeting must produce.
4. Evidence: the author's own approved process notes, supplied separately.
5. Next step: try the question before the next meeting.
6. Constraints: no invented client story, numerical result, testimonial, or offer promise.

This is an illustrative brief. Replace its position and evidence with your own before requesting a draft. If your evidence does not support a claim, narrow the claim or leave it out.

For reuse in Claude, Projects documentation describes uploaded project knowledge and instructions used across chats within the project. Put the approved voice rules in the instructions and the labeled samples in reference material. Supply changing priorities and current facts with the task rather than burying them inside permanent style rules.

We make Distinctful, a social media scheduler for entrepreneurs with or without a newsletter. Its MCP tool reference documents reading positioning, audience, and voice rules through get_content_strategy; it also distinguishes dated drafts from scheduled publication. That can put existing business context beside an assistant's drafting work, but a draft or plan still needs a separate publishing instruction, and the product does not send newsletters.

Whatever tool you use, ask the assistant to summarize the context it actually has. Do not let “I understand your business” stand in for a concrete statement of the audience, evidence, and task.

How do you test a draft against the original evidence?

Give the assistant a new topic that your samples do not already answer. This checks whether the brief guides a fresh explanation rather than producing a paraphrase of a favorite post.

Ask for one complete draft and a separate list of claims that need checking. Review the draft yourself before reading the assistant's explanation of why it fits. You want to notice the language as a reader would encounter it.

Use this review checklist:

• Does the opening answer or frame the actual audience question?
• Can each factual claim be traced to the supplied material or a checked source?
• Does the draft express a position you agree with?
• Which phrase would you never use in conversation or publish under your name?
• Did it copy a distinctive line, anecdote, or structure from a sample unnecessarily?
• Does the ending suit this post's purpose rather than automatically asking for engagement?

Mark the exact sentence that fails and explain the correction. “This is not my voice” gives little direction. “Replace the promise that every client will be delighted with the decision the reader can make” gives the next draft a concrete target.

Then test a different writing job. An educational explanation and an offer invitation need not sound identical. If the rules make both stiff or evasive, revise the rules instead of adding another layer of instructions to compensate.

Keep factual review separate from stylistic approval. A sentence can sound exactly like you and still contain an unsupported claim. Ask the assistant to leave missing evidence visible, then supply it or remove the claim before publication.

When you move from reviewing prose to scheduling it, follow a separate publication check. The Claude scheduling walkthrough covers confirming the complete text, destination, timing, and saved state. Approving a voice brief does not approve every future post written with it.

How do you update instructions without losing useful constraints?

Save the approved brief with a simple version date and a note explaining the latest change. Keep the original samples available so future edits have something concrete to refer to.

After a useful correction, decide whether it belongs in the permanent brief or only in the current draft. “Explain specialist terms on first use” might apply broadly. “Mention Thursday's workshop” belongs to a particular task. Promoting every local edit into a permanent rule creates instructions that are difficult to understand or reconcile.

Ask for a proposed revision before replacing the brief:

Update only the rule affected by this correction. Show the old wording, proposed wording, and reason. Preserve the audience, factual boundaries, and other approved rules. Flag contradictions instead of silently choosing which instruction to drop.

Test the revised brief on one earlier writing job and one fresh one. Check whether the correction helped without removing useful detail or flattening the tone. This is a practical editorial check, not proof that all future drafts will match your voice.

Finally, start a new conversation in the place where you saved the instructions. Ask the assistant to identify the available rules and examples, then write a small draft. Correct any missing context before depending on the setup for a full week of content.

A useful voice brief earns its place by making review easier. Keep the rules that help you make decisions, remove duplicated advice, and retain examples that explain the difference between acceptable writing and writing you would actually publish.