A growth team's numbers, answered with their source.
A consumer brand's growth team wanted answers, a weekly deck and an early warning on tired ads. Compression built them the Growth Pod: agents read the data through one closed door, every number carries where it came from, and a person approves every change.
Built since July 2026 with Claude Code and Codex · the client stays unnamed · every figure here is about the system
through the door, illustrative● healthy
512commits to the system since July 2026
5read-only tools, and no other way in
322real and written questions it is tested against
158pieces of evidence behind one scorecard, read on 15 Nov
01 · a morning, before and after
The team knew what good looked like. Keeping it current took the morning.
02 · ask growth
Ask in Slack. Get the number and its receipt.
# growth thread
placeholder until the real capture
GL
Growth lead 9:04 AM
@Ask Growth how did paid social do last week for the subscription line, against the week before?
AG
Ask Growth APP9:04 AM
Spend was up x% and new customers up y%, so cost per new customer rose to $z on the multi-touch model. Last-touch moved the other way this week, so both are shown. The service line is reported separately.
Metric: cost per new customer · Attribution: multi-touch, then last-touch · Line: subscription only · Window: last full week vs prior · Source: reporting warehouse, read 9:04 AM
1
One defined metricDefinitions live in one registry, so two people asking get the same number.
2
The model is namedMulti-touch and last-touch can disagree. The answer says which it used.
3
Lines never blendedThe two lines of business behave differently and are always reported apart.
4
The window is explicitNo "recently". Every answer names its days.
5
Where and whenThe source and the time of the read, so a stale number shows itself.
03 · the structure
Three ways to ask, one way in.
Click any part to see what it does, and what it will not do.
who asks
the door
the data plane
the sources
every number leaves withvaluemetricattributionline of businesstimeframesourcecustomer definitionfreshness
04 · /sotb
One command, the weekly deck.
Every week the team presents the state of the business. Now someone types one command, and a skill builds the draft deck from the Growth Pod: every field it can back is filled, and everything else is marked as a gap for a person to close.
claude · marketing brain
>
DRAFT
State of the Businessgenerated by /sotb · data through Saturday
DRAFT
Marketing channelsyear to date vs last year
DRAFT
New customer acquisitioneach line on its own
DRAFT
Three insightsonly what a backed number shows
Insight one, with its period and model
Insight two, with its period and model
Actions: for the owners to add
placeholder Drawn slides until the real anonymised deck is captured. Dashed cells are gaps the skill refused to guess.
Never carries last week's number forwardA definition mismatch is a gap, not a numberCommentary says only what a backed number showsColours are data: no leftover red or greenNever edits the source deck
05 · ad fatigue
Move the signals. Watch the call change.
The growth lead had built a fatigue score in a spreadsheet. The Growth Pod reproduces it exactly and runs it on every active ad, every morning. Try it on a sample ad. The thresholds here are invented; the logic is the team's.
sample ad
Sample ad · 30-day window
Quiet by defaultThe morning scan posts only when an ad crosses a line.
Each line on its own thresholdsNever one shared number for two businesses.
No cause it cannot backIt flags delivery risk, never that creative age caused it. On 15 Nov it read every active ad live in about 23 seconds.
06 · the rules
Agents do the reading. People make the calls.
01A merge is not a release.Code can land without reaching anyone.
Each live surface follows its own release branch. Moving one forward takes a named person's approval, so a change can be built, tested and reviewed without the team ever seeing it.
02Readers are added by name.A pilot of up to ten people.
Each reader is approved by name, knowing what they will be able to read, and signs in once. Removing them is one step, and turning reader access off is another.
03Exceptions are written down.Never a quiet workaround.
When rebuilding pacing needed raw sheet cells rather than defined metrics, it got a written exception: one separate tool, an opt-in permission, an end date, and no path from the chat bot.
04Reconcile before anyone relies on it.Against the team's own books.
Each scorecard metric is checked once against the team's own reporting for a closed month, line by line, before any reader sees it.
05The owner approves the change.Agents propose; people decide.
In the pacing rebuild, every proposed change goes in front of the growth lead before it lands. The weekly deck is a draft for review, never the version presented.
07 · the team's brain
Core, running inside a client.
Beside the data system sits the marketing team's own brain, set up from Core and written by the people in it. Open a folder.