Fit-gap analysis is the core discovery activity in any ERP implementation. It systematically compares what a standard ERP system provides against what a business actually needs, producing a clear picture of where the system fits requirements and where gaps exist that must be resolved through configuration, customization, or process change.
The quality of fit-gap analysis in presales directly determines project scope accuracy, budget reliability, and delivery confidence. Poorly executed fit-gap is the single most common origin of scope creep, budget overruns, and failed implementations.
How fit-gap analysis works
The process begins with structured discovery workshops where business stakeholders walk through their processes requirement by requirement. For each requirement, the implementation team assesses one of three outcomes:
Fit — the standard ERP functionality meets the requirement without modification. No custom development is needed. Configuration may be required, but the behavior is within the system's intended design.
Gap with configuration — standard functionality can meet the requirement through system configuration — activating features, setting parameters, or adjusting workflow rules. This is low-risk and typically included in baseline delivery scope.
Gap requiring customization — the standard system cannot meet the requirement through configuration alone. The gap must be resolved through custom development (RICEFW), a process change on the client side, or a formal decision to accept the limitation.
What good fit-gap analysis produces
A well-executed fit-gap produces a structured inventory of every requirement, its fit/gap classification, the resolution approach, and the estimated delivery effort for each gap item. This inventory becomes the foundation of the statement of work, the delivery plan, and the change management framework throughout the project.
Requirements captured during fit-gap should remain traceable through the entire project lifecycle. When a requirement changes between presales and delivery, the impact on scope, timeline, and cost should be immediately visible and formally managed.
The presales risk
Fit-gap analysis conducted under time pressure — or by consultants without deep product knowledge — produces incomplete gap inventories. Requirements that were missed or misclassified during presales surface as surprises in delivery, typically at the worst possible moments: during system integration testing or cutover preparation.
Implementation partners who invest in structured, traceable fit-gap analysis in presales consistently see fewer change orders, shorter delivery timelines, and higher client satisfaction scores.
