What I've built

The AI Product Launch System

One feature in. Every asset out. The whole company armed. Intelligence about what to say flows into one brain, the brain turns it into the positioning, messaging and every launch asset, and a ready-to-post asset arms every team. This is the full stack, end to end.

running today partial on the roadmap
00
Intelligence in
The senses. Everything that tells you what to say, flowing into one place instead of twenty tabs.
Competitor live ads · proxy MCP Competitor digest cron Authenticated sites + pricing · autonomous browser Competitor wiki · 20 brands Sales + customer calls · granola Process interviews Roadmap op ref · Notion Competitor product recordings · screenpipe Reviews · G2 / Capterra Gong
01
The brain
Memory and retrieval. One context layer that reads all of it at once. The moat is here, not the model.
Second brain · PARA Semantic search · Chroma Observer / reflector Context graph Voice DNA Approved-copy library
02
Synthesis
The PMM craft chain. Intelligence becomes the launch, one ordered pass per feature.
research→ audience→ whitespace→ positioning→ messaging→ pricing→ GTM plan→ launch plan→ enablement
Gates over every draft: Maya persona test · humaniser · fact-checker · refine-spec · council on high-stakes calls.
03
Outputs
One approved messaging doc fans out to every launch asset, in one voice.
GTM plan Sales one-pager Website updates Help article Blog Founder post Company-page post Messaging doc Lifecycle emails Battlecard Asset for everyone to post
The engine that already works: elc-content-refresh turns one messaging doc into four derived assets in a pass, with provenance and an approval gate. Generalising it to all of these is the build that turns the pile of skills into the system.
04
Distribution
Arm every team. Each person handed a ready-to-post asset, staged to approve then publish on launch day.
Marketing Sales Product Engineering Founder Creator team
Rails: Composio (LinkedIn / X / YouTube, stage then approve) · Braze (lifecycle email) · Webflow + Vercel (site) · HubSpot marketplace · Canva + Drive + Notion (collateral) · Slack (internal amplification).
Underneath it all

The automation that runs the whole thing.

Agents
Bob · Milo · Hermes (3-agent) Hermes Kanban Flow · the launch chassis create-farmer printing-press · CLI factory Discord multi-agent workspace
Crons
op ref · 2x daily creator intel planning sweep asset go-live monitor self-healing health monitor
MCP stack
proxydexscreenpipe perplexitycontext7playwright granolagwsbeehiiv
Quality gates
refine-specCodex stop-time review council48 reviewer agents

Real today as an operator workflow. The gaps are the roadmap.

Build 01

launch-content-refresh

Generalise the fan-out so one messaging doc produces all nine assets. Closes the biggest output gaps in one move.

Build 02

Launch orchestrator

One entry point that runs intelligence to synthesis to fan-out to arm-everyone as a gated chain, on the Hermes Kanban chassis.

Build 03

Post-launch loop

Pipe the retro and metrics back into the intelligence layer so every launch starts smarter than the last.