Free field notes / Updated 2026-10-21

Build an Honest Smoke Test Landing Page

Test demand with a landing page that says what is not built yet. Plan the offer, visitor sources, and actions worth measuring before you launch.

A smoke test landing page presents a specific offer before the full product exists and measures whether suitable people take a meaningful next step. An honest page states that the product is not built yet, explains what the visitor can actually do today, and avoids implying that signup guarantees delivery. Choose the action and decision threshold before sending traffic.

Define the question before writing the headline

A landing page can test whether people understand a problem, respond to an offer, or accept a proposed price. It cannot answer all of those questions cleanly at once.

Imagine a proposed tool that turns a craft seller's rough inventory notes into a printable packing checklist. The test question is: "Will sellers preparing for a market request a sample checklist after seeing a US$9 proposed price?"

That question is narrower than "Do sellers want better organization?" It identifies a situation, an output, and an action. It also sets up a follow-up: a person who requests a sample can explain their next market date and current process.

If your offer falls into financial, medical, or legal activity, do not launch a demand test based on this guide. Get qualified guidance first. Other safety and privacy concerns also need attention before collecting information or promising outcomes.

Build the page around one clear offer

Use a simple structure that a visitor can read without guessing what exists.

Label a screenshot "concept mockup" if it shows an interface that does not work. If a sample is prepared manually, say that. Place the status near the action, where people will see it before submitting.

Avoid manufactured customer logos, reviews, usage totals, or time limits. A genuine capacity limit can be explained plainly, such as having time to prepare five manual samples. Do not reset that limit whenever the page reloads.

Make the next action honest and usable

The button should describe the immediate action. "Request a sample" is clearer than "Start now" when there is no product to start using. "Reserve, pay nothing now" is clearer than a checkout-style button that unexpectedly becomes a waitlist form.

Ask only for information needed to carry out the promise. An email address and an optional question about the next market may be enough. Explain what messages the person will receive and provide a simple way to stop them.

Keep the page readable on a small screen. Give form fields visible labels, make buttons work with a keyboard, and ensure text has sufficient contrast. Important status information belongs in regular text, not only in an image or tooltip.

After submission, confirm exactly what happened: "You requested a sample. No payment was taken, and this does not reserve a finished product."

Plan a route to 50 to 200 relevant visitors

A target of 50 to 200 visitors is a planning choice for this exercise, not a statistical guarantee or a required benchmark. Relevant visitors matter more than a large count from people who cannot use the offer.

Start by listing permission-based sources:

1. People you know who fit the buyer description and agree to see the page.
2. A community where the rules allow a clearly disclosed test post.
3. An organizer who chooses to include the offer in a relevant member update.
4. A local event where the organizer permits you to display a small card.
5. Your own audience, with a request to share only with someone who actually faces the problem.

For planning, you might hope for 25 visits from your own audience, 40 from one permitted community post, and 15 from an organizer's update. Those numbers are hypothetical estimates, not expected results. If actual traffic reaches only 32 relevant people, report 32.

Do not post the same message across many groups or approach people using scraped contact details. Ask moderators first where the rules are unclear. One welcome post can produce more useful conversations than repeated unwanted promotion.

Measure actions with their context

Track the number of visitors, the source, sample requests, replies, and later commitments. If possible, exclude your own repeated checks from the visitor count. Do not claim precision your setup cannot support.

In a hypothetical test, 100 relevant visits produce 12 sample requests. That is a 12% request rate in this test. If only four people reply to the follow-up and two book a pilot conversation, keep those as separate counts. Twelve requests are not twelve customers.

Write the decision rule in advance. For example: "By Sunday evening, at least ten of the first 100 relevant visitors request a sample, and at least three describe an upcoming market in reply." This combines an easy action with evidence of a real use occasion.

If your primary concern is willingness to pay, do not treat a sample request as the final answer. Use a later price test with an actual offer.

Read a weak result carefully

Low response can reflect the wrong visitors, an unclear page, an unimportant problem, an inconvenient action, or a price that does not match the offer. Your tracking should help you distinguish those explanations.

Ask a few suitable visitors to explain what they thought the page offered. If they cannot tell, clarify the message and start a separately labeled test. If they understand it and describe a satisfactory existing method, reconsider the need.

Do not silently pool results before and after a large rewrite. Save the original copy, note the change, and compare the groups cautiously. A small sample gives you directions to investigate, not a reliable conversion forecast for every future channel.

Common mistakes

• Hiding the "not built yet" disclosure at the bottom.
• Measuring button clicks while the form is broken.
• Counting all visitors as likely buyers.
• Adding a price only after people have signed up.
• Promising a launch date you have no basis to meet.
• Treating email addresses as completed purchases.

Review the waitlist signal ladder before deciding what the page proved. Keep the original success threshold beside the results.

Next step

Paste your idea into the free triage tool to identify the assumption your page should test. The 48-Hour Validation Kit offers a place to organize the copy, traffic plan, and decision rule.