A fit-gap analysis compares a business's requirements with what a software product does out of the box, to show which needs it meets (fits) and which it does not (gaps).
ERP · Reviewed by Ray Rasouli
Ask about fit-gap analysis
Plain answers, with your setup in mind.
Ask anything about fit-gap analysis. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Before choosing or setting up a system, a fit-gap analysis lists each requirement and asks: does the standard product handle this? If yes, it is a fit. If not, it is a gap, and the team decides how to close it.
A wholesale distributor might list needs like customer-specific pricing, lot tracking and EDI orders from big retailers. The new ERP handles the first two out of the box. EDI is a gap, so they plan an add-on rather than custom code.
Each gap has a few options: change the process, configure the system, buy an add-on, build something custom, or accept the gap. Writing down which option was chosen, and why, saves arguments later.
The usual flow, step by step.
In practice
Requirements are vague.
Lines like the system must be easy to use cannot be tested, so everything looks like a fit.
Every gap is treated as must fix.
Teams close gaps with custom code instead of asking whether the process should change.
The analysis is done from demos only.
A polished demo hides limits that show up only when your own data and edge cases are tried.
Ideally during software selection and again early in implementation, once detailed processes are known.
Each gap is closed by changing the process, configuring the system, adding a third-party tool, building custom work, or consciously accepting it.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.