sample report

Content / audience · A hostile input · All sample reports

93/100

Is there demand for newsletter?

Strong signal: the pain is real and documented. The open question is how to enter, not whether anyone cares.

measured 2026-09-10

Strongest signal

52% of 46 signals express real pain, read across 3 live sources.

Biggest risk

Crowded field: multiple existing tools/alternatives referenced — commoditization / race-to-zero risk.

Sharpest next step

Next: this is a published sample — run the same read on your own idea. The free scan takes about a minute.

3sources consulted live46signals readUScountryENlanguage
plan ›1 of 4 planned sources read US specifically; the other 3 read worldwide communities.Sources planned: dataforseo · hackernews · stackexchange_ux · stackexchange_avp
model-assisted read
the words we searched ›newsletter · substack alternative · beehiiv vs substack · convertkit alternative · best newsletter platform · mailchimp too expensive · newsletter monetization tips · how to grow newsletter subscribers · ghost newsletter platform review · struggling to grow newsletter · email newsletter tool recommendations · revue shut down alternative
  • DataForSEO (search intent / Trends)answered
  • Hacker News (Algolia)answered
  • User Experience (Stack Exchange)answered
  • Video Production (Stack Exchange)nothing to say

Evidence-linked heuristics. No market-size number is invented — every claim traces to a cited signal. Absence of a red flag is not proof of demand.

01

Is there real demand?

measured
Signals / sources
46 / 3
Pain ratio
52%
Confidence
high (0.709)
ceiling lifted by measured intent: dataforseo found 52310 monthly searches across 12 keywords (US)
Coverage
measured
34/46
Competition
high

Strongest cited thread — verbatim, verified

I don't want to sign up for your newsletter
hackernewsread the thread ↗match strength 0.6

Top evidence — cited

  • hackernews643▲I don’t want to sign up for your newsletter (2018)
02

Is anyone acting — or just talking?

measured

Each signal counted once, under its strongest register. This reads the words people used — it is not a forecast.

  • would pay0
  • actively looking2
  • already coping, badly1
  • just frustrated0

3 of 18 pain signals used language we could classify; the rest carry pain the words did not label.

03

Can you own the name?

verified live

Proposed names

letterly

Available — verified, best first

  • newsloop.appavailable 🔒 price in full report
  • inkbrief.appavailable 🔒 price in full report

What would kill it

  • No .com is available among the shortlisted names — recall/SEO disadvantage vs an incumbent sitting on the .com.
  • Naming is necessary, not sufficient: a free domain does not clear trademark or social handles — run a trademark + handle check before committing (not performed here).
04

What would kill it?

Checkable against the evidence above

Each of these recomputes from the signals this run cited — you can go and disagree with the data.

  • Crowded field: multiple existing tools/alternatives referenced — commoditization / race-to-zero risk.

Reasoned by the model, not measured

These come from a language model reading the same evidence. They may name figures, companies or products that this run did NOT verify — treat them as leads to check, never as findings.

  • Extreme commoditization: evidence shows a saturated field of newsletter platforms (Substack, Mailchimp, plus numerous open-source/self-hosted alternatives like IndiePubStack and various 'Substack alternatives' threads), meaning a solo operator has near-zero differentiation to compete on.
  • Thin willingness-to-pay signal: the 'Show HN: Easily compare the costs of newsletter platforms' post indicates users are price-sensitive and actively shopping for cheaper options rather than paying premiums, suggesting low margins/high churn risk for a generic entrant.
  • Low switching cost / high churn: multiple threads (self-hosted Substack alternative requests, cost comparisons) show users treat newsletter tooling as commodity infrastructure they'll swap for cost or data-ownership reasons, not loyalty — a solo operator can't retain users against free/self-hosted options.
  • Demand-side skepticism about the core format: 'I don't want to sign up for your newsletter' and 'Do newsletters work?' threads show real audience fatigue and doubt about whether newsletters even deliver value, undermining the total addressable pool of paying publishers who'd need this tool.
  • Platform/incumbent foreclosure: Substack and Mailchimp already bundle publishing, monetization, payments, and distribution at scale with venture-backed resources; a solo operator cannot match their audience network effects or feature velocity.
  • Fragmented, low-value long tail: the 'hyper-focused industry newsletters' and 'find the best newsletters' threads show the market is a long tail of niche hobbyist writers, not high-value business customers, meaning support burden per dollar of revenue is likely high while ARPU is low.

What this read could not establish

  • We read this as: The seed is a single generic word ("newsletter") with no further detail, so it was interpreted broadly as a newsletter creation/publishing platform idea rather than a specific product.
  • Refused source — YouTube: our pipeline cannot keep its engagement signal out of the score, and its API terms require stored data to be refreshed or deleted within 30 days — incompatible with a permanent report. No YouTube signal reaches this read.
  • Refused source — Apple App Store reviews: Apple's Media Services Terms forbid scraping or measuring App Store content. No app-store review signal reaches this read.
  • 8 cited threads verified · 1 shown here — the full report shows them all
  • 5 context signals counted — shown in the full report
  • +5 more names in the full report

What ran — and what is still locked

01 · Demand

Community signal from the problem alone. Ran on this free pass.

02 · Commerce

No marketplace read — this kind of idea does not sell through product listings, so we did not spend a section on one.

Not applicable

03 · Hyperlocal / neighborhood

No on-the-ground read — this idea is not delivered in one place, so a catchment area is not what decides it.

Not applicable
The city is the only answer that unlocks this entire paid section. Without a city we refuse to invent a place — the section stays closed.

04 · Brand & domain

Names proposed; domains recommended only after a real registry check.

Measured

Angles

Where to attack — the theme cut the evidence actually separates. Part of the paid report.

Locked

Where to serve

Countries ranked by what we can actually measure and serve there. Part of the paid report.

Locked

What we did not run, and why

Every axis this report does not carry, named with its reason. An axis that does not apply to your idea is not a gap in the read.

  • No on-the-ground read — this idea is not delivered in one place, so a catchment area is not what decides it.
  • No marketplace read — this kind of idea does not sell through product listings, so we did not spend a section on one.

What the full report would have added to this read

For your idea, the full report contains:

  • all 8 cited threads we verified — real URLs with the verbatim quote the engine checked (the free scan shows 1)
  • the themes your evidence actually separates, each measured against this idea's own baseline — plus what was tested and set aside, and why
  • 90 countries ranked by where you can actually serve
  • no marketplace read — this kind of idea does not sell through listings
  • first-year price on 2 available domains

Every line above is what this sample measured. Your idea gets the same read, on the same sources, today.

Scan my idea

Other samples in this class

Run this read on your own idea of this kind