How it works
A production readiness review first. Weeks, not quarters, to a working system. Acceptance you verify yourself. A license only if you keep it.
The five steps
- 1 Readiness review
- 2 Readiness gate
- 3 Build
- 4 Acceptance
- 5 Run
Every phase ends at a written gate. You can stop at any of them — which is exactly why clients don't.
The production readiness review (free, entry).
From what you show us — a walkthrough of your demo and, if you can share them, its structural traces: the call graph without the data — we assess your demo, your definitions, and your integration surface. No system access. You leave with a written readiness report and a proposal — whether or not you continue with us.
Stage 0 — the readiness gate.
Scope, success metrics, and acceptance criteria agreed in writing. With access in place, we run your full traces through our platform and sharpen the flow map to what the system actually does. If your systems aren't ready, the clock pauses — your budget doesn't burn.
The build.
Your system on our platform: deterministic where it must be, intelligent where it should be, instrumented everywhere — weeks, not quarters.
Acceptance (your verification).
Pass/fail criteria you test yourself — functional acceptance is never hostage to business luck, and business results are measured openly at the gate.
Run (the license).
Your team operates it on a private tenant — monitor, correct, and extend your own flows. We stay for the hard parts.
What's in the production readiness report
A short written document, built from your three answers, one working session in which you walk us through your demo, and — if you can share them — its structural traces. No system access, no data. Yours whether or not we work together. It contains:
- The flow map — deterministic vs. generative. From your walkthrough — and from your structural traces if you can share them — we map your application: which steps are deterministic and belong in explicit flows — prices, lookups, routing, commitments, anything that must be right every time — and which genuinely need a model and stay generative. Structural traces are the call graph of your demo without its data: which step calls which system or model, in what order — the default most tracing tools export when prompts and outputs are hidden. (Once we're working together, we run your full traces through our platform and sharpen the map from evidence.)
- A readiness verdict in the production-readiness-review convention: ready, ready with conditions, or not ready — with blockers (fix before launch) and conditions (fix within an agreed window).
- A review of your definitions — what "working" means, and whether it's measurable as written.
- A map of your integration surface — the systems, data, channels, and payment paths a production application must touch.
- The gaps, in plain language, and what it would take to go live.
- A proposal, if we think we're the right team.
Where humans stay
Your people at the decisions you name; ours on call for the hard cases — always with the full history attached.
What we ask of you
A working demo you can walk us through. If you can, its structural traces — the call graph without the content: exported from your tracing tool with prompts, outputs, and tool payloads hidden; we'll tell you exactly how. No system access and no data for the report. Written answers to what it should achieve and how you'll measure it. A named person who can decide. And, once we're working together: full traces and access to the systems the application must touch before the build starts — because when those are ready, the build is short, and when they aren't, we pause rather than pretend.
What you keep
A running production application on a private tenant your team operates. Your flows as configuration you keep, independent of any model vendor. The acceptance record. The report. And us, on call for the hard parts.
Who we work with
You already have a demo. You've written down what it should achieve. You know how you'd measure success. It doesn't work in production yet. If that's you, the report will be useful even if we never work together. If you're still exploring what AI could do for you — we're not your first stop, and we'll say so.