Skip to content
New guide: how to scope an AI project before you build

Engineering

Digital Transformation

We look at the work end to end and change the parts that actually matter, then build the software to support it.

Typical timeline
6-12 weeks
Group
Engineering
First step
Fixed-price discovery

Scope, price and acceptance criteria are agreed in writing before the build starts.

Why us

Why choose us for this work?

Process before tooling

We map the work and remove steps before choosing software.

Measured

We baseline the current process so the change can be judged honestly.

People involved

The people who run the process help design the replacement.

Staged

We change one part at a time and check that it works before moving on.

Owned by you

The system, data and decisions stay with your team.

What you get

What you get from Digital Transformation

A process that works, supported by the right system.

  1. 01

    A process map

    The current state, with the steps to remove or change clearly marked.

  2. 02

    A baseline

    Numbers for the current process so improvement is measurable.

  3. 03

    A working system

    Software supporting the changed process, built in stages.

  4. 04

    Adoption support

    Training and runbooks for the people running it.

  5. 05

    Documentation

    Decisions, architecture and handover notes.

The problem

What usually goes wrong

Buying a new tool rarely changes a process. The real work is deciding which steps to remove, which decisions to make explicit and how the new system fits the people who run it.

Who this is for. Organisations whose tools have accumulated faster than their processes have been thought through.

Signs you need this

If any of this sounds familiar

  • The same information is entered in several systems.
  • A process exists only as a set of habits.
  • New tools keep being added and nothing gets removed.
  • Leadership cannot see where the time actually goes.

How the work runs

How we deliver it

  1. 01

    Map

    We observe the process and measure where the time goes.

  2. 02

    Decide

    We agree which steps to change and define the measures.

  3. 03

    Build one stage

    The first change is built and tested with the people who run it.

  4. 04

    Check the numbers

    We compare against the baseline before expanding.

  5. 05

    Expand and hand over

    Further stages follow the same pattern, then we hand everything over.

Deliverables

What you receive

  • Process map and baseline
  • Prioritised change plan
  • Working software for the first stage
  • Training and runbooks
  • Measurement report and handover docs

Stack

Tools we expect to use

TypeScriptPostgreSQLReactCloudflarePython

We choose the stack to fit the problem. If your team already runs something else, we plan around it.

Questions

Common questions

Do we need to replace our systems?

Not necessarily. We look at the process first and connect to existing systems where that is the cheaper, safer option.

How do you measure success?

We baseline the current process and compare against it after each stage, including the time spent on exceptions.

Will our team be involved?

Yes. The people who run the process are part of the design and the weekly demos.

Next step

Talk through your project.

A short conversation. You leave with a clear view of what it would take, and whether this service is the right first step.

Prefer email? Write what you are working on and we will reply.

Send a note

By sending this, you agree that we may reply to your enquiry. See our privacy policy.