Engagements


Buy the next decision, not an irreversible platform.

Each engagement is useful on its own. It names the question, custody boundary, deliverables, evidence, acceptance gate and exit before work begins.

01Fit
02Review
03Pilot
04Production
05Operate / exit
NO-COST PREPARATION

Private AI Fit Check

A browser-local planning record for custody, information class, users, archive readiness, authority and exit.

Decision
Is a conversation justified?
Data
No submission; broad categories only.
Run locally →
PAID · FIXED SCOPE

Architecture Review

A short decision pack covering use case, custody, deployment, model and hardware tier, gaps, budget and go/no-go.

Decision
Should you build, pilot or stop?
Exit
The decision pack remains useful without a later purchase.
See deliverables →
PAID · ACCEPTANCE-LED

Proof Node or Model Evaluation

A bounded corpus and workload are tested against agreed quality, citation, refusal, leakage, latency and operating criteria.

Decision
Does the system meet the acceptance envelope?
Evidence
Configuration, test set, results and negative findings.
Inspect the method →
QUOTED · SITE-SPECIFIC

Production delivery

Procurement, integration, hardening, evaluation, documentation, training and acceptance for the agreed deployment boundary.

Decision
Is the system accepted for named workloads?
Boundary
No general-purpose production promise.
See delivery gates →
OPTIONAL · CONTRACTED

Operations and support

Named change, incident, backup, restore, evidence and escalation practices within a written service scope.

Decision
Which responsibilities stay with whom?
Boundary
No public 24/7 or SLA claim.
See the operating model →
BUILT IN

Exit and portability

Exportable configuration, evidence, data and recovery information are defined before dependence becomes difficult to reverse.

Decision
Can ownership be transferred or the service ended safely?
Evidence
Exit artefacts and deletion or return records.
Inspect exit controls →

Every written scope answers eight questions

DecisionWhat must become knowable?
WorkloadWhich tasks and exclusions?
CustodyWhere may data and control travel?
AcceptanceWhich tests decide?
DeliverablesWhich reusable objects result?
ResponsibilitiesWho owns each control?
ChangeHow is drift approved?
ExitWhat is returned, exported or deleted?
PriceWhat is included and excluded?

Start at the smallest defensible step.

No engagement obliges you to buy the next one.

Discuss the decision See planning bands →