Content Creator Agent
How Sasha will build your Content Creator Agent, which turns what your business already knows into drafts in your own voice, the way you would brief a new writer on the team.
Status: in development. The Content Creator Agent template is built and tested. Its first real set-up, on our own Sasha with one agent for each of our products, is not done yet. The agent stays in development until that first set-up is checked. Some parts that this page describes come in later releases. The page says which.
The Content Creator Agent turns what your business already knows into drafts in your own voice. Your best material sits in your meeting notes, proposals and case notes, where a marketing tool cannot see it. Sasha already holds it. Twice a week the agent finds the stories worth telling, writes the best one as a long piece and a short version for each channel you use, and tells you which documents each draft came from. You publish each piece yourself.
It makes content only. It keeps no calendar, sets no date and never posts. When a piece goes out is your decision. It is not the Marketing Agent, which measures your funnel, and not the PR Agent, which watches the news.
About the examples on this page. Northwind Advisory is an imaginary company: a small UK consultancy that also sells its Training as an online portal. Its clients and projects here are invented to show what Sasha builds. Your agent holds your own stories, voice and angles.
How it works - the business view
- Priya, the admin of Northwind Advisory, opens Agents that work for me, chooses New agent and asks for a Content Creator Agent for the advisory practice.
- Sasha reads the practice's projects (meetings, proposals, case notes) and drafts the Content Brief: who the content is for, the voice with two or three pieces the practice wrote itself, the channels that are on (blog, LinkedIn, newsletter), what must never be said or named, and about 12 angles it will rotate through (a customer story, myth and fact, a lesson we learned, the question clients ask most, and so on). Priya edits the angles and the off-limits list and saves.
- On Monday and Thursday the agent reads what is new in the granted projects and what the practice has already published. It finds stories, pairs each story with an angle, and Sasha's script scores the pairs. The agent writes the best one as a long piece and a short version for each channel that is on, each fitted to that platform's format.
- Priya gets one short email: "1 long piece and 2 short versions ready, from 3 new stories", the drafts' first lines and the documents each one used, the next ideas waiting, and anything it could not read.
- In the app she reads the full drafts, with the format checks and a picture brief for each. She copies the LinkedIn post, publishes it herself and marks it Published with its address. She marks the blog piece Later and one idea Not used, with a reason.
- A Published piece is never repeated, a Not used idea does not come back, and while three drafts wait unmarked the agent writes no new long piece.
- Northwind also sells its Training portal. Priya makes a second Content Creator Agent for it, with its own audience, voice, angles and projects, so the two voices never mix.
Why this is good business: most small firms stop publishing because of the blank page, not for lack of things to say. The agent turns the material you already have into drafts in your voice, from sources you can check, and leaves every publishing decision with a person.
The story: a new writer joins the team
Imagine that Northwind hires a writer. On their first day, Priya explains the job:
- "Our best stories are in our meeting notes and case notes. Find them."
- "Write like these three pieces. Never use these words."
- "We are on the blog, LinkedIn and the newsletter. Fit each piece to the channel."
- "Never name these clients or this project. Ask me before you name anyone else."
- "Do not tell the same story twice, and do not pile up drafts I have not read."
- "You write. I decide what goes out, and when."
The Content Creator Agent is that new colleague, and Sasha runs the induction for you.
What it needs before you start
| Source | Required? | How to connect it | What the agent gets from it |
|---|---|---|---|
| Your knowledge | Required | An admin ticks the projects that hold your meeting notes, proposals and case notes in What it may read (in the ⋯ menu) | The stories, each with its document and date |
| What you have published | Optional | Name your blog feed or news page in the Content Brief, then an admin turns on the web in What it may read, for that site only | What is already out, so nothing is offered again |
| Your site's post list | Optional | A read-only connector for your site, added in Settings, Tools | The same, when your site has such a connector |
| Your code history | Optional | GitHub's read-only server, added with Use a key | What shipped, for a "what changed" story. Evidence only: a draft never quotes it |
Sasha looks for your stories in every project, because they are not always in the project with the obvious name. Naming a project in the brief gives no access: an admin ticks it.
The Content Brief, section by section
Every Sasha agent's brief has the same eight sections. These are the parts that are special to the Content Creator Agent.
4. How it judges
## 4. How it judges
**For:** Finance directors (fewer surprises at month end)
**Angles** (it rotates through all of them)
- Customer story: one client, their problem, what changed, the proof
- A lesson we learned: something that went wrong, and what we do now
- The question we get asked: a question clients ask often, answered
- ... 9 more
**Channels on:** blog, LinkedIn, newsletter
**Never mention:** Project Falcon
**Ask first:** a client name (Harbour Foods, Kestrel)
**Volume:** 1 long piece a run; none while 3 wait for a mark
An angle is a way to tell a story, not a subject. One story from one document, told with one angle, is an idea. Sasha's script scores each idea: the angle used least recently counts most, so the agent rotates through all your angles; then a fresh story (the last 30 days); then proof (a client result, a figure or a quote); then your audience.
6. Who follows up
## 6. Who follows up
**Owner:** Priya Shah
**Voice:** plain, warm and direct; never "synergy"
**Examples:** "Our September note" (newsletter),
"Why we stopped sending monthly decks" (blog)
**Report to:** priya@northwind.example
7. When it reports
## 7. When it reports
**Runs and reports:** Monday and Thursday, 06:00 Europe/London
**No calendar:** when a piece goes out is Priya's decision
The formats
Each channel has its own format. A platform's own limit is never broken: Sasha refuses the draft. A style guide is a warning, and your brief can change it.
| Channel | Limit (refused) | Style guide (a warning) |
|---|---|---|
| Blog | A title, a meta description, a slug and headings | 600 to 1,500 words; a meta description of about 155 characters |
| Newsletter item | A subject and a preview line | A subject of at most 50 characters; about 150 words |
| At most 3,000 characters | The hook in the first 200 characters; at most 3 hashtags | |
| X | At most 280 characters a post | A thread of at most 6 posts |
| At most 2,200 characters, and a picture brief | The first line carries it | |
| At most 63,206 characters | The first line carries it | |
| Short video | A hook and three beats, at most 60 seconds |
For a picture, the agent writes a picture brief: what to show, and from which photos. It does not make images.
The first report
This example is the real output of the agent's script on the Northwind example data, as it emails it.
Northwind Content, 19 Oct: 1 long piece and 2 short versions ready, from 3 new stories
Northwind Content
Read to 2026-10-18
1 long piece and 2 short versions ready, from 3 new stories.
ASK FIRST
- Ask the customer before "The one-page agenda that saved our workshops" goes out
The draft uses a client name ("Harbour Foods").
Owner: Sam Shah.
Tell Sasha: Draft a short message from me to the customer, asking whether we may use a client name ("Harbour Foods") in our piece "The one-page agenda that saved our workshops". Do not send it.
DRAFTS READY
- Blog post: The one-page agenda that saved our workshops
Our workshop with a client team ran ninety minutes over.
Sources: advisory/meetings/2026-10-14-client-workshop.md (2026-10-14)
The full text is in the app; mark it Published, Not used or Later there.
- LinkedIn post: Our client workshop ran ninety minutes over.
Sources: advisory/meetings/2026-10-14-client-workshop.md (2026-10-14)
- Newsletter item: One page, three questions
Sources: advisory/meetings/2026-10-14-client-workshop.md (2026-10-14)
WAITING FOR YOUR MARK
Nothing waits for a mark.
IDEAS WAITING
- Prospects ask how long before they see a result.
The question we get asked; score 37; from advisory/proposals/2026-10-proposal-kestrel.md (2026-10-10).
- A client cut its month-end close from ten days to four.
Customer story; score 34; from advisory/case-notes/harbour-month-end.md (2026-09-02).
ANGLES USED RECENTLY
No angle used yet.
WHAT IT COULD NOT READ
Everything was read.
The full text of each draft stays in the app, with its format checks, its sources, its picture brief and the Published, Not used and Later buttons. Published asks for the address where the piece went out.
What Sasha checks before it keeps a draft
Sasha refuses a record that breaks one of these rules, and the agent must fix it:
- a platform's own limit, or a part the format needs (for example an Instagram caption with no picture brief);
- a draft that names a topic or a name the brief puts off limits (whole words, without case);
- a draft that does not list the documents it used, or lists one the run did not read;
- card or bank details anywhere.
Sasha's script also holds back, with why, a draft that repeats something already published, an idea marked Not used, and a draft over the volume limit. Nothing is dropped without a reason.
After the build: the work log
Each draft is a line in the agent's work log, and so is each mark you put on it. This is how the agent knows what is published and never repeats it.
2026-10-19 06:00 run Started. Read: knowledge. Not read: none.
2026-10-19 06:04 drafted Blog post: The one-page agenda.
2026-10-19 06:04 found A workshop ran over; a one-page agenda fixed it.
2026-10-20 11:15 marked Priya: Published (https://northwind.example/blog/one-page-agenda).
What is built and what is not
The Content Creator Agent is in development. The template is built and tested: the Content Brief with its angles, voice, channels, off-limits list and permissions; the format table; the scoring of ideas; the checks for repeats; the volume limit; the report on two days a week; and the Drafts list with its Published, Not used and Later marks. The first real set-up, on our own Sasha with one agent for each of our products, is not done yet. Not built yet: putting a draft on a site's content calendar as a draft (a later release lets an admin approve one such action per platform; it always lands as a draft a person schedules), and reading other agents' findings (the PR, CRM and Project Agents) through the planned hand-off between agents.