Answer
What happens after launch?
After launch, the Build includes 30 days of stabilization at no extra charge. From there you choose one of three paths: Embedded Adoption, a keep-the-lights-on arrangement, or a formal hands-off handover with no SLA.
The first weeks
Launch means release to the agreed production environment with the agreed user group. It starts the 30-day live-use acceptance window, where the crew's use of the tool is measured from your own records against the threshold signed before the build. Stabilization after launch is part of the Build, at no extra charge.
Three paths after that
| Path | What it means |
|---|---|
| Embedded Adoption | Monitoring, business-hours support, a weekly operator review, a monthly executive review, one bounded improvement cycle each month and a managed change queue. Six-month minimum, priced in the Spec conversation. |
| Keep-the-lights-on | An arrangement that keeps the tool running. |
| Formal hands-off handover | The tool is handed to you or to someone you choose, with no SLA from us. |
What makes a handover real
Every Build ships with a handover pack: the architecture, a runbook, a credentials inventory, a data map and the list of models and providers used, updated on every release. You own the tool, your data and your production accounts after payment. That means any of the three paths is a real choice, including running it without us.
A second workflow is a second engagement, specified the same way. See how we work.
Questions people ask
Is support included after launch?
Thirty days of stabilization after launch are included in the Build at no extra charge. Ongoing support after that is part of Embedded Adoption or a keep-the-lights-on arrangement.
Can we run the tool ourselves?
Yes. A formal hands-off handover passes the tool to you, with no SLA from us. The handover pack is written so someone else can run it.
What does Embedded Adoption cost?
Its price is set in the Spec conversation, and it has a six-month minimum.