namla

Insights

How to Validate a Startup Idea Before You Build

Two weeks and a small ad budget will teach you more than six months of building. Five validation tests, and the signals that mean build, narrow, or stop.

February 5, 2026 Startups MVP Validation

Building is the most expensive way to test an idea. Two weeks and a small ad budget will usually tell you more than six months of development, because they answer the question that decides everything else: does anyone care enough to give something up?

That’s the bar. Not “would you use this?” Everyone says yes to that; it’s free. Validation means watching people pay a cost: money, time, a signature, a real reply.

Five tests, cheapest first

  1. Problem interviews. Talk to 8–12 real target users about how they handle the problem today. Don’t pitch; listen for frequency, pain, and money already being spent on workarounds. If you can’t even find 12 people who have the problem, that is the result.
  2. A landing page and a waitlist. One page stating the value, one signup field, a small ad spend to drive strangers to it. Signups from strangers measure pull. Replies to your follow-up email measure it twice.
  3. The concierge test. Deliver the outcome by hand for three to five customers, with no product behind the curtain. If they value it done manually, automation makes it a business. If they don’t, no amount of engineering would have.
  4. Pre-sales or a letter of intent. Ask for a deposit or a signed LOI before anything exists. Uncomfortable, and that’s the point: discomfort filters compliments from demand.
  5. Alternatives audit. What do people use today, including spreadsheets, WhatsApp groups, and paying a person? Strong existing workarounds mean a real problem. A vacuum usually means indifference, not opportunity.

Reading the results

Build when people commit something costly, the same problem repeats in their own words, and today’s alternatives visibly frustrate them. Narrow when interest exists but scatters; sharpen the segment or the problem and run the test again. Stop when you collect compliments and zero commitment; you just saved a build’s worth of money, which is a win, whatever it feels like.

Then aim the build

Validation doesn’t replace building; it aims it. Once you’ve seen real commitment, scope the smallest version that delivers the validated value and ship it: that handoff is the idea-to-app sequence, and the sizing question after it is MVP vs full product.

Run one of the five this week. If it comes back green and you want the v1 scoped against what it should cost, we’ll do that with you.

FAQ

How do I know if my idea is worth building?

When strangers give up something that costs them: money, a signed letter of intent, a real email address they reply from, or hours spent doing the job manually today. Compliments predict nothing. If nobody will part with anything, that's your answer, learned cheaply.

Do I need to build a product to validate the idea?

No, and building first is the most expensive way to find out. A week of problem interviews, a landing page with a small ad budget, or delivering the service manually to three customers each test demand for a rounding error of a build's cost.

How many customer interviews are enough?

Around 8 to 12 focused interviews with real target users, asked about how they handle the problem today rather than about your solution. When the same pain and the same words keep repeating, you have your pattern. When every answer is different, you don't have a segment yet.