Weekly marketing report

Deliverable-led weekly pack so humans spend time deciding, not wrangling data.

Runs in Ergo, as a bespoke install, or as a pattern to copy.

Run in Ergo Book a scoping call

What it does

You name the sources, the KPIs and the audience. The workflow runs the week and ships a pack with the narrative already written.

  1. 01Source pull. APIs, exports and sheets named at setup.
  2. 02Period comparison. This week against last week and against target.
  3. 03Anomaly flags. Only the metrics that crossed your thresholds.
  4. 04Pack assembly. Report, charts, appendix, optional Slack summary.

Setup

Configure the week. The workflow runs the cycle from there.

  • Sources. The APIs, exports and sheets the pack is allowed to read.
  • KPIs and targets. The numbers that count, and the line they have to beat.
  • Audience and cadence. Who the pack is for, and when it lands. Weekly is the default.
  • Narrative questions. What the write-up must answer before anyone opens a spreadsheet.

Ships

Named artefacts your team keeps and runs.

  • Weekly report. The pack leadership reads.
  • Anomaly flags. Metrics that crossed the thresholds you set.
  • Metric appendix. The tables behind the narrative.
  • Optional Slack summary. The same story, short, in the channel.

How it works

  1. CollectPull the named sources for the period: APIs, exports and sheets. Log coverage so missing sources show up.
  2. CompareCompute period deltas against last week and against target.
  3. ExplainDraft the narrative against the questions set at setup. Flag anything past threshold.
  4. PackageAssemble the report, charts and metric appendix. Send the Slack summary if configured.

Add to your marketing system

Bring the sources and the questions. Scoping sets KPIs, audience and cadence; the workflow runs the week.

Run in Ergo Book a scoping call

The scoping call sets sources, KPIs and who the pack is for.

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 sources, the KPIs and targets, who the pack is for, and the questions it has to answer.