Filming a 40-lesson course takes weeks. Finding out nobody wanted it takes one afternoon, if you ask before you record. The mistake most course creators make is the reverse: they outline, shoot, and edit, then open a Teachable page to silence.
A course waitlist fixes the order. You publish a page that describes the outcome, collect emails, ask one question that separates curious from committed, and set a number that decides whether the course gets built.
Put the OperatorStack script tag and <div data-os-widget="waitlist"></div> on a one-page course landing page, tag each traffic source, and send one pre-sale question to every signup. Decide your go threshold before you promote, for example 100 signups and 5 yes answers in three weeks.
What You Need Before You Start
- A one-page landing page that names the outcome ("ship your first iOS app in 30 days"), not the syllabus. Any builder works.
- An OperatorStack account. Free to start. You need the
pk_project key from your embed snippet. - A go or no-go rule, written down before step 1.
Step 1: Add the Waitlist
Paste the script tag once, in the <head> or just before </body>:
<script src="https://operatorstack.dev/os.js" data-project="pk_abc123"></script>
Place the widget where the call to action goes:
<div data-os-widget="waitlist"></div>
The same tag also gives you cookie-free analytics, so you see visits next to signups. The visit-to-signup rate is your first demand signal, before anyone answers a question.
Step 2: Tag Every Traffic Source
Course audiences come from specific places: a Twitter thread, a YouTube video, a newsletter swap, a subreddit. Give each a UTM link so you know which one produces signups and which produces only visits.
https://yourcourse.com/?utm_source=youtube&utm_campaign=cohort1
https://yourcourse.com/?utm_source=newsletter&utm_campaign=cohort1
Visitors who arrive with ?ref=CODE from a friend are tracked separately. See tracking referral sources for how UTM and referral signups are counted per source.
Why this matters for a course: 60 signups from one niche podcast beat 300 from a giveaway thread. The first is an audience you can teach. The second is people who wanted a free thing.
Step 3: Ask the Pre-Sale Question
A signup costs a visitor ten seconds. It proves interest, not willingness to pay. Send each new signup one short email with a single question and a link to a form, using the pattern in surveying waitlist signups.
Pass the email into a hidden field and submit with the SDK so the answer attaches to the right contact:
await OperatorStack.joinWaitlist({ email });
await OperatorStack.submitForm("frm_course_presale", {
email,
answer: "yes",
note: "Would pay 149 for the live cohort",
});
Three questions work well, asked one per email:
- "What do you want to be able to do after this course that you cannot do today?"
- "If I opened the course next month at 149 dollars, would you buy? Yes, maybe, no."
- "What have you already tried?"
Question 1 gives you sales page copy in the buyer's own words. Question 2 gives you the number that matters. Question 3 tells you what you must beat.
Asking "would you buy?" in the signup form itself depresses signups. Keep the form to an email and ask afterward.
Step 4: Set the Go or No-Go Number
Write the rule down before you promote, because after two weeks of effort you will want to move the goalposts. An example for a 149 dollar course:
- Go: 100 signups and at least 5 "yes" answers within 21 days.
- Rework: 100 signups but fewer than 2 "yes". The topic draws interest but not purchase. Change the promise, not the traffic.
- Kill: fewer than 30 signups after real promotion in two distinct channels.
5 yes answers at 149 dollars is 745 dollars of verified intent. It is small, and it is enough to justify a live first cohort built from your survey answers, which is cheaper and less risky than a polished pre-recorded course.
Step 5: Use Referrals for the Final Push
If you are near your threshold, turn existing signups into promoters. After joinWaitlist() resolves, show a share prompt:
const res = await OperatorStack.joinWaitlist({ email });
const links = OperatorStack.getShareLinks(res.referral_code, {
text: "I just joined the waitlist for this course",
});
// links: { twitter, linkedin, email, whatsapp, copy }
Course buyers often know a colleague with the same problem. Offering the first cohort seat or a discount to the top referrers costs you nothing until the course exists. Pick the recipients from each contact's referral count.
Common Mistakes
- Building the platform first. Hosting, checkout and a custom domain are all after proof of demand.
- Selling the syllabus. Visitors buy the outcome. List the result and the timeframe, not the 12 modules.
- Counting free-traffic signups. Judge by source, and weigh signups from audiences who already pay for education.
- No deadline. A waitlist without an end date never forces a decision.
Frequently Asked Questions
How many waitlist signups do I need before building an online course?
There is no universal number, so set your own before you start. A common rule is to count paying intent, not signups: if 100 people join and fewer than 5 answer yes to a pre-sale question, the topic or the audience is wrong. Decide the threshold in advance so you cannot talk yourself past it.
Should I use Teachable or Kajabi for a course waitlist?
Not yet. Those platforms are for hosting a finished course. A waitlist only needs a page, an email field, and a way to see where signups came from. Pick the course platform after demand is proven.
What should I ask people when they join a course waitlist?
Ask one question that reveals intent, such as what they want to be able to do after the course, and a second later about price. Free-text answers write your sales page copy for you.
How long should a course waitlist run?
Run it for a fixed window, typically two to four weeks of active promotion, then decide. An open-ended waitlist with no deadline collects names but never forces the build or kill decision.
Can I put a course waitlist on a landing page I built with an AI tool?
Yes. The widget is one script tag and one div, so it works in Lovable, Bolt, v0, Framer, Webflow, Astro, or plain HTML without a backend.