· 3 min read
How do you validate a startup idea before building it?
Cheap, honest ways to validate a startup idea in 2026 before writing code: landing page smoke tests, ad-click tests, presales and the signals that lie.
Validation has one job: make strangers reveal whether they want the thing, before you spend months building it. The methods below are ordered by how hard the evidence is — and the last section covers the signals that feel like validation but aren't. (Disclosure: published by BidSurvivor, which appears in method two.)
Method 1: The landing page smoke test
One page: the promise, the price if you dare, and a call-to-action that captures intent (email signup at minimum). Build it in an afternoon. The page is the experiment — every visitor either acts or doesn't, and the ratio is your first real number. Homepage vs landing page covers the mechanics.
Method 2: The ad-click test
Before visitors can convert on the page, the idea's one-line pitch has to earn a click from a stranger — and that's testable separately, cheaply. The classic version buys a handful of search clicks (~$5+ each). The free version is ours: claim an empty slot on BidSurvivor — first claim is $0, every account starts with $100 of house credit — put your pitch line and link on the board for twelve hours, and read the published click-through numbers. A pitch that can't earn cold clicks at $0 will not earn them at $5, and learning that before building is the entire economics of validation. (Small board, small samples — run it more than once before concluding anything, per the vanity-metrics rule.)
Method 3: The presale
The hardest currency: money before product. A "founding member" price, a deposit, a paid pilot. Ten emails is interest; three payments is validation. Uncomfortable to ask for, which is why it works — discomfort filters wishful thinking on both sides.
Method 4: The concierge test
Deliver the outcome manually to five customers before automating anything. Slowest method, richest information — you learn the workflow, the objections and the price tolerance while "being" the product.
The signals that lie
Compliments ("I'd totally use this") — social kindness, not intent. Waitlist signups from friends. Upvotes — a launch spike measures curiosity, not demand. And your own conviction on a good day. The test for any signal: did a stranger pay a cost — money, an email address, a click away from something else? No cost, no signal.
Validation doesn't have to prove success — it can't. It only has to make building the wrong thing expensive to ignore. Two afternoons and $0, using methods 1 and 2, buys that much certainty before the first line of code.