DPG Labs · The Framework

A role-based map of procurement technology.

The Principle
"If the solution were removed, what would stop working? That answer reveals its true role in the system."

Each vendor is assigned to a single layer based on what the organisation fundamentally relies on it to do. This shifts focus from what vendors sell to what the system needs. It forces clarity in a world where AI is blurring capabilities, and ensures every vendor is placed once, based on the role they actually perform.

This is the modern, AI-native procurement architecture.

Strip away the users and the ERP beneath — focus on the procurement layer.

Each block has one role — defined by what the system relies on it to do.

And the vendors take their place — the market map.

Business user
Procurement
AI agents
Suppliers
Leadership
Core functionality
Sourcing & category mgmt
Contract lifecycle (CLM)
Supplier mgmt (SRM) & onboarding
Procure-to-pay (P2P)
Procurement enablement
Value mgmt & finance
AI, agentic productivity & autonomous work
4·Process Execution
Where transactions happen — sourcing events, contracts, P2P.
Coupa
SAP Ariba
Ivalua
Jaggaer
Icertis
Analytics layer
Spend analytics
Benchmarking
AI recommendations
Decision support
2·Decision Intelligence
Analytics, AI copilots and agents that turn data into decisions.
Sievo
Tropic
Pando
Globality
Data platforms and repositories
Internal data
Master & spend data
Taxonomy & integration
External data
Supplier risk & ESG
Market & price signals
1·Data Foundation
The clean, classified, connected data layer everything else relies on.
5·External Intelligence
Outside-in signals — supplier risk, ESG, market and price intelligence.
Stibo
Reltio
Tealbook
EcoVadis
Sayari
Mintec
Workflow & orchestration
Intake, routing & system of record across the stack
3·Workflow Control
Intake, orchestration and policy that route work end-to-end.
ORO Labs
Zip
Levelpath
Core ERP
SAP · Oracle · Workday · finance systems
Boundary clarity · what each role is not
Two Types of Overlap

Embedded capabilities vs adjacent capabilities.

The problem is not that vendors have multiple features. The real issue is two fundamentally different types of overlap.

An embedded capability exists purely to enhance the vendor's core role — a CLM platform managing contract data and generating insights, all in service of contract process execution.

An adjacent capability extends into a nearby use case without redefining the product — a spend analytics platform that also surfaces contract expiry dates remains fundamentally an analytics tool.

Vendors are classified by their primary role only. Embedded capabilities strengthen it. Adjacent capabilities extend it without changing it.