A lead capture MVP needs a verified follow-up loop

A lead capture MVP is not just a form.

The full loop is: publish a focused landing page or waiting list, capture qualified intent with a form, store the lead in a simple owned system, verify the email, send the promised next step, and keep the record ready for outreach or newsletter workflows.

In concrete terms:

landing/waiting page -> Formbricks/email/PocketBase capture -> Sheets/JSON/CSV/SQLite/PocketBase store -> email verification -> ESP follow-up -> DNS deliverability -> Listmonk/MailerLite/Smartlead/CRM when useful

The practical version can be small:

• Astro/Next.js page for the offer.
• Formbricks, an email form, or PocketBase for capture.
• Google Sheets, JSON, CSV, SQLite, or PocketBase as the first lead store.
• Email verification before enrichment or outreach.
• Mailtrap, Resend, Mailjet, or another ESP for transactional follow-up.
• SPF, DKIM, DMARC, and provider DNS records before serious sending.
• Listmonk, MailerLite, Smartlead, or a CRM only when the loop already produces useful leads.

The MVP is ready when every lead has a source, enough context to qualify it, a verified address, and a next action.

Until then, more tooling mostly adds complexity.

Related:

• A Quick Waiting List for your SaaS
• A boilerplate to create Landings for lead generation.
• Any SaaS needs this: Leads and a UI
• Forms and Newsletters for your Website
• Formbricks turns static pages into lead capture
• Simple lead stores beat premature CRM complexity
• Email verification protects the pipeline
• Email APIs are product infrastructure
• Mail DNS is deliverability infrastructure
• Waiting to Landing repo
• Simple waiting list repo
• DIY landing boilerplate
• DIY Landing email form
• DIY Landing Formbricks modal
• DIY Landing Formbricks inline component
• Make Landing repo
• Programmatic email script
• Mailtrap ESP notebook
• PocketBase Docker config
• Listmonk Docker config
• Google Workspace DNS check script