Daily lead caps are a fundamental requirement of any agency selling leads to multiple buyers. Buyers have finite sales capacity. Sending a mortgage lender 80 leads on a day they can handle 20 wastes the leads, irritates the buyer, and generates disputes. The cap mechanism — a hard ceiling enforced at delivery time — prevents that.
The challenge is not defining the cap. It is enforcing it reliably under real-time load, applying overflow logic when a buyer hits their limit, and making the state visible to both sides without manual reconciliation.
What cap enforcement actually requires
Enforcing a cap correctly under concurrent load requires three things:
- Atomic counting: the check ("is this buyer under cap?") and the increment ("count this lead") must happen as a single operation. If two leads arrive simultaneously and both check the count before either increments it, both pass a cap that should have stopped the second one. This is a race condition that manual Sheets counters and most Zapier setups cannot prevent.
- Timezone awareness: "daily" means different things to a buyer in New York vs Los Angeles. A cap reset at midnight UTC is 8 PM Eastern, which causes counterintuitive delivery behavior. Cap windows should reset at the buyer's local midnight.
- Overflow routing: when a buyer hits their cap mid-day, incoming leads need somewhere to go. The overflow rule determines that — most commonly skip to the next eligible buyer, but sometimes queue for next-day delivery or pause the campaign.
Why manual cap tracking fails
The typical manual approach is a Google Sheet with a counter per buyer, updated by a Zapier step on each lead delivery. This fails in three scenarios that become increasingly likely as lead volume grows:
- Parallel leads: two leads arrive in the same second. Both Zap runs read the counter before either writes it back. The counter ends up one short, sending the buyer one extra lead.
- Zap failures: if the delivery step fails but the counter step already ran, the count increments without a lead delivered. Or the reverse — lead delivered, count not incremented. Either way, the cap state drifts from reality.
- No overflow logic: Zapier has no native condition that says "if this buyer is at cap, route to the next buyer instead." You'd need to chain multiple conditional paths manually, one per buyer, which becomes unmanageable past three buyers.
Agencies that outgrow manual setups typically choose between enterprise platforms like Boberdoo (which starts at $1,000+/mo on a custom quote) or mid-market tools. LeadMove sits in the middle — purpose-built cap enforcement with atomic writes and timezone-aware resets starting at $149/month — without requiring an enterprise contract.
Setting up caps with overflow in a dedicated router
- Define cap values per buyer: set daily, weekly, and monthly limits. Most agencies set daily caps matching the buyer's stated capacity and a monthly ceiling as a safety net.
- Set the reset timezone: choose the buyer's local timezone so caps reset at their midnight, not yours.
- Configure overflow: for each buyer, define what happens when they're at cap. Common options: route to next eligible buyer in priority order, route to a designated fallback buyer, or hold in queue for next reset.
- Test with burst delivery: send 5-10 test leads simultaneously against a buyer set to cap at 3. Verify that exactly 3 reach the capped buyer and the rest route to overflow correctly. This tests atomic enforcement.
Comparing tools by cap granularity and overflow support
| Tool | Daily cap | Weekly cap | Monthly cap | Overflow routing | Starting price |
|---|---|---|---|---|---|
| Zapier + Sheets | Manual only | Manual only | Manual only | None (custom logic required) | Free–$69/mo |
| LeadProsper | Yes | Yes | Yes | Yes | $499+/mo |
| LeadMove | Yes | Yes | Yes | Yes (next-eligible or queue) | $149/mo |
| LeadByte | Yes | Yes | Yes | Yes | £400+/mo custom quote |
| Boberdoo | Yes | Yes | Yes | Yes | $1,000+/mo custom quote |
Giving buyers visibility into their own cap state
Buyers routinely ask two questions: "Did I get my full allocation today?" and "Am I going to run out this month?" Without a buyer portal, both questions generate support emails. With one, buyers log in and see their delivery count, their cap limit, and how many leads remain in the current window. This is not just a convenience — it is a trust mechanism that reduces disputes about whether leads were over-delivered or under-delivered.
Platforms like Boberdoo and LeadMove include buyer portals with real-time cap status. The difference is access cost: Boberdoo's enterprise pricing puts that feature out of reach for smaller agencies, while LeadMove makes it available on the $149 Starter plan.
Daily caps are a solved problem in dedicated lead routing software. The complexity is not in the concept but in the enforcement details — atomicity, timezone handling, and overflow logic — which manual setups consistently get wrong at any meaningful lead volume.