Agree the operating arrangement
Identify hosting, provider accounts, subscriptions and the people responsible for access and ongoing charges. Define the environments and the access required to build and operate the implementation.
Software and AI engineering
Delivery and support
We prepare implementations for release and provide ongoing support under agreed terms. Deployment, account ownership, operating guidance and maintenance form part of the operating arrangement.
Explore the scopeWhere this fits
A feature needs an environment and an operating owner. Release planning establishes how it reaches users, how the team checks its behaviour and what happens when a provider, process or implementation changes.
- Application environment and release setup
- Operating documentation and handover
- Monitoring and recovery arrangements
- Maintenance and further development
Define the response
before something fails.
Before release, we establish who runs the service, how problems are reported and how incomplete work is recovered. The example shows what changes when a service stops.
01Identify the operating owner
02Retain the relevant processing state
03Review usage and service health
04Keep support and recovery guidance available
The work involved
Prepare the release
Review test evidence, remaining issues and launch conditions. Where appropriate, use a limited rollout and define how to pause processing or return to a previous version if release checks fail.
Hand over a usable implementation
Provide the documentation, configuration, access and source rights included in the agreement. Walk the responsible people through routine use, unresolved work and recovery procedures.
Define ongoing support
Agree the supported systems, contact route, coverage and response expectations. Maintenance may include defects, provider changes, model evaluation and further development according to the selected arrangement.
What you receive
- Release plan and deployment configuration in scope
- Record of launch checks and outstanding items
- Agreed documentation, access and handover session
- Defined support and maintenance terms where commissioned
How we assess the work
The release review confirms the agreed user journeys in the target environment, ownership of the operating accounts and the handover package. Support coverage, duration and response expectations are established in the engagement terms.
Review and acceptanceWhat we need from you
- A nominated release decision-maker and operating owner
- Access to the agreed deployment environments
- Client-owned accounts and billing decisions where applicable
- A decision on the support arrangement after handover
Dependencies and scope
Support conditions are specific to the engagement. Third-party subscriptions, infrastructure charges, new functionality and provider-driven changes are included only where the agreement says so.
Discuss an implementation.
Tell us what you want to achieve and what is getting in the way. We’ll review the next steps with you.