Describe what you want to run, in plain language. The squad — director, orchestrator, analyst, video, social, ads, email — returns a full campaign with deliverables and the tasks to produce them. It's a draft: review it, change it, then decide whether it goes on the board.
The three original functions. Each one reasons over the whole plan and returns a draft — nothing reaches the calendar without somebody deciding it should.
Builds a foundation of posts and content ideas, filling the gaps in what's already planned. Results land in the Ideas queue for review — nothing goes straight to the calendar.
Reads the plan and the actuals you've recorded, then reports what's underperforming and why. It says what it couldn't assess rather than inventing numbers.
Proposes experiments worth running next quarter, each with a falsifiable hypothesis and a number that means it worked. At least one is low-effort and near-zero-budget.
Researches the topic, drafts an outline for you to edit, then writes the article — headline, body, meta description, slug and the Webflow fields. The outline is a deliberate stop: fixing the angle there costs seconds, fixing it in a finished draft costs a whole regeneration.
Every generation, saved — so an analysis or a set of experiments can be reopened without paying to regenerate it.
A term can be a campaign channel, a deliverable platform, a tag, or any combination — one list, so the same word can't drift into two spellings. A deliverable has one platform and any number of tags: platform is where a piece lands, a tag is what it's about. Social decides what gets a lane in the Social view. Offered controls whether it appears in the pickers — turning it off never hides work already using it.
No password here on purpose. Adding someone creates the account with no way in, and hands you a one-time set-password link to send them — they choose the password, you never see it.
Every table as JSON, password hashes
redacted. Take one before any big change. npm run export in a
Render shell writes the same file, but Render's disk is wiped on every
deploy — this copy lands on your machine and survives.