Agree before starting
- Supported stack (containerised app or Mendix, plus identity provider)
- Infrastructure prerequisites and who provides them
- Price and commercial next step if the pilot is accepted
- Named technical owner on the customer side
One-app pilot
A paid first outcome, not a platform-wide decision.
We agree the stack, prerequisites, responsibilities and price before work starts. The pilot ends when one app is running in the agreed environment and the customer’s technical owner accepts the handoff. Then we talk about the next two apps and the recurring operating model.
01Scope and acceptance
Written down first. No free custom builds.
Avoid an unconditional deadline until delivery experience on that stack supports it. Application-level or AI-specific controls that Low-Ops does not provide are identified and scoped separately.
In scope
- Platform available in the agreed environment
- One application deployed and reachable by authorised users
- Network boundary checked against the intended design
- Ownership documented; deployment record visible
- Rollback or restore tested as appropriate for that stack
Out of scope unless priced separately
- Application-level security review of the customer’s code
- AI-model, prompt or training-data controls the platform does not provide
- Organisation-wide rollout, extra client tenants, or custom product work
- Unconditional go-live deadlines