Every form fill becomes a lead.
Inbox, notes, tags, document attachments, PDF export. Workflows fan each lead into Slack, HubSpot, your inbox — whatever you already use.
Why teams turn it on.
One inbox for every site
Run five landing pages? Five sources of leads, one ranked inbox. Filter by site, tag, or assignee.
Built-in workflows
Pipe leads into Slack, HubSpot, Mailchimp, Google Sheets, Twilio SMS — or a webhook to anywhere else. Conditional, retryable, audited.
Notes, attachments and PDF export
Add context, attach documents, generate a branded PDF for the client. The whole record stays searchable.
API + MCP
Read leads from a script, your own CRM, or Claude Code over MCP. Your data, your access.
Three steps, no setup tax.
- 1 Any <form> on a ctrlsignal site auto-posts to your inbox.
- 2 We tag it by site, page, and the form's id — searchable from day one.
- 3 Build a workflow per form: who gets notified, where the lead is routed, what fires next.
Common questions.
Can I import leads from elsewhere?
Yes — CSV import, plus an API endpoint to push leads from other tools.
How do I push to my CRM?
First-party integrations for HubSpot, Pipedrive, Mailchimp, ConvertKit, Beehiiv. Generic webhook for anything else.
Lead CRM, ready to go.
Start with a prompt.
Type what you want to build. We draft the page in seconds and turn lead crm on from day one.
See the lead inbox