This is what a voice profile actually looks like.
Not a tone setting. Not three adjectives. A document that measures your rhythm, names your moves with your own sentences as evidence, and itemizes what you never do. Below: a real one, in full, and the before-and-after it produces on an ordinary status update.
The profile is Leigh's, the founder's, shown with the evidence intact. We'd never publish a customer's: your profile is private, which is rather the point.
Declarative and front-loaded. States the position in the first sentence, spends the rest earning it. Prefers the concrete noun to the category, the number to the adjective. Warmth arrives through specificity, not through softeners. Ends on a landing, never a taper.
Builds in a long sentence, lands in a short one. A one-word sentence appears roughly once per page, always after the longest sentence in the section. Commas light; semicolons almost never.
- Decision first, context second. Strong "We're moving the launch to March. Here's what changed."
- The named number over the vague claim. Strong "Four of the six vendors missed the date. Not 'most.'"
- The colon that hands over the goods. Moderate "One thing actually matters here: the renewal date."
- A dry aside, one per document, never two. Tentative "The vendor calls this a feature. The vendor is alone in this."
- Openers that greet the weather: "I hope this finds you well."
- Stacked hedges: "could potentially help somewhat."
- The triad reflex: "faster, cheaper, and more efficient."
- Buried asks. If there's a request, it appears by line two.
- Exclamation points in anything a boss will read.
Email: ask in the subject line where possible. The deck talk track: shorter sentences still, one idea per beat. The status update: decision, number, blocker, in that order. LinkedIn: the dry aside gets one more seat at the table.
9 samples · 4 formats · 212 sentences read · assembled July 12, 2026 · every claim above traces to a sentence Leigh wrote. Exported as a plain file the day it was built.
The same request, twice.
One status update, asked for the same way both times. Left: the model on its defaults. Right: the model with the profile above in front of it. Nothing else changed.
I hope everyone had a great week! I wanted to provide a quick update on where things currently stand with the Meridian migration project.
Overall, we are making solid progress across multiple workstreams. The data validation phase is largely complete, and we are seeing encouraging results. However, it's worth noting that there are some potential challenges that could possibly impact our timeline, particularly around vendor deliverables, which we are actively monitoring.
We will continue to keep everyone updated as things progress. Please don't hesitate to reach out with any questions!
Meridian slips two weeks. Here's why and what I need.
Data validation finished Tuesday, clean. The slip is entirely the vendor: three of their five deliverables missed Friday, and their revised dates put integration testing into the December freeze. I've moved testing to January 6 rather than rush it into four working days.
One thing I need from this group: approval to hold the January date at Thursday's steering call. Everything else is handled.
Read the left one as the Director receiving it. Now read the right one. That's the whole product, in one screen.
Yours is buildable in an afternoon.
The Voice Kit is the worksheet, the builder that runs in your account, and the filled instruction you leave with. The profile is a file you own, exportable the day you make it, and it works in Copilot, Gemini, Claude, ChatGPT, or whatever your company rolls out next. One price, once. Nothing renews.
Get the Voice Kit · $19or start with the free check →