Newsletterytics Pro

Analytics dashboard for Substack/Ghost creators tracking subscriber LTV, ad CPMs, and churn; sold as creator subscription. · Creator Analytics SaaS

STOP · SKIP

4.2 ShipScore / 10

Strongest: time-freedom of SaaS. Weakest: entry — platforms bundle analytics free.

Condition: Only reconsider if you find 20+ paying newsletters spending on ad-revenue/LTV reporting Substack cannot produce, plus a stable data path (Ghost API, ESP webhooks) that survives Substack having no public API.

Part I — The Verdict what the instruments read

§1 — The ShipScore breakdown

Control

Entry barriers

Need

Time-freedom

Scale

What the five commandments measure

C — Control	Do you own the customer, or does a gatekeeper (an app store, an algorithm, one platform) stand between you and revenue? High = you hold the keys.
E — Entry	How hard is this to copy? High barriers protect you once in — but a well-loved incumbent means breaking in is expensive, and scores this low.
N — Need	Is demand proven with money, not vibes — verified rival revenue, funding, exit multiples, complaint volume? No market evidence caps this at 5.
T — Time	Can income detach from your hours? High = earns while you sleep; low = you bought yourself a job.
S — Scale	How far does it reach without linear cost? High = software margins to thousands of customers; low = growth means headcount.

ShipScore = the mean of the five, scored by Opus 5 on the evidence below — the same rubric for every idea, including the ones we generate ourselves. Inspired by MJ DeMarco's CENTS framework. Full rubric →

§2 — The pace test — $1M/yr

At $29/mo (assumed category price), you need 2,874 subscribers for a $1M/yr pace.

Nearest tracked rivals on that curve:

LLM Gateway

$58k 70%

Peekaboo

$43k 52%

→ moat stable

A rival's moat trend is its verified-revenue trajectory, not its rating — a 4.9★ incumbent with eroding revenue is a different opponent than a widening one. How it's computed →

Part II — The Evidence the receipts, good and bad

§3 — Rival scan — corpus tracks 2 similar

LLM Gateway	verified MRR $58k · CENTS 6.8 (trustmrr)
Peekaboo	verified MRR $43k · CENTS 6.8 (trustmrr)	→ moat stable

Substack (native analytics) — Owns the data and ships free subscriber/open/growth dashboards; zero switching incentive.
Ghost (built-in dashboard + Ghost Explore) — Open-source incumbent already reports MRR, churn and engagement natively for free.
beehiiv — Bundles deep analytics with a built-in ad network, so CPM data is native, not an add-on.

§4 — Demand evidence

No demand evidence: zero Reddit signals found for these keywords.
No funded companies tracked in or near creator newsletter analytics.
The two radar 'similar' products (LLM Gateway $58k MRR, Peekaboo $43k MRR) are unrelated categories — they say nothing about newsletter analytics willingness-to-pay.
Because there is no market evidence of recurring spend here, need is scored low rather than assumed.

§5 — Risks

Substack has no official public API; ingestion may rely on scraping or CSV uploads that break or violate terms.
Free native analytics from Substack, Ghost and beehiiv anchor the price near zero.
Addressable market is only the minority of newsletters that monetize enough to care about LTV and CPM.
Creator tooling has notorious churn and price sensitivity; sub-$30 ARPU with high support load.

§6 — Kill switches — what kills this with one decision

Substack terms/API access — No public API means scraping or session-token access; one policy or markup change zeroes your data pipeline.
Platform bundling — Substack or Ghost shipping an LTV/churn/ad-revenue tab in one release makes the whole product redundant.
ESP OAuth approval (Mailchimp/ConvertKit/beehiiv) — Revoked or rate-limited integration credentials cut off the only alternative data source.

Divergence available · Seeing the cracks? Spin the model — variations of this idea engineered to beat 4.2.

Part III — The Plan if you insist on proceeding

§7 — What this scan can't tell you

Cannot tell whether Substack currently tolerates third-party data access for this use case.
No read on how many newsletters actually earn enough ad revenue to need CPM reporting.
Cannot assess whether you hold an unusual data source or distribution channel into paid-newsletter operators.

Scores judge the market and business model — not your ability to execute. Verified MRR = independently tracked revenue; reviews/upvotes = platform-reported. Judged 2026-08-04.

§8 — The wedge & the next step

Skip the generic dashboard; sell ad-revenue proof-of-performance reports (verified CPM, cost-per-subscriber, sponsor-ready media kits) to newsletters already selling sponsorships — a number platforms don't compute and sponsors demand.

Cheapest next step: DM or email 25 newsletters that ran sponsorships last month, ask what they currently send sponsors and whether they'd pay $29/mo for automated verified reporting; if fewer than 5 say yes, drop it.

Not quite it? Spin the model

Business-model variations of this idea, engineered to beat 4.2 — different vertical, audience, model, or wedge. Same harsh scale.

Monitor this idea

Weekly re-scan against the live corpus. If the market moves this ShipScore by a point, or flips the verdict, you hear about it. Free while we're small.

One inspection a day, by email

App Radar scans TrustMRR, Product Hunt, AppSumo, the App Store, Reddit and X daily — momentum, beatable apps, funding heat.