Marketing board update
Decision-ready board-cycle update from live data.
Runs in Ergo, as a bespoke install, or as a pattern to copy.
What it does
You name the cadence, the plan and the sources. The workflow builds the pack the board actually uses.
- 01Scorecard. Live metrics against the plan and OKRs.
- 02Narrative. What moved, what held, what needs a decision this cycle.
- 03Risks and asks. Issues and requests that belong in the room.
- 04Board pack. Doc or deck, plus the appendix behind it.
Setup
Configure the cycle. The workflow runs from there.
- Cadence. When the board cycle lands.
- Plan and OKRs. The commitments the update is scored against.
- Metrics and finance sources. Where the numbers come from.
- Open asks. The decisions already in play.
Ships
Named artefacts your team keeps and runs.
- Board update. Doc or deck the room reads.
- Decision log. What was asked, what was decided, what is still open.
- Metrics appendix. The tables behind the narrative.
- Suggested asks. The requests the data supports.
How it works
- Assemble scorecardPull live metrics and finance sources against the plan and OKRs.
- NarrateWrite what moved, what held, and why it matters for this cycle.
- Surface risks/asksFlag risks and the decisions the board still owes, including suggested asks.
- PackageCompile the board update, decision log and metrics appendix.
Add to your marketing system
Bring the plan and the open asks. Scoping sets cadence and sources; the workflow runs the cycle.
The scoping call sets cadence, plan and the sources behind the scorecard.
FAQ
What is a workflow?
A fixed-scope agentic automation for one recurring marketing job. Same loop, same outputs, configured to your market.
Ergo or standalone?
In Ergo it runs as a live capability in Slack. Standalone is a bespoke install into your stack. Same workflow either way.
What do I bring?
The board cadence, the plan and OKRs, the metric sources, and the asks already in play.