Skip to content
Food processing group, 2 to 9 sites, 1,480 on roll

From two plants to nine with one extra HR hire

Growth breaks HR before it breaks operations. What changes when bringing a new site live is a configuration task with someone accountable for it, instead of a hiring decision.

Modelled scenario. This is not a named customer story. Every figure below is derived from the inputs in the box on this page, so you can redo the sums with your own numbers.

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, annual billing

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

  1. 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.

  2. 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.

  3. 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.

  4. Seasonal intake as a repeatable batch

    Contract workers are enrolled against a contractor and tracked separately from permanent staff. At season end, attendance by contractor exports to Excel or PDF, and the HR team checks each contractor's bill against actual attendance from that export.

  5. Someone accountable who is not on your payroll

    This is the part that does the real work at nine sites. Our onboarding team sets up each new site from the group template with the HR team, and salary exports for Tally (XML) and SAP go to finance from the Pro plan. The group did not hire a systems function to absorb its own growth.

Before and after

Modelled over the 19 month period described in the inputs box.
MeasureBeforeAfterHow the figure is derived
Sites live294.5 times the sites
Employees on roll3401,4804.4 times the headcount
HR team size451.25 times the team, against 4.4 times the workload
Time to bring a new site live6 weeks4 daysTemplate clone plus device configuration, not a fresh setup
Group payroll calendars91One freeze date, late sites appear as exceptions
Employees per HR staff member85296340 over 4, then 1,480 over 5

The avoided cost, stated as what did not get hired

HR people added, in the model1Headcount grew 4.4 times, from 340 to 1,480. The HR team went from 4 to 5. This line comes straight from the inputs.
Roles not hired, at this group's own starting ratioAbout 12At 85 employees per HR staff member, 1,480 people would have needed about 17. The group runs on 5. This is a ceiling, not a forecast: it assumes the old way of working would have scaled in a straight line.
Annual value of that ceilingAbout ₹46 lakh a year12 roles at ₹32,000 a month fully loaded. It is a ceiling, not a forecast, so read it against the one person the HR team added in this model.
Internal systems function avoidedNot quantifiedThe group never built one. Assigning a rupee value to a team that was never hired would be guesswork, so we do not.

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, so treat the avoided cost as an upper bound. The defensible claim is narrower and stronger: headcount grew 4.4 times and the HR team grew by one person.

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 our onboarding team sets up each site from the group template and finance receives salary exports for Tally (XML) and SAP, 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 and tracked separately from permanent staff. Attendance by contractor exports to Excel or PDF, so each contractor's bill is checked against actual attendance rather than against a submitted claim.