DEV Community: Devin D

Pre-launch waitlist tools in 2026, compared

Devin D — Fri, 14 Aug 2026 14:50:09 +0000

I make Waitlister, one of the tools below. Read this with that in mind.

I wrote it anyway because the roundups I found disagreed with each other on basic facts. Three of them listed three different starting prices for the same product. So where I could check something myself I did, and where I couldn't I say so.

Short version

Hate subscriptions, fixed launch window: LaunchList
Want a real free plan, referrals, email tools: Waitlister
Minimal widget, live in ten minutes, have a budget: GetWaitlist
Running a contest or sweepstakes: KickoffLabs

The rest is why.

The table

Alphabetical, so the running order isn't an opinion.

Tool	Starting price	Free tier	Referrals	Public API	First-party SDK
GetWaitlist	$15/mo	Closed to new accounts	Yes, $15 plan	Yes, unauthenticated	None found
GrowSurf	$125/mo	14-day trial	Yes, core product	Yes	npm + PyPI
KickoffLabs	$19/mo	Yes, 100 uniques/mo	Yes, plus contests	Yes	None found
LaunchList	$19 one-time	Yes, 100 submissions	Yes, on free tier	None found	None found
Prefinery	$49/mo	14-day trial	Yes	Yes	None found
Viral Loops	$49/mo	14-day trial	Yes, core feature	Yes, 16 endpoints	Unverifiable
Waitlister	$19/mo	Yes, 100 subscribers	Yes, $19 plan	Yes	npm

One note on that free-tier column. Three of these have a free plan rather than a trial: KickoffLabs, LaunchList and Waitlister. The rest give you 14 days and then stop, and GetWaitlist's free tier is closed to accounts created after June 12, 2025. When you're still validating, that difference matters more than the headline price.

The tools

GetWaitlist

The pitch is fast setup. Embed a widget, collect emails, track referrals.

Pricing: $15/mo Basic, $50/mo Advanced, $250/mo Pro. No free tier for accounts created after June 12, 2025.
Strongest: simplicity, and an unusual developer surface. The documented API needs no authentication at all. I fetched a live waitlist as JSON with no credentials. Their docs say a much larger authenticated API exists, mostly undocumented, and to ask if you need it.
Honest weakness: the free tier is closed to new accounts, so the cheapest way in is $15/mo. Sending from your own domain is gated to the $250 plan.

GrowSurf

A referral program tool that people sometimes use as a waitlist.

Pricing: $125/mo Startup, $314/mo Business, custom above. 14-day trial.
Strongest: the in-product referral experience. A user's share link is generated the moment they log in, with no separate signup. It also has the most complete developer surface in this list, mine included: an OpenAPI 3.1 spec, official SDKs on npm and PyPI, seven documented webhook events, and an MCP server.
Honest weakness: it isn't built for pre-launch. No landing page builder, no queue position, no move-up-by-referring mechanic. If you want a viral waitlist for an unlaunched product this is the wrong shape of tool, and the entry plan is several times the cost of the pre-launch options.

KickoffLabs

The contest and sweepstakes specialist. Refer-five-friends-to-win mechanics, points leaderboards, compliant giveaways.

Pricing: free plan (100 uniques/mo, branded). Hobby $19, Premium $69, Business $145, Enterprise $289, roughly 30% less annually.
Strongest: contest mechanics and fraud detection. If you want to run a sweepstakes, this is the one. Twelve documented outbound webhook events, with per-plan rate limits published.
Honest weakness: heavier than a plain waitlist tool. Multi-language means duplicating a campaign per language and translating the strings yourself. Its llms.txt doesn't mention the API, so an agent reading that file first won't find it, though the API itself is documented.

LaunchList

The pitch is the pricing model: pay once, no subscription. For a two or three month launch window that's a better deal than paying monthly forever.

Pricing: free tier (100 submissions, referrals, fraud detection). One-time per campaign: $19 for 500 submissions, $79 for 10,000, custom above 100,000.
Strongest: one-time pricing, and a free tier that includes referrals and fraud detection. Embeddable widget for the no-code platforms.
Honest weakness: fewer features than the subscription tools. No email broadcast system, so bring your own ESP. Simpler hosted pages. And if you want to drive it from code, I could not find an API: their docs sitemap lists thirty-six pages and none of them is an API page. Webhooks exist through a plugin on the Grow plan.

Prefinery

Running since 2007, longer than most of this category has existed. Enterprise SLAs, deep API, many custom fields per subscriber, staged beta rollouts.

Pricing: $49/mo Lite, $249/mo Essentials, $499/mo Pro month-to-month; $39/$199/$399 billed semiannually. 14-day trial, no free plan.
Strongest: maturity and flexibility. If you can describe a waitlist mechanic you can probably build it here. Eighteen documented webhook events covering the full tester lifecycle, the most of anyone in this list. Its pricing table is also unusually explicit that API and webhooks are excluded from the entry plan.
Honest weakness: the interface shows its age and setup is slow. For a founder who wants a good-looking waitlist page and a leaderboard by tonight, it's overkill, and $49 is a steep entry for validating an idea.

Viral Loops

The referral-template platform. Pick a template modeled on a famous launch, add your copy, run it.

Pricing: billed annually, $35/mo Start-up through $279/mo Power. Month-to-month is higher. 14-day trial, no free plan.
Strongest: the template library. You start from a mechanic that already worked rather than from zero. Sixteen documented API endpoints with per-endpoint rate limits.
Honest weakness: no free plan. I also could not verify what's gated to which plan: their pricing page returns 403 to automated requests, and their openapi.json returns 403 rather than 404. There's a @viral-loops/widgets package on npm last published in 2022 with no repository or homepage, and I found no vendor page linking to it, so I won't call it first-party.

Waitlister

Hosted landing pages, embeddable forms, referral program, email broadcasts, custom domains, webhooks and a REST API, plus native embeds for Framer, Webflow, WordPress, Shopify, Squarespace and Bubble among others.

Pricing: Free (100 subscribers, 1 waitlist). $19 Launch (unlimited subscribers, referrals, 2,500 emails/mo). $29 Pro (custom domain, advanced analytics). $49 Growth (custom email domain, 30+ translations, referral fraud detection). $129 Business (team seats).
Strongest: the free tier is a plan rather than a trial, and $19 gets you unlimited subscribers, referrals and email broadcasts in one place. Several tools here expect you to bring your own ESP for that last part. On the developer side there's an OpenAPI 3.0.3 spec at waitlister.me/openapi.json, an npm SDK, and an MCP server listed in the official MCP registry. Appending .md to any docs URL returns raw markdown, which is useful if you point an agent at it.
Honest weakness: It's much younger than some other options. And for a referral program that lives inside your product for years, GrowSurf is the right shape.

How to pick

Start with whether you're validating or launching. If you're validating, pick something with a real free plan so you don't pay for a test that may go nowhere. If you're launching and budget isn't the constraint, the question becomes campaign shape instead.

Then the shape. A pre-launch queue with referrals, a contest, and an ongoing in-product referral program are three different products, and forcing one tool into another's job is what makes people hate their tooling.

Solo founder or small team: start free somewhere and pay when you hit the thing you actually need, whether that's referrals, a custom domain, your own sending domain, or translations. Enterprise, contests, or a long-term referral engine inside your app: pick the specialist.

Everything above is checkable, and some of it will be wrong within a month. If you find something that already is, say so and I'll correct it.

I made my SaaS installable by AI agents. Here's what was broken.

Devin D — Fri, 14 Aug 2026 09:18:10 +0000

Two weeks ago I watched an agent run a full product launch on Waitlister, my waitlist tool.

It created the waitlist, generated and published a landing page, signed up a test address, checked the signup was real by fetching the public page unauthenticated, then unpublished and deleted everything it had made.

Nobody touched the dashboard.

The interesting part isn't that run. It's what I found while getting there, because almost none of it was visible from a browser.

Why I bothered

My users are pre-launch founders, which is exactly the group now building landing pages by prompting Claude, Cursor, or v0 instead of opening a site builder. "Add a waitlist to my site" is a normal thing to ask an agent to do, and increasingly nobody types my product name at all.

The uncomfortable part is when an agent hits a 404 or installs a package that doesn't exist, it doesn't debug. It picks a different tool in the next sentence and never tells the user it switched. You lose without ever seeing a bounce.

What I shipped, in order of how much it turned out to matter

Full API coverage for the whole job. Not most of it. More below, because this one was worth the other five combined.
A skill.md route. One page written for an agent rather than a person: a decision tree (no API key yet, go this way; account key, go that way), both code paths, and a self-check at the end so the agent can confirm it worked.
An OpenAPI spec at a fixed URL. Valid 3.0.3 at /openapi.json, all five endpoints, auth, rate limits, error shapes. Endpoint changes update the spec and the SDK types in the same PR or they don't merge.
A real npm SDK, plus four aliases under the names an agent is likely to reach for.
An MCP server, 14 tools, so agents that speak MCP get typed calls instead of reading my docs.
llms.txt and llms-full.txt, an index of the docs in plain text with a short block at the top saying what this product is and where the golden path starts.

What was broken

Honest list.

The file I wrote for agents was the one file agents couldn't read. My llms.txt is proxied from a vendor, the proxy forwards the caller's user-agent, and the vendor had AI-bot blocking switched on by default. Every AI crawler got a 403 on the document whose only purpose is being read by AI
crawlers. I found it by requesting my own files with eight bot user-agents and diffing the status codes. One vendor toggle can put it back, silently, which is why the check now runs on a schedule.

llms-full.txt is too big to be read at answer time. It's 961 KB and grows with every docs page. It serves from my side in about 1.3 seconds, and Claude's answer-time fetcher still timed out on it at 60 seconds. The small index is the one that actually gets read. I haven't fixed this yet;
the options are trimming it or splitting it, and I've done neither.

Agents guess your package name. waitlister-js, waitlister-sdk, waitlister-node, @waitlister/sdk. Instead of arguing with that, I published all four as real packages that re-export the SDK and carry a deprecation notice pointing at the canonical name. A wrong guess installs and self-corrects.

My email validator rejected valid addresses. Agents test with plus-tags, because that's how you make a disposable address on an account you already own. My validator refused some of them. Human users with Gmail aliases had been hitting the same wall for as long as the rule existed.

My 404s weren't 404s. Unknown doc slugs returned a soft page with a 200. An agent reading status codes concludes the page exists and that it guessed the URL right, then builds on it. Real 404s, plus a 301 from the old getting-started URL.

The single page that would have saved five fetches was labeled for the wrong reader. In the first live test the agent's own friction report said the docs were split across pages with no single page giving the complete picture, so it fetched five. skill.md is that page, and /docs/api linked to it in a callout at the very top. The callout was headed "Integrating with an AI agent," which is a label about who it's for, and the agent was reading through a fetch-summarizer where that reads as a sidebar. Reframed as "Fastest path: complete single-page integration guide," it started landing. The link was never missing. It was filed under the wrong thing.

Every run used to die at the same sentence. The agent could create a waitlist through the API and then had to say "now open the dashboard to build your landing page." That one gap ended the automated path every time, no matter how good the rest of the surface was. Creating, updating, and publishing a landing page over the API is what made an end-to-end run possible at all.

The one thing I'd tell someone starting this

Test with the real fetchers, not with curl. Every failure above lived in the gap between what my server sends and what an agent's toolchain actually receives: a user-agent rewritten in transit, a file that serves fine but times out at answer time, a status code that lies, a link that survives the fetch but not the summary. Curl told me everything was fine. It was, for curl.

Where I've got to: four consecutive live runs with zero wrong guesses, a complete correct integration plan from public surfaces alone in about 90 seconds, and a waitlist created from an empty account in three minutes and eighteen seconds.

Check it yourself

All of it is live. If you want to see what an agent actually receives, point yours at waitlister.me/skill.md and ask it to set up a waitlist.

The same path written for a person is at waitlister.me/growth-hub/guides/set-up-waitlist-with-ai-agent.