How Many Leads Can One OSC Really Handle? | Jome

How many leads can one OSC actually handle?

The short answer: 200 to 250 inbound leads a month, if the OSC is good, your CRM is clean, and nobody expects them to close the contracts themselves.

The longer answer is where it gets interesting.

Because 200 to 250 isn't a ceiling. It's a ceiling given the current job description of an OSC at most builders — which is roughly: respond in under 5 minutes, qualify, book, hand off to the onsite team, follow up, nurture, coach, keep the CRM clean, report to the VP Sales on Friday.

If you change the job, the math changes. If you give the OSC the work nobody else has time to do, the math changes harder. This post walks through both.

Where the 200 to 250 number comes from

The New Home Star guide puts the range at "200 to 250 leads per month per OSC." Bokka Group's OSC research supports the same bucket. Zillow's new construction resource center, in its "Why You Need an OSC" brief, implies a similar load.

Underneath those numbers is a simple time calculation.

A well-run OSC does, on average: - 8 to 12 outbound voice attempts per hour on new inquiries - 20 to 30 SMS / email touches per hour across ongoing cadences - 2 to 4 live qualification conversations per hour - Updates the CRM after every interaction - Spends 30 to 60 minutes a day on meetings, reporting, and coaching

If you back that into a 40-hour week at 80% capacity (you do want them to eat lunch), you get roughly 60 to 80 real live buyer conversations per week. That's where the 200 to 250 monthly lead-volume figure lives — it's conversations divided by the fact that most leads need 3 to 7 touches before they engage.

Why most builders quietly miss the target

Here's what the benchmark doesn't say.

The 200 to 250 number assumes the OSC is only handling net-new inquiries. In the real world, most OSCs we talk to are also handling:

• A tail of 3- to 6-month-old leads the team hasn't had the heart to stop calling
• Realtor outreach and co-op program engagement
• Post-appointment follow-up before the handoff to onsite
• No-show rescheduling
• Some portion of the aged-lead bucket — the ones the VP Sales asks about on the Monday call

Add up those secondary buckets and you've carved out 10 to 20 hours a week from the OSC's available capacity for net-new work. The practical ceiling falls to 160 to 200 leads a month per OSC. That's before anyone takes PTO.

Which means: a builder doing 400 leads a month probably needs 2 OSCs, not 1. A builder doing 1,000 needs 4, not 3.

Most builders we talk to are understaffed by about one OSC. It's not a dramatic gap. But it's enough to quietly lose every month.

The math gets worse when you look at aged leads

The 200-250 number assumes aged leads are mostly out of scope. That's because they mostly are, in practice. An OSC who is already 10% over their practical live-lead capacity does not have hours to call leads from a year ago.

So the aged-lead bucket grows.

Consider a builder doing 250 inbound leads a month. Without any intervention, let's say 40 of those leads convert within 90 days. The other 210 go into the aged pool. Over 12 months, the aged pool gains about 2,500 leads. Over 3 years, 7,500.

Now the math: 7,500 aged leads, 0 OSC hours available. The pool can only grow.

Some percentage of that pool is dead — they bought elsewhere, they moved out of market, they aren't buying a house. But a meaningful share — we've seen 15 to 25% across the pilots we've run — is still in the market, still interested, still reachable. They just never got a call back because nobody had the time.

That's not a reach. That's every division we've worked with.

What happens when you free up OSC hours

Here's the quiet consequence of capacity constraints: the OSC's quality drops on everything they do.

A stretched OSC: - Shaves the qualification call from 12 minutes to 6, missing nuance - Sends shorter cadence emails, hitting lower reply rates - Does less prep before the onsite handoff, so the first impression is weaker - Logs less structured CRM notes, so the next touch has less context

When you pull aged-lead outreach out of the OSC's job — either by hiring another OSC or by running AI outreach alongside them — the live-inbound work gets better, not just bigger. In the Arizona pilot we ran, appointment-to-contract rates held at 13% on the AI-generated tours. That's not because the AI was especially good. It's because the OSCs had the hours to prep the onsite team for those tours.

The 200-250 number is a capacity benchmark. It should be read as: if you want your OSC to be great at the 200-250 leads they do touch, pull the other leads off their plate.

Three ways builders get the math right

1. Hire another OSC at 150% of current load

Classic approach. Works when your volume justifies it. Downsides: $65-95K fully loaded, 3-6 months to ramp, doesn't solve the aged-lead backlog.

When this fits: the live-inbound backlog is so bad that response times have crept past 20 minutes and you're losing at the top of funnel.

2. Automate the easy parts

Template responses, auto-routing, speed-to-lead chatbots, scheduling links. This moves the OSC out of the 30-40% of their work that's mechanical.

When this fits: the OSC's calendar is buried under friction (scheduling back-and-forth, duplicate data entry, manual routing). A clean speed-to-lead stack will buy back 5-10 hours a week.

Downside: doesn't add capacity, just reallocates it. Doesn't touch the aged-lead bucket.

3. Run AI outreach on the buckets the OSC can't reach

AI that calls, texts, and emails the aged-lead bucket — and handles the inbound overflow after hours — is a different kind of capacity. It doesn't compete with the OSC; it takes a workstream the OSC was never going to touch.

When this fits: your CRM has 5,000+ aged leads and your OSCs have been at or over capacity for more than a quarter. You're not missing inbound leads; you're missing the follow-up long tail.

In our pilots, this moves a team from 200-250 live-lead capacity to effectively 250 live + 1,500-3,000 aged leads worked per OSC per 60-day cycle. Not because the OSC does more — because the work they weren't doing finally gets done.

The practical takeaway

If you're a VP Sales running this math against your own org, the question isn't "how many leads can my OSC handle." It's "what's the ratio of leads in my CRM to leads we're actually having conversations with?"

If the ratio is 3-to-1 or better, your OSCs are keeping pace. Nice.

If it's 5-to-1 or worse, you have a capacity gap. And the fastest way to close it is not to ask your OSC to work harder — it's to move the long tail off their plate.

FAQs

Is 200-250 the right number for every builder?No. Custom builders doing 20-40 homes a year have different lead volumes and sell cycles; one OSC can handle 100-150 with plenty of buffer. National builder divisions doing 400+ homes a year usually need 2-3 OSCs just to keep up with live inbound.

How many leads per OSC does a national builder staff for?The nationals we've looked at typically staff at 175-225 live leads per OSC, with one layer of overflow (a "shared OSC pool" or similar) for peaks.

Does speed-to-lead change the number?Yes. An OSC on a 1-minute speed-to-lead SLA spends a lot of calories staying alert; their practical monthly ceiling is lower (150-200) than an OSC on a 15-minute SLA (220-260). Faster is better for conversion but costlier per lead.

What about after-hours coverage?Most builders we talk to rely on chatbots for after-hours. Chatbots handle ~15% of the post-7pm inquiries well and miss the rest. AI voice outreach (calling back at the next peak hour) catches a materially higher share.

How does 200-250 translate to a budget?A fully loaded OSC runs $65K-$95K/year. At 200-250 leads a month, that's about $22-40 per lead handled, before any tooling. Whether that's cheap or expensive depends entirely on your average contract value.