Marketing notes your assistant quotes instead of improvising
Positioning, personas and approved copy in one repository, so every draft starts from what the team already agreed.
Who it’s for: Marketing leads, content writers and founders who write about the product.
Drafts drift from the positioning
Each new brief is written from memory. An assistant asked for copy invents claims, tone and audience on the spot.
Approved language as the source
Keep positioning, personas, messaging and approved phrases in Markdown. Ask your assistant to draft from them and it reads the actual notes, not a summary someone pasted in last month.
Change it in one commit
When the positioning changes, it changes in one commit, with a message saying why. The next drafting session reads the new version, in every assistant connected to the repository.
How to structure the repository
- Write each persona as its own note: the role, the job they are trying to get done, the words they use, and what they object to.
- Keep approved claims in a single file. If a claim is not there, the assistant has no source for it, and you can ask it to flag any claim it cannot find.
- Explain positioning changes in commit messages, so the history records why the language changed.
Setting it up
-
Step 1: Move the positioning document, personas and approved copy into Markdown in a private repository.
-
Step 2: Assign the people who write: marketing, sales, founders.
-
Step 3: Connect it to the assistants they draft with, and ask for drafts that name the notes they used.