The shape
Each template is a managed run, not a node graph.
A workflow has the same practical parts every time: a trigger, a context slice, execution, optional review, and a destination for the output.
01
Trigger
02
Context retrieval
03
Run with logs
04
Review
05
Output
Workflow templates we can host first.
The catalog starts with recurring work that has a clear owner, a clear output, and enough context to make the run useful.
Report workflow
HostedWeekly founder digest
A Monday brief that pulls the week together before the first meeting: sales, ad performance, inventory risk, open decisions, and what changed since last week.
Trigger
Schedule · every Monday at 8:00 AM
Output
Three to five issues worth watching this week
View workflow →
Notice + report workflow
HostedROAS postmortem
When paid performance slips, the useful question is not just what dropped — it's what changed across spend, creative, launch timing, landing pages, and inventory context.
Trigger
Event · ROAS drops past a threshold week over week
Output
A short explanation of the likely drivers
View workflow →
Notice workflow
HostedInventory risk alert
A recurring watch on sell-through, reorder windows, and supplier constraints so low-stock surprises stop happening late.
Trigger
Schedule or event · threshold-based watch
Output
A risk summary with days of cover
View workflow →
Answer + report workflow
HostedContent brief generation
Turn campaign context, product history, customer feedback, and past content into a repeatable brief workflow instead of starting from a blank page every time.
Trigger
Manual from chat, or scheduled around campaign planning
Output
Headline angles, audience framing, and key proof points
View workflow →
Have a workflow in mind already?
Bring the rough version. We will tell you whether it belongs in the first setup, needs more context, or should stay manual for now.