Exclusive vs shared territories for lead buyers: how to run both on one pipeline
Every lead seller ends up with both kinds of buyer at once. One installer pays a premium to be the only one who gets the leads from their county. Three agents in the next county each pay a third of that to share whatever comes in. Both arrangements are fine, both are common, and the question is not which to pick but how to run the two side by side without building two of everything.
This article defines the two arrangements the way buyers understand them, prices them, then shows the setup: one pipeline, tiers for who is asked first, and a price per buyer. It also covers the two traps, a lead sold twice across pipelines, and a territory that needs to switch from shared to exclusive mid-contract.
What buyers mean by exclusive
When a buyer asks for an exclusive territory, they mean two things at once, and it pays to confirm both before you promise either.
- Exclusive to them within the territory. No other buyer of yours receives a lead from those zips. This is the part you control with a rule.
- Exclusive full stop. The lead was not also sold by you on another pipeline, and ideally was not sold by the lead's original source to anyone else. The first half is yours to guarantee with duplicate detection across pipelines; the second half depends on where the lead came from, and you should say so.
Shared, in the buyer's mind, means "I know two or three others get this lead, so I pay less and I call fast." A shared buyer who discovers the lead was shared five ways instead of three feels cheated, so the number of buyers a shared lead can go to is part of the deal, not a detail.
Both arrangements sit on top of a territory, which is a condition on the zip, state or city field. If you have not written those conditions yet, start with how to split leads between agents by territory; this article assumes each buyer already has one.
Pricing the two
The price difference between exclusive and shared is the buyer's whole reason to choose one, so set it deliberately rather than by habit.
| Exclusive | Shared (3 buyers) | |
|---|---|---|
| Who receives the lead | One buyer | Every matching buyer, up to the cap you set |
| Price per buyer | Full price, for example $34 | A fraction, for example $18 each |
| Revenue per lead | $34 | $54 if all three take it |
| Buyer's expectation | Nobody else calls this person | Call within minutes, or lose it |
| What breaks trust | A duplicate sold elsewhere | More buyers on the lead than promised |
Two consequences follow. First, shared usually earns more per lead but only while the buyers keep closing; a shared buyer who stops answering fast will churn, and then you are back to two buyers at $18. Second, the exclusive price should be visibly higher than one shared slot, otherwise the exclusive buyer will ask why they are not just taking a shared slot and calling first. A ratio around two to one is common; the exact numbers depend on the vertical and on what the lead costs you.
Price per lead is set per buyer, so the same lead can be $34 to the exclusive buyer and $18 to each shared buyer without any calculation on your side. If a buyer pays more for a better lead, a price rule on the score or on a field of the lead does that per buyer too.
Tiers: who is asked first
Here is how one pipeline runs both. The pipeline's mode is a single setting: one buyer per lead, or every matching buyer. Pick the mode that describes most of your buyers, then use tiers to carve out the exception.
Most buyers exclusive, a shared pool underneath. Set the pipeline to one buyer per lead. Put the exclusive buyers, each with its territory, in the first tier. Put the shared buyers below with no territory or a wide one. A lead is offered to the first tier; if an exclusive buyer's territory matches and they are under their cap, they take it and nobody else sees it. If no territory matches, or the buyer is full, the lead falls through to the next tier. The shared pool in this layout is really a backfill: it receives what the exclusive buyers left, and it can be one buyer or several in rotation.
Most buyers shared, one exclusive territory. Set the pipeline to every matching buyer. Give the exclusive buyer its territory and put it alone in the first tier. Give the shared buyers their territories and put them in the second tier. A lead from the exclusive territory is delivered to the first tier, and the pipeline stops there because the lead has been placed. A lead from anywhere else finds nothing in the first tier and is delivered to every matching buyer in the second, each at their own price.
In both layouts the tier answers the question buyers actually ask: who is asked first, and what happens when they are full. Caps and operating hours are checked at each step, so an exclusive buyer at their daily cap does not block the lead; it moves on, and the trace says why.
Duplicates across pipelines
The exclusive buyer's real fear is not another buyer on the same pipeline. It is the same lead arriving on your solar pipeline from one vendor and on your roofing pipeline from another, and being sold twice. Territories do not prevent that; only duplicate detection does.
Set a duplicate window that spans your pipelines, keyed on email or phone, and decide what a duplicate does: keep it out of distribution, or send it anyway and flag it. For an exclusive territory the answer is keep it out, because the second sale is the one that costs you the buyer. For a shared pool you may prefer to send it and flag it, since the buyer already expects competition.
Say the window out loud in the buyer agreement. "Exclusive for 30 days across all our sources" is a promise you can keep with a rule; "exclusive" alone is a promise the buyer will interpret as forever and everywhere.
Set it up (screenshots)
Take the first layout, exclusive buyers with a shared pool underneath, on a pipeline that already receives leads with a zip field.
- Set the mode. Open the pipeline's distribution settings and choose one buyer per lead. This is the mode for the whole pipeline.
- Give each exclusive buyer its territory and price. Add a condition under When, zip is one of the pasted list or zip starts with the prefix, a daily cap if they want one, and their price per lead.
- Put them in the first tier. Every buyer in the same tier is a peer; the territory decides which one matches.
- Add the shared pool below. Create the shared buyers with no territory, or the wide one, at their lower price, and put them in a second tier. If two shared buyers should split the leftovers, set their weights.
- Set the price per buyer. Each buyer's price lives on the buyer, with optional rules for a higher price on a better lead.
- Turn on duplicate detection across pipelines, keyed on email or phone, with the window you promised the exclusive buyers.
- Send a test lead from an exclusive territory, one from outside it, and one duplicate, and read the routing decision on each.
📸 SCREENSHOT: territory-tiers-backfill.jpg (already in /public/docs-assets, upload as an image block here): the pipeline set to one buyer per lead, a Primary tier holding three territory buyers with prices and daily caps, and a Backfill tier below with one no-conditions buyer.
📸 SCREENSHOT: price-rules.jpg (already in /public/docs-assets, upload as an image block here): a buyer's pricing panel with a base price per lead and an ordered price rule that pays more when the quality grade is A.
The mechanics are in How distribution works and Lead pricing in the docs, and the territory rules themselves in Route leads by zip code, state or city.
When to switch a territory from shared to exclusive
A shared buyer who closes well will eventually ask to take the territory exclusively. Say yes when three things are true: the territory's volume is steady enough that one buyer can absorb it under a cap, the exclusive price covers what the two or three shared slots were bringing in, and the other shared buyers in that territory have somewhere else to go, another territory or the backfill pool. Say not yet when the volume swings, because an exclusive buyer at cap on a busy day means leads falling through to the pool anyway, and the buyer will notice.
The switch itself is small when the pipeline is built as above: move the buyer to the first tier, give them the territory condition and the exclusive price, and remove that territory from the shared buyers' conditions. No new pipeline, no new webhook for the lead source, and the trace on the next lead confirms the change took.
Medicare is the vertical where this comes up most, because agencies buy counties and a county is a list of zips that changes hands between enrollment periods. Medicare lead distribution shows the exclusive-or-shared pattern with the daily caps that go with it.
Frequently asked questions
Can one pipeline have both exclusive and shared buyers?
How much more should an exclusive lead cost than a shared one?
What stops an exclusive lead from being sold on another pipeline?
What happens when the exclusive buyer is at their daily cap?
How do I move a territory from shared to exclusive without a new pipeline?
Continue reading
How to split leads between agents by territory (zip, state, city)
Give each agent a territory as a condition on the zip, state or city field, choose exclusive or shared, and add a backfill for the zips nobody owns.
Zip code routing vs state routing: which one your leads need
Route by state when the constraint is a license or an appointment, by zip when it is a service area or a territory, and stack both when it is both.
What is exclusive vs shared lead distribution?
Exclusive vs shared lead sales: pricing impact, buyer satisfaction tradeoffs, and how to choose per pipeline.
How do I distribute leads to multiple buyers based on zip code?
Distribute leads by zip code to the right buyer automatically. Pasted zip lists, zip prefixes, state gates and overflow logic explained.