<aside> 🛡️
+10% Revenue Per Visitor in 90 days. Or we refund the engagement. Book a teardown
</aside>
The shortcut after all the tools: the five things the operators actually winning with AI do first. None of them is a model or a connector. Start here this week.
Brands buy the whole stack and still ship AI copy that reads like a robot wrote it. The tools were never the moat. The pattern underneath is. After everything in this cookbook, here is what separates the operators pulling ahead from the ones sitting on a tab full of subscriptions. Do these in order. The first two are free, take about a week, and make every recipe in this doc land harder.
The highest-ROI move in here, and almost nobody does it.
Most people write a sharp prompt, get a good output, then close the tab and lose it. Next week they rebuild a slightly worse version from scratch. The operators ahead keep their best prompts in one place, named, with the inputs they take and the output they produce. They treat them like SOPs.
Every prompt in this cookbook (the LP teardown, the VoC mining block, the Meta PAS ad prompt, the CRO audit) belongs in that library the first time it works for you.
| What to log | Why it matters |
|---|---|
| The prompt itself, named (e.g. "PDP teardown v3") | You stop rebuilding it from memory every time |
| The inputs it needs (screenshot, reviews, GA4 export) | Anyone on the team can run it without you |
| The expected output plus one good example | You can tell instantly when a run came back weak |
| The version number | Prompts improve. Keep the lineage so you can roll back |
A Notion database works well here. Notion ships an official hosted connector, so Claude reads and writes back to it. A single Markdown file works just as well. The format matters far less than the habit.
<aside> ✅
Steal this: the next time a prompt produces something you would actually ship, paste it into a named file before you close the tab. Treat a prompt that works like an asset, not a throwaway. That one habit compounds faster than any tool you buy.
</aside>
This is what separates AI copy that sounds like you from AI copy that sounds like AI.
Encode your tone, your banned phrases, your real example lines, and the claims you can and cannot make into one file. Reference it in every copy, email, and ad prompt from then on. You write it once and every output after ships closer to on-brand without you re-explaining yourself.
A voice file is the thing that makes a connected Claude actually useful. Without it, a fully wired setup just generates generic faster.
What goes in it: