Smoke test landing page: test demand before you build

Smoke test landing page

A smoke test landing page is a single public page that states one offer for one audience and asks for one measurable action, with analytics on from the first visit, so you can see whether strangers respond before you build the product. You are not proving product-market fit. You are testing whether the headline and the call to action earn enough intentional behaviour to justify the next spend.

This is for founders and innovation leads in Switzerland who need evidence beyond desk research and friendly feedback. For interviews, concierge tests, and the wider menu, see how to validate a startup idea. Here the focus stays on the page, the action, traffic you can explain, and the decision rule you write before you launch.

Smoke test

A small experiment where failure is cheap and the readout is behavioural, not a survey score.

Primary action

The one thing you count: booking, application, waitlist with a follow-up question, or another step you defined in advance.

Decision rule

What result would make you continue, pivot the message, or stop, written before ads or outreach start.

How to run a smoke test landing page

Keep the page narrow. One segment, one job, one promise, one button or form. Everything else is noise for this test.

1. Write the assumption in one sentence

   Who you target, what they should believe after ten seconds on the page, and what action would falsify a vague “interesting” reaction.

2. Pick an action with honest friction

   Email alone measures curiosity. A calendar slot, a short application, or a priced pre-order step measures stronger intent if you accept lower volume.

3. Publish a page you can measure

   Connect analytics and session recordings from day one so you can see drop-off, not only the final count.

4. Send traffic you can account for

   Organic posts help, but they mix audiences. Paid search or paid social on a small budget gives a cleaner link between message and action if you keep targeting stable.

5. Run for a fixed window

   Two to four weeks is common. Stop when you hit the sample in your decision rule or when the channel misfires.

6. Read behaviour before adjectives

   Scroll depth and form abandonment matter as much as the final count.

What a smoke test landing page can show, and what it cannot

A solid smoke test tells you whether the message reaches the right people and whether enough of them take the action you chose. It can justify rewriting the headline, tightening the segment, or spending on a deeper test.

It does not show that the product works, that users return, that you can acquire customers profitably, or that a marketplace has liquidity. It does not protect the idea: ideas as such cannot be protected under Swiss practice; execution and branding can (IGE on ideas).

Smoke test landing page versus fake door

Both methods use a page before the product exists. The difference is what you ask the visitor to believe.

A fake door test often routes people toward a feature or checkout that is not built yet. That can be legitimate when the copy is honest about what happens next, but it turns toxic when the button pretends the product already exists. A smoke test landing page in the sense used here keeps the promise at the level of the test: waitlist, interview, pilot slot, or deposit, with follow-up you will actually run.

When the question is “will anyone commit time or money on this wording?”, a measured landing page is often enough. When the question is “does the product change behaviour in use?”, you need a real build or a concierge delivery, not another headline tweak. Fake door test versus a real MVP walks that split in more detail.

A made-up example: pilot slots for a B2B workflow tool

A made-up example: a solo founder in Bern targets HR leads in firms with 30–120 staff. The hypothesis is that annual review paperwork still lives in email threads and shared drives, and that leads will book a 20-minute call to see a structured pilot, not a finished product. They publish one page in German, one primary button to Calendly, secondary link to a three-question form for people who will not book yet. GA4 and session recordings are live before the first ad euro is spent.

They set a decision rule: continue if at least eight calls book from paid traffic in three weeks, or pivot if clicks are high but the form is empty. After three weeks, only two calls arrive, both from LinkedIn contacts, not cold ads. They rewrite around “audit trail for review approvals”, run two more weeks, and get five cold bookings. Still no software. The next step is a concierge pilot, not a repo. The first story died cheaply.

Who should run a page test, and who should skip

Privacy and measurement in Switzerland

If you use analytics, heatmaps, or retargeting, inform visitors and handle consent where Swiss practice requires it for profiling or cross-site tracking. Put the notice on the page before ads start. This is not legal advice; ask your adviser when several vendors are involved.

When the landing page package fits

The landing page package fits when you want a dedicated demand page with GA4 and Microsoft Clarity, code you own, and a clean base for ads or outreach, but you are not ready to book a twelve-week product validation build. It is a focused test surface, not a substitute for usage data from a deployed app. If strangers already take your action and the open question is behaviour inside the product, move to a build conversation on the contact page instead of another headline iteration.