RequestHunt: feature request discovery for solo founders

The problem

Solo founders need to make good product bets with limited time. The usual options are slow: scrolling through communities, copying posts into notes, searching GitHub issues by hand, or waiting until you have enough users to see repeated requests inside your own inbox.

The risk is not just wasting time. The bigger risk is building from imagination instead of evidence.

What RequestHunt does

RequestHunt helps you look for repeated demand in public conversations. It is designed around practical product research questions:

• What are people repeatedly asking for?
• Which workflows are painful enough that users complain in public?
• Which existing tools create frustration?
• What feature requests show up across communities?
• What language do potential users already use to describe the problem?

The goal is not to create a perfect market report. The goal is to shorten the loop between curiosity and evidence.

How it fits into a one person company workflow

Use RequestHunt when you are choosing what to build next, validating a narrow SaaS idea, writing landing page copy, or preparing a customer discovery call.

A simple workflow looks like this:

1. Pick a market, community, or product category.
2. Collect public conversations related to that space.
3. Look for repeated pain points and explicit feature requests.
4. Turn repeated signals into hypotheses.
5. Validate the strongest hypotheses with users, landing pages, or small prototypes.

Because RequestHunt exposes an MCP server command, it can also fit into AI-assisted research workflows where you want your assistant to work with real market signals instead of generic brainstorming.

Best use cases

RequestHunt is especially useful for finding Reddit feature requests, reviewing GitHub issues, spotting complaints about competitor products, validating micro-SaaS ideas, collecting customer language, and preparing product discovery interviews.