How we work

How a project runs

Every engagement runs in four phases. We agree the scope and price of each phase in writing before it starts.

Talk to an engineer

ON EVERY PROJECT

You own the source code and repository from the first commit.

An engineer who works on your system is in every meeting about it.

We agree the scope and price of each phase in writing before it starts.

Before we start

What happens when you get in touch

Your message

An engineer reads your message and replies with questions or a suggested next step.

A short call

We talk through the process or system with you. We sign your NDA first if you need one.

A written summary

We send what we would do, in what order, and a price range for the first phase.

The engagement

Four phases, each priced on its own

Discovery

We map the process, the data and the current system. You get an architecture decision record and a plan split into slices, each with its own business case.

First slice

We put one real workflow into production for its real users. It runs alongside the old system until the outputs match.

Further slices

We deliver the remaining slices on a fixed cadence. Each slice has its own rollback plan.

Run or hand over

We operate the system with your team, or hand it over with its runbooks, documentation and audit trail.

Commitments

Five commitments on every engagement

Each one can be checked. Ask any client whether we kept them, and we will give you their contact details.

We find out why a system works the way it does before we change it.

We write down every architecture decision and hand the records over.

An engineer who works on your system is in every meeting about it.

We treat your regulatory and data protection obligations as design requirements from the first workshop.

We build each system so that your team could run it without us.

Handover

Every system ships with the same handover pack

You own the source code and repository from the first commit.

Source code in your repository

Architecture decision records

Automated test suite

Infrastructure as code

Runbooks for your operations team

Audit log and retention settings

Accessibility conformance report

Security test report

Working together

Questions buyers ask

Do you work alongside in-house teams and other suppliers?

Yes. We join existing programmes and work within your delivery process.

Can you work inside our cloud tenancy and security controls?

Yes. We work in your tenancy, with your identity provider and under your security policies.

How do you price work?

We price each phase separately. We agree its scope and price in writing before it starts.

What do you need from us to start?

We need a named owner for the system, time with the people who use it, and read access to the software or its documentation.

Tell us which process or system you want to change.

A senior engineer will read your message and reply with questions or a proposed next step.

Talk to an engineer