Validate before you build: a one-week waitlist test

Building a course, a cohort or a membership takes weeks of work. Finding out whether anyone wants it can take a week. A waitlist test is the simplest way to ask your audience to raise their hand before you build.

This assumes you already have an offer idea grounded in what your audience asks for. If you don’t yet, start with What will my audience pay for?

Day 1: write the promise

Write four short lines. Keep them in your audience’s words.

• The promise: one sentence on the result, for example “Get back to running after a knee injury, with a plan you can follow at home.”
• The format: a six-week group program, a self-paced course, a monthly membership.
• Who it’s for, and who it isn’t for. Saying who it isn’t for builds trust.
• A rough price range. You don’t need a final price, but people judge interest differently at very different prices.

Day 2: set up somewhere to sign up

A simple form or a one-page waitlist is enough. Ask for:

1. An email address.
2. One question: “What’s the one thing you’d want this to help you with?”

That single question is often more valuable than the sign-up count. It tells you, in your audience’s words, what to build and how to describe it.

Be clear that it is a waitlist. Don’t invent scarcity or deadlines that aren’t real.

Days 3 to 6: talk about the problem

The questions creators ask most are how many posts to make, when to mention the offer, and whether to hint at it or give it a post of its own. For a one-week test, keep it simple. Don’t just post “join my waitlist” five times. Keep making your normal content, and point it at the problem:

• One or two posts that teach something useful about the problem.
• One direct post about the waitlist: what it is, who it’s for, and how to join.
• Stories or short updates that answer questions as they come in.
• Personal replies to people who comment or message. These conversations are part of the research.

If you’re worried about sounding salesy

That is the most common worry, and a fair one: most people dislike being sold to, and you don’t want to become the account your audience scrolls past. The way through is to keep the focus on the problem and on the people who asked. Teach something useful, mention the waitlist plainly once, and answer questions as they come. Helping people who asked for help is not the same as selling at them.

Day 7: read the results

Look at three things.

• Sign-ups compared with your usual engagement. A raw number means little on its own. Compare it with how many people normally comment on or click through from your posts. We don’t give a magic target, because audiences differ too much.
• The answers to your one question. Do they match your promise, or are people asking for something slightly different? That gap is often the most useful finding of the week.
• Unprompted “when” and “how much” messages. People asking when it opens, or what it will cost, are showing stronger intent than a sign-up alone.

Some creators go one step further and offer a small paid pre-sale or deposit, which is a stronger signal than an email. If you do, be clear about what people get, when they get it and how refunds work. Taking money before something exists comes with real obligations.

What to do next

• Strong response: build the smallest version that delivers the promise, and invite the waitlist first.
• Mixed response: change one thing, such as the promise, the format or who it’s for, and run the test again.
• Weak response: that is useful too. It may mean the idea needs reworking, or that the better move right now is to keep growing, or to improve something you already sell.

A week spent learning that an idea isn’t ready is much cheaper than two months spent building it. Results vary from audience to audience, and no test guarantees sales, but it does mean your next decision rests on evidence.