01 · Scope
Choose a bounded pilot
Define the product, claim types, evidence sources and independent reviewers. Agree on access requirements and which content may be published.
Pilot and pricing
Start with a review process worth improving.
Agree on the claim set, reviewers, publication destination and success criteria before committing to a wider rollout.
02 · Configure
Prepare the workspace
Set roles, register source text and confirm the review policy. Any identity or CMS connection is configured and accepted for your environment.
03 · Evaluate
Measure the result
Compare review time, correction effort and unsupported approvals with your current process. Decide on continuation from the recorded results.
Commercial terms
A written scope and a clear price.
Pricing is quoted for the agreed pilot. There is no self-service subscription checkout or automatic usage billing in the current product.
The proposal should specify
- Workspace scope and participants
- Onboarding and integration work
- Provider usage and review responsibilities
- Support arrangements and pilot duration
- Acceptance criteria, export and exit arrangements
Dedicated infrastructure, residency commitments, managed operations and contractual service levels require a separate agreement and delivery evidence.
Inspect the workflow before the conversation.
The public walkthrough uses synthetic evidence and does not require customer data. The capability register distinguishes available workflow controls from integrations requiring configuration and services not currently offered.
Walk through an example →Start with one claim
Bring the statement. Bring the evidence.
Scope a pilot around a real review process, named reviewers and an agreed publication destination.