06-reference/research

sanity check list size mac revenue bar

2026-08-04·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
sanity-checkmaclist-sizeconversion-benchmarksinstrumentation-gap

Sanity Check's List Size Isn't Instrumented — So the MAC Break-Even Question Can Only Be Answered as a Sensitivity Table, Not a Forecast

The question

What is the actual Sanity Check list size / growth rate today, and at what list size does an organic MAC launch clear a meaningful revenue bar? (Anchors the audience-first failure mode to RDCO's real numbers.) Surfaced from [[2026-06-13-low-ticket-digital-product-failure-modes]]'s open follow-up #1.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The honest finding is not a number — it's that RDCO cannot currently answer "will an organic MAC launch clear a meaningful revenue bar" because the input the question depends on (list size, and any conversion history at all) has never been instrumented. That is a bigger problem than any specific conversion assumption below, because it means the founder cannot even retroactively check which assumption was right after a launch. The sanity-check.yaml file already names this as the highest-priority open gap independent of MAC — fixing it serves both bets.

Below is a sensitivity table using modeled external benchmarks (course-launch conversion: 1%, 3%, 5%, 8%; MAC's actual founder-decided price of $350, plus the evidenced-landing-zone price of $200 from the prior pricing scan) against hypothetical list sizes. None of the list-size column headers are RDCO's actual number — they are scenario anchors matching the revival-strategy's own planning milestones (500 / 1,000 / 2,500 / 5,000 / 10,000), chosen so the founder can locate wherever the real list turns out to be once it's measured.

Gross revenue at MAC's decided price ($350/unit) — MODELED, not RDCO data:

List size 1% conv. 3% conv. 5% conv. 8% conv.
500 $1,750 $5,250 $8,750 $14,000
1,000 $3,500 $10,500 $17,500 $28,000
2,500 $8,750 $26,250 $43,750 $70,000
5,000 $17,500 $52,500 $87,500 $140,000
10,000 $35,000 $105,000 $175,000 $280,000

Gross revenue at the evidenced-landing-zone price ($200/unit) — MODELED, not RDCO data:

List size 1% conv. 3% conv. 5% conv. 8% conv.
500 $1,000 $3,000 $5,000 $8,000
1,000 $2,000 $6,000 $10,000 $16,000
2,500 $5,000 $15,000 $25,000 $40,000
5,000 $10,000 $30,000 $50,000 $80,000
10,000 $20,000 $60,000 $100,000 $160,000

Reading the table: at the revival-strategy's own Phase-1 milestone (500-1,000 subscribers, not yet confirmed reached), even the strongest warm-up conversion (8%) tops out at $8K-$28K gross, before refunds (unmodeled — no category-specific refund data exists per the prior pricing scan) and before RDCO's stated production/CAC costs. At the 1% conservative-cold-list end (closer to beehiiv's platform-wide median behavior, though that measures recurring subscriptions not one-time purchases), 500-1,000 subscribers clears $1,750-$3,500 — a number that would not cover a meaningful chunk of a founder's time, let alone fund a backend build. The table only becomes interesting past 2,500-5,000 subscribers, which is two to three revival-strategy phases beyond where the vault's last dated evidence (2026-05-18) leaves the newsletter.

The founder has not defined what "meaningful revenue bar" means, and this brief will not invent one for him. Candidate anchors that already exist elsewhere in the vault, offered as reference points rather than a recommendation: the phData-vs-MG decision analysis names "$1-3k/mo by month 12" as a Sanity Check monetization target (a recurring-monthly framing, not a MAC one-time-launch framing); the cert-escalator base-salary bumps he's chasing are $5-10K increments (a useful gut-check scale for "does a MAC launch move the needle vs. a day-job lever"); Sanity Check's own sponsor-rate plan ($200-500/issue at 1,000 subs) implies the founder already treats sub-$1K one-time events as sub-meaningful at that stage. Whatever bar he sets, this table lets him read the required list size × conversion combination off it directly, once he has a real list-size number to plug in.

Why this is in the vault

This is the audience-first precondition check the parent brief ([[2026-06-13-low-ticket-digital-product-failure-modes]]) explicitly named as its top open follow-up before MAC commits to an organic-list launch strategy — and the answer it produces is itself a build item (instrument list size and per-issue engagement now, before MAC's launch date arrives and the founder is flying blind on the one number that determines whether "organic" is even a viable acquisition channel).

Open follow-ups

No other follow-ups clear the bar: RDCO's own send/conversion data is blocked on instrumentation that doesn't exist yet (a build task, not a research question), and the paid-challenge-format question is already substantially answered by the Aamir case in [[2026-05-18-low-ticket-dev-tool-launch-friction]].

Related

Sources