Revenue & Sales Systems
Lead management: one system for every lead, from first touch to won or lost
Where leads go today
How leads are handled today
- 01Inquiries land in several places: form notifications, voicemail, a shared inbox, a marketplace dashboard.
- 02Someone copies them into the CRM or a spreadsheet when they have time, often without recording the source.
- 03Qualification is a judgment call, made differently by each person.
- 04Leads are assigned by whoever is around, or not assigned at all.
- 05Follow-up depends on memory. Leads that don't reply to the first attempt quietly go cold.
Where it breaks: slow first response, duplicate records, leads with no owner, follow-up that stops after one attempt, and marketing decisions made without outcome data.
With the system in place
- 01Every channel feeds one durable intake: forms, calls, email, referrals, and imported lists.
- 02Each lead is normalized and deduplicated, with its source recorded.
- 03Qualification and scoring apply your criteria: explicit rules first, model assistance only where rules can't decide.
- 04Routing assigns an owner by service, territory, availability, or existing account ownership.
- 05Follow-up runs on the lead's state until it replies, books, or is closed out, and escalates when an owner doesn't act.
Outcomes such as booked, proposal sent, won, and lost flow back, so source and conversion reporting reflect what actually happened.
Follow one lead from inquiry to won
Events
CRM record
- Status
- New
- Source
- Web form (spring campaign)
- Owner
- —
- Score
- —
- Stage
- —
- Next step
- —
- Value
- —
Event 1 of 7: lead.created
Built from five capabilities
Qualify
Lead Qualification · Lead Scoring
Explicit rules first, model help only where rules can't decide.
Route
A qualified lead with no owner is still a lost lead.
- service line
- territory
- account owner
- availability
- priority
no match → fallback queue
How the system fits together
Channels
Records
The CRM stays the source of truth for relationships and pipeline state. Around it sit an intake and orchestration layer that receives every channel, an enrichment and classification step, routing rules, a communication layer for follow-up, and an event history that reporting reads from. Shared event names such as lead.created, lead.qualified, lead.assigned, appointment.booked and opportunity.won let automation and reporting agree on what happened. Analytics derive history from the CRM; they shouldn't become the customer database by accident.
Where people stay in charge
Sales conversations stay human
The system prepares context, assigns, and reminds. People have the conversations.
Qualification overrides
Owners can correct a score or disqualify a lead, and the correction is recorded.
Unroutable leads
A lead that matches no rule goes to a named queue instead of disappearing.
Follow-up content
Messages and sequences are approved before they run.
What changes from one business to the next
- Which channels and sources are connected.
- Qualification criteria and scoring weights.
- Routing rules: service lines, territories, rotation, account ownership, working hours.
- Follow-up timing, channels, and stop conditions.
- Which CRM is used, or whether the CRM needs to be redesigned or replaced first.
Technology we usually start from
Usually the CRM you already run, such as HubSpot, or Twenty where an open-source CRM fits; n8n for intake and orchestration; PostgreSQL for intake state and event history; and Twilio or an email provider for follow-up. Enrichment providers and model-assisted classification are added only where they improve decisions. These are starting candidates, not requirements.
Is lead management the right system?
Good fit
- Leads come from several channels and are handled inconsistently.
- Slow response or dropped follow-up is costing you work.
- You want source and conversion reporting you can act on.
- More than one person or team handles leads, so ownership matters.
Not the right fit
- Lead volume is low and one person already handles every inquiry well.
- The sales process isn't defined yet. Stages and ownership have to be decided by the business; software can't settle them.
- The real problem is too few leads rather than how they're handled. That's a growth problem.
How we'd approach it
01
Understand
As much as the problem needs
We map how the work runs today: who does what, which systems hold the records, and where it breaks.
02
Design
Decided before it's built
Ownership, rules, integrations and exceptions, agreed with you and written down with acceptance criteria.
03
Build
Connected to what you use
We build the scoped system, connect it to the tools you already run, and test it on the cases that matter.
Questions about lead management
Is lead management just a CRM?
The CRM is the record. Lead management is everything that keeps the record complete and moving: capture from every channel, qualification, ownership, follow-up and outcomes. Most businesses already have a CRM; what's missing is the system around it.
Do we have to replace our CRM?
Usually not. The system works around the CRM you already run. If the CRM can't represent your stages and ownership, that gets fixed first, as part of the same project.
How does it know which marketing source produced a job?
The source is recorded when the lead is captured and stays on the lead through to the outcome. When the job is won, the win is attached to the original source.
What happens when a lead doesn't fit any rule?
It goes to a named queue with an owner who reviews it. Nothing disappears, and the unmatched cases show where a rule is missing.
Find out where your leads wait
Tell us where leads come from and what happens to them today. We'll show you where they stall and what we'd build first.