Give Every Platform Customisation a Business Case

A practical way to weigh local requirements, long-term costs and the value of extending an enterprise platform.

•November 16, 2026•5 min read•3 views
Share:

An enterprise platform rollout brings together teams with different customers, processes and local obligations. When a standard feature does not match a team's existing way of working, a customisation request can appear to be the straightforward answer.

That request deserves a commercial decision. The proposed change may protect an important customer commitment, support a genuinely distinctive service or meet a verified local requirement. It may also preserve a familiar process whose business value has never been examined.

Giving each material customisation a clear business case helps leaders make that distinction. It creates room for valuable differences while keeping their ongoing responsibilities visible.

Describe the requirement before choosing the change

Start with the business situation that the standard process needs to support. Name the users, the transaction or task, and the consequence if the requirement remains unmet.

“Recreate our current approval screen” describes a solution. “A regional service team needs to route a particular category of exception to an authorised reviewer” describes a requirement that can be assessed against several options.

The distinction matters commercially. It allows the team to consider configuration, a change in the business process, an available product feature or a supported extension before committing to new development. A useful review tests the requirement in a realistic end-to-end scenario, including the connected teams that will receive the resulting information.

Microsoft's Dynamics 365 implementation guidance recommends assessing fit with standard processes before examining gaps. It also advises considering development and maintenance costs, effects on connected processes and the possibility that future product features could make a customisation redundant. Those considerations provide a useful starting point for a business-facing discussion.

Distinguish obligations from advantage and preference

Different requirements deserve different evidence.

A legal or regulatory requirement needs validation by the appropriate specialist for the relevant jurisdiction. A commercial requirement should connect to a specific customer commitment or service proposition. An operational requirement needs a clear description of the work that cannot be completed adequately through the standard approach.

Accessibility and essential usability are functional needs, not merely personal preferences. Establish whether people can complete their work effectively and access the required controls. A familiar screen layout or preferred sequence is a separate consideration: assess its demonstrated benefit without assuming it must be preserved unchanged.

This avoids a simplistic rule that every customisation is undesirable. A well-justified extension can be a sensible investment. The decision depends on the value of the requirement and the continuing effort required to support it.

For a discretionary change, record the current baseline, an agreed success measure and a review date before approving the investment. Measures might include exception rates, processing time or task completion. Required legal, security or other essential controls may still be necessary without a positive financial ROI; document the obligation and the evidence that the control is effective.

Put the ongoing work beside the build estimate

The implementation estimate is only one part of the commitment. Include testing, documentation, support, training and specialist knowledge, together with recurring licence, subscription and cloud-consumption costs. Record the usage assumptions behind those recurring charges.

Include the business team's effort as well. A custom workflow may need someone to maintain its rules, validate changes or resolve exceptions. If that responsibility is absent from the proposal, the apparent price is incomplete.

Before approval, have the relevant specialists check security and access controls, integration impacts and compatibility with platform updates. Confirm who owns regression testing and any remediation. Record uncertain costs as assumptions and reasonable ranges rather than treating unsupported estimates as precise.

For a Global Capability Centre (GCC) supporting multiple business units, also consider who will fund and maintain the local variation. A change requested by one unit may affect a platform used by several others. Those implications belong in the approval discussion.

Make the tradeoff concrete

Consider an illustrative request to add a region-specific approval step to a shared sales platform.

First, establish why the step exists. If it reflects a verified contractual obligation for a defined customer category, the team can examine the narrowest supported way to meet it. If it simply reproduces an old internal sequence, the business owner can test whether the standard workflow already provides the necessary control.

Next, examine who else is affected. A change in the sales process could alter information available to order processing, reporting or customer support. Check the connected integrations and security controls with those teams before approving the design.

Finally, define the evidence for review: record the current exception rate or processing time, an agreed success measure and a review date. If the step is mandatory, measure whether the required control works rather than demanding a financial return. A contract ending or a new standard product feature may justify another review, but neither makes removal automatically safe.

The outcome may be to configure, extend, change the process or defer the request while a material uncertainty is resolved. The quality of the decision rests on the reasoning, not on achieving a target number of customisations.

Keep a short record that remains useful

For each material request, retain a concise decision record:

  • The business requirement and the evidence supporting it.
  • The standard capability or process alternative considered.
  • The baseline, agreed success measure and full lifecycle cost or control requirement.
  • The business owner, delivery owner and funding responsibility.
  • The review date and any earlier event that will trigger reassessment.

Use this record during future platform reviews. Confirm whether the requirement still applies, whether people use the change as intended and whether a simpler supported option is now available. Any retirement should include an agreed transition for affected users and data.

Enterprise platforms need enough consistency to be manageable and enough flexibility to serve the business. A clear commercial case for each material variation gives leaders a practical way to balance both.

If you are evaluating Dynamics 365 requirements or reviewing platform customisations, reach out to our team at sales@satincorp.com to discuss the business case and supported options.

Share: