Kit
Ideas in one end, published pieces out the other, and nothing quietly rotting in drafts.
Ideas rot in drafts, and nobody finds out until the quarter is over. Tell Bryony what you have in flight — what each piece is, what shape it takes, where it has got to and roughly when it should go out — and from then on just say a piece has moved. Every piece on one table with its stage, its owner and its date; the whole belt drawn from the ideas that came in to the pieces that actually went out, with anything you dropped counted honestly beside it; what is going out, on a calendar with each piece's stage on it; and the ideas still waiting their turn. Every Monday Bryony reads the belt and says what has been sitting at one stage too long — then asks. When you want them, the rest of the craft is here too: your plan for the season written down, a brief and an outline for a piece with a search brief from sources it names, a draft in your voice held to a style guide you keep, a piece cut down for other channels, a review checklist you go through one check at a time from the board, and how a piece did, read from Site & Search or Social Presence when you keep them. Ask which piece to do next and Bryony picks one and says why; ask it to rank your ideas, rate one, or propose a schedule and it will. It moves nothing for you, schedules nothing, posts nowhere, and never writes a piece unless you ask.
1 agent, 1 routine, 1 dashboard, 2 datasets, 4 skills. Installing ends with Meet Bryony — a short conversation sets it up, and everything can be retimed or paused after.
every piece with a target date, carrying its stage — the pale one is still in review
Six months of support tickets
Drafting · 19 days at this stageWhat a good handover looks like
In review with Sam · 11 days| Pricing, explained plainly | Scheduled · blog post | out in 9 days |
| What a good handover looks like | In review · guide · Sam | target 30th |
| Six months of support tickets | Drafting · case study | target next month |
| A field guide to our error messages | Idea · guide | no date yet |
The crew
Bryony
Keeps the belt of what you are making moving, and never once tells you to write faster.
Warm, patient, unhurried; keeps everything in view and never once implies you are behind.
What else it installs
One row per piece — what it is, what stage it is really at, who has it and when it should go out.
What a reviewer should check on a piece, one line each, with where each check came from.
Say it in passing — a new idea, a piece that moved, something that went out — and the belt keeps up.
Your plan for the season written down, and a brief and an outline for any piece you ask about, with a search brief from sources it names.
A draft only when you ask, in your voice and from your own brief and notes, held to a style guide you keep, and cut down for other channels.
Who reviews a piece and what they should check, as a list you tick through one check at a time; and, once it is out, how it did.
The belt from end to end — what came in as an idea, what is moving, what is going out and what has been sitting too long.
Mondays — reads the belt, redraws the board, and says what has been sitting at one stage too long.
Runs mondays · 8am
The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.
Data/Content Calendar in your vault — yours to open, search, and edit like any other file.Data/Review Checklist in your vault — yours to open, search, and edit like any other file.The wiring, in one breath: Content idea capture writes to Content calendar · Content calendar shown by Studio · Studio kept fresh by Studio sweep · Studio sweep run by Bryony · Bryony holds Content idea capture · Bryony holds Plans and briefs · Bryony holds Writing desk · Bryony holds Review and results · Plans and briefs writes to Content calendar · Writing desk writes to Content calendar · Review and results writes to Review checklist.
A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.
Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.
Say any of these in chat, or edit them on the kit’s page in the app.
Installing starts a short setup conversation — not a form. Answer roughly, correct later.
Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.
Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.
Install it, run it once against something that already happened, and see whether what comes back sounds like you.
Try it freeEverything it installs can be retimed, paused, or removed.
Last reviewed