
Buying software is only one part of changing how a business runs. Ben Langley, founder and CEO of Suite Generation, talks to Joanna England about “phase zero” – the ERP readiness groundwork that helps companies understand their operations, prepare their people and make a more informed ERP decision.
Part 1 of 5 in the series Phase zero – before you implement.
This interview has been edited and condensed for clarity.
ERP readiness: key takeaways
- Phase zero is the ERP readiness work that comes before choosing a system: understanding processes, data, people and resources, and agreeing what success looks like.
- Ben Langley often joins projects after the software has been bought, when requirements the standard processes do not cover only surface during implementation.
- A profitable business can still rely on hidden workarounds. Understand what they do before removing them.
- A finished phase zero gives a process alignment plan and a far more detailed basis for the software conversation.
What do you mean by phase zero?
Ben: It is the groundwork before an ERP implementation. Before choosing the system, you need to understand how the business works, what you want to change and what it will take to get there.
That means looking at your processes, data, people and resources. It also means agreeing what success looks like. These questions belong together because a decision in one area affects the others.
You also need to account for practical constraints, such as existing subscription dates and planned acquisitions. Those factors can affect when the business is ready to move, even if the software decision itself appears straightforward to the project team.
I call it phase zero because companies often start further along. They have bought the software and brought in consultants before answering some basic questions about their own business.
Why is buying the software first a problem for ERP readiness?
Ben: Sometimes I join a project after the company has already bought NetSuite. The expectation is that the system, together with its standard processes, will solve the problems.
Those processes can be a useful starting point. But businesses do not all work in the same way. When you look closely, there may be requirements that the standard approach does not cover.
If you only discover those differences during implementation, you have to work out how to handle them while the project is already moving. Understanding them earlier gives you a stronger basis for selecting and configuring the system.
Can a profitable business still need ERP readiness work?
Ben: Absolutely. A business can generate substantial revenue while relying on people to carry information between disconnected systems. They know which spreadsheet needs updating and which colleague needs a message before something can happen.
Those people keep the operation working, but the effort is not always visible from the top. Having a profitable business does not mean its processes are efficient or easy to transfer into another system.
You need to understand what is holding everything together before changing it. Otherwise, you risk removing the workarounds without replacing the functions they perform.
Why can’t a tight deadline make everything happen faster?
Ben: An implementation involves a large amount of problem solving. People need to agree new processes, clean up data and understand how their work will change.
They may need an answer from another department or a third party. Someone important may be on holiday. The person making a decision may also be responsible for keeping the business running that day.
These dependencies take time. Setting a more ambitious date does not remove them. When I ask someone when they can finish a task, I also ask what is realistic alongside their day job.
Does phase zero mean delaying improvements?
Ben: You can make improvements during this work. Once you document existing processes, you may find unnecessary steps or parts of the technology stack that can be simplified before changing ERP.
That gives you a clearer understanding of what the new system actually needs to do. You are no longer assuming that every existing process must be recreated.
There is also a cost advantage to doing this thinking earlier. You can use a business analyst to document how things work before asking specialist ERP consultants to design the solution. Those are different tasks, requiring different kinds of expertise.
What should a company have when phase zero is complete?
Ben: A clearer picture of its processes, its data and the people needed to make the change. It should understand its objectives, the risks and the practical constraints around timing.
I bring those findings together into a process alignment plan. That becomes the basis for deciding how to move forward and gives the next stages a more realistic starting point.
It also changes the software conversation. Instead of saying, “We broadly do this; can your system handle it?”, you can explain what the business needs in detail. You can then identify where the product fits and where additional work will be required.
Frequently asked questions
ERP readiness is the groundwork known as phase zero: understanding how the business works, what it wants to change and what it will take to get there, across processes, data, people and resources, before choosing a system.
It is better not to. When companies buy first, requirements the standard processes do not cover are often discovered during implementation, while the project is already moving.
No. Documenting current processes can reveal unnecessary steps, or parts of the technology stack to simplify, before changing ERP. A business analyst can do that documentation before specialist ERP consultants design the solution.
A clearer picture of processes, data and people; an understanding of objectives, risks and timing constraints; and a process alignment plan that becomes the basis for the next stages and for more specific conversations about software.
Related reading
- How to choose an ERP
- ERP implementation checklist
- Before the ERP demo: the questions Gene Hammons wants answered
- Oracle NetSuite: a guide to assessing whether a business is ready
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.
