Clariti.Decide with confidence.

Field Guide No. 03 · First Edition 2026

The ERP Field Guide.

A working reference for the leader accountable for an ERP decision — sponsor, CFO, COO, transformation lead or programme director. The modules, the master data spine, the integration patterns, the controls fabric, the roles and the programme rhythm — and the five decisions that compound for the next decade.

12

modules, with their value streams

18

roles with decision rights

10

industry dial-ups

5

decisions that compound

Aligned to TOGAF Phases B and C, PMI Program Management, BABOK Strategy Analysis and COBIT APO.

Who this is for

You are about to sign an ERP contract, and the operating-model commitments inside it have not been written down.

Your programme is in configuration, and decisions are being made in a workbook rather than in a forum.

You have inherited an estate where nobody can produce a current integration catalogue.

The thesis, in one line

ERP is not a software selection. It is a structural commitment to how the business will run for the next seven to ten years — the chart of accounts, the org structure, the master data model, the integration spine, the controls fabric. The software is the smaller decision. The system of record is the operating model. Anything else is theatre.

What's inside

  1. 01The operating-model thesis
  2. 02The illusion stack
  3. 03Anatomy of a core system
  4. 04Twelve modules, twelve commitments
  5. 05Master data and the spine
  6. 06The integration layer
  7. 07Governance and controls
  8. 08Roles and decision rights
  9. 09Benefits and the ADR discipline
  10. 10AI and the ERP
  11. 11Five decisions that compound
  12. 12The full guide

§11 · Free preview

Two of the five decisions that compound. The rest of the guide is behind the form.

01

The chart of accounts & cost-centre hierarchy

The operating model in numbers. Owned by the CFO; reviewed by the COO; approved by the sponsor.

How the business will measure itself for the next decade. The segment dimensions — entity, function, region, product, project, customer; the account-number structure and depth; the cost-centre hierarchy and its alignment with the position hierarchy; the mapping rules that translate operations into ledger postings.

02

The master data ownership model

Who owns each class. Who can change structure. What the data governance forum's remit is.

For each master data class — customer, vendor, item, GL, position, asset, project, location — three decisions: who is the named accountable owner; who has authority to change structure versus authority to change records; and what the data governance forum looks like, who chairs it, and what its escalation path is.

Three more compounding decisions, and eleven sections, behind the form.

Read the full guide

Twelve sections. No charge.

Tell us where to send it and the guide opens immediately.

Move forward with confidence.

If you are planning a system migration, portfolio reset, or complex multi-vendor delivery, we can help you make the trade-offs, establish the governance, and build a way of working your team can sustain.