How to Validate Demand Before You Finish Building in Cursor

Cursor makes building dangerously easy. You can go from idea to deployed app in a weekend. And that is exactly the problem.

When building is this fast, the feedback loop that used to protect developers from bad ideas — the weeks of development that gave you time to question whether anyone actually wanted the thing — disappears. You can ship something nobody needs in 48 hours and not realize it for months.

I have watched this pattern repeat dozens of times in developer communities: a technical founder builds an impressive product with Cursor, launches it, hears crickets, builds more features, hears more crickets, and eventually abandons the project. Not because the product was bad. Because it solved a problem nobody was willing to pay to fix.

Validation is not optional. It is the highest-leverage thing you can do, and it should happen before you finish building — ideally before you start.

This guide gives you practical, developer-friendly validation techniques that work on a timeline of days, not months.

The Validation Mindset Shift

Developers are trained to think in terms of feasibility: can I build this? Validation requires a different question: should I build this?

"Should" here is not philosophical. It means: is there a group of people who have this problem, know they have this problem, are actively looking for a solution, and are willing to pay for one?

All four conditions must be true. Let us break them down:

1. The problem exists: People actually experience the pain you think they do.
2. They are aware of it: They know they have this problem (some problems are invisible to the sufferer).
3. They are seeking solutions: They have looked for or would look for a way to fix it.
4. They will pay: The problem is painful enough that money is a reasonable exchange for a solution.

If any of these is false, your product will struggle regardless of how well it is built.

Validation Method 1: The Search Test (30 Minutes)

The fastest validation technique. If people are actively searching for solutions to the problem you solve, there is demand.

How to Do It

1. Go to Google Keyword Planner (free with a Google Ads account) or use a tool like Ubersuggest.

2. Search for phrases your potential customer would type when looking for a solution:

   • "how to [solve problem]"
   • "[problem] tool"
   • "[problem] software"
   • "best [solution category]"
   • "[competitor name] alternative"

3. Look at monthly search volume:

   • 100+ searches/month: There is real demand. People are looking for this.
   • 10-100 searches/month: Niche demand. Can work if you are targeting a specific audience.
   • <10 searches/month: Either the problem is too niche, or people describe it differently. Try different keywords before concluding there is no demand.

What the Data Tells You

High search volume for problem-related keywords (e.g., "how to organize client feedback") means people know they have the problem and are looking for help. This is strong validation.

High search volume for solution-related keywords (e.g., "client feedback tool") means people are actively shopping. Even stronger.

High search volume for competitor names means there is an established market. Strongest signal of all — if competitors exist and have customers, demand is proven.

Red Flags

• Nobody is searching for anything related to your problem space
• The only searches are for the exact product category name you invented
• All search volume is for informational queries, none for solutions

Validation Method 2: The Community Test (2-3 Hours)

Go where your potential customers talk about their problems and see if your problem shows up.

How to Do It

1. Identify 3-5 communities where your target audience hangs out:

   • Reddit subreddits related to your space
   • Slack/Discord communities
   • Twitter/X discussions
   • Stack Overflow, Indie Hackers, Hacker News

2. Search these communities for discussions about your problem. Look for:

   • People asking how to solve the problem
   • People complaining about existing solutions
   • People sharing workarounds (spreadsheets, manual processes, scripts)

3. Count and categorize what you find:

   • 10+ discussions in the last 6 months: Strong signal
   • 3-10 discussions: Moderate signal, dig deeper
   • <3 discussions: Weak signal, consider pivoting

What You Learn

The language people use to describe the problem is gold. It tells you how to write your marketing copy. If they say "I'm drowning in client emails," your headline should use the word "drowning," not "overwhelmed by communication overhead."

You also learn what they have tried. This tells you who your real competitors are — often not the products you expected, but spreadsheets, email folders, or just suffering in silence.

For more on finding and reaching your first customers: How to Get Your First Paying Customers as a Technical Founder.

Validation Method 3: The Smoke Test (1-2 Days)

Build a landing page for your product before the product exists. Drive traffic to it. See if people try to sign up.

How to Do It

1. Build a simple landing page with:

   • A clear headline describing the outcome
   • 3 bullet points about key benefits
   • A CTA button ("Get early access" or "Join the waitlist")
   • An email capture form

2. Drive traffic using one or more of these methods:

   • Post in relevant communities (with context, not spam)
   • Run $50-100 in Google Ads targeting your problem keywords
   • Share on your social media with a personal story about the problem
   • Post on Indie Hackers or Hacker News with a "Show HN" or "Ask IH"

3. Measure results over 7 days:

   • 5%+ email capture rate: Strong interest. People want this.
   • 2-5% email capture rate: Moderate interest. Might need better positioning.
   • <2% email capture rate: Weak interest. Revisit the problem or the messaging.

The Advanced Smoke Test: Pre-Selling

Instead of an email capture, add a "Buy now" or "Pre-order" button with pricing. Use Stripe or Gumroad to accept actual payments with a note: "Your card will be charged when we launch. Full refund if we don't ship by [date]."

If people pay before the product exists, you have validated demand definitively. Even 5 pre-orders is a stronger signal than 500 email sign-ups.

Validation Method 4: The Conversation Test (1 Week)

Talk to 10-15 potential customers. This is the most informative validation method and the one developers most want to avoid.

How to Do It

Reach out to people who match your target audience:

"Hi [Name], I'm researching how [audience] handles [problem]. Would you have 15 minutes for a quick call? Not selling anything — just trying to understand the problem better before I build a solution."

The Interview Structure

Questions to ask:

1. "Tell me about the last time you dealt with [problem]. Walk me through what happened."
2. "How often does this come up? Weekly? Daily?"
3. "What do you currently do about it?"
4. "What's the most annoying part of your current approach?"
5. "If I built a tool that [your solution], would you use it?"
6. "Would you pay $X/month for it?" (Name a specific price.)
7. "What would make you NOT use it?"

Questions NOT to ask:

• "Do you think this is a good idea?" (Everyone will say yes to be polite.)
• "Would you use a tool that does X, Y, and Z?" (You are describing a fantasy. Focus on the problem.)
• "How much would you pay?" (Open-ended pricing questions get useless answers. Anchor with a specific number.)

Interpreting Results

Strong validation signals:

• People describe the problem with emotion ("It drives me crazy")
• They have already tried to solve it (and failed or compromised)
• They immediately ask when they can use your product
• They agree to pay the price you suggested without hesitation

Weak validation signals:

• "That sounds cool" (polite but not excited)
• "I don't really deal with that problem" (wrong audience or problem is not real)
• "Maybe if it was free" (not willing to pay means the problem is not painful enough)

Validation Method 5: The Competitor Revenue Test (1 Hour)

If competitors in your space are making money, demand exists. You do not need to validate demand — you need to validate your differentiation.

How to Estimate Competitor Revenue

1. Check review sites (G2, Capterra) for number of reviews. Rough rule: 1 review = 50-200 customers.
2. Check their LinkedIn for employee count. Rough rule: 1 employee = $100K-200K ARR for SaaS.
3. Look for public revenue statements (blog posts, podcast interviews, Indie Hackers profiles).
4. Use BuiltWith or SimilarWeb to estimate their web traffic.

What This Tells You

If competitors have:

• $0-10K MRR: Early market. Validate that the market will grow.
• $10K-100K MRR: Proven market. Focus on differentiation.
• $100K+ MRR: Large market. Find a specific niche to start in.

If no competitors exist at all, be very careful. It usually means one of two things: you have found a genuinely new market (rare), or the market does not exist (common).

Combining Methods for Confidence

No single method gives you certainty. Use at least three:

| Confidence Level | Methods Required | |---|---| | Low confidence | Search test only | | Medium confidence | Search test + community test + conversations | | High confidence | Search test + community test + conversations + smoke test with pre-orders | | Maximum confidence | All of the above + competitor revenue verification |

What to Do When Validation Fails

If your validation comes back weak, you have three options:

Option 1: Pivot the Audience

Same product, different user. Maybe your project management tool is not for freelancers — it is for agencies with 3-5 people.

Option 2: Pivot the Problem

Same audience, different pain point. Maybe freelancers do not care about project management — but they desperately want better invoicing.

Option 3: Pivot the Solution

Same problem, different approach. Maybe the problem is real, but a full SaaS product is not the right format. Maybe it is a template, a course, or a browser extension.

For related reading on market approaches: How to Market a SaaS You Built With Cursor covers positioning after validation is complete.

The Cursor Builder's Validation Advantage

Here is why validation is particularly powerful for Cursor builders: if validation succeeds, you can build the MVP in days. This means you can validate 3-4 ideas in the time it takes a traditional developer to validate one.

Use this speed strategically:

1. Week 1: Validate Idea A (search test + community test + 5 conversations)
2. Week 2: If Idea A fails, validate Idea B
3. Week 3: Build an MVP for whichever idea validated strongest
4. Week 4: Smoke test with real users

A platform like Any can accelerate the marketing validation phases — generating landing pages, running SEO analysis, and identifying market gaps — while you focus on the conversations and product decisions that require human judgment.

Cross-Cluster Resources

For more on the validation and early-stage journey:

• Lovable vs Building Your Own
• Build a Waitlist Before Product Hunt

The Most Expensive Mistake in Software

Building something nobody wants is not a technical failure. It is a validation failure. And it is the most expensive mistake you can make, not in dollars, but in time and motivation.

Spend a week validating. It might save you six months of building in the wrong direction.

What to Do Next

1. Run the Search Test right now. It takes 30 minutes.
2. Spend today browsing 3 communities where your audience hangs out.
3. Schedule 5 conversations this week with potential customers.
4. Based on results, either proceed to building or pivot.
5. When you are ready to go to market, follow the Cursor Startup Marketing Guide.