How to Run a Smoke Test Before You Build (and Actually Validate Demand)
You spent six months building. You lined up a domain, designed a logo, wrote copy, and shipped. Then you launched — and almost nothing happened. A handful of signups from friends. A few polite "congrats" messages. No paying customers.
The brutal part? The problem wasn't execution. It wasn't your landing page copy or your launch timing. The problem was that the market didn't urgently want what you built — and you found out six months too late.
This is one of the most common and most preventable ways startups fail. And the fix isn't "talk to more customers before you build." Customer interviews are notoriously unreliable. People tell you your idea sounds great. They say they'd pay for it. They mean it in the moment. But stated intent and actual purchasing behavior are two completely different things.
The fix is a smoke test: a deliberately minimal experiment designed to measure what people do, not what they say. Run it before you write a line of code. Here's exactly how.
What a Smoke Test Actually Is
A smoke test is a pre-launch experiment that simulates enough of your product to generate a meaningful behavioral signal from real potential customers.
The key word is behavioral. You're not asking people what they think. You're putting something in front of them — a landing page, a button, a pre-order link — and watching what they do. Do they click? Do they sign up? Do they enter a credit card?
Behavior is honest. People vote with their attention and their wallets in ways they never do in a survey or an interview.
A smoke test typically takes one to two weeks to build and run. It costs almost nothing. And if the results are weak, you've just saved yourself months of work building something the market doesn't urgently want. That's not failure — that's the whole point.
Different situations call for different levels of commitment from your test audience. Here are the four formats, from lowest to highest signal strength.
1. Landing Page + Waitlist
Build a single page that describes your product — what it does, who it's for, what problem it solves, and what makes it different. Add an email capture form or a "Join the Waitlist" button. Drive traffic. Measure how many visitors sign up.
When to use it: You're early-stage and just need to know if there's meaningful interest before investing further.
Signal strength: Moderate. An email signup has low friction — it's not proof someone will pay, but a strong signup rate tells you the problem resonates and your framing is working.
What to build: A single-page site (Carrd, Webflow, or even a Notion page) with a clear headline, tight value proposition, and email form. No product needed.
2. Landing Page + Payment
Everything above, but instead of a free waitlist, you add a payment step. A pre-order. A "join the beta for $X" button. A paid reservation.
When to use it: You need stronger evidence before committing serious time or money.
Signal strength: High. A credit card entry is a fundamentally different signal than an email signup. It requires someone to make a real financial decision — to reach into their wallet and bet on you. That's the closest proxy to actual purchasing behavior you can generate without a product.
What to build: Same as above, with a Stripe payment link or simple checkout flow. You can refund everyone if you decide not to build — just be transparent upfront.
3. Fake Door Test
Place a button, link, or feature that would exist if your product existed — and measure click-through. No actual functionality behind it. Just the door.
When to use it: You already have an audience, an existing product, or access to a platform where your target users spend time. Also effective for testing specific features or pricing tiers before building them.
Signal strength: Targeted. Click-through on a fake door tells you a specific offer was compelling enough to act on. Pair it with a short survey or waitlist after the click and you learn even more.
What to build: A button in an existing interface, a post in a relevant community with a "click to learn more" link, or a feature stub in an existing product.
4. Concierge MVP
Instead of automating the product, you do it manually — for real customers, at real prices. Every step by hand, even if it's slow and unscalable, just to prove the workflow delivers value and people will pay.
When to use it: Your product involves a complex workflow that you're not sure people will value until they experience it. Also great when automation would take months but the manual version can be delivered in days.
Signal strength: Very high. You're not measuring intent — you're delivering actual outcomes and charging for them.
What to Actually Measure
Before you launch, define success. Write it down. "I'll run this for two weeks. If I hit X, I'll proceed. If I don't, I'll pivot or kill it." If you set the bar after seeing the results, you'll rationalize your way into building something that didn't pass.
Conversion Rate Benchmarks
For cold traffic (strangers from ads or community posts):
- Below 2–3%: Weak signal. The problem framing or offer isn't landing.
- 5–10%: Meaningful. Worth iterating before committing.
- 20%+: Strong signal. You've hit a real pain point with a compelling offer.
Curiosity vs. Commitment
Clicks and page views tell you people are curious. Signups tell you people are interested. Credit cards tell you people are committed.
Be honest about what level of signal you actually need before proceeding. For a low-cost product, email signups may be enough. For a complex product with a long build cycle, you want payment signal first.
How to Drive Traffic — Cheap and Fast
You don't need a marketing budget. You need 200–500 qualified visitors. Here's how to get them:
Post in relevant communities. Reddit, niche Slack groups, Facebook groups, industry forums. Write a genuine post about the problem you're solving. Link to your smoke test. Be transparent about what it is.
Run $50–100 in targeted ads. Meta and Google let you target narrowly enough that a small budget gets you several hundred qualified visitors. Use this to supplement community posts, not replace them.
Personal outreach to 50 people who match your ICP. Email, LinkedIn, or DM. Short message: here's the problem I'm solving, here's what I built to test it, would you take a look?
Be transparent. Tell people this is a test. Tell them it's not a finished product. People respect founders who are honest about where they are — and it's also just the right thing to do.
How to Read the Results
Passing: You hit your pre-defined benchmark. You're seeing signups — or better, payments — from people who don't know you. The traffic sources that worked give you a clue about where your customers actually live.
Failing: You drove real traffic, used a clear offer, and saw near-zero conversion.
Why a failed smoke test is actually valuable: A failed smoke test is not a failed startup idea — it's a failed hypothesis. Maybe the framing was wrong. Maybe the audience was wrong. Maybe the price point was off. All of that is learnable. What you didn't do is spend six months building a product nobody bought. You ran a two-week test, spent a hundred dollars on ads, and got a clear answer. That's the system working exactly as intended.
Before You Build the Landing Page, Know Your Market
The quality of your smoke test depends on how well you understand the market before you run it.
Who exactly are you targeting? What alternatives are your potential customers already using — and how do you compare? What price point is realistic? What's the one message that will make your ICP stop scrolling and click?
If you're guessing at those answers, your smoke test results will be noisy. You might get weak conversion and not know if it's because demand is low or because your positioning missed.
That's the problem DimeADozen.AI solves before you ever touch a landing page builder. Submit your idea and get a full market analysis: your target audience, the competitive landscape, realistic pricing benchmarks, and positioning context — so you walk into your smoke test with a clear picture of the market, not assumptions you'll have to undo later.
Run the analysis first. Then run the smoke test. In that order, you're not guessing — you're testing.