• Replies 13 replies
  • Subscribers 2 subscribers
  • Views 29 views
  • Users 0 members are here
Options
Related

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

Sylvia Chen

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.

  • Love this thread — so much lived experience here! We want to make sure you're set up for success as you grow, Sylvia.

    A few of you mentioned dispatcher bottlenecks and skill matching. We've actually heard this pattern a lot lately, and there's a feature in early exploration that might help with tech-to-job matching based on competencies. Nothing committed yet, but we want to make sure we're hearing you right.

    Would any of you be open to a 20-minute call to share more about how you're handling this now? Your input shapes what we build. Feel free to DM me or drop a note here!

  • Scheduling fairness.

    At 10, everyone knows who gets the cushy jobs. At 40, you've got techs convinced dispatch plays favorites. We had a near-mutiny over weekend rotation before we published the assignment algorithm (seniority + last weekend worked + skill match).

    Transparency fixes a lot of drama you didn't know you were brewing...

  • Thanks all. Taking notes:

    • Skill matrix — building this week
    • Supervisor training — flagging for leadership
    • Van standardization — fleet meeting Thursday
    • Integration audit — devon, might DM you

    Ray's point on transparency especially hits. We're opaque on assignments and I can see the friction.

    Carla — will reach out on the competency matching. Would be useful to share our spreadsheet approach if you're exploring this.