Modelled scenario. This is not a named customer story. Every figure below is derived from the inputs in the box on this page. Change an input and the arithmetic changes with it.
The setting
- Industry
- Food processing and cold chain
- On roll
- Grew from 340 to 1,480 on roll over 19 months
- Sites
- 2 processing units grew to 9 sites across 4 states
- Shifts
- 3 shifts, seasonal peaks at 2 sites
- Devices
- Mixed estate, ESSL at older units, Matrix COSEC at new ones
- Team
- HR team of 4 grew to 5
- Plan
- Pro with dedicated account manager and custom integrations
Model inputs
Every number below comes from these six inputs.
- Sites at start
- 2
- Sites at month 19
- 9
- Employees at start
- 340
- Employees at month 19
- 1,480
- HR team at start
- 4
- HR team at month 19
- 5
- Old path to bring a new site live
- 6 weeks
- New path to bring a new site live
- 4 days
What bringing a new site live looked like before it was a process
The first two units ran on local habit. Each had its own clerk, its own shift rules written down by whoever set them up, and its own way of handling the seasonal contract intake. That worked because two units is a number one person can hold in their head.
The seventh unit is where it stops working. Not because the system fails, but because every new site arrives with its own local version of the rules, and nobody is accountable for making the nine versions agree. The group had a consolidated P and L and nine different answers to the question of how many people worked yesterday.
Five things that broke as sites four through nine came online
Every new site started from zero
A new unit meant a new clerk, a new spreadsheet, new local shift rules and a six week wait before the group could see its numbers.
Nine payroll calendars
Each site froze attendance on its own day, so the group payroll date was set by whichever site was slowest that month.
Seasonal intake had no template
Two sites doubled headcount for a season. Enrolling and de-enrolling several hundred contract workers was done by hand, twice a year, differently each time.
Mixed hardware, mixed methods
Older units ran ESSL, newer ones ran Matrix COSEC. Each brand had its own export routine, so the reconciliation work scaled linearly with sites.
Nobody owned the rollout
The group had no internal systems team. Every integration question became a project the HR manager was not equipped to run and did not have time to run.
What changed when site onboarding became a checklist
A site becomes a configuration, not a project
Shift rules, leave policy, overtime thresholds and approval chains are cloned from a group template and then adjusted for local law. The parts that must differ by state differ. The parts that only differed by habit stop differing.
One hardware layer over a mixed estate
ESSL terminals at the older units and Matrix COSEC at the newer ones both push into the same register with unit, department and verify mode attached. A ninth site on a tenth brand adds a connector, not a method.
One payroll calendar for nine sites
Attendance freezes on a group date. Sites that are late are visible as exceptions on that date rather than as a delay everyone absorbs.
Seasonal intake as a repeatable batch
Contract workers are enrolled against a contractor, with gate pass, category and end date set at enrolment. De-enrolment at season end is a batch action, and the billing reconciliation against actual attendance comes with it.
Someone accountable who is not on your payroll
This is the part that does the real work at nine sites. A dedicated account manager holds the configuration, and the custom integration into the group's finance stack is built and maintained by our team. The group did not hire a systems function to absorb its own growth.
Before and after
| Measure | Before | After | How the figure is derived |
|---|---|---|---|
| Sites live | 2 | 9 | 4.5 times the sites |
| Employees on roll | 340 | 1,480 | 4.4 times the headcount |
| HR team size | 4 | 5 | 1.25 times the team, against 4.4 times the workload |
| Time to bring a new site live | 6 weeks | 4 days | Template clone plus device configuration, not a fresh setup |
| Group payroll calendars | 9 | 1 | One freeze date, late sites appear as exceptions |
| Employees per HR staff member | 85 | 296 | 340 over 4, then 1,480 over 5 |
The avoided cost, stated as what did not get hired
Where this number stops. The 85 employees per HR staff member ratio is this group's own starting ratio, not a benchmark. Applying it forward assumes the old way of working would have scaled linearly, which is the most generous assumption available to us and should be flagged as such in any deal. The defensible claim is narrower and stronger: headcount grew 4.4 times and the HR team grew by one person.
We will outgrow this, and we cannot run a rollout right now.
Why they say it. Two fears wearing one sentence. The first is being stuck on a tool built for 200 people. The second, the real one, is that they have no internal team to own an implementation and they have been burned by a project that became their problem.
The question is not whether the software scales. It is who configures site nine, and the answer should not be you.
Show the multi site rollout in this order
- Show the group view first, nine sites rolled to one number, then drill into one line on one shift. Scale is easier to believe looking down than looking up.
- Clone a site template live. Set the state, adjust one leave rule, done. This is the four days, visibly.
- Show one register fed by both ESSL and Matrix COSEC terminals. Mixed estates are the norm and buyers expect this to be the catch.
- Name the account manager and say what they own. Then show a live custom integration into a finance system.
Who to say what to
- Group HR head
- Lead with one payroll calendar and one roster across sites. Their pain is nine answers to one question.
- CFO or promoter
- Lead with the headcount that did not get hired, then the group view that arrives without a monthly consolidation exercise.
- Site HR or plant manager
- Lead with what stays local. Fear of losing control of their own shift rules is what kills group rollouts from underneath.
Next step. Ask what their next site is and when it opens. Offer to configure that one site as the pilot, on the real opening date. A rollout with a deadline the buyer already owns is far easier to approve than an open ended evaluation.
Questions a group HR head raises here
How do managed services help HR scale across multiple locations?
They move the work that does not scale off the customer. In this scenario the account manager holds the site configuration and our team builds and maintains the finance integration, so bringing site nine live is a four day configuration task rather than a six week project the HR team has to run without a systems function.
Can one HR team manage payroll for plants in different states?
Yes, provided the system separates group rules from state rules. Professional Tax, minimum wages and holiday lists differ by state and stay local. Shift structures, approval chains and the payroll freeze date are set once at group level, which is why nine sites can run on one calendar.
What happens to seasonal contract workers?
They are enrolled against a contractor with a category and an end date set at enrolment, so de-enrolment at season end is a batch action. Contractor billing reconciles against actual attendance rather than against a submitted claim.