Price the work. Make the value measurable.

Scope, availability, deliverables, duration and fees require a written proposal. Connected execution is a separate delivery scope. There are no published standard rates, online purchases or automatic subscriptions in this release.

Explore the scope before requesting a proposal

The illustrative scope index below combines five planning dimensions. Each dimension has a transparent 0–4 scope rating; the weighted result is 0–100. This is a discussion aid, not a calibrated effort estimator, validated benchmark or readiness score. Two enterprises with the same index can require very different work.

What belongs in the price

Setup + business scope + connector work + evidence processing + expert review + ongoing support. Each proposal should state included quantities, responsibilities, acceptance criteria, processing limits, change control, usage charges and a spending cap. Account for people, infrastructure and support as well as model costs.

Employee count, revenue and overall data volume provide business context. They do not alone establish effort or value. Price the teams and capabilities actually in scope, the evidence that must be processed and the controls that must operate. Revenue should not become an unexplained surcharge. Low maturity may reveal specific remediation work; quote that work explicitly rather than applying a blanket penalty.

Measure maturity and confidence separately

Review business intent, people, processes, applications, data, authority and responsible AI, resilience, and delivery economics. Record unknown, constrained, established or verified in operation for a stated scope, with dated evidence and a named owner. Unknown is not a zero score. Keep evidence confidence and unresolved blockers visible; an average cannot authorise a high-risk action.

KPIs that connect context to outcomes

KPI	Definition
Context coverage	In-scope entities with accepted definitions, owners and evidence ÷ all agreed in-scope entities.
Evidence freshness	Required evidence within its agreed review period ÷ all required evidence.
Semantic accuracy	Accepted entities and relationships in a representative reviewed sample; state sample size and uncertainty.
Discovery cycle time	Elapsed time from agreed start to the first owner-accepted context package; show review waiting time separately.
Decision traceability	Reviewed decisions linked to evidence and applicable authority ÷ decisions reviewed.
Trust-control coverage	In-scope control obligations with an implemented, exercised control ÷ all in-scope obligations; keep critical gaps explicit.
Delivery outcome	Workflow-specific quality, cycle time, exceptions, cost and recovery against an agreed baseline.
Unit cost	Fully attributed cost per accepted context package or successfully completed business outcome.

These are proposed measurement definitions, not reported customer results. Agree denominators, baselines, collection methods and acceptance thresholds before the pilot. Review speed and coverage alongside correctness, risk and human effort.

Request a scoped proposal · Explore Discovery Studio · Understand Contextual Trust