Demand Score
sample0Strong demand
Demand research for indie founders
Find the peoplewho already wantyour SaaS.
Describe your idea in a sentence or two. DemandEcho searches real public conversations for people asking for a tool, complaining about what exists and comparing alternatives, so you find them before you spend months building.
Listening across real public conversations on
- Hacker News
- Stack Exchange
- GitHub issues
- Mastodon
- similar sources
Phrases we listen for
seekingis there a tool that…complainingwhy is it so hard to…comparingany alternative to…askingwhat’s the best way to…seekingI’d happily pay for…complainingway too expensive for a solo…comparingX vs Y for…askinganyone else struggling with…
askinghow do you all handle…seekingdoes anything exist for…comparingswitched from X because…complainingI’m so tired of…askingwhat do you use for…seekinglooking for something that…comparingwhich is better for…complainingevery tool I’ve tried…
Why listen first
Most SaaS ideas don’t die because they were built badly. They die because nobody was asking for them. The people who need your product are already out there: posting, complaining, comparing, asking. Hear them before you write a line of code.
How it works · 10-stage pipeline
From one sentence
to real evidence.
01/ 10
Context check
First, DemandEcho checks that your idea has enough context to search on. If it’s too vague, you’re asked for a little more before a single query runs.
- Queries planned
- ·
- Results found
- ·
- Unique
- ·
- Relevant
- ·
- Strong signals
- ·
Counts from an illustrative sample run.
- 01Context check
- 02Query planning
- 03Source fan-out
- 04Collection
- 05Normalization
- 06Deduplication
- 07Relevance filter
- 08Intent tagging
- 09Scoring
- 10AI summary
The report
Evidence you can click.
A score, the conversations behind it, the tools people mention, when it all happened and a summary written only from what was found. Try the filters and the citations.
AI summary
Written by Gemini from the evidence in this reportFreelancers keep describing late-invoice follow-ups as the most awkward part of getting paid. The strongest signals are direct requests for a tool that sends reminders on its own , mostly from solo workers who find full accounting suites too heavy for the job . A smaller developer thread asks for overdue reminders inside existing tools , a hint that integrations matter. Recurring themes: keeping the tone polite, escalating automatically, and replacing manual workarounds .
polite toneautomatic escalationtoo-heavy suitesmanual workaroundsclient relationships
What’s in the score
- Intent strength84
- Relevance88
- Evidence volume66
- Source diversity90
- Recency74
- Recurring themes79
Conversations
Showing 8 of 47Is there anything that nudges clients automatically when an invoice is a week late? I don’t need full accounting software. I just hate writing the “friendly reminder” email.
View source ↗Every invoicing tool I’ve tried is built for accountants. I’m one person. I want reminders, not a general ledger.
View source ↗Tried two big accounting suites and a spreadsheet with calendar alerts. The spreadsheet won, which says a lot about the options.
View source ↗How do you follow up on an overdue invoice without damaging the client relationship?
View source ↗Would happily pay for something that escalates invoice reminders politely on its own. Does this exist?
View source ↗Feature request: automatic overdue reminders. Right now we export the list and email every client by hand.
View source ↗Has anyone built their own late-payment reminder flow? Curious which edge cases bit you.
View source ↗Cancelled my accounting subscription and went back to templates. Paying for forty features to use one felt silly.
View source ↗
Tools people mention
mentionsTimeline
customers developersOct ’25 · 1 customer · 1 devOct
Nov ’25 · 2 customer · 1 devNov
Dec ’25 · 1 customer · 0 devDec
Jan ’26 · 2 customer · 1 devJan
Feb ’26 · 2 customer · 2 devFeb
Mar ’26 · 3 customer · 1 devMar
Apr ’26 · 2 customer · 1 devApr
May ’26 · 3 customer · 2 devMay
Jun ’26 · 3 customer · 2 devJun
Jul ’26 · 4 customer · 2 devJul
Aug ’26 · 4 customer · 2 devAug
Sep ’26 · 3 customer · 2 devSep
64% customer signals · 3036% developer signals · 17
- Reddit 19
- Hacker News 9
- GitHub 8
- Stack Exchange 6
- Mastodon 5
This sample is illustrative. In a real report, every conversation links to the public post it came from. See a full sample report
Demand Score
Six signals. One number.
0Demand Score · sample
Intent strength
How badly people want it. “I’d pay for this” counts for more than a passing mention.
84
Evidence volume
How many real conversations were found. More evidence means more confidence.
66
Recency
How fresh the conversations are. A pain people mention this month beats one from years ago.
74
Relevance
How closely each conversation matches the problem you actually described.
88
Source diversity
How many different places the signal comes from, so one loud forum can’t carry the score.
90
Recurring themes
Whether the same problems keep coming up across different people and places.
79
A guide, not a verdict. The conversations are the real evidence.
Four kinds of demand
Every conversation gets a tag.
Each one is also marked as a customer or developer signal, so you can tell buyers from builders.
Looking for a solution
“is there a tool that…”
“I’d happily pay for…”
Someone is actively hunting for what you want to build. The strongest signal there is.
Frustrated with what exists
“I’m so tired of…”
“why is it so hard to…”
Pain with today’s options. It shows exactly where current tools fall short.
Weighing alternatives
“X vs Y for…”
“switched from X because…”
People choosing between options, naming the tools you’d be up against as they go.
Asking how others cope
“how do you all handle…”
“what’s the best way to…”
Open questions around the problem. Early signal, plus the words your customers actually use.
Principles
Everything in a report is real.
So is everything on this page.
0
fake testimonials
You won’t find any here. DemandEcho is built on one rule, show only what’s real, and that starts with this page.
0
invented quotes
Every conversation in a report comes from a real public post and links back to it. Nothing is made up.
0
messages sent
It’s research only. No spam, no DMs, no automated outreach. DemandEcho reads, it never writes.
The AI summary is written by Gemini from the evidence in your report, and sits right above the links so you can check every line.
Pricing
Cheaper than building the wrong thing.
- Demand Score with all six signals
- Every conversation, with link, snippet and intent tag
- Tools and competitors people mention, and how often
- Timeline, plus the customer and developer split
- AI summary written from the evidence found
$0.99 per report, or Pro at $4.99/month.
- 01Create your account
Sign in to start and keep every report in one place.
- 02Check out with Polar
Paid reports are confirmed through Polar’s secure checkout before research starts.
- 03Manage it anytime
Change or cancel a Pro subscription from the customer portal in Settings.
FAQ
Fair questions.
Public conversations on Reddit, Hacker News, Stack Exchange, GitHub issues, Mastodon and similar sources. Every conversation in a report has a link, so you can read it in context.
No. Everything in a report comes from conversations DemandEcho actually found. If the evidence is thin, the report shows that, and the Demand Score reflects it.
Gemini writes the summary at the top of your report, using only the evidence that was found. The conversations it’s based on are listed right under it, with links.
Never. It’s a research tool. It doesn’t post, DM, email or automate outreach of any kind.
The first stage checks whether your description has enough context to search on. If it doesn’t, you’ll be asked to add a bit more, like who it’s for or what problem it solves, before anything runs.
That the evidence is thin right now: few conversations, weak intent or old threads. Treat it as a prompt to dig deeper, reword the idea or rethink the audience, not as a final verdict.
Checkout is handled securely by Polar. Pro subscriptions can be managed or cancelled anytime from the customer portal in Settings.
Research your idea before you build it
Before you build it,
hear it.
Your future customers are already talking. Find them in one report.