One pipeline for every lead you capture
Leads from your assistant, your forms and your landing pages all land on the same board. Move them through the stages, see which campaign brought them, export them, or push them straight into your own CRM.
From capture to outcome
- 1
Leads arrive
The assistant captures one in a chat or a call, someone submits a form or a landing page, or you add one by hand. All three land in the same list.
- 2
Move it through the stages
New, contacted, qualified, won, lost. Your team moves the card as the conversation progresses, and the notes and contact details travel with it.
- 3
See what actually works
The traffic-source report groups leads by campaign and shows the daily trend, so you can tell which channel is paying for itself and which is not.
What lead tracking gives you
A five-stage pipeline
New, contacted, qualified, won and lost, with search across every lead in the workspace.
Traffic-source report
Leads grouped by utm_source and utm_campaign, with the daily trend next to it. Untagged traffic folds into a direct bucket instead of disappearing.
Attribution that survives the handoff
utm tags, gclid, fbclid, the referrer and the landing URL are captured at submit and stay on the lead, so the ad that paid for it is still known weeks later.
The whole story on the card
Name, phone, email, note, stage, source and the conversation it came from, so whoever picks the lead up knows what already happened.
CSV export
Take the pipeline out whenever you want. Your leads are your data, not something locked behind our panel.
Into your own CRM
Every capture fires a lead.captured webhook, signed with your secret and carrying the attribution, so your own system can be the system of record.
Only your team sees it
Leads are scoped to your workspace and its projects, and members see what their role allows. Nothing ever crosses to another tenant.
Turns into an appointment
When the assistant books a visit for a lead, the two stay linked, so the appointment and the contact are never two rows nobody reconciles.
Frequently asked questions
- Is this a full CRM?
- No, and it is not trying to be. It is the pipeline between capture and your real system: enough to work a lead on the day it arrives, with CSV export and a webhook for whatever you use downstream.
- Can I change the stages?
- The stages are fixed at new, contacted, qualified, won and lost. They cover the path from capture to outcome, so there is no setup step before your team can start working leads.
- How do I see which campaign worked?
- Tag your ad links with utm_source and utm_campaign. The traffic-source report groups leads by them and shows the trend over time, with untagged visits in a direct bucket.
- Can I export my leads?
- Yes, to CSV, any time. There is no lock-in on your own contact data.
- Can it push leads to my system?
- Yes. A lead.captured webhook fires on every capture, signed with your own secret so your backend can verify it before trusting the payload.
- Who can see the leads?
- Members of your workspace, according to their role. Every query is scoped to your organization, so no other tenant can read your pipeline.
Getting it into the tools you already run
Every lead captured, appointment booked and call finished can be pushed to your CRM, your automation platform or your own backend over a signed webhook, with retries and a delivery log. Nine events, and nothing to install on either side — n8n, Make, Zapier or your own endpoint.
Webhooks and integrations →