2 of 8 episodes are out. New here? Start with episode 0
Where it really starts
The pull request that changes the schema
Outside every guarantee below. Nothing downstream is built to question it.
Layer 1
Supabase Postgres
The record of what happened
Layer 2
Supabase Pipelines
Moves it faithfully, no silent loss
Layer 3
BigQuery
Models it into answerable questions
Layer 4
Your GTM tools
Acts on the answer
Nine entries, eight recordings, one working stack. What we are building, who it is for, and the single picture that explains the whole series. Read this one before you start the recordings.
Watch and read19 August 2026
Four layers, and each owns exactly one job. Read them left to right and something uncomfortable falls out: every guarantee downstream is conditional on the layer to its left. Which is why the stack really starts one step before Postgres.
Watch and read6 August 2026
From an empty BigQuery dataset to a table sitting at Live. The publication is SQL you write yourself, the destination takes four fields, and there are two things nobody mentions until you hit them: who gets the bill, and the region field you can never change.
Watch and read14 August 2026
Publishing every table is the wrong answer, and it takes about a month to find out why. Primary keys, replica identity, and the TOAST problem that quietly eats your updates. Plus the tables we leave behind on purpose, and what it would cost us not to.
Replicated tables do not arrive as tables. Each one is a view over a versioned table, and pointing a dashboard at the wrong object works right up until someone truncates the source. Then the real work: turning faithful copies into models that answer something.
Time to value as one interval with two ends: GitHub App installed, first pull request review posted. Falsifiable, and a good test of whether your collection layer is real. Ours was not. The install row had no usable timestamp, and you cannot backfill a moment nobody wrote down.
Fifty warnings and forty-five fixes is a healthy account. Fifty warnings and two fixes is a conversation you want this week, not the week after renewal. Three signals per workspace, rolled into one score, plus the step most teams skip once they have it.
The same models as account health with the comparison reversed. Which accounts have quietly outgrown the tier they are paying for, measured by repository volume and by how many distinct people trigger reviews. Almost the same query, entirely different conversation.
Four ordinary migrations that break the chain without failing CI or turning a pipeline red. A default that does not replicate, history that never backfills, a type change nobody supports, and a truncate that moves the table out from under your dashboard.
Weekly, for eight weeks
One email per episode. No digest, no drip sequence, no sales cadence. Unsubscribe in one click.
Your address goes on this list and nowhere else.
