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

Fillout is a form builder with deep integrations (Airtable, Salesforce, HubSpot, Notion), branching logic, and a generous free tier. Lighthouse is a launch toolkit where the form is one of four pieces (waitlist landing page with survey on signup, newsletter, feedback page, REST API). They both capture data, but they solve different jobs. 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 plumbing.

Table of contents

• What each tool actually is
• Side-by-side comparison
• Where Fillout wins
• Where Lighthouse wins
• Who should pick which
• Using both together
• Frequently asked questions

What each tool actually is

Fillout is a form builder that positions itself against Typeform on power and price. Drag-and-drop builder with branching, calculation fields, payment collection, and file uploads. Deep integrations with the business-data stack (Airtable, Salesforce, HubSpot, Google Sheets, Notion). Free tier with a real response cap; paid tiers unlock the higher-end integrations and workflow automations. The product is a form + the pipes to whatever already stores your data.

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 your thing, and a REST API on Pro. Flat indie pricing. Built for people whose product is a SaaS or an app, where the form is one piece of a launch arc.

Side-by-side comparison

Two tools shaped for two different jobs. The matrix below is the honest version.

Where Fillout wins

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

• Serious form logic. Branching, conditional fields, calculation, file uploads, multi-page flows with custom logic per branch. Fillout is one of the strongest form builders on the market and Lighthouse surveys are simpler by design.
• Deep business-data integrations. If the form output needs to land in Airtable, Salesforce, HubSpot, or Notion as structured rows with field mapping, Fillout was built for it. Lighthouse offers a REST API instead, which is more work to wire up if your target is Salesforce.
• Payment collection on the form itself. If part of the form flow is charging money (event tickets, paid intake, order forms), Fillout has Stripe integration. Lighthouse does not touch this.
• Forms embedded inside other tools. Fillout's embed and Notion integration are good enough that the form lives inside another product. Lighthouse forms are standalone.

Practical rule: if you need serious form power and integrations with a specific business tool, Fillout is the honest answer.

Where Lighthouse wins

Lighthouse is the better fit when the form is one piece of an indie launch arc:

• Waitlist landing page with a goal counter. Fillout builds forms; Lighthouse builds the full pre-launch page, branded, with a visible “47 of 100 signups” counter that motivates people to share. See what to put on your waitlist landing page for the layout that converts.
• Survey questions on the signup form, as the default. Lighthouse treats the survey-on-signup pattern as the main pattern. Fillout can technically do it, but the waitlist landing page and the goal counter around it are not there. See why answers beat emails for the reasoning.
• Newsletter for the list after the waitlist fills. The launch email lives inside the same dashboard. Fillout has no newsletter. Stitching Fillout and Mailchimp recreates the four-tool stack most indie launches give up on.
• Feedback page after you launch. Fillout stops when the form is submitted. Lighthouse keeps going with the feedback inbox that handles bugs, feature requests, and praise after launch.
• Flat indie pricing. $19 a month does not change when you cross 1,000 or 5,000 subscribers. Fillout's paid tiers escalate quickly if you want the higher-end integrations.

Who should pick which

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

The complex-form runner

You need a form with branching logic, payment collection, and output that lands in Airtable or Salesforce as structured rows. Fillout, every time. Lighthouse is not built for this.

The pre-launch indie 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. With Fillout you end up assembling a stack (Fillout form + Carrd page + Mailchimp + ...) that recreates the launch tooling. See Carrd alternatives for a data-led waitlist for why the standalone landing-page route falls short.

The founder raising capital

You are raising and the bottleneck is the raise itself. Neither Fillout 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 Lighthouse for the public waitlist; pick Fillout if the raise itself needs a complex intake form (e.g. an angel-syndicate sign-up).

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). Fillout for one-off structured intake forms (e.g. “request a demo”, “book onboarding”) that need to sync to your CRM.

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 REST API is the differentiator. Fillout has webhooks and integrations, but the shape of the data is form-submissions, not waitlist-signups; you would have to build the waitlist semantics yourself. See how to add a TestFlight beta waitlist to your iOS app.

Using both together

Sometimes the right answer is both. Two patterns I have seen work:

• Fillout for the complex intake form (post-launch), Lighthouse for the waitlist and launch arc (pre-launch). Use Lighthouse to fill the waitlist and send the launch email. Once the product is live and you need a complex “book a demo” or “request custom onboarding” form that syncs to your CRM, add Fillout for that one form.
• Fillout for an audience-research survey with branching, Lighthouse for the product waitlist. You promote a Fillout survey to a broad audience to gather research data with logic branches; you use Lighthouse for the waitlist and signup of the actual product you are building.

The fit-for-purpose rule: each tool does the job it was built for and you do not try to make one do the other.

Frequently asked questions

Can I use Fillout for a waitlist?

You can build a form that takes an email and a few survey questions, and call it a waitlist. What you lose is the landing page with a goal counter, the cap on signups, the share-lever framing, and the “send a launch email to everyone who signed up” flow as one click. For a quick test it works; for the full launch arc it is half the toolkit.

Fillout has integrations. Isn't that the same as an API?

Different shape. Integrations push data to a specific destination (Airtable row, HubSpot contact, Notion database) when the form is submitted. An API lets you pull data on demand from your own code. If you want to fetch yesterday's waitlist signups from your iOS app or build a dashboard inside your own product showing current waitlist status, you need an API and Fillout does not have one in the same sense Lighthouse does. Lighthouse Pro has a documented REST API for signups, survey responses, and feedback.

How does Fillout's free tier really hold up?

Solid. Free plan gives you unlimited forms and a real response cap; the paid tiers unlock the deeper integrations (Salesforce, HubSpot) and workflow automations. For a one-off audience survey the free tier is fine. For the higher-end integrations the paid plans get real fast at $19-$49+ per month depending on tier.

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), send. Fillout has no equivalent and you would need a separate newsletter tool. See best newsletter tools for a small list for the comparison if you are leaning that direction.

Do I need both?

No. Most indie founders pick one. Choose by the job: a complex-form builder with deep integrations picks Fillout; a launch toolkit with the form as one piece picks Lighthouse. Use both only when you have clearly separate uses (complex intake form on Fillout, product waitlist on Lighthouse).

Pick the tool that fits the actual job. If you need a powerful form builder with deep business-data integrations, Fillout is the honest answer. If you need the launch arc (waitlist landing page, survey on signup, newsletter for the list, feedback after launch), Lighthouse covers it in one place. 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. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.