First 100 Users From a Waitlist: Cap, Date, One CTA

You have a landing page, a few emails, and a product that works in your head. The waitlist is quiet. You need your first 100 users, not a growth system.

A waitlist launch works when the offer has a date, a limit, and a single action. The reader should be able to answer three questions: how many seats are left, when it starts, and where to sign up.

Hark opened a waitlist by 5 August 2026. On 4 October 2026, Brett Adcock said Hark would launch during that week and give the first 100,000 registrants a paid plan at no cost. Hark made Hark Pro available on 6 October 2026 across web, iOS, and Android. The scale is different, but the mechanics are the same: a finite number, a dated window, and a single place to sign up.

• Choose a hard cap.
• Name the launch week.
• Make the waitlist the only CTA.
• Write the fine print before launch.

Cap the seats before you ask for the email

Put a public number on the page: Only 100 seats. The cap should be small enough that you can onboard every person by hand.

The small cap makes the waitlist feel like a cohort. People join because they will be close to the product, not because they are far down a list.

The cap creates scarcity and tells you when to stop. If you can answer every question, fix every bug, and write every reply yourself, the number is right for the first launch.

Do not cap at a number that feels impressive. Treat the first hundred as a support load, not a vanity metric.

Name the week, not the day

Show a visible launch week on the page, not a vague soon.

The deadline creates urgency and gives you a reason to stop polishing and start onboarding. If the product is not ready, move the week and say so. A slipped week with a clear update beats a stalled page.

The named week also helps you plan the unscalable part: the first calls, the first support replies, and the first fixes.

The 4 October X post did not state an exact launch date. As of 5 October 2026, Hark's site still told visitors the platform was launching soon and invited them to join a waitlist. For a small team, the week is the promise, and the waitlist is the proof of intent.

Make the waitlist the only door

Use a single button: Join the waitlist. The button should be the first thing a visitor sees. No booking link, no docs link, no social follow button.

If you have a demo, put it behind the waitlist. If you have a changelog, make it part of the launch email. The page's job is to collect intent, not to explain everything.

Every extra action splits attention. If the page asks for an email, a calendar, and a newsletter, the waitlist becomes just one option. The first signups without ads come from a page that makes one action obvious. The 4 October 2026 announcement directed readers to the waitlist as the sign-up destination.

Write the fine print before launch

Put a short note under the button: what the offer includes, how long it lasts, and what happens after the seats fill.

Keep the note near the button, not in a footer. A footer note is easy to miss. The reader should see the limit, the date, and the scope before they type an email.

Brett Adcock did not disclose the duration or features of Hark's free paid-plan offer, and the 4 October 2026 announcement did not specify the paid tier included. A large company can absorb that ambiguity. You cannot.

For your first hundred, the fine print is the trust detail. State what they get, when they get it, what you will ask of them, whether the offer is free for a month or a trial, and what happens at 101.

Do not launch with a cap and no terms. The pre-launch waitlist needs the fine print before the button goes live. A cap without an end date or scope becomes a complaint. Keep the terms short enough that a person can read them in a single sitting.

Then convert the waitlist to users by emailing the list when the week starts, in the order they signed up, and talking to the first people by hand. Do not wait for a polished onboarding flow.