From SaaS Idea to Validated Problem: The First Two Stages, Recapped

Before you write a line of code, two things have to be true: you've turned your idea into a specific problem someone is already bleeding from, and you've confirmed with real people that the problem is real, repeated, and expensive. That's the entire job of the first two stages, and it's where most SaaS products are quietly won or lost. This post recaps everything we've covered so far in the Forgex SaaS Growth System, and sets up what comes next.

What are the first two stages of taking a SaaS idea to market?

The first two stages are ideation (turning an idea into a sharp problem) and discovery (confirming that problem is real by talking to people who have it), and they both happen before you build anything. Together they answer the only question that matters at the start: is there a specific person with an expensive problem who will pay to make it go away?

Here's the shape of the journey so far and where it's heading:

• Stage 1, Ideation. Convert a vague idea into a one-sentence problem attached to a named person, and decide whether it's a painkiller or a vitamin.
• Stage 2, Discovery. Talk to at least 20 people who fit that person, before building, to confirm the problem is real, repeated, and expensive.
• Stage 3, Demand validation (coming next). Prove people will actually act, sign up or pay, before you commit to building.
• Stage 4, Offer and pricing (coming next). Set a price that makes the market tell you whether the value is real.

Everything in the first two stages runs on one principle: it is far cheaper to find out you're wrong now, in a conversation, than later, after a build. The whole point of doing this work up front is that the cost of being wrong is still small.

Stage 1 recap: how do you turn an idea into a real problem?

You turn an idea into a real problem by stripping away the solution and checking whether a specific, costly, human problem is still standing on its own. An idea is what you want to build; a problem is the expensive pain someone already has whether or not your product exists. The market pays to remove pain, not to reward clever ideas.

The four moves that convert an idea into a problem:

1. Strip the solution. Delete every mention of your product and words like "platform," "streamline," or "leverage." See what pain, if any, remains. If nothing does, you had a solution hunting for a problem.
2. Name one person, not "everyone." Replace your category ("small businesses," "founders") with someone specific enough to find ten of them this week. Narrow beats broad every time, around 70% of successful micro-SaaS founders win one tight sub-niche first.
3. Write the problem in one plain sentence. In their words, with a real cost attached, no product mentioned. "Solo property managers running 20 to 60 short-term rentals lose 10+ hours a week updating prices by hand" is a problem. "An AI platform for property efficiency" is a fog.
4. Score it: painkiller or vitamin? A painkiller is a problem the person is already trying to fix, look for an existing workaround as proof. A vitamin gets a polite nod and a free trial that never converts.

The stakes here are not abstract. Across startup post-mortems, "no market need" is consistently the top cause of failure, cited in roughly 35 to 42% of cases. That is a pre-build mistake, knowable before a single line of code, if you do the ideation work honestly instead of falling in love with your own idea.

Stage 1 recap: why does narrowing your customer matter so much?

Narrowing matters because a product for everyone speaks specifically to no one, and a message broad enough to fit anyone resonates with nobody. "Anyone could use this" is the most common early-stage mistake, and it guarantees weak positioning, scattered features, and marketing that lands nowhere.

The counterintuitive part is that narrowing is a growth strategy, not a limitation:

• The math favors narrow. Capturing 10% of a focused niche is far easier than capturing 1% of a giant market, and it gives you customers who share one problem you can actually solve.
• A category is not a customer. "B2B SaaS companies" is a firmographic bucket with no shared pain or budget owner. A real customer profile has a shared problem, a shared workflow, and a place you can reach them.
• The winners started absurdly narrow. Twilio began with developers, Canva with small-business social media managers, Gong with sales teams. Each chose a market they could own completely, then expanded from strength.

The tool that captures this is a single ICP sentence: "I help [specific person] solve [specific problem] so they can [specific outcome]." If you can write that clearly, every later decision has a fixed point to align to. If you can't, they scatter no matter how good your product is.

Stage 2 recap: what does customer discovery actually involve?

Customer discovery is talking to at least 20 people who fit your target, before your product exists, to learn whether the problem is real, repeated, and expensive. It's the stage founders skip because it's slow and uncomfortable, and it's the single highest-leverage thing you'll do, because the information that saves you from building the wrong thing exists before you build, and asking is the only way to get it.

The essentials of doing it well:

• The number is about 20, but the real signal is pattern repetition. For a focused segment, themes start repeating by interview 5 to 8, and confidence solidifies around 20. You're done when you can predict the next person's answer before they give it.
• You don't need an audience. Find people through targeted outreach on LinkedIn (and Sales Navigator), niche subreddits, Slack and Discord communities, and Indie Hackers. Expect to message 100 to 200 people to book 10 to 20 calls, and ask every one for two or three introductions.
• The cost math makes it non-negotiable. A round of 20 interviews can run a few hundred dollars and stop you from spending $15,000 building the wrong thing. The interviews are almost never the expensive part.
• Wrong people and lukewarm answers both mislead. Ten conversations with non-ICP people are worth less than one with a real fit, and "sort of interesting, but I wouldn't pay" is a soft rejection dressed as encouragement. A flat no is cleaner data.

Discovery is where a hypothesis becomes a finding, or falls apart cheaply. Either outcome is a win, because both save you from the expensive version of finding out.

Stage 2 recap: what separates a good interview from a useless one?

A good interview is about the person's real past behavior; a useless one is about your idea and their predictions of the future. The framework most founders use for this is The Mom Test: ask questions so grounded in the person's actual life that even your mom couldn't give you a misleading answer.

The rules that make interviews worth running:

• Talk about their life, not your idea. The moment you describe what you're building, every answer becomes a reaction to your pitch instead of an honest account of their problem. Keep your solution out of the room until the end.
• Ask about the past, never the future. "Walk me through the last time this happened, what did you do?" produces facts. "Would you use this?" produces fiction, because people are poor predictors of their own behavior and inclined to answer politely.
• Count evidence, not compliments. Real validation comes in three currencies, time (a test session), reputation (an intro to their team), or money (a pre-order). "I love this" costs nothing and proves nothing.

The reason this matters so much: bad interviews aren't just a waste of time, they're dangerous, because a false yes convinces you you're on the right track and funds months of building the wrong thing. The discipline of asking about the past instead of the future is what separates expensive delusion from genuine signal.

What's the one thread connecting both stages?

The single thread running through ideation and discovery is this: chase evidence, not encouragement. Every trap in the first two stages, the "everyone" market, the vitamin mistaken for a painkiller, the polite yes, the friend who loves your idea, is a version of mistaking encouragement for evidence. Every good practice is a way to hunt for the harder, truer signal instead.

What "evidence, not encouragement" looks like in practice:

1. Evidence is behavioral. An existing workaround, a specific recent story, real time or money already spent. These happened, so they can't be faked into politeness.
2. Encouragement is verbal. "That sounds useful," "I'd totally use that," "great idea." These cost the speaker nothing, so they measure nothing but goodwill.
3. The whole game is telling them apart. A founder who can distinguish a compliment from a commitment will spend their build time on something real. A founder who can't will build a product people like and won't buy.

If you internalize nothing else from the first two stages, internalize this. It's the same discipline that carries into everything ahead, validation, pricing, launch, and retention are all just more sophisticated ways of chasing evidence over encouragement.

What's coming next in the Forgex SaaS Growth System?

Next, the series moves from confirming the problem to proving people will act on it, first through demand validation, then through pricing. Discovery tells you the problem is real. The next stages tell you whether people will sign up, and pay, to solve it, which is a higher bar and a different kind of proof.

Here's what's ahead:

• Demand validation. The move from "people say the problem is real" to "people act." You'll build a smoke-test landing page, drive real traffic to it, and measure whether strangers with the pain will hand over an email, or better, a pre-order. The only true validation is when people commit something, and this is where you find out if they will.
• Offer and pricing. Pricing isn't a Stage-10 afterthought, it's a validation instrument you set up now. We'll cover why launching paid from day one beats freemium for early signal, how to price against the value you remove rather than your hosting bill, and how a little pricing friction filters for people with the real pain.

The Forgex SaaS Growth System is a series that walks every step of the journey from a raw SaaS idea to a launched, growing product, one stage at a time. We've covered turning an idea into a validated problem. Demand validation and pricing come next, followed by MVP scope, launch, retention, and building an acquisition engine. Follow along to get each stage in full as it lands.

Frequently Asked Questions

What should I do before building a SaaS product?

Two things, in order: turn your idea into a sharp, specific problem attached to a named person, then confirm that problem is real by talking to at least 20 people who have it. An idea is a solution looking for a problem, which is backwards; the market pays to remove pain, not to reward ideas. Roughly 35 to 42% of startups fail from "no market need," a mistake you can catch in conversations before you write any code.

How do I know if my SaaS idea is worth building?

Run it through two filters. First, can you state the problem in one plain sentence, in your customer's words, without mentioning your product? If not, you have a solution hunting for a problem. Second, are people already using a clumsy workaround, a spreadsheet, a manual process, a contractor, to solve it? An existing workaround is proof the pain is real and worth paying to remove. No workaround usually means a vitamin, not a painkiller.

How many customer interviews do I need before building?

At least 20 with people who fit your target, because that's roughly where a focused segment reaches pattern repetition and you can predict answers before people give them. Themes often start repeating by interview 5 to 8, but 20 confirms the pattern is real. The stopping signal isn't a fixed count, it's saturation: when new interviews reinforce what you already know instead of teaching you something new.

What comes after customer discovery?

Demand validation, then pricing. Discovery confirms the problem is real; validation proves people will actually act on it by signing up or paying, usually through a smoke-test landing page that drives real traffic and measures commitment. After that comes setting your offer and price, which doubles as a validation instrument. The principle carries through all of it: chase evidence (real signups, real money) over encouragement (compliments and stated interest).

What is the Forgex SaaS Growth System?

It's a series of articles that walks every step of taking a SaaS from a raw idea to a launched, growing product, one stage at a time. So far it has covered ideation (turning an idea into a validated problem) and customer discovery (confirming that problem with real people). Upcoming stages include demand validation, pricing, MVP scope, launch, retention, and acquisition. Follow along to get each stage in full as it publishes.

---