AI sounds generic because it doesn't know you yet. Here's the one-page brief that fixes that, and where to keep it as tools change.

To make AI sound like you, give it a brief before you give it a task: who you serve, what you stand for, a few samples of your real writing, and the words you never use. AI sounds generic because it doesn't know you yet. Save that brief once, reuse it every time, and keep the final edit for yourself.
That's it. No magic prompt. No secret setting. Just a page about you that AI reads before it writes.
Here's how it usually goes. You're tired. You have a launch in eleven days and a kid with a science fair project that involves a potato. So you hand your Instagram captions to AI for a month. Then your welcome emails. Then your sales page.
At first it feels amazing. Everything gets done. Then, slowly, you notice it. Your captions sound like a motivational coffee mug. The replies dry up. A longtime customer emails to ask if you hired someone. And when you sit down to write something yourself, you're weirdly rusty, like you forgot where you keep your own opinions.
That's the outsourcing hangover. You handed off the work, and the part you handed off turned out to be the part that made you, you.
In 2006, as part of a rescue plan to cut costs during serious financial trouble, the LEGO Group outsourced a large share of its production to a manufacturing partner, Flextronics. It didn't go to plan. LEGO's own history page describes start-up problems that left the company short of molded parts and unable to meet customer demand, and says that in 2008 LEGO negotiated an agreement to end the partnership and bring production back into its own factories.
The line on that page I keep thinking about comes from the company's then chief operating officer: "The molding of bricks is a core competency, and that we should not hand over."
LEGO didn't stop working with partners. It figured out which part of the work was the brick, the thing nobody else could do the way it did, and kept that one close.
For a small business, the brick usually isn't the typing. It's the judgment behind it:
AI can absolutely do the typing. It can't invent your brick. When you hand it a task with no brief, it fills that gap with the average of everything it has ever read, which is why so much AI writing sounds like the same polite stranger.
Here's my position: the problem isn't that AI writes badly. The problem is that most people ask it to write before they've told it anything worth knowing. They use it like a search box. The people getting results brief it like a collaborator.
A good brief fits on one page and has six parts:
Then, every time you ask for a draft, add the real piece of work: the offer, the customer question, the launch date. Backstory, an example of good, and a real task. That combination is what turns a generic assistant into something that sounds like your business.
The good news this fall: the big assistants now share the same idea. You write your instructions once, save them, and reuse them. Claude, ChatGPT, and Gemini all call that a skill.
One caution, and it's the LEGO lesson again. OpenAI's migration guide says custom GPTs are being moved to plugins and will eventually stop working, without a public date yet. Gems are on the same path. Features change. So keep the master copy of your brief in a plain document you own, and paste it into whichever tool you're using this month. The brick stays with you.
Give AI the jobs that eat your evenings: first drafts of captions and emails, rewriting a dense paragraph so it breathes, turning voice notes into an outline, checking a draft against your brief and flagging anything that doesn't sound like you.
Keep the final read. Every time. Read the draft out loud and ask one question: would I say this to a customer's face? If not, fix it or toss it. That last pass is where your voice lives, and it's also how you avoid the hangover. If you want more on where the line falls, where AI helps in your business goes job by job.
The difference is usually obvious enough to be a little annoying.
AI isn't stealing your voice. It just never met you. Give it a page about who you are, keep that page somewhere you own, and keep the last read for yourself. For the bigger picture of standing out when everyone has the same tools, read how to stand out when everyone uses AI, and find more practical setups in building with AI.
Write a short brief before you ask for anything: who you serve, what you stand for, three samples of your real writing, and words you never use. Save it, reuse it every time, and do the final edit yourself.
AI fills any gap in your instructions with the average of what it has read. When it doesn't know your customer, your opinions, or how you talk, it defaults to polite, safe, and forgettable.
You don't need to train anything. As of October 2026, both let you save reusable instructions called skills, so you can include writing samples and style rules once and use them in every draft.
Keep the master copy in a document you own, then paste it into whatever AI tool you use. Features like custom GPTs and Gems are being replaced, and your brief shouldn't disappear with them.
Let AI handle first drafts and busywork, but keep your opinions, stories, and the final read. Those are the parts that make customers trust you, and they're hard to get back once you've handed them off.
Learn AI with Belles
Start with the library, then keep building with new trainings, templates and tools, plus a monthly build and Q+A with Lily.
Keep reading
All articles