Pricing / Pilot to deployment
Prove the workflow.
Then agree the right scope.
Discuss the fit first. If there is a useful starting workflow, agree a paid validation pilot before considering an annual deployment. Scope and fees are agreed in writing.
Quote-led pricing. Scope and fees agreed in writing. No automatic pilot-to-annual rollover.
Choose the stage, then define the scope
A focused start.
A deliberate expansion.
Explore the paid pilot and the two annual deployment paths. These describe the scoping conversation—not a fixed bundle of unconfirmed entitlements.
Paid validation pilot
Validate the workflow before the annual commitment.
Begin in Shadow Mode with one recurring audit or assurance exception workflow, customer-reviewed cases and explicit success criteria. Inspect resolution quality, outstanding reviews and actual reviewer effort before making a separate decision about human-approved live use.
- Commercial basis
- A scoped pilot fee, agreed in writing before the pilot starts.
- Scope to agree
- One represented entity, agreement coverage, approved alternatives and evidence requirements, source mappings, reviewer scope and cases to validate. Continuing-assurance internal acceptance is a separately agreed pilot scope, not automatically included or activated.
- Evidence to review
- Shadow evaluation records, decision reports and a findings review covering incorrect progress, unnecessary escalations, missing evidence, review effort and unresolved disagreements.
Browsing these options does not select a plan, submit a request or activate a workspace. Your written proposal confirms the scope, fees and services.
What shapes the quoteThe 30-day paid validation pilot
Agree what good looks like.
Then inspect the evidence.
Choose one recurring vendor DPA workflow and its connected data-risk terms. Start in Shadow Mode with agreed cases and criteria. Review the findings before separately approving any human-controlled live sending path.
- 01 / Before the pilot
Define the baseline
Agree the represented entity, policy, decision owners, customer-reviewed cases and success criteria. Confirm data handling and the conditions that must hold an external action.
- 02 / During validation
Review the pilot evidence
Receive Shadow evaluation records, readable decision reports and a findings review with your specialists. Review incorrect progress, unnecessary escalation, evidence gaps and measured reviewer effort, with sample counts and unresolved disagreements.
- 03 / Before expansion
Make a written decision
Compare findings with the agreed criteria. Approve live use only after current release evidence, owners and the destination are validated. Confirm any annual scope separately. There is no automatic annual commitment.
What shapes your quote
Scope the governed work.
Not just the logins.
Professional and Enterprise are annual platform agreements. Included activity, user capacity, connections and services are documented before activation.
The written order records allowances, limits, overage treatment, implementation fees, renewal terms, taxes and service commitments.
01Negotiation activityIncluded agreements, analyses and rounds; the measurement period, limits and any agreed overage treatment.
Make the counting rules explicit, including revised drafts, retries and any excluded activity. Do not assume an unlimited allowance.
02Agreement and authority coverageVendor DPAs, connected schedules, approved playbook packs and the decision workflows to configure.
Identify approved rule conditions, package dependencies, evidence requirements and current Legal, Privacy, Security and TPRM decision scope for the first workflow. A department label does not confer approval rights.
03People, agents and entitiesUser capacity, represented legal entities, rollout footprint and any registered-agent scope.
Agent access is limited to supported actions and separately configured grants. Commercial access never substitutes for a current contractual-authority decision.
04Connected systemsMailbox, document, TPRM or risk-source connections and any configured CLM handoff.
Agree the exact exchange, tenant permissions, mappings, validation and recovery responsibilities. Provider-specific availability is confirmed during scoping.
05Security and serviceIdentity, evidence, data handling, residency requirements, support and service levels.
Confirm the deployment-specific commitments with your reviewers. A pricing description is not a certification, data-residency guarantee or agreed SLA.
06ImplementationOne-time onboarding, playbook configuration, integration work and validation, agreed separately.
Record what is included in the platform fee, what is separately charged, approved rules and mappings, reviewer/delegation scope, dependencies and customer acceptance criteria. Configuration is not permission to send.
Commercial access ≠ contractual authority
A larger deployment does not mean fewer controls.
A plan defines the service you buy. Your approved policy determines which contractual actions may progress. Neither an upgrade nor an agent credential bypasses the current package, evidence and decision-rights checks.
Current authority
Connected terms, evidence and responsible decisions remain part of the evaluation.
Explicit activation
Live vendor sending requires customer-approved policy and scope, named human approval and a fresh exact-content/destination check. A plan purchase does not activate that authority.
An exact-action check
DataHalt-governed external actions need a valid permit and a fresh gateway check.
Acceptance remains human-controlled. Ready for signature is not corporate signing authority. Unsupported lifecycle actions remain blocked.
Inspect the action boundaryBring your reviewers into the conversation
The scope should stand up to scrutiny.
Review what the product does, what your deployment needs and which connections must be proven before treating them as live.
Financial services, insurance and other regulated teams can frame that first workflow around their existing third-party-risk decisions.
Find your operating contextBefore you commit
Questions from your buying team.
Clear distinctions between an assessment, a paid pilot and an annual deployment.
Does a pilot establish that our GRC controls are effective?
No. If customer-control alignment is included in the agreed scope, validate one defined control, representative cases and the evidence your independent reviewers need. Recorded assessments are customer judgements, not certification or proof of production operation. Your company must separately accept the control evidence and approve any live deployment.
Inspect control-testing limitsWhy is pricing quote-led?
The commercial scope depends on the negotiation activity, agreement coverage, entities, connections and service requirements you agree. Professional and Enterprise are annual platform agreements. The signed order records fees, allowances, limits, overages, implementation, renewal terms and taxes before activation.
See what shapes the quoteIs the Authority Audit the same as the paid pilot?
No. The Authority Audit examines a completed negotiation and the limits of its historical record. The paid pilot validates an agreed operating workflow using your vendor agreements. Neither automatically approves a wider deployment or activates external sending.
Explore the Authority AuditWhat happens after the 30-day pilot?
Review the results against the agreed baseline and decide whether to progress. A pilot does not automatically roll over into an annual term. Any annual deployment, implementation work or expanded scope requires written agreement.
Review the pilot checkpointsDo we need to replace our CLM or buy a connector first?
No. Scope the workflow and required exchange first. Your CLM can remain the system of record and retain signing authority. Provider design guides describe adapter paths, not live, native or certified integrations; each connection needs customer-specific configuration and validation.
Inspect connection requirementsCan our enterprise agents use the authority layer?
Registered agents can request supported counterproposals where included in the agreed deployment. Scoped credentials and grants do not replace current policy, package, evidence and execution checks. Live vendor sending requires human approval and a fresh exact-content/destination check. Position and final-package acceptance remain human-controlled; unsupported lifecycle actions remain blocked.
See the people and agent boundaryHow are our contracts and model-provider terms handled?
Review the deployment’s data boundary, retention, model-provider terms and security evidence before sharing live material. Do not infer provider training, residency or zero-retention guarantees from a plan label. Optional structural learning is a separate customer choice.
Review security and data handlingStart with a scope, not an assumption
Bring the workflow you want to govern.
A 15-minute conversation about one recurring vendor workflow, the teams involved and whether a scoped pilot is a fit. No contract upload needed for the first conversation.
Deployment scope. These workflows are available for pilot validation, not presented as verified live capabilities. Confirm the enabled scope and current release evidence before live use. Examples are illustrative, not customer outcomes or permissions. Live vendor responses require human approval and a fresh check of current authority, exact content and destination. A permit or wording approval alone is not permission to send.