Explainability
↑ higher betterAbility to surface why a model made a recommendation.
Pick any two of 10 dimensions. Vendor position reflects evidence-weighted scoring; halo radius reflects confidence.
Set your buyer context. With simulation on, vendor positions shift in real time to reflect how scores read against your industry, region, and implementation profile.
The Domain Map is not a quadrant verdict. Every position is the output of an evidence-weighted score on the two dimensions you choose. Use the keys below to read it like an analyst would.
Each dot is one vendor. Position = (X dimension score, Y dimension score). Amber dots are AI-native; blue dots are incumbents or AI-augmented vendors.
The faint halo is confidence. A tight halo means many corroborating evidence sources; a wide halo means the score is real but should be read as approximate.
Both axes run 0–100. Scores are normalised per dimension so a 70 on AI sophistication means the same percentile as a 70 on enterprise readiness. Quadrant labels (Leaders / Visionaries / etc.) are reference only — they shift every time you change axes.
Public docs, customer references, product trials, filings, repo activity, hiring signals, and structured vendor submissions are continuously ingested into a per-vendor evidence graph.
An LLM scoring pipeline converts evidence into a 0–100 score per dimension, with a rationale and an evidence count. Higher evidence volume + agreement = higher confidence (0–100).
On the map, position is raw. In Buyer query and the Explain panel, scores are reweighted by your context (priority, IT depth, segment) so the same data answers your question.
Formula (weighted fit): Σ (score/100 × weight × confidence/100) ÷ Σ weight × 100. Click any vendor on the map to see this calculation expanded for that vendor.
Depth of native AI: model quality, explainability, automation.
Ability to surface why a model made a recommendation.
How much of the planning loop runs without human intervention.
Depth of ML/AI in forecasting, optimization, and autonomous decisioning.
Commercial maturity, ecosystem, momentum, pricing.
Partner network, marketplace, integration breadth.
Pace of meaningful product release and roadmap execution.
Implementation, time-to-value, customer success, support.
TCO relative to delivered value for mid-to-large enterprises.
How quickly an average enterprise gets a working deployment.
Inverse of implementation complexity and required internal expertise.
Product architecture, depth, and engineering quality.
Modern composable architecture, API maturity, scalability.
Security, observability, governance, and operational maturity.