Skip to content
XSIS
An engineer monitors systems from a control room

How we work

Fixed-outcome projects and round-the-clock managed services

Fixed-outcome projects with named delivery leads, and managed services that keep them running.

A live system needs an owner

A live system needs an owner after launch: someone who answers for its service levels, its incidents and its next release.

Managed services give that ownership to one team, either as a fixed-outcome project or as ongoing application managed services.

What the model covers

A fixed-outcome project runs to a fixed scope and milestones with a named delivery lead. Managed services take the system into production and keep it there.

  1. A fixed scope

    The project is scoped and priced before it starts.

  2. Milestones

    Delivery is tracked against milestone acceptance.

  3. A named delivery lead

    One lead answers for the delivery, from mobilisation to handover.

  4. Managed services

    24/7 application managed services with L2 and L3 support, SLA governance and continuous evolution.

Two ways to engage

The same team can deliver a defined outcome or run the system that follows it.

  • A fixed-outcome project

    A defined scope, a milestone plan and a named delivery lead.

  • Application managed services

    Outcome-led support for a live system, with service levels and continuous evolution.

Questions and answers

What is a fixed-outcome project?

A fixed-scope, milestone-driven delivery with a named delivery lead. The proposal fixes the scope and the price before work starts.

What does the managed service cover?

Outcome-led application managed services: L2 and L3 support, SLA governance and continuous evolution, 24/7.

When does managed services start?

When the system goes into production, or when an existing system needs an owner for its service levels and incidents.

Do you keep improving the system?

Yes. Continuous feature evolution is part of the service.

Start with a conversation, not a contract.

Tell us what you need to build, connect or secure. An architect goes through it with you, then recommends where to start.

What happens next

  1. Agreeing a time

    Our team emails you to agree a time for the session.

  2. Pre-consulting session

    A free 30-minute online pre-consulting session: we go through your goals, systems and constraints.

  3. Readiness review

    In a free 48-hour readiness review, a Principal Architect checks your project against the 6-point Definition of Ready and recommends the track that fits.

  4. Choosing the track

    Scope-ready projects receive a binding proposal within 3–5 business days. Concept-stage projects start in the Blueprint Studio. A live system that is failing, undocumented or needs integration starts with a diagnostic of 1–2 weeks. The Blueprint Studio and the diagnostic each have a fixed fee, quoted in the proposal.