Clear scope Visible Ownership

At every stage you know who decides
— and what you get.

Getting Started

From the first message to kick-off — four simple steps.

First conversation
You tell us what the system does and what needs to change.
Discovery review
We look at the workflow, the code and the people involved.
Proposal
Scope, responsibilities, acceptance and timing — in writing.
Kick-off
Access is set up, owners are named, work begins.

Four stagesOne Clear Path

01

Understand
We review your workflow, code, interfaces and support runbooks, and confirm scope and access.

who decides
You and us, together

you get
Scope & ownership map
02

Agree
Responsibilities, acceptance criteria, access and timing are confirmed.

who decides
You approve

you get
Work plan & agreement
03

Deliver
We build, review and test, then release with approval, test evidence and a rollback plan.

who decides
We run it, you accept

you get
Tested release & evidence
04

Support
We triage and escalate tickets, confirm recovery with users, review ageing tickets and keep known issues current.

who decides
Agreed service scope

you get
Runbook & change log

Ways to workTogether

fixed scope

Project

A defined build or improvement with a clear scope and handover.

monthly

Ongoing support

Maintenance and user help within an agreed service scope.

rolling

Improvement plan

A steady backlog of enhancements, released on a rhythm.

transition

Takeover

We receive code and documents from another team, prove we can build and run it, and carry it forward.

scheduled

Standby & continuity

Scheduled sessions alongside your current team — assigned L1–L4 work, release readiness and rehearsals — ready to take over when authorized.

Who does what?

you bring

A named decision maker

Access to systems, code and environments

Knowledge of how the business uses the system

Timely feedback and acceptance

Named owners for infrastructure and site

Written authorization for production changes

we bring

A named delivery owner

Reviewed, tested changes with a rollback plan

Clear progress updates and release notes

Documentation the next person can use

Named accounts with least-privilege access

Ticket status and incident reporting

What youReceive

Documents you keep, whatever happens next.

Scope &
ownership mapDiscovery

Work plan & agreementAgreement

Test evidenceDelivery

Release notesDelivery

RunbookSupport

Change logSupport

Staying In Touch

No chasing for updates.

One point of contact

A single owner who knows the work.

Shared backlog

Everything requested, visible to both sides.

Regular updates

Progress, risks and decisions — written down.

Release notices

You know what changed, and when.

Three rulesWe Work By

They apply to every project and every support request.

own it

Visible ownership

Every task and decision has a named owner on both sides.

test it

Controlled changes

Reviewed, tested and released with a rollback plan.

write it

Usable documentation

Written for the next person who has to act.

ServiceControls

A visible ticket workflow and clear production authority.

Ticket ownershipA named owner, priority and escalation path for each request.

Production changesAuthorized approval, test evidence and a rollback plan.

Service reportingTicket status, handling effort and recurring-incident trends.

Service hours, response targets and workload capacity follow the agreed service schedule.

Taking overA System

From the first handover to day-to-day support — with evidence at every step.

prepare

Code custodyReceive code, history and dependencies. Build and deploy independently, keep a version baseline.

PilotRun one real workflow end to end — test a failure, prove recovery and rollback.

Full handoverComplete the inventory, configuration and SOPs, confirm roles, run a full rehearsal.

operate & return

StandbyScheduled sessions with your current team on L1–L4 tickets, releases and rehearsals.

ActivationWith written approval, check versions, access and data, then lead application support.

ReturnWhen authorized, hand back code, history, runbooks and open issues — with sign-off.

KnowledgeTransfer

A structured handover — with proof the new team can repeat the work.

Application knowledge

In the sessionArchitecture, workflows, site differences and dependencies

Proof you receiveApplication inventory & open-question log

Build & deployment

In the sessionThey demonstrate, we repeat, they review

Proof you receiveIndependent build & deployment record

Operational support

In the sessionTicket walkthroughs, logs, known issues and escalation

Proof you receiveRunbook & supervised ticket evidence

Recovery & release

In the sessionFault diagnosis, approved fix, rollback and rehearsal

Proof you receiveTest results, recovery record & sign-off

Security &Controlled Change

Delivery controls that align with your approved security requirements.

Identity & accessNamed accounts, least privilege and approved production access.

Access approvalsPeriodic review

Code & dependenciesVersion baseline, reviewed changes and a dependency inventory.

Change recordComponent register

Data & environmentsMasked test data and controlled handling of logs and secrets.

Environment recordsData-handling records

Release & recoveryTest results, approval, a release log and a rollback procedure.

Release evidenceRecovery record

Specific security remediation or certification needs a defined control baseline and an agreed work package.

let's talk

Have a systemto build or look after?

Discuss your project

What happens next

Tell us about the systemWhat it does, who uses it and what needs to change.

We reply to arrange a callA short conversation to understand the situation.

Agree scope and next stepsClear responsibilities before any work begins.