How a Chicago Plumbing Company Scaled to 3 Locations Using BPO

· GSD 500 BPO · 7 min read · Outsourcing

How a Chicago Plumbing Company Scaled to 3 Locations Using BPO

Windy City [Plumbing](/blog/plumbing-company-growth-bpo-strategies) had a good problem: too much demand and not enough capacity. Their single location on the northwest side of Chicago was booked solid 3 weeks out. Customers were calling, getting told "our next opening is in 22 days," and hanging up to call a competitor. The owner, Tomasz Kowalski, knew he needed to expand — but the operational complexity of running multiple locations with separate front desks terrified him.

This is the story of how a centralized BPO team allowed Windy City Plumbing to open 2 additional locations in Naperville and Schaumburg without hiring a single receptionist for any of them.

The Pre-Expansion Numbers

Windy City Plumbing before the BPO partnership:

  • 1 location: Northwest Chicago (Irving Park area)
  • Annual revenue: $2.1M
  • Service calls per month: 340
  • Technicians: 8
  • Office staff: 2 (receptionist + dispatcher)
  • Front desk cost: $92,000/year (2 employees, fully loaded)
  • Answer rate: 74%
  • Average wait for service: 18-22 business days
  • Customer loss rate due to wait time: ~35% of callers
  • The math was painful. Tomasz estimated that 35% of callers were hanging up because of the wait time. At an average ticket of $780, that represented roughly $7,000/week in lost revenue — or $364,000 per year walking out the door.

    Why BPO Before Expansion

    Most companies expand first and fix operations later. Tomasz did the opposite, and it was the smartest decision he made.

    His logic: "If I open two new locations with the same broken phone system, I'll have three locations losing 35% of calls instead of one."

    The plan: 1. Deploy a BPO team to handle all phone operations for the existing Chicago location 2. Prove the model works for 90 days 3. Use the same BPO team as the centralized call center for all 3 locations 4. Never hire another receptionist

    The Centralized BPO Model

    We designed a system where 5 BPO agents in [Medellin](/blog/building-remote-sales-team-colombia-guide) would handle all inbound and outbound communications for every Windy City Plumbing location:

    Call Routing:

  • Single phone number for each location, all routing to the same BPO team
  • Agents identify which location the customer is calling and greet accordingly
  • Geo-based scheduling: customers automatically matched to the nearest location and crew
  • Emergency calls (burst pipes, gas leaks) escalated to the on-call technician at the nearest location
  • CRM Integration:

  • All 3 locations on one ServiceTitan instance
  • Shared customer database — a customer who moves from Chicago to Naperville keeps their history
  • Technician availability visible across all locations
  • Cross-booking capability: if Naperville is booked, the agent can offer the Chicago crew if they're available in that zone
  • Language Handling:

  • Chicago's northwest side has a significant Polish-speaking community
  • We trained 2 agents on basic Polish greetings and common plumbing terms
  • All agents fluent in English and Spanish (critical for both Chicago and the suburbs)
  • The Expansion Timeline

    Months 1-3: Chicago Location + BPO

  • Deployed 3 agents for the existing Chicago location
  • Answer rate: 74% → 97%
  • Average wait for service: 22 days → 14 days (same technicians, just better scheduling)
  • Appointments per month: 340 → 428 (26% increase from previously missed calls)
  • Tomasz's office staff reassigned: receptionist became fleet manager, dispatcher stayed
  • Month 4: Naperville Opens

  • Added 1 BPO agent (total: 4)
  • Naperville location staffed with 4 technicians (2 transferred from Chicago, 2 new hires)
  • BPO team handled all Naperville calls from Day 1 — no local office staff needed
  • Grand opening week: 67 appointments booked, no phone issues
  • Month 7: Schaumburg Opens

  • Added 1 BPO agent (total: 5)
  • Schaumburg staffed with 3 technicians
  • Same seamless call handling from Medellin
  • By end of Month 7: all 3 locations running at 90%+ utilization
  • The Numbers: Single Location vs. Three Locations

    Revenue Growth:

    | Period | Locations | Monthly Revenue | Technicians | BPO Agents | |--------|-----------|----------------|-------------|------------| | Before BPO | 1 | $175,000 | 8 | 0 | | Month 3 (BPO, pre-expansion) | 1 | $221,000 | 8 | 3 | | Month 7 (all 3 open) | 3 | $412,000 | 15 | 5 | | Month 12 (optimized) | 3 | $538,000 | 18 | 5 |

    Annual revenue went from $2.1M to $6.46M in 12 months.

    Cost Comparison: BPO vs. In-House for 3 Locations

    If Tomasz had hired local receptionists for each location:

  • 2 staff per location × 3 locations = 6 employees
  • Average cost per employee (Chicago market): $52,000/year fully loaded
  • Total: $312,000/year
  • Actual BPO cost:

  • 5 agents × $1,600/month = $8,000/month
  • Annual: $96,000
  • Savings: $216,000 per year — and the BPO team outperformed what 6 local hires would have delivered.

    The Operational Advantages Nobody Talks About

    1. One Training Program, Three Locations When Tomasz added a new service (tankless water heater installation), he updated the script once. All 5 agents were trained in one session. With 6 local receptionists across 3 offices, that would have required 3 separate training sessions with inconsistent quality.

    2. Zero Snow Day Disruptions Chicago winters are brutal. When a blizzard hits, local office staff can't get to work. Tomasz's office was unstaffed for 4 days during the January 2026 polar vortex. His BPO team in Medellin (where it's 75°F year-round) didn't miss a single call. Those 4 days generated $34,000 in emergency plumbing calls (frozen pipes) that competitors' empty offices couldn't answer.

    3. Cross-Location Load Balancing When Naperville had a 2-week backup, the BPO team automatically offered customers the option to book with the Chicago crew traveling to their area. This cross-booking capability kept utilization above 85% at every location and prevented the customer loss that comes with long wait times.

    4. Unified Customer Experience Every caller gets the same greeting, the same qualification process, the same professionalism — regardless of which location they're calling. This consistency is nearly impossible to maintain with different receptionists at different offices.

    5. After-Hours Emergency Capture Plumbing emergencies don't happen 9-to-5. The BPO team covers 7 AM to 10 PM, capturing after-hours calls that generate premium-rate emergency service calls averaging $1,200 (vs. $780 for scheduled work).

    Tomasz's Takeaway

    "Everyone told me I needed to hire office managers for each location. That would have been $312K in payroll for people sitting at desks answering phones. Instead, I spent $96K on a team that answers faster, books more accurately, and never calls in sick because of a snowstorm. The $216K I saved went into a fourth service truck and more marketing. That's how you grow."

    The Formula for Multi-Location Expansion

    If you're a home service company considering expansion, here's the model:

    1. Fix the phone before you expand. A broken phone system at one location becomes a broken phone system at three locations. Get BPO right first. 2. Centralize call handling from Day 1. Don't hire local receptionists — you'll just have to fire them later when you realize the BPO model is superior. 3. Use one CRM across all locations. Cross-booking and shared customer data are only possible with unified systems. 4. Staff new locations with technicians only. The BPO team handles everything else. This dramatically reduces the cost of opening a new location. 5. Track the data. After 12 months, Tomasz knew exactly which zip codes, services, and time slots were most profitable at each location.

    From 1 location doing $2.1M to 3 locations doing $6.46M — with lower per-location overhead than a single-location competitor. That's the power of centralized BPO.

    Planning an expansion? Let's build the phone infrastructure first: calendly.com/manuel-gsd500bpo

    Related Reading

  • [BDR vs SDR: What's the Difference and Which Do You Need?](/blog/bdr-vs-sdr-difference-which-do-you-need)
  • [How to Build a Remote Sales Team in 2025](/blog/how-to-build-remote-sales-team-2025)
  • [Nearshore vs Offshore Outsourcing: Why Colombia Wins](/blog/nearshore-vs-offshore-outsourcing-why-colombia-wins)