We help you pick the change worth making, build it, and stay until your people are working the new way.

We take on the whole span: talking through what is worth changing and in what order, getting the operation ready to carry it, building it or buying it, and staying through the period where a new way of working either becomes routine or disappears. Every step produces a result on its own before the next one starts.

The old spreadsheet is still on the shared drive, and someone is quietly using it. That is not a technology problem. It is the part nobody planned for — and it is where most of this kind of work succeeds or fails.

What the work actually looks like

Every business is different, so the territory varies. Some common areas where this kind of work lands:

What we do is digital transformation: changing how a business operates so it competes better. We use AI wherever it genuinely helps, and that is more often than it used to be. But AI is the means, not the objective — and the objective is always the change to how the business runs. So sometimes the answer is AI. Often it is ordinary software nobody has configured properly. Sometimes it is a process that needs rewriting and no technology at all. We would rather say that in the first conversation than six weeks in.

The strategy: what it settles

Before any building, we produce a short document. A clear picture of where the business is now, where it needs to be, which single change goes first and why, which problems are not worth solving at all, and what is deprioritised for now.

What that document settles matters as much as what it contains. The strategy process involves the people who actually do the work, not only those who manage it, because the shape of a problem in practice is often different from its shape on paper. Hidden dependencies, workarounds that have become load-bearing, the real reason a process works the way it does — those come out in conversation, not in a briefing document. What the strategy produces is an honest picture of what the operation can genuinely change, and in what order.

That document belongs to the business either way. It is also the point where a decision is made about whether to build anything at all.

Every step has to earn its place

Nothing is worth doing unless it produces a result on its own, whatever size it is.

Some changes take an afternoon. Some take weeks. Some take months, because the data behind an ERP cannot be fixed quickly and everything downstream depends on it. What matters is that these are not different kinds of work — they are different scales of the same thing. A small change is part of a larger one; the larger one is part of the overall direction the strategy set. Each level stands up on its own, each one makes the next easier, and the strategy is what tells you which small thing is worth doing this month.

The first result arrives before the second step starts. That is also when it is easiest to judge whether the work is worth continuing.

What a step looks like in practice

The shape of a step depends on what it is. An afternoon job skips most of what follows. A months-long programme repeats the loop many times. A weeks-scale change tends to look like this — management reporting is a common example, because it is where the decision-bottleneck problem is usually most visible.

1. First, the truth about what currently exists.

   Following the information a senior person uses to make a decision: where it comes from, how long it takes to assemble, who maintains it, what happens when that person is absent. This turns up the same things in almost every business: data held in three places that do not agree with each other, a spreadsheet updated by one person and trusted by everyone, decisions made on numbers that are two weeks old. None of it is anybody's fault. All of it matters.

2. Then the foundation.

   Agreeing what information is actually needed to make the decision well, where it should live, who owns it, and what the acceptable lag is. This is the unglamorous part, and it is the one that decides whether the rest works.

3. Then building or buying.

   If something on the market does the job, it gets configured properly rather than recreated. Where something is built, it is the smallest thing that works end to end on the systems already in use. It is visible and testable as it goes, not at the end.

4. Then live, with us still there.

   The first real decisions go through the new route while we are in reach. Whatever was missed surfaces now and gets fixed. Then the process is written down, in plain language, for whoever needs it later.

5. Then making the new way the easy way.

   When people are busy, the old habit comes back. If the new route is slower under pressure, the route gets fixed. A check-in happens once the novelty has worn off. The measure: is this being used without anyone being reminded to use it?

6. What is left at the end.

   Management information that arrives reliably, decisions that can be made without escalating to one person, a business that functions when that person is unavailable. The next step moves quicker because the data is already in order and the habit of changing things is already there.

What stays yours

Everything built belongs to the business, runs on its systems, and is in its name. Data stays where it is unless otherwise decided; where something needs to go elsewhere, the business knows exactly what, where, and who can see it before it moves. The current IT supplier keeps their work.

If the first step does not earn its place, that is where it ends — and the business keeps the strategy, the cleaned data, and a working process.