We close
the loop

Most organisational change stops at a recommendation. We map how a company actually works, redesign what deserves it, build the result, and stay until the people doing the work have it in hand.

Nobody closes the loop

Every organisation runs on a description of itself — the org chart, the process documentation, the way the ERP was configured. That description is always partly out of date and partly fiction. Decisions get made on it anyway.

Two industries sell an answer. Both stop before the part that matters.

1.0

The consultancy

Twenty to forty interviews in an organisation of two thousand. One to two percent, chosen by the client, with people who know they are talking to a consultant.

Stops at a deck. Nobody builds it.

2.0

The platform

Process mining reads transactions — rows a system wrote when something happened. It tells you a step took four days. It cannot tell you why.

Stops at a licence. The work comes after.

3.0

The whole loop

Ask everyone. Redesign with AI in the process rather than beside it. Build it on the process that actually runs. Land it on people's screens. Measure whether it worked.

Doesn't stop. The map stays.

One shared map,
three roles

No consultancy can build. No software vendor can diagnose. No training firm can do either. The loop only closes when all four moves are owned end to end — and they need genuinely different businesses to perform them.

So this is not one company with three departments. It is two companies in the group and a layer of independent partner development agencies who do the building. What holds them together is a single artefact.

Metison ASKS EVERYONE 15 min · every role Partner agency INDEPENDENT · BUILDS IT Remy LANDS IT on the screen, per person change spec new process The map HOW THE ORGANISATION ACTUALLY WORKS · KEPT CURRENT · OWNED BY THE CLIENT writes: roles, variants, the gap reads: what to build, already signed off writes: friction, adoption, did it land round 2: re-ask only what moved
Solid outlines are companies in the group; the dashed one is an independent partner. The path across the top is what a client buys once. The dashed path on the left is why it compounds — the map persists, so the second round does not repeat the first.

Two companies
and a partner layer

Each stands on its own. Metison and Remy are ours; the build layer deliberately is not. An agency that would otherwise compete for the same work becomes the party that receives it — pre-scoped, with the discovery already paid for.

Metison

What should change — and what shouldn't

Maps how an organisation actually works by asking everyone, not a sample. AI-conducted interviews, fifteen minutes, at the person's own desk. Every statement is tagged to a role and a process, never to a person.

Conversation four hundred can push on the contradiction that conversations twelve and eighty-seven exposed — the thing a human interviewer cannot do.

Launching · metison.org ↗

Partner agencies

Building it on the process that runs

Specialist development agencies who take the change specification and build the real thing. Partners, not subsidiaries — separately owned, free to work with anyone.

Chosen per engagement for the work in front of them, and named on a shortlist the client picks from — never a single house agency.

Independent · selected per engagement

Remy

Getting the change into people's hands

A screen-aware buddy that reads the live interface and flies the cursor to the exact button — in any application, including the legacy and mainframe systems a browser tool cannot reach.

It also produces a signal nothing else does: where people slow down and give up. Aggregated and anonymous by construction, never per employee.

helloremy.app ↗

AI beside,
AI inside

Beside: you put a copilot next to step four. The shape of the process doesn't change. You win five percent on one step of a process that has twelve steps it shouldn't have. This is where most AI budget goes, and why the spend never shows up in the numbers.

Inside: you ask what this process would be if you designed it today, knowing what a model can do. The answer removes steps far more often than it speeds them up.

AI BESIDE — A COPILOT ON STEP 4 copilot Twelve steps. Eleven untouched. The shape of the work is exactly what it was. AI INSIDE — THE PROCESS IS REDESIGNED Five steps. Seven deleted, not accelerated.
Filled marks are AI. Above, it hangs off the side of a process that keeps its shape. Below, it is load-bearing and most of the original steps are gone — but you cannot draw the second row without first knowing what the twelve steps really are.

Start with
the map

If you recognise the gap between how your organisation is described and how it actually runs — that is the conversation.

[email protected]