
Going live doesn’t automatically mean an ERP investment has delivered returns. Gene Hammons, a business consultant specialising in ERP acquisition and deployment, talks to Joanna England about benefits realisation: building a realistic business case, tracking improvements over time and keeping financial expectations connected to the people and processes that will deliver the results.
This interview has been edited and condensed for clarity.
Key takeaways
- Gene Hammons builds an ERP business case by identifying requirements, asking what satisfying them would mean and putting numbers against them.
- Compare the investment with the cost of continuing as you are, including the cost of delaying the decision.
- Use conservative assumptions rather than the best result seen elsewhere, and expect benefits realisation to build gradually after go-live.
- Benefits realisation depends on measurement: put targets on users’ dashboards and keep asking whether they are being met.
Where do you begin when building an ERP business case?
Gene: First, I identify the requirements. Then I ask what satisfying them would mean. If the business grows, could the accounting team handle that growth without needing the same increase in headcount? What would better inventory management change?
You need to work through those items and put numbers against them. The discussion becomes more useful when you can explain the business effect of a requirement. Instead of saying that the system has a feature, you are explaining what people expect to achieve by using it.
Why is judging the project by its price alone a problem?
Gene: A company might hear the proposed cost and immediately say it is too much. My question is: based on what? You need to compare the investment with the value of solving the problem.
I have visited businesses with very different staffing levels despite similar size and complexity. That makes you ask how much manual work the existing setup creates. It does not mean every business will achieve the same savings. It means the business case needs to examine the cost of continuing as you are, as well as the cost of changing.
Delay belongs in that discussion too. If the business expects an improvement from the project, postponing the decision also postpones that benefit. Understanding the payback helps leaders decide what resources to commit.
How do you avoid making the forecast too optimistic?
Gene: I reduce the assumptions rather than taking the best result I have seen and promising it to the next client. One company may make an exceptional improvement in inventory, but that does not mean another will achieve the same result.
We look at what the client can realistically reach. The forecast should give people something credible to work towards. If they later find further improvements, that is welcome, but the initial case should not depend on matching an unusually successful example. You do not want to set the team up to fail.
Should benefits realisation begin as soon as the system goes live?
Gene: People often assume it will, but go-live is when staff begin learning how to use the system in their everyday work. The improvement can take time.
I build that into the projection. An inventory manager is not necessarily going to deliver the full target in the first month. The early change may be small, followed by further gains as people understand the tools and improve their processes. The point is to give the business a realistic progression rather than assuming that switching the system on produces the whole return immediately.

How do you make those targets useful to the people doing the work?
Gene: Put them where people can see them. We might set up an inventory manager’s dashboard so they can see their progress for the month whenever they log in.
Then keep returning to the numbers. Are we achieving what we expected? If we are not, why? That is the conversation I want after implementation. Some businesses treat a working system as the finish line, but the business case was about better performance. Measuring the result helps us see whether the processes and the way people use the software are delivering it.
What if benefits realisation needs more work after launch?
Gene: The ERP may help with inventory control but only take you part of the way. You might need additional steps or another tool, such as warehouse management, to achieve the outcome you identified.
That is why I keep bringing the conversation back to value. Additional spending should be considered against the benefit still available. You cannot make that judgement properly if nobody is measuring the return. When people understand their business, learn the tools and pay attention to the results, they can identify improvements beyond the original plan. But they need to keep looking, rather than assuming the job ended at go-live.
Benefits realisation: frequently asked questions
It is the work of making sure the improvements that justified the investment are delivered and measured after the system goes live. For Gene Hammons, the business case was about better performance, so a working system is not the finish line.
Rarely, in Gene’s experience. Go-live is when staff begin learning the system in their everyday work, so he builds a gradual progression into his projections rather than assuming the full return arrives immediately.
Reduce the assumptions instead of promising the best result seen at another client, and set a target people can credibly reach. Any further improvements are welcome, but the case should not depend on them.
Put targets where people will see them, such as a dashboard showing monthly progress, and keep asking whether you are achieving what you expected and, if not, why.
Related reading
- NetSuite ROI: how to build a business case your CFO will sign
- NetSuite dashboards and custom KPIs
- Post go-live support
- Software adoption starts before the ERP training session
- APM: what is benefits management?
- UK Government Project Delivery guidance, chapter 19: benefits management
About
Gene Hammons is an experienced ERP leader with over 400 projects. He helps CEOs, CFOs and COOs turn complex software investments into measurable strategic value. Bridging finance, operations and enterprise tech, he provides the proven methodology midsize companies need to bypass implementation pitfalls and build scalable systems that drive long-term control and profitability.
Author

Joanna England is Marketing & Growth Operations Lead at Suite Generation and an award-winning tech and business journalist with more than 25 years' experience. A former Editor-in-Chief of Insurtech Insights, Fintech Magazine and Insurtech Digital, she was named one of MPVR's Top 30 Journalists in Fintech & Insurtech in 2023.
Follow us on LinkedIn
New NetSuite field notes, UK pricing guidance and implementation practice, as we publish them.
