The OSC Capacity Playbook (Template) | Jome
Cover image prompt
Photorealistic, wide aspect ratio. A printed spreadsheet on a wooden conference table, pen and coffee mug nearby, a calculator and a half-eaten granola bar in frame. The spreadsheet has rows labeled in legible font: “Communities,” “Leads / month,” “OSCs,” “Hours / week” — with numbers handwritten in the margin. Soft top-down warm light. No people, no logos. Documentary, slightly cluttered, real. Color palette warm beige and muted blue.
The OSC Capacity Playbook: A Template for Right-Sizing Your Online Sales Counselor Team
Every January, every spring, and every fall, a VP of sales at a home builder is in a room defending an OSC headcount number to a CFO. The math is always rough. The number always lands somewhere between “what we had last year” and “what marketing’s lead forecast suggests we need.”
This post is the template that goes between those two numbers. It’s not a magic ratio — there isn’t one — but it’s the working model that lets you answer “do I have enough OSCs” with arithmetic instead of vibes.
You can copy the structure below into a spreadsheet in twenty minutes. The output is a defensible per-community staffing number, plus the line items where capacity will break first.
Step 1: Pin down the unit of analysis
OSC capacity is almost always sized at the community level, not the division level. Two communities with the same total monthly leads can need very different staffing if one is open for sales and the other is in close-out.
For each community in scope, write down five inputs:
- Lead volume — total monthly inquiries to that community (from every source: website, Zillow, Realtor.com, walk-ins captured into the CRM, builder marketplaces).
- Lifecycle stage — pre-sell, open for sales, close-out. Pre-sell is highest follow-up intensity per lead because nobody is buying yet. Close-out is lowest because the inventory is gone or going.
- Average inquiry-to-tour conversion — the OSC’s local number, not the corporate average. If you don’t have it per community, use the rolling 90-day average.
- Average tour-to-contract conversion — same caveat.
- Operating hours — when is the model actually staffed, and when is the OSC reachable. Most builders have a gap between “model open” and “OSC available” that they haven’t named.
Five numbers per community. If you can’t get them, that’s the first finding — your CRM data isn’t telling you what you need to staff the role correctly.
Step 2: Build the workload model
For each community, the monthly OSC workload is the sum of four buckets:
Bucket A — new lead follow-up. This is the touches every fresh inquiry should get in the first 14 days. For a healthy cadence, plan on 5 to 7 attempted contacts per new lead in the first two weeks. Multiply: monthly leads × 6 touches × 5 minutes per touch.
Bucket B — aged lead follow-up. Every lead older than 14 days that isn’t disqualified should be touched on a cadence of roughly once per month. The volume here is multiplicative: a community that’s been open 18 months has 18 months of CRM accumulation. Multiply: aged lead count × 1 touch × 4 minutes per touch.
Bucket C — appointment delivery. Every booked tour, design center session, or walkthrough requires prep, the appointment itself, and follow-through. Plan on 90 minutes per appointment, including prep and post-tour notes.
Bucket D — internal coordination. Sales meetings, lender check-ins, marketing alignment, CRM hygiene. This is roughly 8 to 10 hours per OSC per week — non-negotiable, and the first thing that gets cut when capacity breaks.
Sum the four buckets in minutes. Divide by 60. Compare to the OSC’s working hours per month — about 160 hours for a full-time employee, minus PTO and training, so call it 145 working hours net.
If the workload number exceeds the working hours number, you’re already underwater on that community. Move on to step 3.
Step 3: Test the ratios
Three ratios fail before the OSC does. If any of them is breaking, that’s where the team is silently giving up:
Speed-to-lead. What percentage of new inquiries get their first contact attempt within 5 minutes during business hours? Within 1 hour after hours? If you don’t track this per community, instrument it before you do anything else. The teams that hit it under 5 minutes consistently convert leads at materially higher rates.
Aged-lead touch ratio. What percentage of aged leads (older than 30 days) received a contact attempt in the last 30 days? In most builder CRMs the honest answer is single digits. The math we covered in 7 Aged-Lead Mistakes Builder Sales Teams Make shows why: the OSC literally doesn’t have the hours.
After-hours coverage. What percentage of inbound inquiries arrive between 6pm and 10am or on weekends? The category-level number across most builders is 40-55%. What percentage of those get a same-day response? In most teams, well under 20%.
If speed-to-lead is over 5 minutes, you need more inbound capacity. If aged-lead touch ratio is under 30%, you need more outbound capacity. If after-hours coverage is broken, you need either an extended-hours human team or an automation layer.
Step 4: Decide where capacity comes from
You have four practical options when the model says you’re short:
- Hire more OSCs. Works if the volume is sustained, the lead quality justifies the loaded cost (call it $90K-$130K all-in per OSC depending on market), and you can recruit qualified candidates in the geography. Slow to ramp.
- Hire an inside sales team. Centralized BDRs taking inbound and qualifying for community OSCs. Works for larger builders with the volume to justify a dedicated team. Common ratio is one BDR per 3-5 communities.
- Outsource to a call center. Lower per-hour cost but typically lower conversion. Works well for inbound after-hours capture; less well for outbound follow-up where buyers want continuity.
- Automate the follow-up grind layer. An AI BDR sits on top of the CRM and handles the high-volume, low-intensity work — the third call, the fifth text, the aged-lead reactivation — without taking the close out of the OSC’s hands. This is the system Jome built, and the wedge is exactly where the model usually breaks: aged leads and after-hours. (We compare the four options in detail in AI Voice Agent vs Inside Sales BDR vs Outsourced Call Center.)
The right answer is usually a mix. Most builders we work with run option 1 (OSCs for the close, sized to appointment volume) plus option 4 (Jome for the follow-up grind, sized to lead volume).
Step 5: Sanity-check the output
Take the per-community staffing number the model produces, sum across the division, and compare to current headcount. Three sanity checks:
- Per-community lead volume. Is any single community sized to more than 80 monthly leads per OSC? That’s the threshold above which speed-to-lead breaks even with a fully staffed model.
- Lifecycle mix. Are pre-sell communities getting at least 25% more OSC time per lead than open-for-sales communities? They should be.
- Coverage hours. Does the staffing model cover at least 11am-7pm on weekdays and Saturday afternoons, when buyer activity is highest? If not, name where the gap is and plan for it explicitly.
If the model says you need significantly more OSC time than current headcount provides, the conversation with the CFO is not “hire more OSCs.” It’s “here is the work we are not doing, here is the pipeline we are not capturing, and here are the four options for closing the gap.”
That conversation gets approved. The vibes conversation does not.
What the playbook is really for
The point of running this template isn’t to nail a perfect headcount number. It’s to make the trade-offs visible. Once you can see which communities are underwater on which bucket of work, the staffing conversation stops being a budget fight and starts being a system design conversation.
Most builder sales leaders we talk to have all the inputs to run this playbook sitting in their CRM right now. The blockers are time and tolerance for the answer. The teams that pull this together and update it quarterly know exactly when to add a human, when to outsource, and when to put a system underneath the OSC. (For why this question is getting more urgent across the industry, see The 2026 Adoption Gap.)
FAQ
How often should I rerun this template? Quarterly, with a check-in on the ratios monthly. Lead volumes and community lifecycle stages change fast enough that an annual review is too slow.
Should the OSC be measured by activity or by appointments? Appointments. Activity metrics reward looking busy. Appointment-and-contract metrics reward the outcome the business actually pays for.
What’s the right OSC-to-community ratio? There isn’t a universal one. A pre-sell community with 80 monthly leads can saturate a full-time OSC. A close-out community with 20 monthly leads can share one across three locations. The ratio falls out of the workload model; don’t try to set it as a corporate standard.
Does this template work for spec-heavy builders vs build-to-order? Yes, but adjust bucket C (appointment delivery time). Spec sales have shorter appointment cycles. Build-to-order has longer ones, with more design center time per appointment.
Want help running this for your division?
If you want a working version of this playbook applied to your own communities — using your CRM data — book a Jome walkthrough. We’ll run the capacity math with you and show you where the gaps are before you decide whether the answer is more OSCs, a system underneath them, or both.
Give your OSC their hours back — see how Jome carries the follow-up load at ai.jome.com.