Carrd is the go-to for indie hackers launching a single-page thing: $19/year, drag a form, ship to Product Hunt in an afternoon. The form component supports several integrations — ConvertKit, Mailchimp, Buttondown, Formspark, Basin, Zapier webhook, plus built-in email notification. Each has a different deliverability profile.
Picking the wrong one costs you leads you never knew existed. For a launch where every signup matters for early traction, this matters more than the hero copy.
For founder notifications, route Carrd via Zapier (or a Formspark/Basin webhook forwarder) into Resend or Postmark on your domain. For list signups, use ConvertKit or Buttondown directly. Avoid relying on Carrd's built-in email notification for anything important.
What Carrd form options actually do
Built-in email notification
- Sends from Carrd's mail infra on a shared envelope.
- No DKIM on your domain, no bounce control.
- Fine for one-off signals; unreliable at volume.
Formspark, Basin, Formspree (paid form services)
- Sender reputation is dedicated to the form service — usually much cleaner than Carrd's shared pool.
- Some offer DKIM on a subdomain of your choosing (Formspree Gold tier).
- Reliable placement for single-recipient notifications.
ConvertKit, Buttondown, Mailchimp (list integrations)
- Submission feeds a list; welcome email goes from the ESP.
- Best deliverability of the bunch because ESPs authenticate on your domain.
- Team notification still needs a separate path.
Zapier / Make webhook
- Full flexibility: submit → anywhere.
- Route to Gmail send, ESP send, Slack, Discord, CRM.
- Best for founders who want Slack or Discord alerts in real time.
Seed test your current Carrd setup
- Add seed recipients (Gmail, Workspace, Outlook.com, M365, Yahoo, ProtonMail, Fastmail) to whichever notification channel you're using.
- For built-in email: add as additional recipients in the Carrd form config.
- For Formspark/Basin: add to their notification list; both support multi-recipient.
- Submit five plausible entries from incognito.
- Log per-provider placement.
If your seed shows Gmail placement in Promotions rather than Primary, that's not necessarily a deliverability failure — but for indie founders it usually is, because nobody checks the Promotions tab for a one-line "new lead" alert. Treat Promotions as a miss for notification workflows.
Recommended indie stack
The setup that works consistently for indie single-pagers:
Carrd Form
--> Zapier / Make webhook
--> Action 1: Resend API
from: alerts@yourdomain.com (DKIM-signed)
to: you@yourdomain.com
subject: New signup: {{email}}
--> Action 2: Discord / Slack webhook
content: ":tada: New signup: {{email}}"
--> Action 3 (optional): ConvertKit tag
subscriber: {{email}}
tag: launch-dayThat stack: email notification you can search later, real-time ping in your chat, and the lead lands in your list for launch-day follow-up. Total setup time: under 30 minutes.
Set up your sending domain properly
The weak link for most indies is not Carrd, it's their own sending domain being unauthenticated. Minimum DNS:
SPF:
v=spf1 include:_spf.resend.com ~all
DKIM (provided by ESP):
resend._domainkey.yourdomain.com TXT "p=MIGf..."
DMARC (start permissive):
_dmarc.yourdomain.com TXT "v=DMARC1; p=none;
rua=mailto:dmarc@yourdomain.com"Two minutes in Cloudflare DNS, reputation starts building immediately. Add a couple of hand-sent emails from your domain to warm the sender before launch if you're expecting volume.
Decide per channel, not per form
- Team notification: always webhook + your ESP. Never built-in.
- List growth: ConvertKit or Buttondown directly.
- Real-time awareness: Discord or Slack webhook.
- Built-in Carrd email notification: only if you have zero infra and it's a hobby page.