A lead pipeline is an overview in which every lead sits in a stage of its follow-up process – for example new, contacted, offer sent, won or lost. The sales partner moves the lead along as soon as something happens; head office sees in real time where every lead stands. In decentralized sales, i.e. wherever a head office distributes leads to independent partners, the lead pipeline closes the gap after lead distribution: without it, head office's view ends at delivery.
Typical stages
A few clearly separated stages have proven themselves, usually five:
- New – the lead has reached the partner but has not been worked yet
- Contacted – the partner has reached the prospect
- Offer sent – there is a concrete offer
- Won – the deal is closed
- Lost – closed without an order, ideally with a reason
Any further stage is only worth it if it answers a question of its own, such as "appointment booked" for sales organizations that advise on site. Too many stages lower the update rate.
How it differs from a CRM pipeline
A CRM manages the contacts, activities and offers of your own sales team; its pipeline shows that team's opportunities. A lead pipeline has a different job: it tracks the leads a head office has bought or generated and distributed, across all partners – regardless of which system each partner uses. The two complement each other: if a partner works with a CRM, the CRM reports the status back to the lead pipeline via API.
What a lead pipeline needs to do
- Feedback without extra effort: The partner updates the status where they work anyway – in their own account via drag and drop, with one click from a reminder email, or automatically from their CRM.
- Reminders instead of control: If a lead sits in a stage too long, the partner is reminded – once per stage and during working hours, not daily.
- Measurability: Because every lead carries its source, cost and recipient, the stages yield the contact rate, close rate and cost per deal per source and partner. Leads under complaint do not count as lost.
Relation to Leadnodes
In Leadnodes, the lead pipeline is a Kanban board that connects directly to distribution. Each lead type belongs to exactly one pipeline and new leads land there automatically; stages can be renamed, added and reordered. Sales partners work directly in their Leadnodes account, see only their own leads and move them through the stages. Per stage you can set after how many hours an email reminder is sent; the status can be changed straight from the email or reported back from a CRM via API. Every status change is logged on the lead and can trigger automations. Head office sees all leads of all partners on one board and in the pipeline report. How the pipeline fits into the overall process is shown in the guide Lead management in decentralized sales.
Frequently asked questions
Do sales partners need their own CRM for the lead pipeline?
No. Partners work directly in their Leadnodes account and update the status there. Anyone already using a CRM can have the status reported back from there automatically, so nothing is maintained twice.
How many stages should a lead pipeline have?
As few as possible, usually five: new, contacted, offer sent, won, lost. Additional stages only if they answer a question of their own.
What is the difference between a lead pipeline and a CRM pipeline?
The CRM pipeline shows one sales team's opportunities in its own system. The lead pipeline shows head office the status of all distributed leads across all partners and systems – including source and cost per lead.
Want to see what becomes of every distributed lead? Start your free assessment
