Price the evidence review around the workflow.
Planisphere is priced and quoted by what must be proven, what systems are in scope, what sources can be preserved, and who needs to review the result. Start with one blocked AI workflow, then expand only when the evidence record is useful.
Commercial packages.
Every engagement begins with a scoped claim: the workflow, buyer or compliance audience, source systems, approval gate, and evidence already available. The output is a review-ready record; it is not a certificate, legal conclusion, regulatory endorsement, or guarantee of savings.
| Package | Best for | Deliverable | Pricing |
|---|---|---|---|
| Phase 0 Evidence Scope1 workflow · first blocker | A buyer, compliance lead, counsel, or investor is asking what evidence exists. | Workflow map, source inventory, claim boundary, acceptance gate, and next-step evidence plan. | Quoted |
| Workflow Evidence Report1 workflow · full record | A high-stakes AI workflow needs internal or external compliance review before approval. | Graph rows, harness readouts, hashes, source links, supported statements, blocked statements, and review instructions. | Quoted |
| Vendor Comparison3-5 systems · same battery | A team is choosing between AI vendors or consolidating overlapping tools. | Comparable evidence table showing behavior, source coverage, unresolved gaps, and decision risks. | Quoted |
| Drift Witnessbaseline · re-check · delta | A model, workflow, policy, or integration changed and the team needs to show what moved. | Baseline record, re-run record, delta note, blocked claims, and re-check cadence recommendation. | Quoted |
| Program Evidence Cadencemulti-workflow · repeatable loop | A regulated team needs a recurring evidence loop across departments, vendors, or systems. | Operating cadence, route map, repeat harness, internal status readouts, and review-ready records. | Custom |
| High-Security Environmentrestricted data · special handling | Evidence work must be scoped for air-gapped, restricted, or customer-controlled infrastructure. | Engagement-specific operating plan. Availability and handling depend on requirements, access, and approvals. | Custom |
What changes the quote.
More systems, integrations, and approval gates require more graph rows and review paths.
Logs, evals, policies, questionnaires, sample outputs, and run records change evidence depth.
Source coverage, permissions, output quality, drift, handoff, and human approval each add checks.
A one-time report is different from a recurring re-check loop with delta readouts.
The right first buy is usually not a platform migration. It is one blocked workflow, one evidence record, and one clear decision about what can proceed.