ERP selection checklist: the foolproof five step process
As the average ERP selection project takes around seven months - you’ll want all the headstarts you can get.
Key rule of project management: when doing something new, ask someone else how they did it before. Yet the problem is, with large-scale software projects like an ERP selection, there’s no guarantee that the person who managed the process is still around.
If you’re at the point where you’re replacing an ERP, the likelihood is that your legacy system has been in place a very long time (unless you’re company has done something really wrong, in which case you’ve got even more work cut out for yourself…). You’ll need to find another way to get a headstart.
Rather than providing an overwhelming wall of information we’ve broken down the process down into manageable chunks. This complete ERP software selection checklist covers everything you need to know - and we mean everything.
From deciding that you want to move forward with finding a new ERP for your business to drawing up contracts and service level agreements, we’ve got you covered with quickfire checklists, actionable tips and industry expertise on:
- Identifying the need for new ERP software
- Understanding which features you need
- Crafting, sending out and evaluating RFPs
- Navigating vendor demos and making a final selection decision
1. Check for warning signs that ERP change is needed
Why should I select a new ERP?
This is largely dependent on your organization’s circumstances - there is no universal way of telling when your ERP becomes officially out-of-date.
That said, there are some common signals that your ERP no longer suits your needs. If your ERP:
- Was selected before your company expanded into new areas
- Can’t help you meet current compliance needs
- Doesn’t integrate well with the software you need to do business in the 21st century
...it might be time to audit your existing system and start gathering requirements for an upgrade to your ERP.
2. Survey key stakeholders and draw up an ERP requirements list
How do I define my ERP requirements?
Requirements gathering is a lengthy process, so it’s important to approach it methodically.
Don’t dive straight into identifying all the shiny new features you want. Instead, take a step back and:
- Map out key processes that your new ERP should support
- Identify areas where your current ERP is falling short - maybe you have bottlenecks in your supply chain, or it can’t integrate with your e-commerce system
- Forecast your existing growth and the functionality you’ll need to support this. Are you expanding into new markets, for example?
You can then start discussing the features your new ERP should have.
Who should be involved in ERP requirements gathering?
At least around 20% of your workforce is likely to be comprised of ERP users. That percentage increases for smaller companies:
Needless to say, a system that lets down 20% of your workforce is a no-go, so you’ll need to be thorough in surveying your workforce’s ERP needs.
To understand the needs of your organization as a whole, you should carry out an extensive stakeholder analysis. This will ensure your new software addresses the needs of your business as a whole and provide a firm base for user engagement further down the line.
|Stakeholder||Area of interest|
|Senior management||Analytics, BI|
|Department managers||Analytics, BI, department relevant functions, HR|
|Accounts department||General ledger, accounts, asset & cash management|
|Shop floor workers||Document management, inventory, designs|
|Warehouse staff||Inventory, supply chain management, mobile device integration|
A basic example map of stakeholder requirements in a mid-sized organization
Remember: not all your requirements will be process-focussed. For example, you may need a system that is mobile compatible, runs on a specific version of Windows or is local to your production plant.
Should I choose cloud or on-premise ERP?
Both cloud and on-premise systems have their advantages - but will suit different companies. The table below outlines some key differences between the two:
Usually per-person per month with no upfront feeVendor hosts software on their servers - you access via the webNo extra required, as long as you have internet access
|Cloud||Usually per-person per month with no upfront fee||Vendor hosts software on their servers - you access via the web||Taken care of by third party experts||No extra required - as long as you have internet access|
|On-premise||One off license fee for perpetual ownership with no further payments||You host the software on-site on your own servers||Your responsibility. You own the software - procedures are up to you||Your hardware needs to be up-to-date enough to run the software. If it isn’t, you need to replace it|
This article explains the differences between cloud and on-premise ERP in more detail - check it out if you need a more in-depth overview.
Cloud software seems to be the industry trend du jour among tech journalists - and there has been a shift in interest towards the SaaS model from those selecting an ERP. Equally, it’s not a drastic one. Whilst more ERP project managers are actively searching for cloud software than for on-premise (26% vs 16%), the majority (57%) were undecided on deployment model.
There’s a pronounced split across industries too:
Source: ERP project report 2016
Distribution’s strong preference for cloud reflects the need for a real-time system that integrates with client and supplier’s systems. Meanwhile, process manufacturing companies’ relative lag in seeking out cloud software could indicate security and compliance concerns specific to the sector.
Whilst cloud is new and exciting - especially so in the ERP space - don’t overfocus on it. If it meets your requirements, great. If not, there’s plenty of excellent on-premise ERPs that will suit your needs.
Will I need an industry-specific ERP?
Short answer: if you need industry-specific functionality, yes. Otherwise, no.
You might be a made-to-order manufacturer, but if all you want from your ERP is an upgrade to Quickbooks and integration with the systems you already have in place there’s little point paying extra for functionality you have elsewhere.
On the other hand, if you do have niche requirements that your ERP must address, industry-specific ERPs are a good route to go down. Generally they will be designed around workflows similar to yours and require less customization to fit your needs.
For more information, take a look at these industry ERP whitepapers - you’ll find information on key vendors and the features their software offers:
- Electronics ERP Buyers' Guide
- Manufacturing ERP requirements template
- Seven steps to selecting distribution ERP
2. Shortlist potential vendors
There’s lots of ERP vendors out there, so whittling them down into a shortlist may seem a daunting prospect!
It doesn’t have to be though. There are several ways to get a better idea of vendor suitability:
- Competitor analysis using Datanyze
- Recommendations from your network
- Online community requests
To start with, we’ve created a super-useful ERP comparison tool. You can use this to compare vendors by industry, key features and delivery method. This will give you a more workable number of ERPs to deal with.
Following this, there are several ways to distinguish further between potential vendors:
1. Competitor analysis using Datanyze
This is a very simple premise. If lots of your competitors are using a certain system, it’s highly likely that it will suit your own needs reasonably well.
Obviously you’re going to have your work cut out trying to get your competitors to share their technology strategy with you.
That’s where technographics tools like Datanyze come in, which monitor the technology choices of millions of different companies. They’re often used as prospecting tools by vendors looking for opportunities to sell.
They’re also pretty useful for researching what your competitors are using. As an added bonus, Datanyze has a free trial - so if you’re organized you can make full use of the insights it can provide without having to pay a penny.
- Pros: finds systems that are definitely in use in your industry
- Cons: doesn’t take into account company culture. If you and your competitors both manufacture car parts but your workflows differ, a competitor’s system might not be the best fit.
2. Recommendations from your network
You’ll likely know a lot of people in your industry. Ask recent hires what they used at their last place, for a start. You could also ask suppliers or client companies what they use. Your needs won’t be identical, but they will be able to vouch for how robust the system is, and how efficient their support offering is - as well as pointing out any major red flags.
- Pros: people will provide you with on-the-ground experience of particular ERPs. If a system’s UX isn’t up-to-scratch, this is one of the first things they will mention.
- Cons: hard to tell if these are isolated opinions or not, without seeking out lots of recommendations from the same source
An RFI (request for information) is a document sent out to vendors to collect further information on them. You send the document out, ask for replies within a certain timeframe and compare your responses.
This is not the same as an RFP (see below for more information). Ideally these should be less detailed than an RFP and used for gathering extra information on a vendor and their product, rather than asking vendors to address specific requirements.
- Pros: as it’s a uniform document, responses can be compared across a predefined set of criteria
- Cons: time consuming. Also, be prepared to receive sales pitches rather than completely objective considerations about whether their system suits your needs
4. Online community requests
Whilst going off the recommendations of some guy on the internet might seem an odd choice, there’s actually a lot to be gained from doing this.
Start with LinkedIn - post on relevant discussion groups asking for input and experiences with the systems you are interested in. Quora is also a useful tool for asking niche software questions to an open audience - though it’s admittedly less targeted than posting in LinkedIn groups.
- Pros: you can survey a much wider range of people online than you can by asking for recommendations face-to-face
- Cons: people commenting on internet posts tend to be motivated to do so by extreme experiences. The feedback you receive will likely be skewed to ‘very good’ or ‘very bad’ rather than anywhere in the middle.
4. Send out an RFP and evaluate responses
When should I send out an RFP?
- Created a final list of key software requirements
- Solidified a shortlist of vendors that you think could meet them
...it’s time to start working on an RFP (request for proposal).
In this document, you’ll outline your list of requirements, and allow recipients to explain how their system can meet them. Of course, the better structured and more detailed your RFP, the more useful the responses will be.
How should I structure my RFP?
There are a number of things to include in an RFP. A good basic template to work from is as follows:
|Section||What to include|
|Summary of project purpose||Background on your company, why you want a new ERP, which departments will be using it and general information on what processes it should take care of|
|Project timeline||When you plan on selecting an ERP by, and a goal implementation timeline broken down into key stages|
|Requirements||Include for each requirement: reason you want it, how much of a priority it is for you, which area of the business has the requirement, what it should integrate with, and whether you want it straight out of the box (i.e would long-term development of a customized solution be acceptable?)|
|Vendor qualifications||What you want from the vendor. Include: request for client recommendations, what services you want them to provide, what level of support you’d like, what sort of company culture you expect|
|Proposal evaluation criteria||Let your vendor know how you propose to evaluate their response. This should include a deadline date for the return of responses to your RFP|
If you want a more detailed look at the RFP process, then be sure to check out our step-by-step guide to creating and evaluating ERP RFPs.
How to evaluate RFP responses
It’s important to decide on a uniform set of criteria for evaluating your RFP responses.
Have your selection team read through the RFPs and score each out of five against these criteria. Total these up, and have a meeting to discuss the five highest scoring systems, and aim to whittle this down to a final three to invite to demo.
Remember: the three you invite to demo won’t necessarily be the three highest scoring systems. If your highest scoring ERP doesn’t meet your timescale or vendor culture requirements, you’ll probably want to drop it.
Once you have decided on your final three systems, it’s time to invite them to demo their product.
5. Invite vendors to demo and make a final selection decision
Consider this stage the culmination of the ERP vendor Hunger Games. You’ve eliminated the candidates that don’t perform. Only the strong survive.
You’ll judge them against each other in one final showdown - known in no less exciting terms as the ERP demo stage.
How should software demos be structured?
Firstly, remember this: you are in charge. They are selling to you. Make sure the way your demos are structured reflects this.
To avoid sitting through sales pitches that won’t give you the insight you need to choose the right ERP for your business, it’s a good idea to draw up a demo script to send to vendors. This will allow you to control the direction of the demo. It’s also
You can find a template software demo script here.
If you want an in-depth rundown of how to get the most out of ERP vendor demos, give our demo guide whitepaper a look - it offers a step-by-step guide to how to plan for demos, who should be on the team and the best ways to evaluate them.
Talking of demo teams, here’s a quick checklist of who you should be inviting to view the demos:
- You (the ERP selection project manager)
- Heads of department
- Representatives from all key user groups
- Your executive sponsor
You should invite representatives from all key user groups as well as their department managers. They will use the ERP in a different way to management, and this should be reflected in the makeup of those viewing the demo.
How to evaluate ERP software demos
Another advantage of providing vendors with scripts is that it provides a uniform format with which to evaluate them.
It’s a similar process to the one for evaluating RFPs outlined above - get your team to score each vendor out of five for how well they meet each requirement. Meet to discuss.
Again, your highest-scoring system might not be the one that you end up choosing - you’ll definitely want to prioritize some requirements over others, for example. You might want to choose an ERP that hits the top scores for your key requirements but has a lower score overall. It’s not an exact science.
Once you’ve found your ideal ERP you’ll need to call your legal team, and enter contract negotiations...but that’s another topic for another article.
For now, take a breather and congratulate yourself on getting through the first part of your ERP replacement project.
Featured white papers
ERP Software Pricing Guide
Get your comprehensive guide to the cost of ERP softwareDownload
70 features to look for in your next ERP
A comprehensive guide to help you identify requirements for your ERP selectionDownload
60-Step ERP Selection Checklist
Get the comprehensive checklist for your ERP selection projectDownload
5 steps to successful ERP requirements gathering
Five critical steps to successful ERP requirements gathering
Best features for a restaurant ERP
The functionality you should look for when selecting a restaurant ERP
4 critical features to consider when selecting an ERP solution
These features should be at the top of your ERP requirements list