Workflows — Index
Workflows grouped by vertical, following the five sub-OSes drawn off
Mktg OS on page 1 of ../roadmap_ref_extracted.md.
A workflow here is a repeatable path from trigger to output — WF on the
whiteboard. An agent is the LLM step inside one; those are documented
separately in ../agents/.
The five verticals
| Vertical | What it covers | Built today |
|---|---|---|
| ATL | Mass reach and brand — creative, social, video scripts, ORM | 🟡 Script production is live; creative assets are not |
| BTL | Targeted, direct, one-to-one — messaging, bots, branch and DSA | ⬜ Nothing built |
| Digital | Owned and paid digital — blogs, SEO, performance media, CRO | 🟡 Blog and SEO paths live; media buying is not |
| Program | Customer lifecycle — retention, acquisition, segments, NBA | ⬜ Governance is live; no lifecycle programs |
| Analytics | Measurement and intelligence — dashboards, competitors, learning | 🟡 Intelligence is live; unified analytics is not |
Status legend, used identically in every vertical doc:
| Meaning | |
|---|---|
| ✅ Live | Shipped, in the product, usable today |
| 🟡 Partial | Some of the path works; a named step is missing |
| ⬜ Planned | On the roadmap, nothing built |
Where the work actually is
ATL ████████░░░░░░░░░░░░ scripts + hooks live · creative, ORM, media open
BTL ░░░░░░░░░░░░░░░░░░░░ empty
Digital ███████████░░░░░░░░░ blog E2E + SEO + discovery live · media, CRO open
Program ██░░░░░░░░░░░░░░░░░░ approvals + governance only
Analytics ██████████░░░░░░░░░░ competitor + learning live · unified dash open
Two honest observations from mapping the code against the whiteboard:
- BTL is completely empty. No messaging integration of any kind exists —
no WhatsApp, SMS, RCS, Clevertap or Netcore. Page 2 of the roadmap plans an
entire channel dispatch layer (
A5); none of it is started. This is the single largest gap between the sketch and the product. - Everything live today is a production workflow — nothing is a distribution workflow. The system reliably makes content and stops. Blog drafts wait for a human to send to the CMS; scripts land on a calendar nothing publishes from. Every vertical's biggest gap is on the far side of "content exists".
The one workflow abstraction that exists in code
app/src/lib/content-workflows.ts defines two shipped, user-facing workflows
under Make Content:
| Key | Label | Route | Actions |
|---|---|---|---|
main_daily | Daily Studio | make-content/main-daily | generate · approve · schedule · open studio |
custom | Custom Lab | make-content/custom | generate · open studio |
Both are ATL script-production workflows. They are templated —
WorkflowTemplate carries allowed source types, setup fields, defaults and
action flags — so adding a third workflow is configuration, not new plumbing.
Everything else described in these docs is either a pipeline without a workflow UI (blogs, discovery) or unbuilt.
How verticals map to agents
| Vertical | Discovery Agent | Compliance Agent | Creative Agent |
|---|---|---|---|
| ATL | feeds topic selection | ⬜ scripts get keyword scan only | ✅ scripts, hooks |
| BTL | — | — | — |
| Digital | ✅ every feed item | ✅ source + draft review | ✅ blog drafts |
| Program | — | — | — |
| Analytics | writes the scores dashboards would read | — | — |
The blank rows are not oversights — they are the build list.
Folder convention
workflows/
index.md ← this file
<vertical>/
README.md ← the vertical: definition, workflow table, gaps, dependencies
Each vertical doc carries the same sections: What this vertical means · Workflows · What's live in detail · What's missing · Dependencies · Roadmap source.