DOC ROI · PROCUREMENT COMPASS · EVIDENCE + ABCD + SPO + S

Evidence becomes demand, purchase orders and supplier service control.

Start with evidence already created across the DOC ROI journey. Connect Buyer Persona, Marketing-to-Purchase, RFM and NPS to the ABCD layer calculated inside Compass, convert observed demand into supplier purchase plans, and finish with purchase orders, SLA requirements, contracts and management indicators.

Session starts emptyComplete 266-customer ExampleMarketing → Sales → PurchaseUnknown ≠ 0CSV + PDF onlyHuman approval required
SESSION
Empty session Load Example or import your own DOC ROI CSV evidence.

00 · Evidence & Customer Context

Procurement starts with evidence already created upstream. Load the three foundation files below. If you want the customer-level SPO working layer, add RFM and NPS; ABCD is calculated inside this pill from the loaded commercial and product evidence.

REQUIRED ENTRY
INPUT GATE · OPEN

Load Marketing → Purchase and Strategic Goals & Objectives. Buyer Persona / 4P evidence is recommended. Add RFM and NPS to calculate the customer-level SPO working layer.

OPEN
Required · Commercial evidence

Marketing → Purchase Handoff

Customer/order evidence with customer key, UTM/4P, product, quantity, price, benefit, conversion and handoff status.

Get source ↗
Required file not loaded.
Required · Governance evidence

Strategic Goals & Objectives

Objectives, budget evidence and evidence gates that explain what Procurement must protect and measure.

Get source ↗
Required file not loaded.
Recommended · Customer context

Buyer Persona / 4P Evidence

Need, trust and 4P keyword evidence used to interpret product, service and procurement requirements without inventing demand.

Get source ↗
Recommended file not loaded.

To calculate the customer-level SPO working layer

Load the same stable customer_key in RFM and NPS. ABCD is generated here from the loaded commercial/product history, so no separate ABCD file is required.

RFM + NPS
SPO input · Behaviour

Dynamic RFM

Customer behavioural intelligence. Compass reads the stable customer key and the supplied cognitive/RFM evidence.

Get source ↗
RFM file not loaded.
SPO input · Relationship

NPS

Customer relationship/satisfaction evidence. Survey history is consolidated to the latest valid customer record for the SPO working layer.

Get source ↗
NPS file not loaded.
Loaded customer / 4P evidence interpretation
No Buyer Persona evidence loaded.
Customer-level evidence

Loaded evidence snapshot

This block validates the stable customer keys across Marketing → Purchase, RFM, NPS and the ABCD layer generated inside Compass.

EMPTY
No evidence loadedUse Example or import your own upstream CSV files.

Objective alignment

Source governance evidence is preserved as loaded. Compass adds only the Procurement reading needed to connect it with purchase, SLA and control.

Objectives not loadedImport the Strategic Goals & Objectives CSV or use Example.

01 · ABCD Product / Offer Intelligence

Compass uses the evidence already loaded to do most of the ABCD work. Revenue, volume, current purchase, 4P offer, transaction frequency and repeat evidence are derived automatically. You only complete the economic or strategic evidence that does not exist upstream. NPS is shown beside the result for customer context, but it is not used to calculate ABCD.

What Compass derives automatically

The user should not re-enter evidence that already exists in Marketing → Purchase or RFM.

Customer / source IDProduct + commercial offer / 4PRevenue + unitsPurchase frequency + repeat evidenceRotation / usageRFM contextNPS contextABCD factor A=4 · B=3 · C=2 · D=1

What may still need configuration

Variable cost per unit when the commercial file does not contain usable cost evidence, plus cross-sell potential, upsell potential and strategic relevance. Missing evidence remains UNKNOWN and blocks a definitive ABCD class. The Example supplies explicit classroom assumptions for these fields.

ABCD scoring model
Complete only the evidence that is not already upstream
Product / offer4PVariable cost / unit €Cross-sell potential %Upsell potential %Strategic relevance /100Evidence status
Load Marketing → Purchase evidence to create the configuration rows.
ABCD waiting for evidence. Load the upstream files or use Example.
Methodological boundary. ABCD is the product / service economic-intelligence layer. RFM and NPS remain separate customer-intelligence layers. RFM transaction frequency may be reused as source evidence for purchase frequency / repeat behaviour, but RFM score and NPS do not enter the ABCD score. Unknown is never converted to zero.

Customer-level ABCD classification

One row per customer. The purchase keeps its RFM and NPS context, while the ABCD column states what that product / offer consumption represents economically and strategically.

ABCD classification not availableLoad evidence and complete the missing ABCD configuration.

02 · SPO Customer Intelligence & Demand Planning

This is the SPO build point. Before any priority is calculated, Compass checks the three customer-level sources required by the operating model: RFM, NPS and the ABCD customer intelligence created in the previous step. Only when the customer keys match and all three layers are usable does the SPO calculation become available.

SPO + DEMAND
SPO model

One customer. One traceable priority record.

The formal structure remains SPOi = CCi · ABCDi · NPSi. In this Procurement implementation, the available RFM-derived customer factor feeds the operational CC layer, ABCD contributes product/service relevance and NPS contributes relationship evidence. The result is a working priority used to protect demand and define supplier service requirements. This operational layer does not redefine the formal KAI·ROI architecture.

SPO source validation

Confirm the three customer intelligence layers

If a source was already loaded upstream, Compass shows it as ready. Otherwise, load it here. ABCD may be imported as a CSV or consumed directly from the classification created in Step 01.

PENDING
PENDING

Dynamic RFM

Behavioural/customer evidence using the same stable customer_key.

Get RFM ↗
RFM pending.
PENDING

NPS

Relationship/satisfaction evidence consolidated to one current customer record.

Get NPS ↗
NPS pending.
PENDING

ABCD Product Intelligence

Use the customer-level ABCD created in Step 01 or import a compatible ABCD customer CSV.

ABCD pending.
Waiting for RFM, NPS and ABCD.
Load and align the three sources to enable the calculation.

03 · Purchase Planning by Supplier

Map the ABCD demand portfolio to the suppliers, components and services required to deliver it. Supplier plans are ordered by SPO-informed service priority before execution urgency, while quantities remain driven by demand, stock, MOQ and lead time. Example auto-loads a complete supplier configuration; real files may leave these columns blank and Procurement completes them here.

PROCUREMENT
No suppliers identifiedAdd a supplier manually or load Example.
Purchase plan not availableCommercial demand and at least one supplier are required.

04 · Purchase Orders

Compass creates one purchase order per identified supplier. Each PO carries the ABCD exposure and the customer-level SPO service priority that Procurement is protecting. Every PO remains conditional when critical evidence is missing and is printable as a clean PDF-ready document.

OUTPUT 1 · PO
No purchase orders yetComplete the supplier mapping and demand plan.

05 · Service-Level Agreement + Signature-Ready Contract

Each purchase requirement creates a service requirement. Compass tightens supplier-specific SLA targets as the SPO service priority of the protected customer demand increases, then builds a personalised agreement that both parties can review, print and sign.

OUTPUT 2 · SLA + CONTRACT

Buyer identity

Governance

Measurement & remedies

SLA source. Compass keeps the core SLA management logic — replenishment lead time, customer delivery, order acceptance, stock availability, returns, incident response and customer rating — and adds Procurement gates such as OTIF, documentation, traceability, incoming quality, inventory accuracy and breakage/loss. Higher customer-level SPO service priority tightens working SLA targets continuously; it does not create automatic penalties. Actual performance remains unknown until execution evidence exists.
SLA portfolio not generatedPurchase plans are required first.
Contracts not generatedComplete supplier and buyer data to create signature-ready drafts.

06 · Procurement Control Tower

Final management view connecting customer-level RFM + NPS + ABCD, operational SPO priority, demand, purchase commitments, supplier exposure, cash, lead time, evidence quality and SLA readiness.

OUTPUT 3 · MANAGEMENT

ABCD management reading

—

Procurement gates

—
METHODOLOGY AT THE END OF THE JOURNEY

DIIIP turns commercial evidence into a repeatable procurement decision.

Purchasing starts with customer-demand evidence, not with the supplier. The journey structures that evidence into ABCD intelligence, demand planning, purchase commitments and measurable service governance.

D
Data

Marketing → Purchase customer/order evidence, strategic objectives, customer-level RFM, NPS, ABCD, stock, supplier terms and service evidence.

I
Information

The CSV contract structures product/offer demand, supplier scope, inventory constraints and customer promise.

I
Intelligence

ABCD classifies product intelligence; RFM and NPS complete the customer evidence; Compass builds an operational SPO working list and translates demand into purchase requirements by supplier.

I
Insights

The model reveals which offer classes, suppliers, lead times, costs and evidence gaps are driving risk.

P
Personalization Actions

Human governance approves purchase orders, supplier conditions, SLA commitments and corrective actions.

KAI·ROI EQUATION · CUSTOMER EQUITY

Procurement evidence can feed the KAI·ROI operating layer without changing the formal equation.

This Compass does not redefine KAI·ROI. ABCD, demand, supplier service and purchase evidence are operational assets that can later support Customer Equity, SPO and ROI analysis.

The formal KAI·ROI v1 structure remains sovereign. Unknown data remain unknown, and operational implementation never substitutes the formal architecture.

EXECUTIVE RESOURCE

The KAI·ROI Equation Book

A concise guide to understand how data, ROI, Customer Equity and strategic decisions connect inside the DOC ROI ecosystem.

Inside the document:
  • What the KAI·ROI Equation is
  • Why Customer Equity matters
  • How ROI becomes a decision system
  • Why operational data must be monetized with purpose
Access the KAI·ROI Equation →