Indie Hacker Playbooks

Validating SaaS Demand with Lead Magnets

Test a SaaS promise by routing useful playbooks into a minimal early-access waitlist

Definition

A pre-product demand test pairs useful material for a specific problem with a one-headline, one-field early-access page, then treats completed signups as stronger evidence than survey intent.

Perspectives

Nicholas Dulait (2026-09-10, X)

Build the landing page in two days with one headline, one email field and one early-access CTA. Publish problem-specific SEO lead magnets from the founders' existing LinkedIn accounts and point them to the waitlist instead of asking hypothetical willingness-to-pay questions. ChatSEO collected 400 signups in 24–48 hours this way before its prototype existed.

Use the waitlist to recruit a bounded beta, but charge earlier than ChatSEO did: its 100-user unlimited beta generated expensive repeated analyses and delayed the payment test even though the usage itself showed demand.

How to apply

  • Fits B2B software whose founder can teach the target problem credibly and already reaches some of that audience on LinkedIn.
  • Use this before Rapid B2C App MVP only when the value can be explained without a working interaction; behavior-heavy products still need a prototype.
  • Continue to Gating a Paywall After the Activation Event once beta behavior reveals a repeatable first-value event.
  • A signup is demand for the lead magnet and promise, not proof of retained willingness to pay.

Limits

  • The 400 signups, timing and contribution of each founder's audience are self-reported, with no unique-visitor or later-payment cohort.
  • The source does not compare this test with interviews, deposits or paid acquisition.

Original article

On this page