Type a question into Claude on Monday. Type a similar question on Wednesday. Get two answers that don't sound like they came from the same place, let alone the same business.
If that's happened to you, you've probably blamed the tool. Maybe you thought Claude was having an off day. Maybe you figured AI just isn't as smart as everyone says.
Here's the truth. The tool isn't broken. Nobody ever told it who you are.
The Part Nobody Explains to You
AI doesn't walk into the conversation knowing your business. It doesn't know your tone. It doesn't know you write short sentences, or that you can't stand the word “leverage,” or that your customers are busy parents who don't have time for fluff. Every new chat starts at zero. Claude is guessing at who you are and what you need. And guessing produces generic.
That's why your tenth prompt of the week sounds nothing like your first. The tool didn't get worse. You just never gave it anything to build on.
Think about hiring a new employee on their first day. You wouldn't hand them a blank desk and say “go write our newsletter.” You'd give them old newsletters to study. You'd tell them who reads it and why. You'd explain the voice you use and the topics you avoid. Without that, even a talented new hire produces something that technically works but doesn't sound like your company.
Claude is that new hire. Every single conversation. Unless you change that.
The Fix Is Simpler Than People Think
You don't need a better prompt. You need a permanent set of instructions Claude reads before it writes a single word, every time you open a chat.
Three things go into that file.
Who you are. What you sell, who you serve, and what you actually sound like when you're not trying to impress anyone.
How you write. Real samples of your past work, so Claude studies your rhythm instead of guessing at it.
How you work. The steps you actually follow. The structure you already use. The rules you don't want broken, even by accident.
Once that file exists, you stop re-explaining yourself every time you open a new chat. Claude already knows. You just ask.
A Real-World Example:Two Podcasters, Same Tool
Picture two podcast hosts, both using Claude to write their weekly show notes.
The first one, we'll call her Maria, opens a blank chat every Sunday night. She types something like “write show notes for this week's episode about burnout in small business owners.” Claude hands back something polished and professional. It reads fine. It also reads like it could belong to any podcast about burnout, anywhere, hosted by anyone.
Maria edits it for twenty-five minutes. She swaps a few phrases. She adds a joke that sounds like her. She still isn't thrilled with it, but it's Sunday night and the episode drops Tuesday, so she hits publish.
The second host, we'll call him Dave, built a Claude instruction file three months ago. It includes five of his old show notes, a short paragraph on his audience, and a note that says “I always open with a question, never a summary, and I never use the word ‘journey.'” Dave types one sentence about this week's topic. What comes back already sounds like him. He fixes two lines and he's done in eight minutes.
Same tool. Same Sunday night. Completely different outcome. The difference wasn't skill. It was that one of them gave Claude something to work from.
A Real-World Example:The Small Business Owner Drowning in Emails
Now picture a contractor named Frank who runs a small landscaping company. Frank uses Claude to write replies to customer emails, quotes, and the occasional social media post.
Without an instruction file, Frank types things like “write a polite email telling a customer their quote went up because materials cost more.” Claude gives him something correct but stiff. It sounds like it came from a corporate customer service department, not from Frank, who answers his own phone and knows half his customers by name.
Frank starts rewriting every reply to sound less robotic, which eats up time he doesn't have between job sites.
After building an instruction file with a few of his real emails and a short note about his tone (“I'm friendly but I get to the point, and I never sound like a call center”), the same request produces something Frank could send without touching it. He saves real time, the kind that matters when you're running a crew and answering emails from your truck.
This Isn't About Typing Better Prompts
A lot of people spend hours hunting for the perfect prompt. They collect lists of “magic phrases” that promise better output. They treat prompting like a secret code to crack.
That's solving the wrong problem.
The prompt was never the issue. Claude had nothing to work from in the first place. Give it your voice once, in writing, and you stop needing tricks. You stop hunting for the right words. You just ask for what you need, the same way you'd ask a coworker who already knows how you operate.
Why This Matters More Than People Think
Inconsistent output isn't just annoying. It costs time, and time is the one thing nobody gets back.
If you write five posts a week and spend twenty minutes fixing each one, that's almost two hours gone, every single week, just smoothing out something that should have sounded like you from the start. Multiply that across a year and you're looking at over a hundred hours spent rewriting AI output instead of doing the work that actually grows your business.
There's also a trust cost. When your content sounds inconsistent, your audience feels it, even if they can't name what's off. A newsletter that sounds different every week. A social post that doesn't match your usual tone. None of it is a disaster on its own. But it chips away at the sense that they know who you are.
Who Actually Needs This
If you're a podcaster writing show notes or scripts every week, this saves you from the Sunday night scramble.
If you're a content creator posting daily and tired of sounding like a template, this gives your output a personality again.
If you run a small business and use AI for emails, quotes, or social posts, this turns Claude into something closer to an assistant who already knows your business instead of a stranger you have to retrain every morning.
If you've ever stared at an AI response and thought “this isn't bad, but it's not me,” that gap is exactly what this fixes.
What Goes Into Building One
Building this file isn't complicated, but it does take some real material to work from. The best ones include:
- A handful of your past posts, emails, or scripts, the ones you're proud of
- A short, honest description of your audience and what they care about
- A few specific rules about your tone, including words you avoid and phrases you actually use
- The basic structure you follow when you create something, even if you've never written it down before
Most people already have all of this. It's just scattered across old emails, old posts, and habits they've never put into words. The work is pulling it together into one file Claude can actually use.
What I Build
I take what you already have, your past posts, your emails, your tone, the workflow you already follow without thinking about it, and turn it into one custom instruction file built for Claude.
You hand it over once. From that point forward, Claude already knows your voice before you type a single word. No more rewriting the same prompt five different ways. No more polishing generic output until it sounds like you. You open Claude, you tell it what you need, and you get something close to final on the first try.
If your week could use a few of those hours back, here's where to start:
Build a Custom Claude AI Skill for Your Business Workflow
Send a few examples of your work. I build the file. You start using it the same day.
Joe Foley
Joe Foley is the creator of AI for Ordinary People. He helps beginners, parents, creators, and small business owners use AI in simple, practical ways. Joe has been podcasting since 2013 and creates plain-English guides, prompts, and workflows for people who want useful help without tech jargon. His goal is to make AI feel less confusing and more useful for real life, real work, and everyday decisions.