How to test startup demand with a landing page

What can a landing-page experiment tell you?

A landing-page experiment shows whether people from a particular traffic source take a stated next step after seeing your offer. It can help you test a message or find people to speak with. An email signup does not establish willingness to pay, repeat use, or a viable business.

Choose one question before writing the page. "Will independent consultants request a sample weekly proposal review?" is narrower than "Does the market want my startup?" It gives you a specific audience, offer, and observable action.

This is a planning guide. The numbers below are hypothetical examples, not Marketing Loop results or conversion benchmarks.

State the offer and product status honestly

Explain who the offer is for, the problem it addresses, and what happens after the visitor acts. A request for a sample review should lead to a sample review. A launch-update signup should promise launch updates, with no suggestion that it creates a product account.

If the product is not available, say so near the action. Do not show invented customer logos, testimonials, limited places, pricing discounts, or a launch countdown. If you are testing a manual service, describe the work you can actually deliver.

Keep the page focused. Give the reader enough detail to decide, then use one clear primary action. Answer likely questions about availability, cost when known, and what information you need. Link to the relevant privacy information before collecting contact details.

Write the experiment record before sending traffic

Copy these fields into your notes:

• Assumption: What do you believe about this audience and offer?
• Audience: Who should see the page, and who is outside this test?
• Traffic source: Where will visitors come from?
• Offer: What exactly can someone request or join?
• Primary action: What completed behavior will you count?
• Measurement: How will you record eligible visits and completed actions?
• Window: When does the test start and end?
• Decision rule: What result would make the next action worthwhile?
• Limits: What would this test still leave unanswered?

Use the one-page startup marketing plan to connect the audience and offer to your chosen channel. Change one major assumption at a time when practical, so the result is easier to interpret.

Count visits and completed actions consistently

Choose your denominator before looking at results. Eligible visits might mean visits from one tagged campaign during the test window, excluding your own checks and known automated traffic. Record what your analytics tool can actually measure. If it cannot identify unique people reliably, call the count visits rather than people.

Count a signup after the server confirms it was saved. A button click, a rejected address, or a failed request is not a completed signup. Repeated requests from the same address should not look like new prospects.

For a simple record, write the source, test window, eligible visit count, completed action count, and any known gaps. Do not put email addresses or private participant details in analytics event properties.

When comparing traffic sources, retain separate counts. A message to existing contacts and a public post reach different audiences. Combining them can hide the very difference you need to understand.

Interpret a hypothetical result

Suppose a founder sends a relevant community post to a page offering a sample proposal review. During seven days, the page receives 80 eligible visits and records 6 completed requests. That is 6 out of 80 visits, or 7.5%, under the chosen measurement definition.

Before starting, the founder chose a working rule: if at least 5 requests arrive, deliver the sample and ask whether the recipient wants to discuss their current process. That rule makes the next action manageable. It is not a universal threshold for demand.

The result supports delivering the promised samples. It does not justify projecting revenue or declaring the business validated. The next evidence is whether the recipients engage with the sample, describe a recurring problem, or accept a concrete paid offer.

A small count can change sharply with one extra action. Report the raw counts with the rate. Keep the traffic source and offer attached to the result so someone reading it later understands what was tested.

What should you do with few or no signups?

First check delivery and measurement. Did people reach the page? Did the form work on a phone? Did the server save valid submissions? Were you counting the intended traffic?

Then separate the uncertainties. A low visit count may tell you little about the offer. Relevant visits with no action could reflect unclear copy, an unsuitable next step, low trust, or a problem that people do not care enough to address. The count alone cannot tell you which explanation is right.

Ask a few people in the intended audience to describe what they understood and why they would or would not act. Use customer discovery questions to investigate their current behavior. Record objections without rewriting them into praise.

Choose the next test

Keep the expected signal, observed result, decision, and next action together. You might continue with the same offer, change the audience or message, stop pursuing this version, or gather more evidence.

Write the reason for that choice. "Six sample requests from one community post; deliver the samples and check follow-through" is more useful than "Landing page validated."

Use the marketing experiment template for the next record. Marketing Loop is in development and has no announced launch date. These templates can be used in your own document today.