The growth tax: how coordination costs scale in manufacturing
Every time a manufacturer doubles headcount, the hours lost to chasing status double too, and the paths an update can get lost on grow four times as fast. The math, and how to stop paying it.
Jose Acevedo · CRO and co-founder, Indax
· 4 min read
Summary. Hours spent chasing status grow in a straight line with headcount. The number of paths an update can travel grows with the square. At 1,000 people, the cost is about 200 full-time jobs. One live record, delivered where people already work, stops the tax from growing with the company.
The math
Start with a conservative assumption: each person spends about 8 hours a week chasing status. Where is that PO? Did the supplier confirm? What did we quote last time?
| Team size | Hours lost per week | Full-time jobs lost | Paths an update can travel |
|---|---|---|---|
| 125 | 1,000 | 25 | 7,750 |
| 250 | 2,000 | 50 | 31,125 |
| 500 | 4,000 | 100 | 124,750 |
| 1,000 | 8,000 | 200 | 499,500 |
- Hours grow in a straight line. Double the team and you double the hours lost. At 1,000 people, 200 people do nothing but look for answers.
- Paths grow much faster. Going from 500 to 1,000 people roughly quadruples the ways information can get lost. That is why large plants feel slower than small ones, even with better systems.
Why more systems do not fix it
The usual response is another system: a new ERP module, a new CRM, a new tracker. Each one holds a piece. Email, Teams, the ERP, MES, PLM and SharePoint each know something about the same order, and none knows everything, so people rebuild the full picture by hand for every question.
For a global manufacturer with a U.S. plant, add time zones and languages. Headquarters is 13 or 14 hours ahead, threads run in two languages, and a simple status question becomes a two-day relay.
What it costs in dollars
Take a 1,000-person manufacturer and count only the 400 people who coordinate orders: purchasing, planning, production control, quality, logistics, customer service and sales operations.
- Total coordination cost: 400 people × 26 hours a week × $62.50 loaded cost × 52 weeks = $33.8M a year.
- Recover 40%: about 10.4 hours per person per week, or roughly $13.5M a year, before counting expedites, lost RFQs or late-order penalties.
How to grow without paying it
- Measure your number. Survey the people who coordinate orders: how many hours a week go to finding answers versus acting on them?
- Build one record, not another system. One live view of every order, quote and project, on top of the systems you already run.
- Deliver answers where people work. If someone has to open a dashboard, they will not. Answers belong in email, Teams or the AI tool they already use.
- Flag changes before anyone asks. When a supplier moves a date, every affected plant should know the same day.
- Start with one plant and one use case. Prove the hours in 30 to 60 days, then expand.
The goal is that every answer stays one question away, at 125 people or at 1,000.
