Start with the problems you can already see
The most persuasive reason for change is a concrete pain: a close that takes too long, inventory that does not match the books, billing errors, audit adjustments, or inability to support a new entity. Document each with evidence, such as the hours spent, the errors found, or the opportunities missed. A case built on observed problems is far more credible than one built on generic promises of efficiency.
- Time and people spent on manual consolidation and reconciliation.
- Errors, write-offs, or audit adjustments traced to current tools.
- Growth plans the current setup cannot support.
Count the full cost honestly
Understating cost is the fastest way to lose a CFO's confidence. Include subscription fees, implementation services, data migration, integration, internal staff time, training, and the ongoing cost of support and enhancements. Internal time is often left out, though it is a real cost, especially for the finance team. Show a range for uncertain items and state the assumptions behind each.
Our NetSuite ERP practice →Identify benefits you can measure
Group benefits into categories you can verify: time saved in routine finance work, faster billing and collections, reduced inventory and write-offs, avoided costs of other systems and spreadsheets that can be retired, lower audit effort, and improved decision quality. For each, state the current baseline, the expected change, and how you will measure it. Distinguish hard savings, such as retired licenses, from softer ones, such as time freed for analysis, and be conservative about the latter.
Baselines make the case testable
Record the current numbers before the project begins: days to close, number of manual journals, invoices per employee, inventory accuracy, or time to produce a board package. After go-live, measure again. Presenting the same measures a year later shows whether the investment delivered and builds credibility for future proposals.
Implementation and integration services →Risks, alternatives and the cost of waiting
A balanced case also covers what could go wrong and how you will manage it: data quality, adoption, schedule, and integration risk. Describe alternatives honestly, including staying with the current system, upgrading it, or choosing a different product, and explain why the recommended path fits best. Include the cost of waiting, such as the growing burden on staff or the risk of failing an audit, since doing nothing is also a choice with costs.
Decisions to settle before you present
- Time horizon. Choose a period, often three to five years, over which costs and benefits are compared.
- Assumptions. List every assumption, its source, and how sensitive the result is to changing it.
- Ownership of benefits. Name a leader accountable for each benefit, since benefits do not realize themselves.
- Review points. Schedule checkpoints after go-live to compare results with the case.
A realistic path to a case in 30 days
- Week 1. Interview finance and operations leaders, list the top problems, and gather baseline data.
- Week 2. Request estimates for subscription, implementation, and integration, and calculate internal effort.
- Week 3. Draft benefits with conservative ranges, risks, and alternatives, and test the assumptions with the people who own them.
- Week 4. Finalize the document, practice the presentation, and agree how results will be tracked.
Pitfalls to avoid
- Inflated benefits. Aggressive claims invite skepticism of everything else in the case.
- Leaving out internal time. Omitting staff effort understates cost and surprises the budget owner later.
- No baseline. Without current measures, you cannot show improvement.
- Ignoring the people side. A case that omits change management and training understates both cost and risk.
