Test the Idea Before You Build the Thing

The most common way to waste development money is to build something nobody wants, then find out after it's built. The fix isn't a better requirements document. It's testing the idea before you write any code.

What "Testing the Idea" Actually Means

There's a spectrum from cheap-and-fast to expensive-and-thorough. Most early-stage product ideas don't need the expensive end of that spectrum. What they need is a clear answer to one question: will anyone actually pay for this?

The cheapest version: describe the product to 10 people who would be the target customer. Don't pitch it — describe it and ask if they have the problem it solves. If they do, ask how they currently handle it. If most of them don't recognize the problem, the product is solving something that isn't actually painful enough to pay for.

The Sign-Up Page Test

One level up from conversations: a landing page that explains the product and asks for an email to be notified at launch. No product yet. Just a page describing what it does and a form.

This tests two things: whether people understand what you're building (if the description lands), and whether they want it enough to give you their email. An email address is a small commitment, but it's real. "Yes, sounds interesting" in conversation costs nothing. Entering an email costs a little friction.

A few hundred targeted visitors to a sign-up page — from relevant Reddit communities, Facebook groups, direct outreach to the target market — gives you signal before you've committed to a build.

What to Do With That Signal

Fifty sign-ups from targeted traffic means something. Zero sign-ups after real effort to drive relevant traffic means something too. The signal only works if you're honest with yourself about what it's telling you.

The failure mode: "well, the traffic wasn't really targeted" or "the page wasn't optimized" or "people don't understand the concept yet." These can all be true. They can also be rationalizations for ignoring a clear signal. If ten different relevant people saw the page and none signed up, the problem is real.

What Validation Doesn't Tell You

Sign-ups tell you people are interested. They don't tell you people will pay, use the product consistently, or recommend it. The validation stack keeps going after launch: getting the first paying customer, getting the second one without heroic effort, seeing if people come back.

A sign-up page test is about deciding whether to start building, not about proving the product will succeed. It's a cheap gate before a more expensive commitment.

The Prototype Option

Between a sign-up page and a full build, there's often a prototype — something that looks like the product and simulates the core workflow, but isn't production-ready underneath. Figma mockups, a partially manual backend, a single feature with no surrounding infrastructure.

Prototypes are good for testing whether the core experience works before investing in the full build. They're not good for testing market demand — for that, a sign-up page is faster and cheaper.