How we work

From first conversation to working system.

One partner through four stages. We start with how the work is really done, agree what success looks like, build with your team and stay to keep it running.

01

Diagnose

Understand how the work is done today and where the time really goes.

We sit with the people who do the work, follow the data from where it starts to where it ends up, and measure where effort and errors pile up. Often the biggest cost is somewhere nobody was looking.

You come away with

  • A clear picture of how the work flows today.
  • Where time and accuracy are being lost, and roughly how much.
  • A short list of what is worth fixing first, and why.
02

Design

Agree what good looks like and how we will measure it.

Before anything is built, we agree the outcome in plain terms: what will be faster, more accurate or no longer needed, and how we will know. We design around your existing systems and the way your team likes to work.

You come away with

  • An agreed scope, in plain language.
  • The measures we will judge success by.
  • A plan that fits around your team's day-to-day work.
03

Build

Put working tools into live use quickly, with your team.

We build in small steps and get something real in front of your team early, using your own data. Their feedback shapes each step, so what we deliver is what they actually need, and they are confident using it.

You come away with

  • Working tools in live use, not a slide deck.
  • A team that has helped shape them and knows how to use them.
  • Results measured against what we agreed.
04

Run

Keep it running and improving as your business changes.

Businesses change, and the systems that support them need to keep up. We stay on to keep things running smoothly, fix what needs fixing and improve them as your needs grow.

You come away with

  • A system that stays reliable, with someone accountable for it.
  • Regular improvements as your needs change.
  • Clear documentation, so nothing depends on one person.
Getting started

What the first few weeks look like.

A conversation

You tell us what is slowing your team down. We ask questions, and tell you honestly whether we think we can help.

A focused first piece of work

If there is a fit, we agree a small, clearly scoped first step in writing, so you know exactly what you get before it starts.

Results on your own work

You see what changes on your own data and processes. Only then do we talk about anything longer term.

Questions

What people usually ask.

Do we need our own data team?

No. Most of the teams we work with don't have one. We need time with the people who do the work today, and someone who can make decisions. We handle the rest.

Will you replace our existing systems?

Rarely. We would rather make what you already have work harder. We connect to your existing systems and only suggest replacing something when it is clearly holding you back.

How long does a project take?

It depends on the problem, so we agree timings during the design stage. We always aim to put something working in your team's hands early, then build on it.

What happens to our data?

It stays yours. We build to run inside your environment wherever possible, we only use what the work needs and you decide what leaves. Our principles set out how we handle it.

What if we don't know exactly what we need?

That's normal, and it's what the diagnose stage is for. Tell us where the time goes and we'll help you work out what is worth fixing.

Tell us what's slowing your team down.

A few lines is enough to start. We reply within two working days.

Start a conversation