
“Better reporting” sounds like a sensible ERP objective, but what does it mean in practice? Ben Langley, founder and CEO of Suite Generation, talks to Joanna England about defining ERP success, aligning group and subsidiary priorities, and giving an implementation a clear business purpose before work begins.
Part 2 of 5 in the series Phase zero – before you implement.
This interview has been edited and condensed for clarity.
ERP success: key takeaways
- Going live on a new system is not an objective in itself. ERP success should be defined by what the organisation wants to achieve.
- “Better reporting” needs detail: financial information, cash flow, inventory, headcount and project profitability are different requirements.
- In a group, the centre’s ambition and each subsidiary’s priorities both need to be understood and aligned deliberately.
- Agreeing the indicators of ERP success at the start gives the business something meaningful to assess at the end.
Why isn’t getting onto a new ERP enough of an objective?
Ben: Because having the system does not tell you whether the business is working better. You can reach the end of an implementation and still struggle to explain what you achieved.
If nobody agreed what success would look like, how do you judge the result? You may have delivered the software, but you have not necessarily checked the things that mattered to the business.
The starting point should be what you want the organisation to achieve. The ERP then supports that. Otherwise, the project can become a collection of decisions without a clear purpose connecting them.
What is missing from an objective such as better reporting?
Ben: The detail. Do you want clearer financial information? A better understanding of cash flow? Visibility of inventory? Do you need to understand headcount or see which projects are profitable?
These are different requirements. Saying that you want better reporting leaves too much open to interpretation.
That matters particularly in a group, where the information needed at the centre depends on what individual businesses can provide through their processes.
You need to explain what information you want and what success means for the people using it. An ERP has a lot of functionality, but the availability of a feature does not tell you whether it answers your business question. You have to establish that connection yourself.
How does ERP success change when the business is a group?
Ben: You need to understand the group’s ambition and the priorities of its individual companies. They will not necessarily describe success in the same way.
A group might have a broad growth strategy, while a small subsidiary is focused on delivering a particular service in a local market. Both perspectives affect how the business operates.
Phase zero is where you bring those views together. The group needs a coherent direction, but it also depends on its subsidiaries continuing to function. You cannot assume that one statement from the centre resolves every operational difference underneath it.
Does alignment mean making every subsidiary work identically?
Ben: There needs to be a shared direction, but you have to understand how that direction will work for the companies involved. That can mean running different streams and asking different parts of the group to adjust.
The point is to make those choices deliberately. You look at what each company does, what it wants to achieve and how that fits the group’s requirements.
Without that work, differences can emerge much later, when you are trying to put the system into use. By then, changing the approach becomes much more disruptive for the people delivering the work.
Who needs to contribute to decisions about ERP success?
Ben: The people who understand the work as well as the people setting the strategy. Senior leaders can explain the overall direction, but department heads and operational managers know how the business runs each day.
They work with the data and understand the processes their teams follow. They are also the people who will have to make many of the changes happen.
If their perspective is missing, you can agree an ambition without understanding what it will demand. Bringing those conversations together helps turn a broad objective into something the business can actually work towards.
What happens if the objectives remain vague?
Ben: You start making decisions as ideas appear. Someone suggests a useful feature, another person wants a different report, and suddenly you have several priorities that may not fit together.
Then you are deciding, during the implementation, which ideas matter most. That is harder if there is no agreed picture of success to refer back to.
You also have to explain the investment to people inside the business. You want to be able to say what the project achieved and why it mattered. Defining the indicators of success at the beginning gives you something meaningful to assess at the end, rather than relying on the fact that the new system is live.
Frequently asked questions
Start from what the organisation wants to achieve, then spell out the information and outcomes people need, such as clearer financial information, cash flow visibility or project profitability. Agree those indicators of success before work begins.
It leaves too much open to interpretation. Different reporting needs are different requirements, and the availability of a feature does not show that it answers your business question.
The group’s ambition and each subsidiary’s priorities may not match. Bring those views together in phase zero and decide deliberately where companies adjust, rather than discovering the differences when the system goes into use.
Senior leaders who set the strategy, together with department heads and operational managers who understand the processes, work with the data and will make many of the changes happen.
Related reading
- Before you buy an ERP: Ben Langley on getting the business ready
- ERP project health check and milestone reporting
- ERP implementation checklist
- APM: what is benefits management and project success?
About Ben Langley
Ben Langley is a NetSuite consultant and the founder and CEO of Suite Generation – 30+ implementations, multiple OneWorld accounts, and over 200 automations built inside NetSuite. Follow him on LinkedIn for more thought leadership on ERPs and NetSuite.
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.
