What's the hardest part of scaling from 10 technicians to 50?

We're at 14 techs now and planning to hit 40+ by Q2 next year. I've scaled teams before but never in field service.

  • Dispatcher bottleneck — feels like we're already there at 14
  • Quality consistency — harder to keep standards with more crews
  • Tooling — what breaks first in FieldPulse at this size?

What's the thing that actually hurt worst? Not theoretical — what actually happened.

  • You're already seeing it: dispatch. At 10, one good dispatcher can hold the whole puzzle in their head. At 30+, that model collapses.

    What actually hurt us: technician skill visibility. We hired fast, assumed "experienced" meant "can handle anything," and started getting callbacks on complex jobs we used to nail. FieldPulse tracks completion rates but not confidence levels per skill type.

    My fix: we built a tech skill matrix in a spreadsheet (I know, I know) and now tag jobs with required competencies. Dispatch cross-references before assignment. Manual but necessary until we find something better.

  • Skill matrix is smart. Did you tier techs (junior/mid/senior) or go granular by equipment type?

  • Granular by equipment — HVAC, electrical, plumbing, plus elevation (ground vs. rooftop vs. confined space). Took a weekend to build, now updates monthly.

    Pro tip: we also track customer preference — some clients request specific techs. That's its own column. Prevents the "why did you send someone new?" calls.

  • Communication latency.

    At 10, you walk the floor. At 50, you don't know who's pissed off until they quit. We lost 3 good techs in 6 months because issues sat in supervisors' inboxes.

    FieldPulse didn't fix this. We added a weekly 15-min pulse survey — one question, anonymous. "What's blocking you this week?" Caught problems we'd never hear otherwise.

  • The shift from owner-operator to manager-of-managers is the structural break that most underestimate.

    At 10, leadership touches every job. At 50, supervisors run crews you've barely met. The hardest part isn't operational — it's trust architecture. Can your supervisors actually supervise? Most promote your best technician and assume skill transfers. It doesn't.

    We front-loaded supervisor training for 6 months before scaling. Delayed growth but reduced callback rate during expansion by 40%.

  • This. We promoted too fast, realized our new leads couldn't read a P&L or hold a corrective conversation. Now we require 90 days shadowing before any promotion.

    What's your supervisor span of control? We're at 8:1, considering 12:1.

  • We run 6-8 per supervisor. 12:1 erodes quality control in my view — your service mix may vary.

  • From the field side: tool and van standardization.

    At 10, everyone knows where the pipe bender is. At 40, you've got 18 different van layouts and techs spending 20 minutes finding gear. We thought "they're professionals, they'll organize" — nope. Every van became its own system.

    Pro tip: we now have a van kit photo guide. Same layout, same labeling, same restock list. Took 3 months to convert the fleet but saved ~45 min/day per tech.

  • lol yeah my van was a disaster until they made us redo it. basically i thought i was being efficient with my "system" but turns out i was just the only one who could find anything. took like a week to retrain my brain but now i get why they did it — especially when you're covering for someone else's van and everything's actually where it should be

    also the restock list is clutch forgot to grab nitrogen once and now i just check the list every friday

  • Integration debt hits harder than expected.

    At 10, you patch things with Zapier and nobody notices. At 50, you've got 6 different systems (payroll, inventory, CRM, fleet tracking) and the API calls start timing out. We hit FieldPulse's rate limits twice during payroll sync before I built proper queuing.

    YMMV, but audit your automation before you scale. What's "reliable enough now" won't be.