For years, ERP projects were built on a risky assumption: “The system must adapt to the customer, no matter the cost.”
This mindset produced:
Business Central SaaS breaks this pattern.
And it does so with a clear methodology: Fit‑to‑Standard.
Fit‑to‑Standard does not limit the customer.
It frees them from unnecessary complexity.
1. What Fit‑to‑Standard really means
Fit‑to‑Standard is a methodology where:
the implementation starts from the standard capabilities
customer data is analysed before making decisions
gaps are identified based on evidence, not assumptions
configuration is prioritised over development
the system remains update‑friendly
the ERP stays aligned with Microsoft’s SaaS evolution
It is a pragmatic, modern and sustainable approach.
Official Microsoft guidance:
Business Central Implementation Overview
Configure Business Central
Business Central Application Design
2. Why Fit‑to‑Standard is a data‑driven methodology
The goal is not to “force the customer into the standard”.
The goal is to use real customer data to decide what truly needs adaptation.
✔ Historical data
Sales patterns, purchasing cycles, inventory movements, production volumes.
✔ Operational data
Seasonality, exceptions, lead times, bottlenecks.
✔ Usage data
Which processes are used, which are ignored, where friction occurs.
✔ Data quality
Duplicates, inconsistencies, incorrect structures.
With this evidence, the functional consultant can say:
“This process already exists in standard.”
“This exception occurs only 2% of the time.”
“This customisation does not add measurable value.”
“This requirement can be solved with configuration.”
Fit‑to‑Standard transforms the conversation from subjective to objective.
3. Practical examples of Fit‑to‑Standard in Business Central
Example 1: Inventory management
A customer requests a custom process for special locations.
Data shows only 3% of stock passes through them.
Solution:
→ Standard location rules + configuration.
→ No custom development.
Example 2: Purchasing approvals
The customer wants a 7‑level approval chain.
Data shows 92% of purchases are low‑value.
Solution:
→ Two approval levels + thresholds.
→ No unnecessary complexity.
Example 3: Demand forecasting
The customer wants a custom forecasting model.
Data shows clear seasonal patterns.
Solution:
→ Standard forecasting + manual adjustments.
→ No bespoke model.
Fit‑to‑Standard simplifies with evidence, not by force.
4. Fit‑to‑Standard and the update lifecycle (major & minor updates)
One of the biggest advantages of Fit‑to‑Standard is protecting the update lifecycle of Business Central:
✔ Major updates (twice per year)
Microsoft releases significant functional and platform improvements.
Fit‑to‑Standard ensures the system can adopt them without breaking.
✔ Minor updates (monthly)
Security, performance and reliability enhancements.
Minimal customisation = minimal risk.
✔ Reduced technical debt
Fewer extensions → fewer conflicts → smoother updates.
5. The critical role of customer participation and key users
Fit‑to‑Standard succeeds only when the customer is actively involved.
✔ Key users must:
validate standard processes
provide real operational data
identify exceptions that truly matter
participate in workshops and testing
understand the impact of customisations
✔ The customer organisation must:
commit to process alignment
accept evidence‑based decisions
collaborate in data cleansing
adopt standard terminology and flows
Fit‑to‑Standard is a co‑creation process, not a consultant‑only exercise.
When key users participate, the implementation becomes:
6. How Fit‑to‑Standard elevates the functional consultant
The consultant stops being:
And becomes:
Fit‑to‑Standard elevates the functional role to a position of decision and leadership.
7. Benefits for the customer
• Faster implementations
Less development, more configuration.
• Lower total cost of ownership
Reduced maintenance and technical debt.
• Update‑friendly system
Major and minor updates without disruption.
• Cleaner, more consistent processes
Fewer exceptions, fewer deviations.
• Decisions based on evidence
Not on assumptions or personal preferences.
To Conclude
Fit‑to‑Standard is not a restriction.
It is a strategic, data‑driven and sustainable way to implement Business Central.
It protects the update lifecycle.
It reduces complexity.
It empowers key users.
It elevates the functional consultant.
And it ensures the ERP remains healthy, modern and aligned with Microsoft’s roadmap.
It is, without doubt, the right methodology for any organisation adopting Business Central SaaS.
