Skip to content

Home/Onboarding

The pilot

A free 90-day pilot, from your documents to production.

One versioned system, fitted to your estate in three gates: Prove (days 0–30), Expand (31–60), Industrialize (61–90), stopping at day 90 if targets are missed — then you run software, not a project.

One artifact, one version numberNo per-customer branches Exit at any pilot gatePilots are free
How to start

Three ways in. No discovery call.

What we do not have yet

No named production customers and no published accuracy figure: 13 packs ship in the US edition and 8 are drafts; none is yet measured on a customer’s labelled documents. Gothink Witness is built; we are looking for design partners. The sandbox is a guided evaluation, not self-serve.

What happens, and when it ends

A pilot with an end date.

Free, in three gates, stopping at day 90 if targets are missed. Everything customer-specific is configuration.

01
Prove · days 0–30

Estate & schema

Document families mapped to the pack schema; one connector pointed at your sources; an eval report scored against your reviewers.

From you: a data owner and a platform engineer, part-time

eval report vs your reviewers
02
Expand · days 31–60

Gates & ground truth

Two more document types; your experts label the ground truth and your risk function sets each threshold from it (0.95 in the shipped packs is only a starting point).

From you: a steward or SME, and the risk-policy owner

thresholds set, truth labelled
03
Industrialize · days 61–90

Industrialize & decide

Reviewer workflow in daily use; the business case signed off on measured numbers. Targets missed at day 90: you stop.

From you: whoever signs off on a wrong value reaching a client

measured, then your decision
1Provefree 2Expandfree, if you continue 3Industrializefree, if you continue Targets missed at day 90 → stop
1 · Provefree
2 · Expandfree, if you continue
3 · Industrializefree, if you continue

Three gates. You decide whether to continue at each one; the pilot is free.

Who does the work

An engineer, not a sales team.

The person who runs your pilot writes the runtime and reports to engineering.

Inside engineering

Not a delivery bench on billable hours. What they learn ships.

The promotion rule

It ships to everyone or becomes a pack — or it is not built. No fork.

Measured by what ships

Share of pilot work shipped to everyone within a quarter. Not hours.

Partners on request: implementation partners are not yet running pilots.

Configuration, not code

What is yours is data, not a branch.

Two deployments differ only by a set of files you could read.

Schemas and fields

A versioned file in the pack, extended for you.

Confidence thresholds

Per field, set by your risk function. Change it without a release.

Routing and validation

Which exception goes where; which checks must hold.

Connectors

Sources, masters and targets, from the released library.

The eval set

Your experts' ground truth. Scores every release; yours to take.

Never: a runtime branch

If it cannot be generalised, we decline rather than fork.

Where it runs

Same artifact. Different install profile.

Location is a modifier on the licence, not a rebuild. Move in-boundary later without re-fitting.

gothink Cloud

An isolated tenant in the region you choose.

Same imageYes

Fastest path; no infrastructure work.

Your VPC

AWS, Azure, GCP or Kubernetes, under your IAM and keys.

Same imageYes

With local-only models, no outside AI provider sees a page.

Air-gapped / sovereign

On-prem or a national cloud, offline update channel.

Same imageYes

When no outbound path is allowed.

Signed releases cross inward. With local-only models (models.localOnly), no outside AI provider sees a page; with a cloud model configured, the provider sees only the pages you send it. The data boundary

After go-live

Nobody stays behind.

What recurs is software and a guarantee.

Updates and patches

Releases as changes are approved, each with a change record, on a changelog with an SBOM.

Form updates as packs

A revised form or statement layout ships as a new pack version. No re-fit.

An SLA and a queue

Business hours; 24×7 severity-1 with a named security contact on Sovereign.

Your set scores every release

An upgrade cannot quietly cost you accuracy.

Accuracy re-measured

An add-on: recalibration and drift, new document types, and accuracy re-measured on your ground truth.

What the licence carries →

If you stop, nothing switches off

Configuration, calibration, records and lineage stay yours; the deployed version keeps running.

The ownership schedule →

Do not take our number. Generate your own.

Score it yourself. Prove it in a free 90-day pilot. Own what it learns.