All guides
In Hone Studio·11 min read

Voice Training: Teaching Hone Your Firm's Tone

Voice doesn't transfer in instructions — it transfers in artifacts. A four-stage cycle for teaching AI to write the way your firm sounds, and the three surfaces voice actually lives on.

TB

Todd Burner

Founder, Hone Labs

Twenty minutes into the brief, you realize you're typing the same paragraph you typed last week. And the week before. Three sentences about how your firm hedges. Two about your audience. One about formatting. Voice instructions, on repeat, every prompt. Forever.

This is the part of AI nobody warned you about. The model is fine. The retrieval is fine. The problem is that every session starts at zero. Everything you taught the chatbot yesterday is gone today. Whatever it picked up from the last ten drafts vanished with the chat.

Generic chatbots are senior associates you fire every thirty minutes. Voice training is the practice of breaking that loop — keeping what you teach, compounding it forward, getting back the leverage that should have been yours from the start.

To do that well, it helps to understand how voice actually transfers between people in the first place. When a senior partner trains a new associate, voice doesn't transfer in instructions. It transfers in artifacts.

Voice lives on three surfaces

Ask a senior partner — twenty years in, hundreds of clients deep — what makes their firm's voice different. They'll pause, then list four or five things. Concrete. Specific. Articulable. "We never lead with the company name. We hedge in adverbs, not main clauses. We end on a turn." Then they'll say: "But honestly, mostly... you read 200 of our memos and you'll just know."

That last sentence is the whole problem — and the whole map. Voice in senior practice is partly rules, partly cadence, mostly pattern recognition built up over years. It lives on three different surfaces. Most people write down the first. Some upload the second. Almost nobody captures the third on purpose. The third is where the deepest signal lives.

Surface 01

Explicit

Instructions

Rules you can articulate. "We hedge in adverbs." "Never lead with the company name." Five to fifteen of these per firm.

Surface 02

Demonstrated

Examples

Actual finished work. The rules in motion. The cadence between the rules. Where roughly 80% of voice signal actually lives.

Surface 03

Accumulated

History

Every prior draft. Every edit. Every "no, like this." The deepest layer. Almost nobody captures it on purpose.

A firm that has only Surface 01 sounds like a brand-guidelines PDF. A firm with 01 and 02 sounds like itself, mostly. A firm with all three is the senior associate at month six — the one whose drafts you can't tell apart from a partner's.

Why generic AI never quite gets there

The structural reason generic chatbots fail at senior-practice voice isn't that the model is too small or too generic. The model is fine. The problem is that every session starts at zero. The voice you described yesterday is forgotten today. The thirty edits you made on last week's draft never made it into anywhere the next session can see.

You compensate by stuffing voice instructions into every prompt. Three paragraphs of context, every time. The voice description eats most of your prompt budget. The actual task gets a sentence at the end. The model dutifully follows instructions and produces something that sounds described rather than embodied.

What fills the AI's context window every session

Generic AIstateless
Voice instructions you retype
Today's task
Trained instancestateful
Rules
Past work
Edit history
Today

The trained instance carries more context, but more importantly it carries the right kind of context. Examples beat rules. Fifty memos sitting in retrieval tell the model more about your voice than any list of stylistic instructions can. Both Anthropic's and OpenAI's public prompting guidance points the same direction: when you want a model to adapt to a specific style, show it, don't tell it.

Voice is a frequency, not a syntax. You can't describe a frequency. You can only let the model hear enough of it.

In Hone Studio

The Knowledge Base holds your past work — every memo, brief, or release you upload sits in retrieval at draft time. The Memory module holds explicit rules — voice notes, constraints, do/don't preferences. Both feed every Assistant conversation automatically. You don't re-establish voice every prompt; you've already taught it once. Single-tenant infrastructure means none of that voice signal ever mingles with another firm's training data.

The voice training cycle

Once your AI has memory and retrieval, voice training stops being a prompt-engineering problem and becomes a habit. Four stages. Each small. Repeated, they compound into something nobody else has.

↻ The cycle

01

CURATE

Pick documents

02

TEACH

Add rules

03

USE

Generate drafts

04

CORRECT

Save fixes

Stage 04 loops back to 01. New corrections seed new curated patterns over time.

01 · Curate

Pick 10–20 documents that represent your firm at its best. Not all your work — your best work. The memos partners forwarded as templates. The releases the client never edited. The decks that landed the account. Quality over volume by an order of magnitude. Twenty exemplars beat two hundred mediocre drafts every time.

02 · Teach

Write down the rules you can articulate. Five to fifteen of them. Not a brand-guidelines document — that's marketing. Operational rules. "Stakeholder messages: opening sentence is two clauses, max twenty-six words." "Never use ‘leverage’ as a verb." "Internal updates to clients always end on a forward turn — what we'll do next, not what we just did." These rules surface what you've been doing unconsciously. Writing them down forces clarity and gives the model an explicit floor to work from.

03 · Use

Give the AI a task in your real voice — short, brief, the way you'd ask a senior associate. Not a paragraph of instructions. A one-sentence ask. The AI is supposed to know what your firm sounds like by now. If it doesn't, the issue isn't the prompt. It's the training data underneath.

04 · Correct

When the draft misses, don't just edit and move on. Edit, then write the rule. "Next time the audience is investors, the opener names the dollar figure first." The correction becomes a memory note, not a footnote in your brain. The next time the AI drafts an investor message, that rule is already loaded. You taught the model once; it carries the lesson forward.

Stage 04 is where most people break the cycle. They correct in their head and never write the rule down. Six weeks later, the same blunder keeps coming back. The discipline is small — thirty seconds to save a memory note — and the leverage is enormous. Every saved correction becomes a permanent floor.

In Hone Studio

Curate by uploading your 10–20 best documents to the Knowledge Base. Teach by opening Memory and adding voice rules as notes. Use by asking the Assistant to draft — both surfaces feed in automatically, no special invocation required. Correct by writing the missed rule as a new memory note. Subsequent drafts pick it up on the next turn. The cycle takes about three minutes a week to maintain after the initial curate. The Assistant you have at month six is materially different from the one you had on day one — that difference is your firm's voice.

What "trained" actually looks like

The visible difference shows up in two places. First, your prompt gets shorter — a one-line ask replaces three paragraphs of voice explanation. Second, the first draft is closer to final. Less rewriting. Less "this isn't quite right but I can't put my finger on it."

Before · Generic AI

Your prompt

Write a stakeholder memo announcing our merger with Ricci Communications. Use concise active sentences. Hedge in adverbs, not main clauses. Don't lead with the company name. End with a forward-looking turn. Audience: current clients, mostly mid-sized B2B and a few late-stage startups.

Output

We're announcing today that Henderson Strategic and Ricci Communications have agreed to merge. The combined entity will leverage both firms' deep client relationships and complementary expertise to deliver enhanced strategic value across markets. We're excited about the opportunities this creates for our clients.

Generic. Bullet-shaped. "Leverage," "deliver enhanced," "excited about the opportunities." Sounds like a company. Doesn't sound like your firm.

After · Trained Hone

Your prompt

Stakeholder memo: Henderson + Ricci merger. Audience: current clients.

Output

Henderson and Ricci will operate as a single firm starting July 1. For your day-to-day work, nothing changes — your team stays, your contracts stand. What does change is the bench you can pull from when you need it, quietly, without the friction of a referral. We'll send the formal announcement Tuesday; we wanted you to hear it from us first.

Concrete. Anti-corporate. Acknowledges the client's actual question — "what changes for me?" — before answering. Ends on a turn. Sounds like the firm.

The improvement isn't that the model got smarter between Tuesday and Friday. The improvement is that on Friday, the model knows more about you. About what you've published. About what you've corrected. About what you call good.

Voice as compounding asset

The senior partner at the start of this piece — the one who said "read 200 of our memos and you'll just know" — was telling you exactly how voice training works. The mechanism is the same. The only difference is whether the entity learning is a person who'll eventually leave the firm or a system that won't.

For twenty years, every blue-ink edit a partner made on a junior draft taught one person, once. Then that person walked out the door and took the lesson with them. The work was real. The compounding wasn't.

Voice training shifts the geometry. Each correction — saved as a memory note, attached to a body of work in the Knowledge Base — accrues to the firm itself, not to a person. The senior associate at month six is now a system you keep. When the next associate joins, they marinate alongside it. When this one leaves, your voice stays.

The brief that took twenty minutes to write last week takes one line this week. That's the part that compounds.

Want to see this in your firm's context?

Book a 30-minute demo and we'll walk you through Hone Studio using your organization's actual work product.