For a manufacturing CFO, the ERP is a strange kind of asset. The business can’t run without it, yet it is often the thing holding the business back. It is slow to change, hard to report from, and expensive to customize. When the frustration builds up, someone eventually says the words every CFO dreads: “Maybe we should replace it.”
A full ERP replacement is one of the riskiest projects a manufacturer can take on. It is expensive, it takes a long time, and it puts the whole operation at risk while it happens. The good news is that it is rarely the only option. Many manufacturers are getting more from the ERP they already have by building focused tools around it, one improvement at a time.
Why a full replacement is so risky
A new ERP touches everything: orders, inventory, purchasing, production, shipping, and accounting. That means a long project, a large budget, months of data migration, and a cutover where everyone has to learn a new system at once. If anything goes wrong, it goes wrong everywhere.
There is a quieter problem too. A new ERP doesn’t automatically fix the issues that made you unhappy with the old one. If the real problem was spreadsheets, manual handoffs, and disconnected shop floor data, a new ERP can bring all of those problems along with it.
The alternative: build around the ERP
Instead of replacing the whole system, you leave the ERP in place as the system of record and add small, focused tools that connect to it. Developers sometimes call this a microservices approach. In plain terms, each tool does one job well and shares data with the ERP.
Common examples in manufacturing include:
- Job costing tools that capture labor, material, and machine time as work happens
- Shop floor data capture that replaces paper travelers and end-of-shift data entry
- Quality tracking for inspections, nonconformances, and corrective actions
- Scheduling tools that plan around real capacity instead of a shared spreadsheet
- Dashboards that pull ERP and floor data into one live view for leadership
Because each tool is separate, you can build, test, and launch one without touching the rest. The business keeps running the whole time.
How CFOs are funding it
The biggest advantage of this approach is financial. Instead of one large bet, you make a series of small ones, and each one has to earn its keep.
- Start with the biggest leak. Look for the place where money or hours are clearly being lost, such as inaccurate job costs, excess inventory, or hours spent retyping data.
- Put a number on it. Estimate what the problem costs today and what fixing it is worth. That becomes the payback target for the first project.
- Fund one tool at a time. Approve the next project only after the last one proves its value. Budget stays under control, and the business case builds on real results.
- Keep the ERP as the source of truth. Every tool reads from and writes back to the ERP, so reporting stays consistent and nothing lives in a side system.
This keeps technology spending tied to measurable outcomes, which is exactly where a CFO wants it.
Questions to ask before you start
- Which processes around the ERP still run on spreadsheets, paper, or memory?
- Where do the numbers in the ERP disagree with what is actually happening on the floor?
- What would a 10 percent improvement in that area be worth per year?
- Does our ERP have a supported way to connect other tools to it?
- Who owns each new tool after it launches?
The bottom line
Modernizing doesn’t have to mean starting over. For most manufacturers, the smarter path is to keep the ERP doing what it does well and fix the work around it in focused, fundable steps. You lower the risk, you control the spend, and every step has a result you can measure.
If you want to see where your ERP is costing you the most, we can help you find it. Learn more about how we build operational systems around your ERP.
