Run an honest waitlist or intent test

Decide what the test can prove

A waitlist can test whether a defined audience understands an offer well enough to volunteer a contact method. It does not show that people will use the product, pay, or remain customers. A transparent intent test can go one step further by asking visitors to choose a real next action—request an interview, book a demo, or review a clearly priced pilot—but still records intent rather than completed delivery.

Write one question before building the page. Examples: “Will freelance translators handling more than ten client projects a month request a demo of a terminology handoff tool?” or “Will local studios ask for early access to a reporting workflow at this stated price?” Avoid “Would you use this?” without specifying the audience, job, and offer.

Make the experiment candid

Say what is available now and what is only a concept. A useful call to action might read: “This tool is in research; it is not available yet. Join the list if you want an invitation to test it. We will email you about this test only.” If you show a prototype, label it as a prototype. If manual work will deliver the pilot, say so. Never accept payment for an undefined product or imply that people are already using something that does not exist.

Do not invent user counts, testimonials, scarcity, deadlines, or limited stock. The U.S. Federal Trade Commission’s dark patterns report describes interface tactics that can mislead or steer consumers, including false scarcity and obscured information. Its legal discussion is U.S.-specific, but the design lesson is broadly useful: do not improve a conversion metric by making the choice less informed.

Collect the minimum information needed to run the test. Explain why you need it, who will contact the person, and whether you will retain or share it. GOV.UK’s informed-consent guidance recommends explaining the purpose, data collected, use, retention, and voluntary nature of research participation. That page covers research participation; marketing consent requirements are separate and vary by jurisdiction. Use a clear, unselected consent control if you want to send future product updates beyond the requested test. Follow privacy rules that apply to your audience and service; see privacy by default for a data inventory and retention approach.

Measure a qualified next step

Define the denominator before sharing the link: qualified visitors from one channel, geography, and period. Exclude your own visits and obvious automated traffic where practical. Track:

1. Eligible visitors who saw the actual offer.
2. People who clicked the primary action.
3. Completed signups or booked conversations.
4. The share matching your target segment after a short fit question.
5. The source and cost of reaching them.

Keep one version long enough to get interpretable feedback; change only one major variable at a time where possible. With small traffic, a few signups can help you identify confusing language or recruit interviewees, but cannot support a stable market conversion estimate. Pair the behavior with follow-up: ask what problem led them to sign up and what they do today. Record non-signups from observed sessions, too.

Close the loop

At the end date, stop acquisition, send the promised update, and delete contact data that no longer has a justified purpose. Report the result with the audience, channel, time window, denominator, exclusions, and uncertainty. If the result is weak, check targeting and message comprehension before concluding the problem is absent. If it is strong, test a concrete workflow or a transparent paid pilot next; see test demand with a landing page and design a clear offer.