Selecting the right Enterprise Resource Planning (ERP) software should not be an easy decision. The biggest mistake most companies will make is rushing into it without first establishing their ERP requirements checklist. A slap-dash approach will only end up costing you time, money, and resources.
There are a lot of downloadable ERP requirements checklists online. Very few of them are useful as they tend to focus on generic features rather than the specific needs of the team that will be using the ERP for years to come.
Best practice would be to establish a custom checklist based on your specific needs. That way you won’t end up wasting more money on flashy features that have very little to do with your company’s goals.
Use these ten steps to ensure you build an ERP requirements checklist that is right for your company. Equip your team with the criteria and questions needed to assess each system and find one that will work best.
Here are the steps you should take when establishing your ERP requirements checklist:
- Survey team and establish a list of business requirements.
- Get upper management to actively engage in the process.
- Consider in-house expertise and get full user support.
- Make a comprehensive list of all functional requirements.
- Figure out integration with existing systems and processes.
- Consider the capabilities the ERP should have as you scale.
- Set a realistic budget covering implementation, integration and onboarding.
- Crunch the numbers and calculate the total cost of ownership and ROI.
- Research industry-specific solutions and avoid expensive customizations.
- Decide what kind of team you want to work with.
Make a comprehensive list of all your business requirements for the ERP. You will need to survey the people it will impact most i.e. the users and those directly impacted by its functionality. There is no one-size-fits-all checklist, and you will need to speak to employees at all levels of your company to get a feel for the right criteria. It might be useful to make a list of those who will use the system, and then start by asking them what they need it to be able to do with it. Then, you may want to ask upper management what sorts of reports they need to see to make financial decisions. You also want to ask trusted customers and suppliers what would help them.
Use this feedback to build a tiered list of requirements
If you do this well, you will end up with a large list of ideas. Take this list and use it to form a tiered list of requirements. Working with your team, establish what are the “must-haves”, “good to haves” and “nice to haves”. Your list may have more tiers than this. The overall aim is to get a clear picture of the essential features for your ideal ERP system and which features you can maybe live without.
Once the list is tiered, get the entire team to evaluate it. Can someone fight for a feature that got pushed to the bottom of the list? Be flexible and try to listen to everyone’s input. Weigh the costs and benefits of what they advocate for before you finalize the list.
At the end of this process, you will be able to start looking at some of the other technical requirements of a good ERP. Looking at solutions before you know exactly what you need can have dizzying results. It may even prevent you from making a decision grounded in your business requirements.
It’s up to you to convince upper management of the importance of the project. Getting their total buy-in and full support is key. Your list of business requirements should be one tool that will make it easy to show them the potential of the right ERP system. You will need more from them than just budget approval. Without their buy-in, you may end up getting a cheaper solution with less functionality than you require and find that it costs you in the long run.
Before you approach upper management, be sure to have read through this list comprehensively. As we’ve detailed many things that you may want to be aware of (and have answers for!) before you book a meeting.
Chances are that there are members of your team who have a wealth of experience using different ERPs at previous jobs. Many of these ERPs will be specific to your industry’s needs. As part of your checklist, get their suggestions on the systems they’ve loved throughout their careers. This is important information and can cut down on training costs later. If you end up choosing a solution that some of the team is already familiar with, they can help with training the wider team. It’s also important to understand what they loved about those systems so that you can be sure any new ERP will get their full support.
You need your team’s full support to make the system work. After all, they will be using the system, and the learning curve can be steep. Sometimes, companies make the mistake of landing their teams with a new system, without first supporting them in the transition. Think about how to manage the change to a new ERP from a human perspective. Your team needs to know that documentation and training will both be readily available.
Once you’ve got a clear understanding of your team’s abilities and requirements, it’s time to get technical. Consider what functional requirements your ERP needs to make your company run smoothly. For instance, should it be hosted on-premise or in the cloud? Will you be using this in addition to a CRM system or run your sales processes out of your ERP? Other functionalities might be the ability to manage multiple currencies and companies.
It’s as important to establish the functional requirements you don’t need. For instance, if you don’t manage inventory, then the system you choose won’t need to have that functionality. Many ERPs are built specifically for certain industries. It’s worth considering which functionalities are crucial to your business.
Some general functionality questions to ask:
- Will you need the ERP to have the functionality to support multi-company, multi-warehouse and international companies
- Do you need it to handle different pricing and billing models per product or service?
- Will you need to support accounting functions like General Ledger (GL), Accounts Payable (AP), Accounts Receivable (AR), cash management and tax management?
- Do you need it to support a complete quote-to-cash cycle?
- Do you need it to support inventory management?
- What legal frameworks and tax laws do you need to be aware of?
Your company already has processes and systems in place. Your new ERP solution should not interfere with these workflows and technologies, unless necessary. The ERP must be easy to integrate. Otherwise, you will end up creating an administrative nightmare that will make it impossible to fully optimize your systems.
For example, if you’re already using Microsoft 365 it makes sense to opt for ERP systems that will integrate with that system. Basically, you need to actively look for companies that have built solutions for your industry. These companies will likely have processes in place to integrate your systems with the ERP.
In some cases, you may find your current systems are all out-dated. It will end up making the most sense not only to invest in an ERP but also the other tools and systems that integrate with that system. Although this may feel daunting, it will save time and money in the long run.
Whatever you decide, make sure your ERP requirements checklist has a section outlining the systems it will need to integrate with. There’s no point wasting time researching ERPs that won’t function in your workplace.
It’s also important to think about the future when deciding on your ERP requirements checklist. Most likely, your company plans to scale, and as it grows your systems need to be able to seamlessly manage that growth. That means choosing a solution that will be as good for your company tomorrow as it will be today.
If you do plan to scale and won’t need all functionality immediately, it’s important that you think about scalability and updates to the system as time passes. How easy will it be to ramp up operations? Do the ERP providers have clear guidance and systems in place to help you manage growth?
Deciding how much money is realistically available for an ERP system is crucial. This is an investment in a system that will operate at the very heart of your business for at least a decade. It’s important to weigh up how much you’re going to spend. Be sure that management understands the benefits before you start whipping numbers out of the air.
In 2019, a report that analyzed data from over 2,000 projects. They found that the average budget per user for an ERP project was USD 7,200. Training costs, integration costs and the system cost are all part of the expenditure you can expect in getting your ERP up and running. Make sure your requirements checklist understands the true budget required to get the job done.
Once you establish a budget, it’s time to calculate your return on investment. Make sure these costs and benefits are spread over time so that you get a clearer picture of the ROI over time. Once you know how much it will cost, you can start to think about the improvements and benefits of the system and calculate the money that can be saved. E.g. processes that once took hours, may now only take minutes.
Now that you will have a system taking care of labour-intensive work, you may be able to free up staff to provide valuable services that were impossible in conjunction with arduous reporting and invoicing processes. This will be very different for each company and comes back to the business requirements. Your team must understand the time and money that will be saved and that this is an investment that will have a measurable ROI.
9. Consider industry-specific solutions to avoid expensive customizations when creating ERP requirements checklist
One of the biggest costs in implementing any ERP system is requiring a lot of customizations, this is often because the solution is too general and not fit for purpose. Ask yourself is your company so unique that no other company has ever needed the same tools? Although this is possible, it’s not likely. You should be able to find an ERP that has been tried and tested and that has functionality specific to your industry. Whenever you find an ERP system pushing customizations, ask yourself if those features might be standard in a system built with your industry in mind.
For instance, a healthcare provider looking to manage materials is going to have completely different requirements from a SaaS company that wants to streamline its subscription billing. Both companies will need a system that can support industry-specific extensions that supplement the core ERP rather than relying on overpriced customizations built by ERP providers who don’t usually operate in their industry.
One way of establishing whether or not a software provider has the tools you need is to look for case studies or examples that exist where similar business models to you have successfully implemented and used that ERP. If you are going to need customizations, be sure you focus on providers who have a team of skilled developers who will be able to quickly and efficiently tweak your system.
One component that often gets left off ERP checklists is deciding what sort of team you intend to work with. It’s a piece of software! Why does it matter as long as it has the right functionality? The people behind the product matter when a system is integral to the day-to-day running of your company.
Make sure you know how helpful they’re willing to be? If they will be hands-on with training? If an implementation framework exists? How have other companies found working with them? The right global ERP system will also have demonstrated success in the countries where you operate, so make some of your selection criteria the availability of useful resources, case studies and references that are relevant and industry-specific. Compare and contrast how well different ERP systems work within your space.
By establishing what it is you’re looking for as part of your ERP checklist, it will then be easy to research different solutions and make sure that the team behind the system will be as responsive and helpful as you need.