How to Run a Smoke Test for Your Startup Idea

You can find out whether anyone wants your product in a weekend. Not whether they think it's a nice idea. Whether they'll take an action that costs them something.

That's a smoke test, and it's the cheapest way to kill a bad startup idea before it eats a year of your life. Most first-time founders skip it because building feels like progress and asking feels like stalling. Then twelve months later they launch to silence and call it a marketing problem.

It usually wasn't. CB Insights has been publishing startup post-mortems for over a decade and "no market need" sits at the top of the list nearly every year, showing up in roughly four out of ten failures. That's not a product quality problem. It's a demand problem. And demand problems are testable before you write a line of code.

Here's how to run the test properly, including the parts most guides skip: how much traffic you actually need, what a passing number looks like, and the four ways a smoke test will lie to you if you let it.

What is a smoke test for a startup idea?

A smoke test is a small public experiment that measures whether real people will take a costly action toward a product that doesn't exist yet. Costly means it costs them time, money, or social risk. Clicking a button, entering an email, or putting down a card are all costly in different amounts.

The term comes from hardware. You plug the board in, you see whether it catches fire. The startup version is the same logic. You put the smallest honest representation of your product in front of strangers and watch whether anything happens.

What makes it a test rather than marketing is the threshold. You decide before you launch what number means yes and what number means no. Without that, you're just collecting data you'll rationalize later. And you will rationalize it. Everyone does.

How is a smoke test different from an MVP?

A smoke test measures demand. An MVP delivers value. They answer different questions and they cost wildly different amounts.

An MVP is a working product, stripped down. Someone can use it and get something out of it. That takes weeks at minimum, usually months, and it commits you to a technical direction before you know whether the direction matters.

A smoke test delivers nothing. It's a page, a video, a button, a form. Nobody gets a product at the end. What you get is a number.

This distinction matters more in 2026 than it did five years ago, because AI coding tools have collapsed the cost of building a rough product. Plenty of founders will tell you it's faster to just vibe-code the thing than to test for it. Sometimes that's true. But shipping a working product creates gravity. Once it exists you'll defend it, iterate on it, and try to market your way out of a demand problem instead of walking away. A test you can throw out is worth more than a product you can't.

If you're not sure which stage you're at, our guide on how to validate a startup idea covers the sequence in more detail. Smoke tests belong near the front of it.

What does a good smoke test actually look like?

There are four formats worth knowing, and they measure progressively stronger signals.

The landing page test. One page describing the product, one call to action, one email capture. This is the default and it's the weakest of the four, because an email address is cheap to give away.

Joel Gascoigne's version of this for Buffer is the one everyone cites, and it's worth understanding why it worked. He didn't just build a landing page. He built two, then three. The first page described the product and had a "Plans and Pricing" button. Clicking it took you to a page that said the product wasn't built yet, and asked for your email. Then he added a middle page with actual prices, so visitors had to pick a plan before they could sign up. That last step is the whole trick. He wasn't measuring interest. He was measuring willingness to look at a price and keep walking.

He collected 120 emails over roughly seven weeks. That's a small number. But 50 of those people became users at launch, and he had a paying customer within three days.

The fake door test. You add a button or menu item for a feature inside a product you already have. Clicking it says the feature is coming soon and offers a waitlist. This is stronger than a landing page because the person wasn't recruited by an ad. They found the door on their own while trying to do something else.

The demo video test. You show the product working without building it. Drew Houston's Dropbox video is the canonical case: file sync across operating systems was brutally hard to build, so he made a four minute screencast of the experience instead and posted it to Digg and Hacker News. The beta waitlist went from around 5,000 to 75,000 close to overnight.

The reason that story gets misused is that the video wasn't the clever part. The audience was. He put it in front of people who were already living with the exact problem, every day, and who had the vocabulary to recognize the fix instantly.

The preorder or deposit test. You take money, or an explicit commitment to pay, before the product exists. This is the strongest signal available short of shipping, and it's the one almost nobody runs, because it's uncomfortable and because you have to be ready to refund everyone.

Run the weakest test you can get a clean answer from, then escalate. If a landing page can't clear its threshold, a preorder page definitely won't.

How much traffic does a smoke test need to mean anything?

Around 300 to 500 targeted visitors is the working floor for a directional read. Below that, normal variation swamps the signal and you're reading tea leaves.

Understand what that number is and isn't. Three hundred visitors will not give you statistical significance in the formal sense. Proper A/B testing usually wants closer to 1,000 visitors per variant before you can trust a p-value under 0.05, and if your site sees fewer than 10,000 visitors a month you'd need a conversion lift over 30 percent for a test to declare a winner at all.

But you're not A/B testing. You're asking a much blunter question: is this closer to 0 percent or closer to 10 percent? That question survives a small sample, as long as you treat the answer as a range rather than a decimal.

The word that matters most in "300 targeted visitors" is targeted. Three hundred clicks from a subreddit full of your actual users tells you something. Three hundred clicks from a cheap traffic source tells you what cheap traffic does. Traffic quality is the variable that ruins more smoke tests than sample size ever will.

What conversion rate counts as a pass?

Set your threshold before you launch, then use benchmarks only to sanity check it. Working ranges as of 2026:

Signal	Weak	Worth pursuing	Strong
Fake door click inside an existing product	under 2%	2 to 5%	above 5%
Landing page email capture, cold traffic	under 2%	2 to 5%	above 8%
Landing page email capture, warm traffic	under 3%	3 to 8%	above 10%
Preorder or deposit, any traffic	under 1%	1 to 3%	above 3%

For context, the median dedicated landing page across all industries converts at roughly 4 percent, and the top quartile clears 11 percent. So a 4 percent email capture on cold traffic isn't evidence of a great idea. It's evidence you built an average landing page.

Here's the part that separates a real test from theater. Your threshold shouldn't come from a benchmark table. It should come from your own math. Work backward: what does a customer need to be worth, and how many do you need in year one, and what conversion rate does that imply given what traffic costs you? If a 5 percent signup rate still leaves you with unprofitable unit economics, then 5 percent is a fail even though the table calls it strong.

That backward calculation is the actual work, and it's worth doing in something structured rather than in your head. A spreadsheet is fine. So is Causal, LivePlan, or a planning tool like Foundra that walks first-time founders through the financial model and the validation plan in the same place. The tool matters less than writing the number down somewhere you can't quietly move it later.

How do you run a smoke test in a weekend?

Six steps, and the first one is the one people skip.

1. Write the hypothesis and the threshold. One sentence each. "At least 5 percent of visitors from r/smallbusiness will enter an email to join the waitlist." If you can't write the threshold, you don't have a test.
2. Build the page. Carrd, Framer, Webflow, or plain HTML. Headline, the problem in the reader's words, three or four specifics about the solution, one call to action. Ninety minutes, not two days.
3. Add a price. This is the Buffer move. Even a fake price on a "plans" page filters browsers from buyers, and it costs you one extra screen.
4. Instrument it. Plausible, Fathom, or GA4. You need visitors, clicks on the CTA, and completions. Three numbers.
5. Drive targeted traffic. Communities where your users already are, direct outreach, or paid. Budget for this properly: Reddit CPCs run roughly $0.50 to $3.00, and B2B and startup subreddits sit at the higher end near $1.50 to $3.00. That's $450 to $900 for 300 clicks. Google Search is worse for B2B SaaS, averaging around $5.34 per click in 2026 and often much more, which puts 300 clicks north of $1,600. Organic and community traffic is free but slower and biased toward people who already like you.
6. Stop at your sample size and read the number. Not before. Not after you've had time to talk yourself into it.

What makes a smoke test lie to you?

Four failure modes, in rough order of how often they wreck a result.

Wrong traffic. You posted in a founder community and got founders, not customers. Founders sign up for everything. This is the most common way a smoke test produces a false positive.

Measuring the wrong thing. Email capture is a proxy for intent, and it's a weak one. If your threshold was built on emails and your business needs paying customers, you've validated a mailing list.

Moving the goalposts. You said 5 percent, you got 2.8 percent, and now you're explaining that the traffic was unusual and the copy was rushed. Sometimes that's true. Write it down as a new hypothesis and run the test again rather than editing the old one.

Burning trust. Fake doors involve real deception, and it's fair to be careful with them. The rule that holds up: the post-click message should be immediate, honest, and useful. Say the feature isn't built, say why you're testing, offer the waitlist. Don't run fake doors repeatedly on the same audience, and don't run them at all in flows touching pricing, eligibility, health, money, or someone's job. People are surprisingly generous about being told the truth. They're not generous about dead ends.

Key takeaways

• A smoke test measures demand, not usability. Nobody gets a product at the end. You get a number.
• Decide your pass threshold before you launch, and derive it from your own unit economics rather than a benchmark table.
• Around 300 to 500 targeted visitors is the working floor. Targeted is the load-bearing word.
• Add a price step. It's the cheapest way to separate curiosity from intent, and it's what made Buffer's test useful.
• Escalate signal strength: landing page, then fake door, then preorder. Don't start with the hardest one.
• Budget for traffic. Three hundred Reddit clicks in a startup subreddit costs $450 to $900. Free traffic isn't free, it's just slower and more biased.
• A failed smoke test is a good outcome. It cost you a weekend instead of a year.

FAQ

How long should a smoke test run?
Until you hit your sample size, usually three days to three weeks depending on traffic source. Set the sample size in advance and stop there. Running longer to chase a better number is how you turn a test into a hope.

Is a fake door test dishonest?
It involves deception, so it depends entirely on execution. It's defensible when the post-click message is immediate and truthful, the test isn't repeated on the same users, and it stays out of sensitive flows like billing, health, and employment. It's not defensible when it dumps people into a dead end with no explanation.

Can I smoke test without spending money on ads?
Yes. Community posts, direct outreach, cold email, and existing audiences all work, and the traffic is often higher quality. The tradeoff is speed and bias: people who know you convert better than strangers, which inflates your result.

What if my smoke test fails?
Figure out whether the idea failed or the test did. Wrong audience, unclear copy, and a mismatched call to action all produce false negatives. If the test was clean and the number was well below threshold, that's your answer, and it's worth more than the year you didn't spend.

Do I need a real product name and brand?
No. A working name and a clean page are enough. Spending two weeks on a logo before you know if anyone wants the thing is the exact failure mode a smoke test exists to prevent.

Should I smoke test if I can build the product in a week with AI tools?
Often yes, because the cost of building isn't the only cost. A built product creates commitment, and commitment makes you market harder instead of walking away. If you can truly build and abandon without attachment, build. Most people can't.