# Find whitespace in what experts call unsolved

> Practitioners openly list what's broken in their field; harvest the "nobody has figured out X yet" moments as an opportunity map.

- For: Founder / CEO
- Category: Market & Competitor Research
- MCP tools: deep_query
- HTML version: https://veridive.com/mcp/use-cases/whitespace-from-open-problems

## The problem

Every industry maintains a public list of its unsolved problems. It isn't written anywhere — it's *spoken*: the moment in a panel when an expert sighs "honestly, nobody's cracked this," the podcast tangent where two operators trade complaints about the tool that doesn't exist, the Q&A answer that starts with "great question, and the honest answer is we all just work around it."

Founders hunt for exactly these moments and mostly find them by luck — you happened to hear that episode. The systematic version is a different game: collect what practitioners across a field repeatedly name as broken, missing or endured, and you're reading a demand backlog written by the customers themselves, before anyone builds the supply.

## How veridive MCP helps

**deep_query** is built to answer questions whose evidence is scattered across hundreds of conversations. Ask it what experts in a field describe as unsolved and it researches the spoken record — panels, podcasts, conference Q&As — and returns the recurring complaints **with citations to each moment of frustration**.

The output reads like an opportunity map with provenance: which problems come up once (anecdote) versus everywhere (market), who exactly suffers them, what the current workaround costs, and the language practitioners use — which later becomes your landing-page copy, because it's literally the customer's phrasing. Re-run it quarterly and you also see which whitespace is closing, and which keeps being named year after year because it's genuinely hard — or genuinely yours to take.

## How to run it

1. **Connect veridive MCP** — One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.
2. **Harvest the open-problem list** — Ask for what the field itself calls unsolved. The answer aggregates recurring pain across many conversations, cited per moment.

   ```
   What do practitioners in <field> repeatedly describe as unsolved, broken or endured — the 'nobody has figured this out' moments? Group by theme, cite each — use veridive's deep_query.
   ```
3. **Qualify the pain** — For the promising themes, dig into who suffers and what the workaround costs — the difference between an annoyance and a budget line.

   ```
   For <problem theme>: who specifically complains about it, what workarounds do they describe, and what do those cost them? Citations please.
   ```
4. **Check the graveyard before you build** — Whitespace is only white if attempts haven't quietly died there. Ask what's been tried and why practitioners say it fell short.

   ```
   Has anyone tried solving <problem theme>? What do people say about existing attempts and why they don't suffice? Cited.
   ```

## Problems it solves

- Opportunity discovery runs on serendipity — the episode you happened to hear, the panel you happened to attend.
- One loud complaint is indistinguishable from widespread pain without aggregation across many voices.
- The workaround economy (spreadsheets, agencies, duct tape) is invisible in market reports but narrated constantly on air.
- You can't tell uncontested whitespace from a graveyard of failed attempts without the field's own post-mortems.

## Why it's valuable

- A demand backlog written by the market itself — problems named repeatedly, by name, with receipts.
- Pain qualification built in: who suffers, how often it's named, what the workaround costs.
- The customers' own phrasing, ready to become positioning that sounds like it read their mind.
- Quarterly re-runs show which whitespace persists — the durable kind worth building on.

## Example prompts

```
What do practitioners in <field> repeatedly call unsolved or broken? Group by theme with citations — use veridive's deep_query.
```

```
For <problem>: who complains, what workarounds do they use, what do those cost? Cited.
```

```
What's been tried for <problem> and why do practitioners say it falls short? Citations.
```

## FAQ

**Isn't this just doing customer discovery interviews?**

It's the layer before and around them: hundreds of practitioners already said the candid thing on the record. Harvest that first, then spend your interview slots validating the two themes that survived aggregation.

**How do I avoid building for a vocal minority?**

Ask for recurrence explicitly — the synthesis distinguishes a theme named across many independent conversations from one person's crusade, and the citations let you count the voices yourself.

**What makes the citations matter for a founder?**

Investor and co-founder conversations. "Operators keep naming this exact problem — here are eleven of them saying it on camera" is a fundamentally different pitch than a hunch.

## Related use cases

- [Map expert consensus before entering a market](https://veridive.com/mcp/use-cases/map-expert-consensus-before-market-entry.md) — Ask one question — "is this market saturated?" — and get a grounded answer built from what practitioners actually say, with timestamped citations.
- [Mine review videos for user pain](https://veridive.com/mcp/use-cases/user-pain-mining.md) — Reviewers narrate friction in real time; harvest the "why is this so hard" moments across your category.
- [Find the gaps your niche hasn't covered](https://veridive.com/mcp/use-cases/content-gap-finder.md) — Ask what questions keep coming up with weak answers; the uncovered intersection is your content calendar.

---

Part of the veridive MCP use-case library: https://veridive.com/mcp/use-cases.md
Server docs for agents: https://veridive.com/mcp.md