Services & pricing

Decision governance for the commitment ahead.

Choose a defined service for one consequential decision, connected project decisions, external requirements or a recurring governance workflow. Scope, deliverables and fees are agreed before work begins.

Start with a brief, non-confidential summary.

Four defined engagements

Start with the decision
you need to govern.

Choose a service to inspect its scope and a representative output. Each engagement is scoped separately.

View selected explanation ↓

One fixed example. Four explanatory views. Changing a service never changes the recorded disposition.

01 / Decision Review

A reconstructable basis
for one commitment.

When it fits. A consequential choice needs its evidence, unresolved tensions and authority boundary made explicit before commitment.

What you receive

  • Evidence and contradiction review
  • A Decision Basis Record and executive readout
  • Authority boundaries and reconsideration triggers

What you bring

The decision, its stakes, available evidence, accountable owner and commitment condition.

Authority & scope. Your accountable human retains decision authority. The engagement provides a bounded basis; it includes no approval or guaranteed outcome.

Representative output

Decision Basis Record

SYN-DBR-01 v1.0

Synthetic example — no client matter or live authorization.
SYN-LAUNCH-01 v1.0 · initial phase · fictional as-of 14 Oct 2026

Decision

Whether to authorize the phased launch within the stated scope and concurrence conditions.

Basis

E1–E4 evidence lines; A1 resource availability assumption. Working records retained during HOLD.

Tensions

C1 · Resolved by dated scope/funding reconciliation; history retained.

C2 · Unresolved: supplier mobilization unverified. Bounded to the launch dependency.

Authority

Illustrative program sponsor records HOLD, subject to launch scope and required concurrence.

Inspect the complete specimen →

Brief, non-confidential summary only. Opens an inquiry draft below.

02 / Project & Program Decision Review

Make connected decisions
and dependencies visible.

When it fits. Investment, supplier, scope or delivery decisions depend on one another and need clear owners and escalation conditions.

What you receive

  • Linked decision records and dependencies
  • Accountable owners and escalation conditions
  • Reconsideration triggers across the agreed scope

What you bring

The connected decisions, dependencies, existing owners and approval conditions.

Authority & scope. The review does not replace a PMO, scheduling, cost control or project execution. Accountable decision owners retain authority.

Representative output

Linked decision records

SYN-LINK-01 v1.0

Synthetic example — no client matter or live authorization.
SYN-LAUNCH-01 v1.0 · linked decisions · fictional as-of 14 Oct 2026

D–01 · LaunchHOLD remains recorded.Owner: program sponsor
D–02 · Supplier readinessDated crew and mobilization evidence required.Owner: supplier lead
D–03 · ReconsiderationDepends on updated C2 and required concurrence.Owner: review lead → sponsor
Dependency

D–01 cannot be reconsidered on an unchanged basis. C2 remains unresolved and bounded to launch.

Escalation

If supplier evidence changes the launch scope, record the change and return it to the accountable owner before a new recommendation.

Inspect the complete specimen →

Brief, non-confidential summary only. Opens an inquiry draft below.

03 / Governance Translation

Bring requirements into
the decision’s working basis.

When it fits. Named policy, standards, regulatory or contractual requirements need to be traced to a bounded decision and the evidence needed to review it.

What you receive

  • A versioned requirement-to-control-to-evidence map
  • Source and applicability context
  • Unresolved interpretations and responsible owners

What you bring

Source documents, versions, intended applicability and the rightful source authority.

Authority & scope. This service does not provide legal advice, certification, an audit or a conformance determination. Interpretation questions remain visible for the proper authority.

Representative output

Requirement → evidence map

SYN-MAP-01 v1.0

Synthetic example — no client matter or live authorization.
SYN-LAUNCH-01 v1.0 · fictional source SYN-LAUNCH-CONDITIONS v1.0, initial phase only.

SYN–R01 · Confirm launch resourcesProposed check: obtain dated availability evidence before reconsideration.
Evidence: E3 supplier readiness claim

C2 unresolved. Mobilization and crew availability are not verified.

SYN–R02 · Record concurrenceProposed check: sponsor review requires applicable concurrence.
Interpretation remains open

Required concurrence scope to be confirmed with the rightful source authority.

Inspect the complete specimen →

Brief, non-confidential summary only. Opens an inquiry draft below.

04 / Decision Governance Design

Define who may decide,
and under what conditions.

When it fits. Recurring approvals have unclear roles, exceptions or stop conditions and need a bounded governance workflow.

What you receive

  • An authority model and review gates
  • Exception paths and reconsideration triggers
  • Acceptance-test specifications for the agreed workflow

What you bring

The current workflow, authority roles, recurring exceptions and required operating boundaries.

Authority & scope. Production software, live controls and integrations are excluded unless separately qualified and agreed. A design is not an operating authorization.

Representative output

Authority & gate model

SYN-GATE-01 v1.0

Synthetic example — no client matter or live authorization.
SYN-LAUNCH-01 v1.0 · SYN-GATE-01 v1.0 · proposed model; no implemented control.

G1
Basis review · program review leadCheck E1–E4, retain A1, document C1 and bound unresolved C2.
G2
Human Authority · program sponsorRecords HOLD within launch scope and applicable concurrence conditions.
↺
Exception & reconsiderationChanged scope or missing evidence returns to the review lead. No automatic release from HOLD.
Test case

Given C2 remains unverified, completing the explanation must never display a launch authorization.

Inspect the complete specimen →

Brief, non-confidential summary only. Opens an inquiry draft below.

Scope & fees

A defined engagement.
A written proposal.

Every engagement is individually scoped and quoted. Fees reflect the work required for your decision, evidence and governance context.

01Decision scope

The decisions, boundaries and consequences in scope.

02Evidence workload

The volume, readiness and examination of the evidence.

03Governance complexity

Authority, dependencies and applicable requirements.

04Delivery requirements

The agreed outputs, timing and handling needs.

What your proposal establishes

Outputs, exclusions, your responsibilities, authority boundaries, acceptance criteria, timing and fees.

Payment, expense, change and termination terms are addressed in the agreement.

From inquiry to engagement

  1. Send a brief, non-confidential summary of the decision or workflow.
  2. We review fit and identify the information needed to scope the work.
  3. Agree the written proposal and appropriate handling channel before work begins.

Delivery may take the form of a Diagnostic, Sprint, Controlled Pilot or Bounded Implementation, as agreed in scope. These are optional formats, not a purchasing sequence. An inquiry creates no engagement or authorization.

Inspect the basis

Follow the same case in detail.

Inspect the complete client walkthrough, then follow its evidence, authority and next actions into the same Cockpit case.

Explore the example · seven threads, one recorded disposition

Synthetic example — no client matter or live authorization. Playback reveals a pre-authored account; it does not decide an outcome.

Seven traceable threads through reviewFour evidence lines, one assumption, one resolved contradiction and unresolved contradiction C2. The recorded Human Authority disposition is HOLD. Line organization does not grant authority.
  • E1 Scope baseline
  • E2 Funding confirmation
  • E3 Supplier readiness claim
  • E4 Applicable requirements
  • A1 Resources remain available
  • C1 Scope / funding mismatch
  • C2 · Mobilization unverified

Inputs. E1–E4 are distinct evidence lines; A1 remains an assumption. C1 and C2 begin as contradictions. Organizing them establishes neither correctness nor agreement.

Examined basis. C1 is resolved by the illustrative scope/funding reconciliation dated 14 Oct 2026; its identity and history remain. C2 stays unresolved and bounded to the launch dependency.

Recorded disposition. The illustrative program sponsor records HOLD within launch scope and applicable concurrence conditions. Supplier evidence, review and reconsideration are required. No launch is authorized.

SnapshotState and conditions at a recorded point. Working records exist before Human Authority review and remain during HOLD.
Decision Basis RecordEvidence, tensions, governing context and authority status. C1 keeps its history; C2 keeps its boundary and effect on the next action.

A clearer, bounded basis, not a guaranteed outcome. The canonical 6+1 Method defines Frame → Derive → Contradict → Reconcile → Commit → Extract, with +1 Reinsert governing adaptation.

Start a conversation

Bring the decision.
Define the work.

Tell us what is being decided, why it matters now and what would be useful to leave with.

We review fit and the information needed for scoping, then agree the proposal and handling channel before work starts.

Send a brief, non-confidential summary only. Confidential, regulated, privileged, proprietary, security-sensitive or client-controlled material requires a separately authorized channel. Do not attach evidence to this initial inquiry.

Opens your email app. An inquiry creates no engagement or authorization.

Looking for the separate no-charge Phase 1 Founding Decision Review? See the application route, subject to fit and capacity.