Before go-live
Source scope, named owners, review route, success measures and acceptance criteria recorded in writing.
Do not buy a promise.
Test a control route.
The Launch Programme is a bounded production deployment for the first three production customers. It is designed to produce an operating record—not a vague innovation experiment.
US$20K first 12-month term03 production customers30 SEP 2026 order-form window
WHAT THE LAUNCH SCOPE INCLUDESOne real
One real
environment.
- One customer-hosted production environment
- Three supported standard connectors and 50,000 DPU initial backfill
- Up to three governed domains and 40 published production workflows
- Named reviewers, controlled publication, version history and drift review
- Standard support, implementation enablement and a written go-live record
During operation
Source changes, review decisions, drift signals, usage and support activity observed through the agreed workflow.
At review
A factual pilot record: what was configured, what changed, what was reviewed and what evidence was retained.
COMMERCIAL CLARITYKnow the capacity,
Know the capacity,
not just the price.
Plus 100,000 combined REST and MCP engine requests, 20,000 skill invocations and 12 drift scans per bound source each month.
Extracted text is aggregated monthly and rounded up. Unchanged material with the same stored content hash is not counted twice; OCR content counts at twice the extracted-character rate.
No charge is made for a first period over an allowance. Notice is given only after a second consecutive month over, followed by 30 days to agree any change in writing.
Support runs Monday–Friday, 08:00–17:00 South Africa time. First-response targets are not a contractual uptime SLA and carry no service credits.
The launch rate includes a learning programme—without giving us access to your documents.
Customers agree to a 30-minute review every two weeks with the named commercial owner and reviewer. Company Brain may analyse operational telemetry—such as processed capacity, request volumes, review minutes, support hours and drift-alert decisions—but not document content outside the customer environment. Any published case study, name or logo requires separate written publication approval.
IMPLEMENTATION ROUTE
Move from a material workflow to a written go-live record.
- 01 / Scope
Confirm the source scope, owner, review decision, success measures and acceptance criteria.
- 02 / Configure
Deploy the agreed environment, enable the selected connectors and prepare initial governed workflows for review.
- 03 / Release
Complete reviewer enablement, go-live review and a written record of known limitations and next actions.
The cohort is designed to validate operating evidence—not to manufacture customer claims.
Public case studies, quantified outcomes and named references will be published only when success measures are met and the customer has approved their use.
Start with one material workflow →