How to Find Startup Ideas Before You Open Claude Code (Evidence Over Vibes)

You can scaffold a working app in a weekend now. Cursor, Claude Code, and Codex have collapsed the cost of building so far that "can I build it?" is barely a question anymore. Which means the only question left is the one most of us skip: should this exist at all?

Here's the uncomfortable part. The most common reason startups fail isn't bad code or slow shipping — it's building something nobody needs. The cheaper building gets, the more dangerous that failure mode becomes, because nothing stops you from shipping a beautiful solution to a problem zero people have.

So before you open your editor, here's how to find startup ideas worth building, in four steps:

1. Collect problem signals, don't brainstorm. Hunt for recurring complaints, manual workarounds, and rising searches — not whiteboard concepts.
2. Name the specific gap those signals expose (underserved audience, missing feature, broken workflow, mispricing, trend-driven opening).
3. Confirm demand is real by triangulating across independent sources. One signal is noise; convergence is evidence.
4. Pressure-test fit against your actual constraints, then score the survivors so you commit to the strongest opportunity, not the most exciting one.

That's the whole method. The rest of this post is how to run it like an engineer — with provenance, multiple sources, and a bias toward evidence over enthusiasm.

Ideas Are Discovered, Not Invented

The "flash of inspiration" founder myth is mostly survivorship bias. In practice, good ideas are downstream of problems. Someone keeps hitting a painful workflow, builds a hacky workaround, and realizes thousands of other people are duct-taping the same thing. The idea was the answer to a problem they could already see.

This is good news for builders, because it means finding ideas isn't a creativity test — it's a search problem. You're not trying to be clever. You're trying to be observant, then verify. Demand exists before your product does. Your job is to locate it, not conjure it.

Brainstorming fails precisely because it optimizes for novelty instead of need. A whiteboard rewards clever-sounding concepts, but cleverness is uncorrelated with whether anyone will pay. Worse, an idea generated in isolation arrives with zero attached evidence — so you can't tell a real opportunity from a daydream until you've already burned a weekend (or a quarter) building one.

The Gap Categories: Where Opportunities Actually Hide

A "market gap" is just a specific, unmet need inside an existing market — a place where current solutions leave money on the table. Naming the category of gap turns a vague hunch into a thesis you can test. Most startup-sized gaps come in a handful of recognizable shapes:

• Underserved-audience gaps — the product serves the mainstream well but ignores a segment with different needs: solo founders, a specific industry, a non-English market, a budget tier nobody bothers with.
• Feature gaps — the category exists, customers are vocal about a missing capability, and incumbents are too big or too slow to ship it.
• Workflow gaps — people stitch together three tools and a spreadsheet to get one job done. The duct-tape is itself proof of demand.
• Positioning and price gaps — a capable tool exists but is mispriced, overbuilt, or aimed at the wrong buyer, leaving room for a focused alternative.
• Trend-driven gaps — a new technology, regulation, or behavior shift makes a previously impossible product viable, and the first credible entrant defines the category.
• Quality and trust gaps — the category is full of solutions people actively distrust, which is itself an opening.

If you can't name which shape your gap is, you don't have a gap yet — you have a guess.

Reading Demand Signals (Like You'd Read Logs)

Once you have a candidate gap, the real question is: is anyone actively trying to solve this problem right now? You answer it by reading demand signals — and the single most important discipline is to never trust one source.

Any single signal can lie to you. A Google Trends spike might be seasonal noise. A loud Reddit thread might be a vocal minority of five people. Heavy VC funding might mean the space is already a knife fight. Convergence across independent sources is what separates a real opportunity from a mirage. Think of it like distributed tracing: one span tells you nothing; the pattern across spans tells you the truth.

Here's what each source actually tells you when you're doing market gap analysis:

• Google Trends — whether search demand for the problem is rising. Problem-shaped queries (how do I…, alternative to…, why is X so hard) matter far more than brand awareness.
• Reddit — unfiltered pain. The most valuable threads are people describing the manual workaround they built because nothing adequate exists. A workaround is direct evidence of willingness to act. (This is the modern GummySearch alternative workflow — mining community pain instead of paying for a dead tool.)
• Product Hunt — what's launching and getting traction, so you can tell a validated category from a saturated one — and spot where launches are thin.
• Hacker News — technical critiques of existing tools and early signals of shifts that open new categories. This is where developer-shaped pain shows up first.
• VC funding data — where institutional capital is flowing. Rising investment signals validation; over-funding warns of a market that's already overheated.
• G2 / Capterra reviews — exactly what users hate about incumbents. Every one-star review naming a missing capability is a feature gap with a name attached.
• X (Twitter) — what builders and early adopters are talking about before it goes mainstream.

The power is in the overlap. When rising searches, a recurring Reddit complaint, healthy-but-not-overheated funding, and a wall of one-star competitor reviews all point at the same unmet need, you're not guessing anymore. You're looking at converging evidence that a real audience is actively shopping for a better answer.

The Workaround Test: the strongest demand signal is a workaround. When people are stringing together spreadsheets, copy-paste rituals, and a chain of half-fitting tools, they're already paying for the problem with their time. A product that removes that pain has a buyer waiting. Hunt for "how I hacked together…" and "my current process is…" posts.

If you want the deep-dive on mining communities for these signals, the find startup ideas on Reddit playbook breaks down exactly which threads count as evidence.

Is the Gap Real? (Demand AND Fit)

Finding a gap and confirming it's worth your time are two different jobs. A gap can be real and still be a bad idea for you specifically — too small to sustain a business, too crowded to enter, too cheap to monetize, or a poor fit for your runway and skills.

So "is the gap real?" has to be answered on two axes:

Demand axis — look for three confirmations: people are actively searching for a solution (intent, not just awareness), they're already spending time or money on inadequate alternatives, and the pattern shows up across more than one independent source. If demand only appears in one place, treat it as a hypothesis, not a finding.

Fit axis — be honest about your constraints. A funded YC team and a bootstrapped solo dev should chase completely different gaps in the same market. This is where generic idea tools fail you: they hand the same advice to everyone, regardless of whether you have one weekend or eighteen months of runway.

This second axis is the one builders consistently underweight. You can vibe-code a prototype of almost anything now — but you can't vibe-code distribution, runway, or a market that's a fit for a solo operator. Decide before the build whether this opportunity matches your actual reality.

Turn a Competitor's Website Into a Wedge

Some of the best ideas are hiding in plain sight on a competitor's own homepage. An established product tells you, for free, who the customer is, what the category looks like, and — crucially — what it chooses not to do. The features it omits, the segment it ignores, and the complaints in its reviews are the outline of your wedge: the narrow, specific entry point where you can win before expanding.

This reframes a scary thought into a useful one. "A competitor exists, so the market is taken" becomes "a competitor exists, so the market is validated — and here's precisely where it's weak." A crowded market with a clear wedge is often a far better bet than an empty one, because the demand is already proven; you just need a sharper angle. The full move is broken down in the competitor → wedge walkthrough.

From Ideas to a Scored Shortlist

Here's where I'll show how I run this loop. I built Gaplyze to automate the heavy parts of exactly this method, so the workflow looks like a pipeline:

1. Generate candidates from real signals. Give it a topic, niche, audience, or even a competitor's URL, and Idea Generation researches the space across seven-plus real sources (Google Trends, Reddit, Product Hunt, Hacker News, VC funding, G2/Capterra, X) and returns six evaluated opportunity candidates, each with estimate scores and a framing dossier. You start from an evidence-backed list, not a blank page.
2. Read the signals and name the gap. For each candidate, check whether the demand signals converge across sources and identify which gap category it exploits. Candidates whose signals don't converge get cut here, fast.
3. Mine competitor sites for the wedge. Web Insights takes a competitor URL and turns it into a scored opportunity report with specific, impact-estimated recommendations — surfacing the underserved audiences, missing capabilities, and positioning gaps the incumbent left open. That's how a vague "there's something here" becomes a defensible entry point.
4. Score every survivor across eight dimensions. PI Scoring rates each idea across eight dimensions — market demand, success probability, competition, innovation, scalability, time to market, cost efficiency, and risk — on a consistent nine-tier scale, with a confidence level and rationale for every score, plus a SWOT, a commercial verdict, and the three-to-five killer assumptions you still have to test.
5. Rank, compare, and commit. Because every idea is scored on identical criteria, you compare them like a portfolio. The candidate that sounded best in conversation often scores weakest on competition; the one you almost dismissed sometimes has the strongest demand.

The part that'll resonate with engineers: when you go deep, Strategic Vectors adds an evidence ledger that tags every claim as supported (with a source), inferred, or missing proof. It's provenance for your thesis — the same instinct that makes you distrust a function with no tests should make you distrust a business claim with no source. A gap built on supported demand is worth your weekend. A gap built on inferred claims is a research task, not a build task.

And because your constraints shouldn't get lost between steps, Project Framing threads your actual reality — team size, budget, runway, stage, geography — through every artifact, so an opportunity is assessed against your situation, not a hypothetical founder's.

Honest Comparison: Where Gaplyze Fits vs the Alternatives

If you've searched for how to find startup ideas, you've probably met two kinds of tools. Let me be straight about where each one fits.

Curated idea databases — IdeaBrowser is the best-known — publish a daily idea and a big library of pre-researched concepts with validation metrics. They're genuinely useful for inspiration and for seeing how an opportunity gets analyzed. The trade-off is that a database is a fixed catalog: the ideas are generic to the catalog, not generated for your context, your niche, or the competitor you're actually up against — and everyone browsing sees the same entries. Gaplyze works the other way around: it generates and scores opportunities for your input, and shows the multi-source evidence behind each one.

Generic "market gap analysis" and GIS tools dominate those search results, but most of them analyze geographic or retail gaps — where to place a physical store, which territory is underserved on a map. That's a completely different problem from finding a software or business-model opportunity. They won't tell you whether founders are complaining about a missing feature on Reddit, or whether VC money is flowing into a category. If you're trying to find SaaS ideas or find business opportunities in software, map-coordinate tools are the wrong instrument.

The deeper differentiator is the connected journey. Most tools stop at a verdict or a list. Finding the idea is step one of a chain — discovery → validation → strategy → blueprints → roadmap — not a destination.

Beware the "AI said yes" trap. Plenty of tools will validate any idea you give them in a few seconds with no sources — and an idea that passes a credulous checker is more dangerous than no validation at all, because it manufactures false confidence. As builders we already know this instinct: a test that always passes is worse than no test. Insist on seeing the evidence. That's the entire point of an evidence ledger that tags each claim supported / inferred / missing proof — so a "yes" you can't trace never sneaks into your decision.

Make It a Habit, Then Go Build

Finding good ideas isn't a one-time lucky strike — it's a practice that compounds. The more candidates you run through this loop, the faster you recognize converging signals and dismiss noise at a glance. Each pass calibrates your judgment.

So make it a routine. Pick a space you understand. Generate a batch of candidates from real signals. Read where the demand converges. Mine the incumbents for a wedge. Score the survivors. Most candidates die early — that's the point. The few that survive multi-source evidence and an honest fit check are the ones worth opening Cursor for.

The goal isn't to fall in love with the first idea you find. It's to build a pipeline of evidence-backed opportunities and let structured scoring point you to the strongest one — so that when you finally do start vibe-coding, you're building the right thing.

Try it on a space you care about: generate startup ideas from real signals →

This is a syndicated post. The canonical, continuously-updated version lives on Gaplyze.