Building the CapEx Case for ERP and AI Projects
A CapEx case for an ERP or AI project is a financial argument that the investment returns more than the company's cost of capital, supported by benefit estimates that can be traced to operational data and measured after go-live. Most ERP business cases fail not because the return is poor but because the benefits are asserted rather than derived, and because nobody commits to measuring them. CFOs approving a $2 million ERP modernization or a $400,000 AI automation program want three things: a credible baseline, benefits tied to specific mechanisms, and an accounting treatment that has already been agreed with the auditors.
The Financial Metrics That Decide the Decision
Four numbers carry the case. Net present value discounts projected cash flows at the company's weighted average cost of capital, commonly 9 to 14 percent for mid-market manufacturers, and must be positive. Internal rate of return is compared against the hurdle rate, which is usually set above WACC to account for execution risk, often 15 to 20 percent for IT projects. Simple payback matters politically even though it ignores the time value of money; most boards want under 36 months and many want under 24. Return on invested capital shows the effect on the metric the business is actually measured by. Present all four, model a five-year horizon, and include a downside case where benefits land at 60 percent of plan.
Building a Benefit Model That Survives Scrutiny
Every benefit line needs a mechanism, a baseline, and an owner willing to accept the number in their budget. Inventory reduction is credible when it is derived from a safety stock recalculation across the item master, not from a benchmark percentage. Margin improvement is credible when it is derived from repricing a specific set of items priced off stale costs. Labor avoidance is credible when it names the processes eliminated and the hours involved. Separate hard benefits that show up in the P&L or balance sheet from soft benefits like improved decision speed, and do not let soft benefits carry the NPV. If a benefit cannot be measured after go-live from a report that already exists, treat it as a qualitative argument rather than a cash flow.
- Tie each benefit to a mechanism and a baseline measured from actual ERP data before the project starts
- Have the budget owner accept the benefit in their forecast, which converts an estimate into a commitment
- Model one-time working capital release separately from recurring P&L benefit; they are not the same cash
- Run a downside case at 60 percent benefit realization and confirm the project still clears the hurdle rate
Capitalization Rules for ERP and AI Software Costs
Accounting treatment materially affects reported earnings and should be settled before the case is presented. Under ASC 350-40 for internal-use software, costs in the preliminary project stage are expensed, costs in the application development stage such as configuration, coding, interfaces, and testing are generally capitalized, and post-implementation costs including training and data conversion are expensed. For cloud arrangements that are service contracts, ASU 2018-15 permits capitalizing implementation costs on a similar basis, amortized over the term of the hosting arrangement including reasonably certain renewals. The practical consequence is that a subscription-based cloud ERP shifts a large portion of what used to be capitalized license spend into operating expense, which changes EBITDA even when total cash outflow is similar.
- Expense preliminary project stage work: vendor selection, requirements definition, and feasibility analysis
- Capitalize application development stage costs including configuration, interfaces, and testing labor
- Expense training and data conversion regardless of when they occur in the project
- For cloud arrangements, amortize capitalized implementation costs over the hosting term including likely renewals
Presenting Total Cost of Ownership Honestly
Business cases lose credibility when the cost side is thin. A complete five-year TCO includes software license or subscription, implementation services, internal labor at fully loaded cost including the backfill for seconded subject matter experts, infrastructure or hosting, integration development and ongoing maintenance, data migration and cleansing, training and change management, and a contingency of 15 to 20 percent for a project of meaningful scope. For AI projects add inference and model usage costs, which scale with adoption and are frequently understated at approval time, plus the ongoing effort to monitor and maintain the models. Internal labor is the line most often omitted entirely, and on a large ERP program it commonly represents 25 to 40 percent of true project cost.
How Netray Builds Defensible ERP and AI Business Cases
Netray builds the baseline from your own ERP data rather than from industry benchmarks. We quantify inventory excess item by item, identify margin leakage by item-customer combination, measure actual hours consumed in the processes targeted for automation, and translate each into a benefit line with a named owner and a post-go-live measurement method. The resulting case includes NPV, IRR, payback, and a downside scenario, alongside a five-year TCO with internal labor and AI inference costs made explicit. Because the baseline comes from live transaction data, the benefits can be tracked in the same reports after go-live, which is what converts an approved business case into realized value rather than a document nobody revisits.
Frequently Asked Questions
What payback period do CFOs expect for an ERP project?
Most boards want simple payback under 36 months, and many mid-market manufacturers set an internal expectation of 24 months or less for technology investments. Payback alone is not sufficient because it ignores the time value of money, so present net present value at your weighted average cost of capital and internal rate of return against a hurdle rate as well. Include a downside case where benefits land at roughly 60 percent of plan.
Can ERP implementation costs be capitalized?
Partly. Under ASC 350-40 for internal-use software, application development stage costs such as configuration, interface development, coding, and testing are generally capitalized, while preliminary project stage activities like vendor selection and requirements definition are expensed, as are training and data conversion. For cloud-based arrangements accounted for as service contracts, ASU 2018-15 allows capitalizing implementation costs and amortizing them over the hosting term including reasonably certain renewals.
How do you quantify the ROI of an AI project in manufacturing?
Derive each benefit from a specific mechanism measured against a baseline in your own data. Examples include inventory released from recalculated safety stock, margin recovered by repricing items running on stale standard costs, hours eliminated from a named manual process, and reduced expedite freight. Model recurring P&L benefits separately from one-time working capital release, include AI inference and model maintenance costs on the cost side, and commit to measuring each benefit post go-live.
Key Takeaways
- 1The Financial Metrics That Decide the Decision: Four numbers carry the case. Net present value discounts projected cash flows at the company's weighted average cost of capital, commonly 9 to 14 percent for mid-market manufacturers, and must be positive.
- 2Building a Benefit Model That Survives Scrutiny: Every benefit line needs a mechanism, a baseline, and an owner willing to accept the number in their budget. Inventory reduction is credible when it is derived from a safety stock recalculation across the item master, not from a benchmark percentage.
- 3Capitalization Rules for ERP and AI Software Costs: Accounting treatment materially affects reported earnings and should be settled before the case is presented. Under ASC 350-40 for internal-use software, costs in the preliminary project stage are expensed, costs in the application development stage such as configuration, coding, interfaces, and testing are generally capitalized, and post-implementation costs including training and data conversion are expensed.
Put this into numbers
Free interactive tools for exactly this problem. No signup to use them.
CapEx Payback and NPV Calculator
Build the payback period, net present value, and lifetime ROI numbers your capital approval request needs for equipment, automation, or ERP investments.
Free ToolERP Business Case Calculator
Build a defensible ERP business case from inventory carrying cost reduction, administrative labor recovery, and expedite savings, with payback period and five-year ROI.
Free ToolProcure-to-Pay Efficiency Calculator
Quantify the labor cost buried in your purchase order and invoice processing, including exception handling, and benchmark your cost per invoice against automation leaders.
Terms used in this article
Ask Netray to build a data-backed business case for your ERP or AI initiative, with benefits derived from your own transaction history.
Related Resources
Budgeting and Forecasting in ERP
Budgeting and forecasting in ERP: driver-based models, rolling forecasts, budget ledgers, and 13-week cash views for manufacturers who miss their numbers.
ERPWorking Capital Optimization for Manufacturers
Working capital optimization for manufacturers: cut the cash conversion cycle with DSO, DPO, and inventory levers driven from ERP data, not spreadsheets.
ERPGross Margin Analysis by Product and Customer
Gross margin analysis by product and customer: build a contribution model in ERP, allocate freight and rebates, and find the 20 percent of SKUs losing money.