Skip to content

All best practices

BP-002Grade C11 supporting cases (10 counted), 0 counter-examples

Decide what truly differentiates before buying standard software; change the process for everything else

The practice

Before selecting packaged software, name the few processes that genuinely differentiate the business, budget explicitly for those, and adopt the package's standard process everywhere else.

Why it works

Packaged software embeds a model of how the business works, down to valuation, pricing and posting rules. When a company keeps a convention the package does not support, the change reaches deep into the core and every later upgrade, interface and report inherits it. The cost arrives gradually, as performance problems and rework, rather than as one visible decision, so programmes drift into customisation nobody approved as a whole. Deciding the differentiating processes up front turns that drift into an explicit, costed choice. Keeping the number of platforms small has the same logic at portfolio level. The limit is real local variation: a single design imposed over differences the business already knows about fails in the other direction.

KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).

How to apply it

  • Run a fit-gap on the five to ten conventions that drive the ledger and operations (valuation, pricing, margin, promotions, returns, pay rules) before contract.
  • For each gap, decide adopt or adapt at executive level, with a cost estimate and an owner; treat any core-model adaptation as a separate business case.
  • Default to changing the product or process to fit the package; record the exceptions and why they differentiate.
  • Choose the platform per market deliberately and keep the number of distinct platforms small.
  • Re-check the exception list at each design gate; growth in exceptions is a re-approval event.

Warning signs

  • Requests to 'just configure' a valuation, pricing or pay rule.
  • Performance tuning on core postings during build.
  • Vendor workarounds that cannot be carried through an upgrade.
  • No one can list which processes are meant to differentiate.

When it applies

  • ERP, HR and payroll, core-banking and merchandise-system replacements.
  • Any packaged-software selection.

When it does not

  • The process is the competitive advantage and no package supports it; then build or customise knowingly, with cost and risk on the record.
  • Local variation is real and material (regulation, award rules, clinical practice); standardise only what is genuinely common.

Evidence grade: Grade C

Anything below B. Plausible, but not yet tested in the KB at the B bar.

Why this grade

Grade C by schema 4.10 route: below the B bar of 14 counted cases across 4 primary regions (6 per 100 cases in the knowledgebase, 235 cases). B needs at least 14 counted supporting cases across at least 4 primary regions; this practice has 10 counted case(s) across 5 region(s). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does. 1 supporting case(s) rest only on company-reported claims and are not counted toward the grade.

Where it applies

Transformation type
  • T01 Digital
  • T05 ERP and core systems
Topic (business problem)
  • Legacy ERP and fragmented systems block execution
  • Cross-functional processes are slow and broken
  • Data cannot be trusted for critical decisions
  • Technology spending is growing without business returns
  • Competing transformation programs overwhelm resources
Function
  • Finance & FP&A
  • IT, ERP & Digital
  • Customer Experience & Support
  • Procurement & Strategic Sourcing
  • Risk, Compliance & Internal Audit
Starting situation
  • New initiative
  • In-flight initiative
  • Stalled or failing (turnaround)
Industry
  • Commercial Banking
  • Discrete Manufacturing
  • Electric Power Utilities
  • Grocery and Food Retail
  • Other (cross-industry)
Region
  • Africa
  • Latin America
  • North America
  • Oceania
  • Western Europe

Supporting and counter cases

Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026

Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.