Layer 1 · Software · selling now
We keep it working, or we run it. You keep owning it either way.
The boundary
What this buys, and what it does not.
Published together, because a promise without its limit is marketing. If your situation is in the right-hand column, we would rather tell you now than in week three.
✓ What this includes
- AMC — fixes against the acceptance criteria, security and dependency patches, compatibility updates, an agreed change allowance, business-hours support
- Operated — all of the above, plus monitoring, incident response, an on-call rota, and restores tested rather than assumed
- The exit handover, current from day one instead of written at the end
- The runbook and dependency policy, handed over whether or not you buy either
✕ What it does not — so we will not promise it
- An on-call rota we have not agreed in writing
- Operating software we did not build, without a review first
- Anything the monthly allowance does not cover — quoted separately, never absorbed silently
What you end up with
The deliverables.
- A running system, and someone answering for it
- Runbooks kept current, not written once
- An exit pack you could act on this month if you chose to
Best fit: AMC for teams with an engineer who do not want to track dependency advisories. Operated for teams without engineers to spare, who want the ownership without the operational load.
Commercials
What it costs.
- Price
- AMC from $300/mo · operated from $2,400/mocancel anytime · exit handover included
- Agreed
- In writingbefore we start
- Hourly drift
- None
The price is published, and it is the same number whoever is asking — it does not depend on how much we think you will pay. What changes it is you changing the scope, and then we requote before doing the work rather than after.
Not sure this is the right one?
The teardown ranks your own stack and tells you which engagement fits — including telling you to do nothing, where that is the honest answer.