Every time I talk to an Indiana manufacturer, the same hire comes up. The analyst.
BI analyst. Business analyst. Supply chain analyst. FP&A analyst. Sales analyst. Different titles, but the job underneath reads the same: pull data from the ERP, clean it up in Excel, build the reports leadership needs, and fix the CRM while you're at it.
I understand the instinct. One smart hire feels like the fastest way to get reliable numbers. But in most of the plants we work with, that hire ends up solving the wrong problem.
Two Systems, One Customer, No Agreement
The ERP knows what was built, what shipped and what's past due. The CRM knows the account, the open quote and the next call. Both describe the same customer, but nobody ever made them agree. We covered how that gap plays out for sales in Your ERP Isn't Wrong. It's Just Not Talking to Sales.
When the systems disagree, the real answer ends up somewhere else: a planner's side spreadsheet, an overnight export someone set up years ago, or simply in someone's head. That is the gap the analyst gets hired to fill.
What the Analyst Actually Does All Week
Six months in, the picture usually looks like this. A talented person spends most of the week matching two versions of the same order by hand. The ERP says order #4417 ships October 14. The CRM says October 7. They re-run the overnight export, rebuild monthly_numbers_FINAL_v3.xlsx, and field a 7:42 AM message from leadership asking which ship date is right before the forecast call.
None of that is analysis. It's reconciliation. The hire becomes the integration.
The Risk Nobody Puts in the Job Description
When one person is the integration, the integration goes on vacation when they do. It leaves when they leave. The logic for which number wins lives in their workbooks and their memory, not in a system anyone else can maintain. We see the same pattern in finance teams, where month-end close breaks down at the handoffs rather than the tasks themselves.
And the cost compounds. Every report built on hand-matched data inherits its errors, and every decision made from that report inherits them too.
Three Questions Before You Post the Role
Before you open the requisition, or while you're interviewing for it, ask:
- Which decisions are we making on numbers someone had to rebuild by hand? If the answer includes the forecast, pricing or production scheduling, the problem is bigger than headcount.
- When the ERP, CRM and spreadsheets disagree, who settles it, and how long does it take? If the answer is one person and a few days, that person is your integration.
- Do we want this hire keeping the systems in sync, or finding answers in them? Those are two different jobs, and only one of them needs a human.
Fix the Plumbing First
Connect the systems before you staff around them. Order status, ship dates and past-due balances should flow from the ERP into the CRM automatically, and quote and account data should flow back. Give that sync one owner who treats it as infrastructure to maintain, not a project that shipped once during implementation.
Then hire the analyst. They'll spend their week finding margin leaks, spotting late-order patterns and telling leadership something new, which is the job you were hiring for in the first place.
Our Take
We don't tell manufacturers to stop hiring analysts. We tell them to stop hiring analysts to be the integration. When we start an engagement, the first thing we map is how far apart the ERP, the CRM and the spreadsheets really are, and who is holding them together by hand. Close that gap, and the next analyst you hire gets to do actual analysis.