Validating demand means searching for the problem, not the product, then grading what you find: the same complaint recurring across months, "is there a tool that…" posts that never reach a consensus answer, people building their own workarounds, and friction that has reached budget-holders. Draper ran this method on AI meeting tools, pulling Reddit threads from January 2024 to October 2025 (plus X posts through May 2026) across r/sales, r/sysadmin, r/Zoom, r/productivity, r/MicrosoftTeams and r/selfhosted. The category already had funded incumbents — Otter.ai, Fireflies, Read.ai — and the signals still pointed at one unserved wedge: consent and control, not transcript quality.
That wedge is now a checkable answer. Granola launched in May 2024 as a bot-free notepad — no participant joins the call; audio is captured on the user's own device and deleted after transcription — and went from a $250M valuation in May 2025 to $1.5B by March 2026. The earliest threads in this sample predate that launch; the later ones accumulated as bot-first incumbents kept supplying complaints. What follows is what the signals looked like, and what noise looks like next to them.
Draper query: How do I validate demand for a startup idea before I build it? Pull the demand signals for a real category from Reddit and X — recurring complaints, tool-seeking posts, workarounds, willingness-to-pay language — and show genuine demand versus weak demand, with example threads.
What counts as a real demand signal?
Five signal types, graded in rough order of strength:
| Signal | What it looks like | Why it matters |
|---|---|---|
| Workaround behaviour | "I built my own using n8n" | Users have already rejected every existing product and committed hours to a substitute |
| Institutional friction | IT admins banning a tool org-wide | The problem has reached someone with a procurement budget |
| Recurring pain | Same complaint, different users, across months | The problem is structural, not one person's bad day |
| Tool-seeking posts | "Is there a tool that…" with no consensus answer | Active demand that incumbents aren't satisfying |
| Willingness-to-pay language | Price comparisons, tier discussions | Bridges from problem to market |
What does strong demand look like in real threads?
The most repeated complaint in Draper's AI-meeting-tools sample (Reddit, January 2024 – October 2025) is uninvited AI bots joining calls: six distinct threads across five subreddits, naming three different tools, over nearly two years. Recurrence, breadth and specificity in one cluster. A r/sales thread titled "AI Meeting Notetakers are the bane of my existence" came from a user who otherwise likes Fireflies; the complaint was bots joining external client calls without consent. That nuance matters — it's product-specific pain, not category rejection.
The same complaint shows up at procurement level. A r/sysadmin thread from May 2025 documents an IT admin removing Read.ai for an entire organisation; a r/MicrosoftTeams thread from January 2024 asks how to block Otter.ai org-wide; an October 2025 r/sysadmin thread calls a Teams note-taker a "virus". When admins ban a tool company-wide, read the inverse: if a compliant version existed, that organisation is a buyer, and not at $20 a month.
Tool-seeking threads showed the open window. Across r/AIAssistants, r/ChatGPT, r/Zoom and r/productivity, "best AI meeting tool" posts through 2024 produced contradictory recommendations and no consensus winner, in a category with five-plus incumbents. A r/Zoom thread's top reply pointed to Zoom's native feature; the follow-ups called its quality poor. Solved on paper is not solved in practice.
Workarounds appeared in every community sampled. A top comment on an August 2025 r/productivity comparison thread: "I built one myself using n8n and WhatsApp." A r/selfhosted developer is building a fully open-source meeting note-taker, framed around privacy and data control. On X, a two-minute DIY Claude meeting-notes workflow from @rubenhassid pulled 162 likes and 17,100 views in May 2026 — a measurable audience for a hand-built workaround in a category full of commercial products.
What do weak demand signals look like?
The contrast case sits in the same AI-meeting-tools category. Threads like "What's your best AI productivity trick?" (r/Entrepreneur) and "7 AI tools I use to boost my productivity" (r/productivity) look like demand but grade out as noise: the answers are vague ("dumping my messy brain on Claude"), the engagement is low-effort or sarcastic, and no specific complaint recurs. The tells, generalised:
- No specific pain. You can't build a product around "AI helps me think".
- No recurrence. One or two posts, then silence.
- No workarounds. If nobody is hacking their own solution, the pain is tolerable, and tolerable pain doesn't generate paying customers.
- Satisfied users. Single-tool praise with no complaint creates no gap to build in.
A useful completion test: if you can't finish the sentence "people keep complaining that X doesn't Y", there is no product yet.
How did Granola find its wedge in a saturated market?
The threads weren't complaining about transcript quality. Users objected to tools behaving in ways nobody authorised — a consent and control problem, which defines a different product: no bot in the call, audio captured on the user's own machine, nothing that creeps out clients or trips IT alarms.
Granola built the bot-free version of that wedge. It launched in May 2024, inside the window these complaints were accumulating, raised $43M at a $250M valuation in May 2025, and closed a $125M Series C at a $1.5B valuation in March 2026, led by Index Ventures. The strongest signals in the dataset — recurrence, institutional friction, workarounds — located the opportunity a feature-comparison spreadsheet would have missed: every incumbent was competing on transcript quality while the market was asking for consent.
Validation also stays rereadable as the market moves. The bot-consent wedge is taken, but the October 2025 "virus" threads postdate Granola's rise, the r/selfhosted builders still want fully local, self-hostable processing that no incumbent offers, and org-wide admin controls remain what the sysadmin threads keep asking for. Saturated categories with loud complaints aren't dead markets. They're validated problems with an execution gap, and the threads say where the gap is now.
What should I check before building anything?
| Check | Strong signal | Weak signal |
|---|---|---|
| Recurrence | Same complaint 5+ times across 12+ months | One or two posts, then silence |
| Specificity | "Bots joining external client calls without consent" | "AI could be more useful in meetings" |
| Community breadth | Complaint appears in 3+ subreddits | Lives in one niche community |
| Workarounds | DIY automations, open-source alternatives | No DIY attempts anywhere |
| Willingness to pay | Price comparisons, procurement decisions, org-wide bans | "Cool if it were free" |
| Incumbent failure | No consensus winner in tool-seeking threads | One tool dominates every recommendation |
| Emotional intensity | "Bane", "virus", warning posts | Neutral or positive commentary |
The checklist costs an evening with Reddit search. The Granola counterexample shows what's on the other side of running it well.
Want to run analysis like this on your own brand or category? Try Draper free →