The database that runs my channels: Notion as a video production tracker

The least glamorous tool in my stack is the one that makes the rest of it smarter. Every video across my channels lives as a row in a Notion database before, during, and after production, and that boring habit is where all the receipts on this site come from.

What one row holds

Each planned video gets a row with:

The receipts

ItemNumberSource
Uploads tracked in the database40Notion query
Rows with view counts recorded back13Notion query
Average views on recorded rows676Notion query
Best recorded video2,318 viewsNotion query

Notice the honest gap: 40 uploads tracked, only 13 with results written back. Writing results back is the habit that keeps slipping, because it has no deadline and no immediate reward. I’m publishing that gap on purpose; if your tracker has one, you’re normal, and the fix is making result-entry part of the upload ritual, not a someday task.

Why a database beats a folder of scripts

The difference shows up the day you ask a question. “Which title style holds retention?” was answerable for me in one query because the tags existed. Every experiment verdict that now lives in my scripting rulebooks started as a query against this database. A folder of scripts can’t answer anything; it can only be reread.

Small print: mine is Notion because the pipeline reads and writes it programmatically, but nothing here is Notion-specific. A spreadsheet with the same columns delivers the same power.

What you can use today

  1. Make a tracker with five columns: title, status, title-style tag, views, one-line result note. That’s the whole system.
  2. Backfill your last ten uploads today. Ten rows is enough to see your first pattern.
  3. Add result-entry to your upload checklist so it happens the same minute you publish, not “later.”

This tracker is also where this site’s own numbers will live. Whatever the blog earns or fails to earn, the receipt gets published here.

Here are the receipts.