Field notes › Running the business
Scaling labour hire operations without scaling office headcount
The growth pattern nobody questions
Labour hire has a default growth pattern. Win a contract, put on more crew, then hire another coordinator to handle the extra rostering and compliance work. Win the next contract, repeat. The field headcount and the office headcount climb together, and because everyone does it this way, it feels like a law of nature.
It is not a law of nature. It is a symptom of how the work is done. If every roster change, compliance check and status question has to pass through a human in the office, then more crew means more office. Change how the work is done and the pattern breaks.
Where the office hours actually go
Watch a rostering coordinator for a day and very little of their time is spent making decisions. Most of it goes on three kinds of work.
- Checking. Before a name goes on the roster, someone confirms the tickets are current, the induction is done, the worker is not already booked elsewhere and they are actually available. Manually, that is a lookup across several places, per booking, every time.
- Chasing. Certificates that are about to expire, workers who have not confirmed availability, paperwork for new starters. Chasing is endless because the list refills itself.
- Relaying. Passing information between people who cannot see the roster: telling workers their shifts, telling clients who is coming, telling everyone about changes.
None of that is judgement work. All of it scales linearly with crew size, which is exactly why the office grows in step with the field.
Hand the checking to the software
Checking is the easiest to remove because a machine does it better. Mustr runs the checks server-side on every single booking: competencies, inductions, availability, double-bookings. A booking that fails a check is blocked before it exists, so the coordinator cannot make the mistake even on a bad day at the end of a long week. The checking workload per booking drops to zero, whether you have forty crew or four hundred. How that works is covered at how it works.
The chasing shrinks too. Expiring certificates surface up to 60 days out with one-click reminder emails, so staying ahead of expiries is a short weekly glance rather than a standing project.
Let people serve themselves
Relaying disappears when the people asking can see for themselves. Workers use a portal on their own phones to check shifts, set availability, put their hand up for open shifts and upload certificates. Clients log in to see their own site's live roster and raise shift requests directly. Publishing an open shift and letting qualified workers register interest replaces a ring-around that used to swallow an afternoon.
Bulk matters at scale too. New contract with eighty inductees? Workers and clients come in by CSV import rather than being typed in one at a time, so the office effort to stand up a new contract stays flat no matter how many names are on the list.
The quiet cost that scales with headcount
One more thing grows with crew size if you let it: the software bill. Per-seat rostering apps charge you for every worker you add, which means your tooling cost rises exactly when your margins are stretched by growth. Mustr charges one flat monthly price per organisation, stepped by crew size, with everything included in every plan. Adding your next ten casuals costs nothing until you cross into the next bracket. The numbers are public at pricing.
Growth should be won on the strength of your crew, not throttled by your back office, so book a demo and see what your operation looks like when the office stops being the bottleneck.