The Platform / Domains / Vendor Intelligence
Vendor Intelligence is the XOPS domain that continuously reconciles commercial, operational, risk, responsibility, and relationship evidence into one Vendor Position. Declared outcomes govern how that Position is evaluated, while evidence remains attributable to the systems that produced it.
4
Constituent positions
16
Principal entity types in the subgraph
18
Pre-built Vendor Intelligence outcomes
The architecture, end to end
Systems of Record
ERP · S2P · CLM · SAM · VMS · Risk · HRIS · Identity · Benchmark feeds
Commercial Procurement Subgraph
Normalize · Resolve · Relate · Version
Vendor Position
Commercial · Operational · Risk and Responsibility · Relationship
Declared Outcome Evaluation
Detect drift · Determine gap · Recommend action
Published Surfaces
Briefings · Portfolio views · API · MCP · BI · Existing procurement tools
What Vendor Position contains
Commercial, operational, risk and responsibility, and relationship evidence converge into a continuously maintained Vendor Position for each vendor and across the supplier portfolio.
Commercial Position
Spend · Price · Contract · Entitlements · Usage · Benchmarks · Alternatives
Operational Position
Commitments · Co-terms · SOWs · Lead times · Service performance · Delivery obligations
Risk & Responsibility Position
Concentration · Sole source · Financial health · Security · Compliance · Labor · ESG
Relationship Position
Owner · Sponsor · Vendor contacts · Sentiment · Coverage · Escalation
The principal entity types
How the graph is assembled
Before evidence can inform a decision, it has to be resolved into a common commercial model. This is the normalization layer beneath the Vendor Position.
Identity
Resolving the same vendor referenced differently across ERP, S2P, and CLM into one identity.
Identity
Mapping subsidiaries, resellers, and brands back to the commercial entity that actually holds the contract.
Classification
Every spend line normalized to a common taxonomy, so concentration and overlap can be evaluated across systems.
Structure
Master agreements, amendments, order forms, and SOWs resolved into one contract structure per vendor.
Structure
Renewal dates, commitment floors, and co-terms linked across related contracts so a change in one is evaluated against the others.
Entitlement
What was purchased, mapped to what it entitles, so usage can be evaluated against the actual contract terms.
Relationship
Business owner, executive sponsor, and vendor contact resolved and linked to the entities they're accountable for.
Context
Linking a vendor's footprint to the device, software, and workplace domains it touches.
History
Every entity and relationship versioned over time, so the Position at any past moment can be reconstructed.
The operating loop
Read evidence from connected systems.
Resolve identity and classification conflicts.
Update the Vendor Position.
Evaluate it against the declared outcome.
Detect drift, missing evidence, or an opening decision window.
Publish updated views and the recommended action.
Preserve evidence lineage and prior state.
The loop does not stop when a briefing is published.
It runs continuously, so the Position never has to be rebuilt from scratch.
Evidence, governance & control
Vendor Intelligence is non-destructive by default. It publishes synthesized state and recommendations to Procurement, Finance, and executive consumers. External actions require approved controls. Every artifact remains attributable to its source and reproducible on demand.
Least privilege from day one. Standard protocols, standard auth, no proprietary agents.
Every fact in the Position is linked back to the system and record that produced it.
Every value carries how current it is and how much the model trusts it, not just what it is.
Write-back is scoped, policy-gated, and enabled only where your team has signed off.
Any recommendation can be reconstructed: what evidence produced it, and when.
XOPS prepares the position. Procurement owns the decision, the negotiation, and the commitment.
Restores prior attribution, KPI, and benchmark state when evidence needs to be corrected or contested.
The Position at any prior date can be rebuilt from the versioned subgraph, for audit or dispute.
The outcome library
Organized around six categories of decision, each drawing from the same Vendor Position.
1
Renewal approach generation, activated 120, 60, and 30 days out with benchmark, alternates, and negotiation posture already assembled.
2
Ownership and escalation coverage, account health, contact integrity: surfaced before a gap becomes a renewal risk.
3
Category overlap, vendor proliferation, and spend-at-risk, rolled up for finance, procurement, and executive review.
4
Concentration, sole-source dependency, financial and security risk, compliance and responsible-sourcing obligations.
5
Benchmark drift, pricing variance, usage-versus-entitlement gaps, and the modeled counter before the conversation starts.
6
A vendor's footprint mapped across device, software, and workplace domains, so a vendor decision accounts for what else depends on it.
Renewal
Pre-negotiation
Activates 120, 60, and 30 days before renewal. Pulls benchmark drift, concentration risk, alternate vendor mapping, and category position into a negotiation pack, complete with leverage profile, talking points, and walk-away terms, before procurement opens the conversation.
Coverage
Periodic
Continuous sweep across the vendor portfolio: relationship health scoring, account coverage, contact integrity, escalation readiness. Surfaces vendors where coverage has degraded before the relationship matters, not when it's already broken.
Portfolio
Continuous
Continuous portfolio-level rollup of spend-at-risk, category concentration, benchmark variance, and cross-domain dependencies. Publishes one operational view for finance, procurement, and executive, refreshed as the data underneath changes.
Illustrative scenario
How the reconciliation loop actually runs
Nobody had to notice the departure.
The Position noticed it for them.
Outputs and surfaces
The Vendor Position is the maintained state. Every surface below is a view published from it, not a separate system holding its own copy of the truth.
Procurement briefing
Executive portfolio view
Finance exposure model
Risk & responsibility view
Ownership map
API
MCP / AI surface
Existing BI & procurement tools
