Skip to content

The challenge

“Digital transformation” usually means digitising a broken process, which produces a faster version of the same problem.

The software gets delivered, adoption stalls, and the old process continues alongside it.

How we approach it

A1

Map and fix the process

Before deciding what to build.

A2

Sequence the change

Each step usable on its own.

A3

Train and support

The people doing the work, in their language.

A4

Measure adoption

Use, not delivery, is the success measure.

How delivery runs

The same four phases, whatever we are building.

  1. 012–3 weeks

    Discovery

    We map your current process, users and constraints, then define scope in writing.

  2. 022–4 weeks

    Design

    Interface and data design, reviewed with the people who will use the system daily.

  3. 036 weeks+

    Build

    Delivery in two-week increments, each one testable, with progress visible throughout.

  4. 04Ongoing

    Launch & support

    Deployment, training and documentation, then optional support at a level you choose.

What you get

Process map
Current state, including the informal workarounds.
Roadmap
Prioritised by value and risk, with a first phase you can fund.
Phased build
Delivered in usable steps.
Training
Role-based, in the languages your staff work in.
Adoption review
Measured after rollout, with corrections agreed.

What changes

Process fixed first

Not automated in its broken form.

Usable at each step

Value before the final phase.

Measured on use

Adoption is the deliverable, not delivery.

Questions

About this work specifically.

General questions about scope, ownership and timelines are answered on the resources page.

Almost always with a two-to-three week discovery: we map your process, scope the work and give you a fixed proposal. It is fixed-price, and the map is yours whether or not you continue with us.

Tell us what you need built.

We reply within two working days with honest scope and next steps — including when we are not the right fit.