Lead distribution software: what it does and what to evaluate
Lead distribution software receives leads from sellers, checks them, and sends each one to a buyer whose rules it matches, usually in real time. It runs ping/post auctions, applies routing rules, caps and filters, validates data, stores consent records, tracks returns and reports what sold. Evaluate it on those features, its APIs and its reliability.
Key points
- Lead distribution software sits between sellers and buyers: it takes in each lead, checks it, picks a buyer and delivers it.
- The features to evaluate are ping/post, routing rules, caps, filters, validation, duplicate checks, consent record storage, returns, reporting and APIs.
- Test any system with your own buyers, sellers and lead fields before you sign, and measure response time and errors.
- Brokers, networks, aggregators and large buyers use it; a seller with one buyer usually does not need it.
What does lead distribution software do?
Lead distribution software is the system that moves a lead from the seller who produced it to the buyer who will contact the person. For each lead, it runs the same sequence:
Intake
Receives the lead from a seller by API, form post or file, and records the seller and source ID.
Check
Validates required fields, phone, email and address, and checks for duplicates against recent leads.
Match
Finds buyers whose filters, schedules and caps fit the lead.
Price
Pings eligible buyers for bids, or applies a set price, and picks the winner under the routing rules.
Deliver
Posts the full lead and its consent record to the winning buyer and records the buyer’s response.
Account
Records the sale, any later return, what the buyer owes and what the seller is due.
How this matching works across a whole network is explained in lead distribution explained. This page is about the software that runs it.
Who uses lead distribution software?
- Lead brokers and networks, to route leads from many sellers to many buyers. See what is a lead broker.
- Aggregators, to combine supply from many sources and serve their own buyer programs.
- Large buyers, to receive leads from many vendors and route them to offices or teams.
- Lead generators with many buyers, to sell their own leads without going through a broker.
A lead generator that sells to one broker usually does not need it: the broker’s system does the routing. See how to sell leads you generate.
What features should lead distribution software have?
| Feature | What it does | What to ask |
|---|---|---|
| Ping/post | Sends a partial lead to buyers for bids, then posts the full lead to the winner | How many buyers can be pinged at once? What is the timeout? Are both ping and post logged? |
| Routing rules | Decides the order and share of buyers: priority, weighting, tiers, fallback | Can rules be combined and changed without a developer? Is there a test mode? |
| Caps | Limits leads per buyer per hour or day, and budget limits | Are caps per buyer, per campaign and per source? What happens at the cap? |
| Filters | Matches leads to buyers by state, ZIP code, sub-type and form answers | Can filters use any field, including custom ones? |
| Schedules | Opens and closes buyers by day and hour, in their time zone | Are holidays and time zones handled? |
| Validation | Checks phone, email and address before routing | Which checks are built in and which need outside services? |
| Duplicate checks | Rejects or flags leads seen recently | Over what period, and matched on which fields? |
| Consent record storage | Keeps the consent record with each lead and passes it to the buyer | Which consent record formats are accepted? How long are records kept? Can one be retrieved by lead ID? |
| Returns | Records buyer returns and reverses them for the seller | Can return reasons and windows be set per buyer and per seller? |
| Reporting | Shows sold rate, price, returns and margin by seller, source and buyer | Can reports be exported or read by API? How current are they? |
| APIs and delivery | Connects sellers and buyers: inbound API, outbound post, email, CRM connectors | Is the API documented? Which delivery formats are supported? |
| Billing | Totals what each buyer owes and each seller is due | Does it invoice, or export data for your accounting system? |
| Access and audit | User roles and a log of every change | Can sellers and buyers have limited logins? Is every rule change logged? |
Ping/post and auctions
If you sell to buyers who bid, ping/post is the core feature. Check that the software sends pings to all eligible buyers in parallel, enforces a timeout, and logs every ping, bid and post. Ask how ties are broken and whether a buyer can accept the ping and then reject the post. The exchange itself is explained in ping post explained, and tiers and floors in what is a ping tree.
Routing rules, caps and filters
Routing rules decide which buyer wins when more than one is eligible. Look for priority, weighting, tiers with price floors, schedules and fallback, and the ability to combine them. The rule types are explained one by one in lead routing.
Validation and duplicates
Checks that run before routing stop bad leads from reaching buyers and coming back as returns. Ask which checks run in real time and how a failed check is handled: rejected, flagged, or routed to a different buyer. See lead validation.
Consent record storage
Buyers need proof of consent for each lead they call. The software should accept the consent record from the seller (consent text, time stamp, IP address, page URL, or a third-party certificate), keep it with the lead, pass it to the buyer, and let you retrieve it later by lead ID. See consent record-keeping.
Returns and reconciliation
Returns should be recorded against the original lead, with a reason and a date, and reversed on both the buyer and the seller side. Reports should show returns by source, so you can act on sources that cause them.
Lead distribution software evaluation checklist
Use this list when comparing systems:
- Supports ping/post and direct post, with a configurable ping timeout.
- Routing rules: filters, priority, weighting, tiers with price floors, schedules and fallback.
- Caps per buyer, per campaign and per source, by hour and day.
- Filters on any lead field, including custom fields for your vertical.
- Real-time validation and duplicate checks, with a clear outcome for failed leads.
- Consent record stored with every lead, passed to buyers, and retrievable by lead ID.
- Return reasons and windows set per buyer and per seller, reversed on both sides.
- Reports by seller, source, buyer, state and hour, exportable or available by API.
- Documented inbound and outbound APIs, with test environments.
- User roles for staff, sellers and buyers, and a log of rule changes.
- Stated uptime, response time and support hours, in writing.
- Data security practices and where data is stored.
- Pricing model clear for your expected volume, with no surprise per-feature charges.
- A way to export all your data if you leave.
How to run a trial of lead distribution software
- Write down your real setup: lead fields, sellers, buyers, their filters and caps, and the routing order you want.
- Ask each vendor for a test account and build that setup yourself, without their staff doing it for you.
- Send test leads that should match, should fail validation, should be duplicates and should hit a cap, and check each result.
- Connect one real buyer and one real seller in the test environment and run pings and posts end to end.
- Measure response time from intake to post, and check the logs for every step.
- Process a test return and confirm it reverses on both sides and shows in reports.
- Retrieve the consent record for a test lead by its lead ID.
- Read the contract for data ownership, exit terms and support commitments before signing.
Should you build or license lead distribution software?
| License | Build | |
|---|---|---|
| Time to launch | Shorter: configure and connect | Longer: design, build and test |
| Upfront cost | Lower | Higher |
| Ongoing cost | License fees that may grow with volume | Developers, hosting and maintenance |
| Control | Limited to what the vendor supports | Full control of rules and data |
| Fits | Most new brokers, networks and buyers | Operations with rules or volume no licensed system handles |
If you are starting a brokerage, how to start a lead brokerage covers where the software fits with supply, demand, compliance and finance.
Have MVA or home improvement traffic but no distribution setup? Publish to Summit landers and earn rev share on sold leads.
Common mistakes
- Choosing from a demo. A demo uses the vendor’s setup. Test with your own fields, buyers and rules.
- Ignoring consent record handling. If the software cannot store and pass consent records, buyers may refuse the leads.
- No plan for returns. Returns handled in spreadsheets drift away from what the system shows.
- Locking in your data. Confirm you can export every lead, sale and return if you change systems.
- Not testing timeouts. Slow pings lose bids; measure response time under load.
Frequently asked questions
What is lead distribution software?
Software that receives leads, checks them, and sends each one to a matching buyer by ping/post or direct post, while tracking consent records, returns and payments.
Is lead distribution software the same as a CRM?
No. A CRM manages the follow-up of leads a business already has. Lead distribution software decides which buyer or team receives each lead in the first place.
Do I need lead distribution software to sell leads?
Not if you sell to one broker or buyer: their system does the routing. You need it when you sell to many buyers directly or run a brokerage or network.
What is the difference between lead distribution software and lead routing software?
Lead routing software is the part that applies rules to choose a recipient. Lead distribution software includes routing plus intake, validation, ping/post, consent records, returns and billing.
Related guides
- Lead routing: The rule types, with worked examples.
- What is a ping tree: Tiers, floors and fallback.
- Ping post integration for buyers: What a buyer integration needs.
- TCPA for ping/post delivery: Consent across a ping/post sale.
- How to start a lead brokerage: Where software fits in a brokerage.
Run the traffic. We handle the rest.
Every publisher is reviewed before going live. Email us your verticals, traffic sources, states and expected volume.
Or write to team@summitleads.ai. We reply by email.
What happens next
- Step 1: You email us.
- Step 2: We reply by email.
- Step 3: Every publisher is reviewed, and return and payment terms are agreed during onboarding, before you go live.
Already generating leads on your own forms? Sell your leads instead.