Validate your indie game idea in one day by checking five pass/fail signals: real revenue in your genre, an active community, a named player profile, measurable prototype response, and whether you'd play it yourself. Vibe coders ship fast; this checklist proves demand exists before you sink a weekend or a quarter into the build.
What Does Market Validation Mean in Indie Game Dev?
Market validation is proof that players already want a game like yours, gathered before you write the code. Not opinions from friends. Evidence: people paying for similar games, communities discussing the genre, a wishlist or waitlist that grows when you show something.
Why bother? Because the base rate is brutal. Industry analyses of Steam releases consistently find that the median indie game earns only a few thousand dollars in its first years, with a small top slice capturing most revenue (VG Insights). Building for three months and then discovering nobody wants it is the default outcome, not the exception.
Validation flips that. It turns "I think players will like this" into a pass/fail checklist you can run in a day, before you sink a weekend or a quarter. The same discipline applies whether you're shipping a game or a SaaS: define the exact player, find where they hang out, and test demand with something cheap first. If you've never mapped your player that precisely, our guide on finding the gap in your positioning walks through it step by step.
Why Do Most Indie Games Fail to Find Players?
Most indie games don't fail on code or art. They fail on demand: the builder shipped something polished that nobody was searching for, in a genre already crowded, aimed at a player they never defined. Sound familiar? It's the same trap solo SaaS founders hit: three months of building, zero people who want it.
The pattern is building first and validating never. You pick a genre you like, copy mechanics from games you've played, and only think about players after launch. By then the Steam page is live, the wishlist count is embarrassing, and there's no budget to fix it.
The fix is cheap: run the five signals below before writing a line. If you want the deeper mechanics of why "build it and they'll come" dies quietly, that's the same authority trap covered in why authority is the wrong game.
Signal 1: Are Players Already Paying for Games Like Yours?
Read the genre, not the idea
Your idea is unvalidated. Your genre is not. Open the Steam top sellers chart and check whether games mechanically similar to yours are sitting in paid positions right now. If three or more are, spending demand already exists and your job is differentiation. If none are, you are not competing, you are educating a market with no budget.
This is the same trap documented in indie postmortems again and again: the game ships polished, gets zero wishlists, and the developer realizes the build was never the bottleneck. Distribution was. Building fast with Cursor or Lovable makes this worse, not better, because you can now ship a quarter of work into a dead market in a weekend. The same pattern shows up outside games, which is why we wrote about why every AI startup sounds the same: copying what already exists feels safe and validates nothing.
Pass/fail thresholds for genre demand
Run this in 30 minutes:
| Check | Pass | Fail |
|---|---|---|
| Similar games in Steam top sellers | 3+ | 0 |
| Similar games with 1,000+ reviews | 2+ | 0 |
| A paid game in your genre released in the last 6 months | Yes | No |
Two or more passes: proceed to Signal 2. Zero passes: change genre or change game.
Signal 2: Is There a Live Community Talking About This Kind of Game?
A community proves demand when people discuss problems your game solves, not just memories of games they loved. Nostalgia sounds like "they don't make them like this anymore." Demand sounds like "I'd pay $15 for a roguelike with X mechanic." Same subreddit, completely different signal.
Where to look: subreddits, Discords, itch.io comments
Search Reddit for your genre plus the specific hook (r/roguelikes, r/indiegaming, genre Discords, itch.io comment sections on comparable games). Read the last 30 days, not the all-time top posts. Sort by new.
Activity signals that beat member counts
A 200k-member subreddit with three posts a week is weaker than a 5k Discord where people post clips daily and argue about mechanics. Look for: recurring "anyone know a game where..." threads, wishlist or purchase questions, and comments on similar indie games that name what's missing. Those are players describing the game they can't find yet.
If every thread is screenshots and hype with zero "I wish this existed" posts, the community is consuming, not buying. That's a fail for now, not forever. Write down the exact phrases people use, because they become your store page copy later. The same trap applies to landing pages that describe what you built instead of what buyers want: see 7 signs your homepage describes the build, not the buy.
Signal 3: Can You Name the Exact Player and Where They Hang Out?
"Roguelike fans" is not a player. "People who liked Vampire Survivors but want co-op" is. If you can't write one sentence describing your player's habits, you can't find them, and a game nobody can find is a game nobody buys.
Run this test in an hour. Open Steam's top sellers list and check whether games like yours chart in your genre's tags. Then name the two subreddits, Discords, or YouTube channels where those players already talk. If you can't name them, that's a failed signal, not a research gap to defer.
Specificity also decides how you test demand later. A vague audience gives you vague wishlist numbers; a named one gives you posts you can reply to and a trailer you can put in front of actual fans. The same discipline applies before any launch: our pre-launch waitlist framework walks through deciding whether early signups are real demand or polite noise.
Pass: named player, named channels, genre demand confirmed. Fail: "everyone likes fun games."
Signal 4: Does a Prototype or Trailer Pull Measurable Response?
You test demand by shipping the smallest honest slice of the game and counting how strangers react. Not friends, not Discord regulars who feel bad for you. Strangers who have no reason to be polite.
The weekend prototype test for vibe coders
You can build fast, so use it. Pick the one mechanic that makes your game different and build only that in a weekend with Cursor or Lovable. Ugly art, no menus, no tutorial. Then make a 30-second clip of it and post the clip where your exact player already hangs out: the right subreddit, a relevant X community, a TikTok with the genre tag.
The clip is the test. The prototype behind it just has to look fun in motion, not be finished. If you cannot isolate one mechanic worth showing, that is itself a fail on Signal 3, because it means you cannot name what makes the game worth playing.
What counts as a pass: response rates to watch
Set numbers before you post so you cannot rationalize later. A pass looks like: a wishlist add or email signup rate of 5%+ of people who watch the clip, at least one comment asking when it drops or how to play, and someone else sharing it without you asking. Two of those three is a pass. Zero or one is a fail, and the fix is usually the mechanic, not the video editing. Run the test again with a different mechanic before you write a single line of the real game.
Signal 5: Are You Your Own Player?
The Leadmore AI founder shipped for three months and found no users. His own diagnosis: he was never a user of his product, so he copied competitor features and built things nobody asked for. The same failure mode kills indie games. If you would not install your own game and play it tonight, that is a failed signal, and no amount of polish fixes it.
Run the test honestly. Open your build, play for 30 minutes, and log every moment you got bored. If you cannot finish a session without forcing yourself, neither will a stranger.
Then post a devlog publicly and watch whether strangers return. itch.io's built-in devlog and community tools exist exactly for this: you publish progress updates, and follow counts and comments tell you whether anyone cares enough to come back (itch.io creator docs). Returning strangers are the signal. Polite one-time comments are noise.
What Do You Do When a Signal Fails?
One failed signal means scope down. Two or more means kill or pivot. That's the rule.
Scope down when the community exists and players pay for similar games, but your prototype got a weak response. The demand is real; your angle isn't. Cut the feature set to the one thing testers reacted to, rebuild the prototype around it, and re-run Signal 4 in another weekend.
Kill when you can't name the player or find a live community. No audience, no comparable sellers, no place to post means you'd be building for nobody. Drop it and take the next idea through the same checklist.
Pivot when the genre passes but you're not your own player. That's the Leadmore AI lesson: building features copied from competitors, for people who aren't you, produces things nobody asked for. Change the concept to one you'd actually play, then validate again.
A failed signal costs you a day. Skipping validation costs a quarter.
Frequently Asked Questions
How do I validate an indie game idea before building it?
Run five pass/fail signals in a day: check whether similar games sell on Steam's top sellers chart, find a live community discussing the genre, name your exact player and where they hang out, post a weekend prototype clip and measure response, and confirm you'd play it yourself. Two or more failures means kill or pivot.
Can you actually make money as an indie game dev?
Yes, but the base rate is brutal. Industry analyses of Steam releases consistently show the median indie game earns only a few thousand dollars in its first years, with a small top slice capturing most revenue. The games that earn do so because demand was proven before the build, not after.
How long should I spend validating a game concept?
One day. The genre checks take 30 minutes, naming your player takes an hour, and the prototype test fits a weekend. A failed signal costs you a day; skipping validation costs a quarter. If validation stretches past a week, you're researching instead of testing, and the numbers you set beforehand should settle it.
Do I need a Steam page before I validate my game?
No. Validation starts with the Steam top sellers chart as research, not with your own page. Your first test is a 30-second prototype clip posted where your players already gather, counting wishlist or email signups from strangers. Build the Steam page after a signal passes, when you know the store copy worth writing.