In partnership with
Most people who complain that their writing tool sounds robotic have not taken the time to teach it anything. They type a vague request, get a vague result, and blame the tool. That is not a tool problem. That is a setup problem.
Claude can learn your writing voice. Your rhythm. The specific way you open a paragraph or close an argument. But it needs you to show it what good looks like. This issue walks you through doing exactly that, from the right model to a daily workflow that actually holds.
Pick the Model That Fits Your Work
Claude comes in different versions, and choosing the right one upfront saves you a lot of friction. Here is how they break down for writing work.
|
Claude Opus 4.5
The most capable model available. Best for high-stakes work like board presentations, major client proposals, or articles going to a large audience. Use it when the quality ceiling genuinely matters. |
Claude Sonnet 4.5
The best option for everyday writing. Available on the free plan. It handles nuance, recognizes patterns, and holds context across long conversations. For style training, this is your starting point. |
Think of Opus 4.5 as the specialist you bring in for one critical project. Sonnet 4.5 is the reliable writer who handles everything else and does it well. Both are accessible through claude.ai, on web, mobile, and desktop.
700+ teams have Viktor reading their Google Ads every morning.
Your media team opens Slack at 8am. There's a cross-platform brief in #growth: Google Ads spend vs. ROAS, Meta CPA by campaign, Stripe revenue by channel. Viktor posted it at 6am. Nobody asked for it.
Last week, one team's Viktor caught a spend spike at 2am on a broad match campaign and flagged it in Slack: "CPA up 340%. Recommend pausing and shifting budget to the top two performers." That would have burned $3K by morning. The media buyer woke up to a problem already handled.
Your strategist reviews spend trends. Your account manager checks revenue attribution. Same Slack channel, same colleague, before anyone's first coffee.
Google Ads, Meta, Stripe. One message. No Looker, no Data Studio. Anomaly detection runs around the clock. Cross-platform reporting runs on autopilot.
5,700+ teams. SOC 2 certified. Your data never trains models.
"Viktor is now an integral team member, and after weeks of use we still feel we haven't uncovered the full potential." — Patrick O'Doherty, Director, Yarra Web
Build a Project, Not Just a Conversation
One of the biggest mistakes people make is treating every session like a fresh start. They re-explain their preferences each time, wonder why nothing sticks, and eventually give up. The fix is Projects.
A project is a persistent workspace inside Claude that holds your instructions and writing examples across every conversation within it. You set it up once. Claude references it every time. No more starting from scratch.
What Goes Inside Your Project
- → Upload five to ten of your strongest writing samples. Real emails, memos, newsletters, or posts that got results.
- → Include variety. If you write both client-facing content and internal updates, include both so Claude learns the difference.
- → Write a personal style guide. Note what you always do and what you never do: sentence length, jargon, how you open and close.
- → Add a clear instruction in the custom instructions field. Something like: "Match my tone, sentence structure, and word choices. Reference my samples whenever you draft content."
- → Name the project clearly. "My Writing Style" is fine. Clarity beats cleverness here.
Write Your Master Style Prompt
The examples you upload teach Claude your patterns. The style guide makes those patterns explicit. But the master style prompt is where you bring everything together into one clear instruction set. This lives in your project's custom instructions or at the top of any important conversation.
The most useful prompts cover all the small details people rarely think to document: which words you never use, how long a typical paragraph runs, whether you lean on questions to engage readers, how you prefer to close. Claude needs the specifics. Vague instructions produce vague results.
What Your Prompt Should Cover
Voice and tone. Sentence length and rhythm. Words you never use. Paragraph structure. How you open and close. Whether you use humor. Here is a practical example you can adapt:
The more specific you are, the more consistently Claude matches your voice.
The Best Place to Invest $1,000 Right Now
This AI tech could go down in history as the crown jewel of Elon's career. It could send ChatGPT offline forever and trigger a 70X investment boom. Watch the free presentation.
Train Through Correction, Not Just Setup
Setting up your project is the foundation. But the real training happens in the feedback you give. When Claude writes something that doesn't sound like you, do not just say "this doesn't sound like me." Point to the exact line and say what you would write instead.
"I wouldn't say 'our analysis revealed the following findings.' I'd write 'here is what we found.'" That kind of correction is specific enough for Claude to learn from and apply consistently going forward.
Keep correcting. Your voice sharpens with each iteration.
Keep It Current
Your writing evolves. Your project should too. When you write something you're proud of, add it to your examples. If you start writing for a new audience or shift to a different format, update your instructions to reflect that.
In longer conversations, Claude can sometimes drift toward a more generic tone. A quick prompt brings it back: "That's getting too formal. Back to my usual style." It recalibrates immediately.
You can also ask Claude to flex your voice without abandoning it. "Write this in a more formal version of my style" or "keep my directness but soften it for this audience." The core voice stays yours. The register adjusts to fit the moment.
The setup takes a few hours. The refinement takes a few weeks. After that, you spend ten minutes editing instead of an hour writing from nothing.
The tool isn't the problem. The lack of training is. Now you know how to fix it.
Get started at claude.ai.
