You write more than anyone on the team. It should sound that way.
Investor updates, launch posts, hiring notes, replies to customers, all drafted fast and with help. One guide, built from an interview, that every tool you use can follow.
Someone can tell.
An investor update that reads like a press release. A launch post with a sentence a hundred other launch posts used this week. A reply to a customer that is polite and says nothing. You know when a draft sounds assisted, and so does the person reading it.
The fix is not a better prompt. A prompt holds tone. What makes your writing yours is the way you explain the product to someone smart outside your field. It is the claim you refuse to make about it, and the stories you tell about why it exists.
Half an hour, eighteen questions, one guide.
"Explain what you do to a smart fourteen-year-old." "What did you believe about your work five years ago that you no longer believe?" "What do you refuse to do for clients or customers, even when they ask and will pay?"
The guide holds your explanations in the order you give them. It holds your stances with your lines quoted, and your stories with their points. It holds how you open a note to a customer about a problem, and what you would never say.
Claude on Monday, ChatGPT on Tuesday, the same voice.
The files are built for each assistant. A Skill folder for Claude, and a CLAUDE.md snippet for Claude Code and any agent. Custom instructions and a project file for ChatGPT, an instruction block for Gemini, and VOICE.md for anything else. Install once each. When something changes, a re-interview updates every file at once.
Start with the free snapshot.
Paste your last investor update and a post. The snapshot shows your vocabulary, your rhythm, three moves, three things to avoid, and one paragraph rewritten in your voice.