Back to Blog

Waitlister vs Lighthouse: Which Fits an Indie Launch? (2026)

Waitlister wins on referral mechanics. Lighthouse wins on survey depth, feedback after launch, and a REST API for indie iOS/SaaS onboarding.

Posted by

Hand-drawn illustrated header reading Waitlister vs Lighthouse
Waitlister wins on referral mechanics. Lighthouse wins on survey depth, feedback after launch, and a REST API shaped for indie SaaS onboarding.

Waitlister is a modern waitlist tool with clean landing pages, position-based referral mechanics, and pricing that lands in roughly the same range as Lighthouse. Lighthouse is a launch toolkit where the waitlist is one of four pieces (waitlist landing page with survey on signup, newsletter, feedback page, REST API). The price is similar; the shape of the product is not. This is the honest comparison from someone who has used both for different things.

I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. Different audiences, same indie-dev frustration: every new project rebuilt the same pre-launch plumbing.

Table of contents

What each tool actually is

Waitlister is a waitlist product focused on capture and referral. Clean drag-and-drop landing page builder, position-based referral (users see their rank and move up by inviting friends), custom domain on paid tiers, embeds, and basic analytics. Pricing lands in the same range as Lighthouse. The product is a waitlist tool, executed well, and stops when the launch happens.

Lighthouse is a launch toolkit for indie SaaS founders. A waitlist landing page with survey questions on the same form, a newsletter for keeping the list warm after launch, a feedback page for once people are using the product, and a REST API on Pro. Flat $19 monthly, $29 with API. Built for people whose product is a SaaS or an app, where the waitlist is one piece of a validate-then-launch-then-iterate arc.

Side-by-side comparison

Two tools priced in the same range but shaped for different jobs. The matrix below is the honest version.

CapabilityWaitlisterLighthouse
Waitlist landing pageYes, headline featureYes, headline feature
Referral mechanics (position-based)Yes, the differentiatorNo, not the lane (yet)
Survey questions on the signup formBasic custom fieldsYes, native pattern with analytics
Survey answer segmentation for campaignsNot the focusYes, filter list by answer, send
Newsletter / campaigns to the listBasic broadcastYes, campaigns baked in
Feedback page after launchNoYes, baked in
REST API for signups and answersBasic, capture-focusedYes on Pro, indie-shaped, onboarding-focused
Custom domainYes on paid tiersYes on Pro
Pricing rangeSimilar to Lighthouse$19 flat, $29 with API
Post-launch useWaitlist onlyNewsletter + feedback + API

Where Waitlister wins

Be honest about this part. Waitlister is the right tool for a real list of jobs:

  • Position-based referral mechanics. “You are #128 of 4,213” is a specific social-proof shape that reads well for consumer-facing launches. Waitlister has the referral engine that Lighthouse does not (yet) offer.
  • Focused product surface. If the whole job is capture-signups-with-referral and nothing else, Waitlister does that job with fewer distractions. No extra tabs, no post-launch modules. Simpler shape when the launch is a one-off.
  • Consumer-launch positioning. Waitlister is priced and marketed for consumer product launches (apps, courses, physical products) where the referral graph is the whole story. Lighthouse targets indie SaaS, which is a different audience with different signup shapes.
  • Fast landing-page setup. Waitlister landing pages take a few minutes to set up. Lighthouse is similar speed but the extra survey and campaign scaffolding is visible even when unused; if you never plan to use it, the surface area feels heavier than it needs to be.
Practical rule: if the launch is a one-off consumer push with a referral loop as the whole story, Waitlister is the honest answer.

Where Lighthouse wins

Lighthouse is the better fit when the waitlist is the start of a longer arc and the price gets used across more than the capture step:

  • Survey depth on the signup form, as the default. Lighthouse treats the survey-on-signup pattern as the main pattern. Multiple-choice, short-text, long-text, email question types, with answer segmentation ready for the launch campaign. Waitlister has custom fields, but the survey UX and the “email everyone who answered X” flow are not the focus. See why answers beat emails and how to segment your waitlist by survey answers.
  • Feedback page after launch. Waitlister stops at the launch. Lighthouse keeps going with a feedback inbox for bugs, feature requests, and praise on the same dashboard. For where dedicated feedback tools fit, see best product feedback tools.
  • REST API shaped for indie SaaS onboarding. Lighthouse Pro exposes waitlist signups, survey answers, and feedback as REST endpoints your product can pull. The data shape is waitlist-with-survey-answers, so an indie iOS or web app can use it directly for onboarding personalisation. Waitlister has an API, but the shape is capture-focused; the onboarding semantics you would build yourself. See how to add a TestFlight beta waitlist to your iOS app for the pattern.
  • Newsletter and campaigns for the list. The warmup emails, the launch email, and the 72-hour follow-up all live in the same dashboard as the waitlist. See how to convert waitlist signups into paying customers for the full sequence.
  • Same price, more surfaces used across a launch. At roughly the same monthly cost, the number of product surfaces the subscription actually gets used for is materially higher on Lighthouse (waitlist capture + survey answers + newsletter + feedback + API). Waitlister excels at one of those; Lighthouse covers four.

Who should pick which

The choice is rarely “which one is better”. It is “which job is this for”. Five founder shapes:

The consumer-launch founder

You are shipping an app, course, or physical product with a viral referral story. The launch is a single burst and referral is the whole mechanic. Waitlister, every time. Lighthouse does not have the referral engine.

The pre-launch indie SaaS founder

You are weeks from beta and you need a public landing page with a signup form, survey questions on the form, and a way to email the list when you launch. Lighthouse, every time. Waitlister gets the signups but the survey UX, campaign flow, and feedback page are missing. See what to put on your waitlist landing page for the layout Lighthouse ships.

The founder raising capital

You are raising and the bottleneck is the raise itself. Neither Waitlister nor Lighthouse is the headline tool here. Dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the investor side. Pick Waitlister if the raise story leans on a viral-share signup graph; pick Lighthouse if the raise story leans on survey answers and audience insight (more common for a B2B SaaS pitch).

The post-launch SaaS founder

You shipped, you have customers, you want to send updates and collect feature requests. Lighthouse for the bundled flow (newsletter and feedback inbox in one dashboard). Waitlister is a pre-launch tool; the product surface stops at the launch email.

The indie iOS developer

You want a beta waitlist with survey questions and the data flows into your iOS app for onboarding personalisation. Lighthouse on Pro. The waitlist-with-survey-answers REST API is the differentiator. Waitlister has an API but it is capture-focused, not onboarding-focused; you would build the semantics yourself.

Using both together

Rarely worth it at similar price points. Two patterns exist:

  • Waitlister for a viral consumer campaign, Lighthouse for a separate SaaS product. A studio running two projects (a consumer app on Waitlister, an indie SaaS on Lighthouse) picks each tool for its own product. No overlap, no data sharing.
  • Waitlister as the referral top-of-funnel, Lighthouse as the qualified sub-list. Signups go into Waitlister for the referral push; once someone completes referral milestones, they are invited to a Lighthouse waitlist with a survey to qualify. Two tools, two lists, one handoff. Only worth it if the referral loop is actually working; otherwise it is one tool too many.

The fit-for-purpose rule: each tool does the job it was built for. Most indie founders should pick one.

Frequently asked questions

The prices are similar. Why does it matter which I pick?

At the same price point, the question is what the product actually does across the arc of a launch. Waitlister excels at pre-launch capture with referral. Lighthouse covers capture + survey answers + newsletter + feedback + REST API on Pro. If the tool is only used for the capture step, Waitlister is a cleaner fit at similar cost. If the tool is used across four surfaces over the launch and post-launch year, Lighthouse gives you more product for the same price.

Does Lighthouse have referral mechanics?

Not today. Referral is on the roadmap. If a viral referral loop is the whole launch story, Waitlister is the honest pick for now. If the launch story is “survey answers, warm the list, ship the launch email, keep going with feedback”, Lighthouse covers the full arc that Waitlister stops halfway through.

Can Lighthouse send the launch email to my waitlist?

Yes. That is the second piece of the toolkit. Compose a campaign in the dashboard, pick the list (your waitlist signups, filtered by survey answer if you want), send. For the launch email shape, see how to write your first launch email. For the sequence around it, see how to convert waitlist signups into paying customers.

Can I migrate from Waitlister to Lighthouse?

Export signups from Waitlister as CSV, import into Lighthouse. Survey answers do not carry across cleanly (the data shape is different), so plan on sending a one-time segmentation email once the list is imported. Referral position rank is not preserved; if the referral graph was the whole point, stay on Waitlister.

Do I need both?

No. Most indie founders pick one. Choose by the job: a viral referral loop picks Waitlister; a launch toolkit with the waitlist as one piece of a validate-then-launch arc picks Lighthouse. Use both only when you have clearly separate uses (viral campaign on Waitlister, product waitlist on Lighthouse).

Pick the tool that fits the actual job. If the launch is a one-off consumer push with a viral referral story, Waitlister is the honest answer at a similar price. If the launch is the start of a validate-then-launch arc where survey depth, newsletter, feedback, and a REST API all matter, Lighthouse gives you more product for the same money. Most of the disappointment with either tool comes from buying it for the job it was not built for.


Lighthouse gives you the waitlist with survey questions, the newsletter for keeping the list warm, and the feedback page for after you launch, in one place. 7-day free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.

Join Discord