Waypoint
Know what one process actually costs and what to decide about it.
Most processes run nothing like the diagram says they do. Waypoint maps one of yours the way it actually works — the real numbers, the people who run it every day, and the customers on the other end of it — and hands you costed options you can decide between. It works on any process you own, with or without a system, integration or AI decision already on the table. Fixed scope, fixed price, three to six weeks.
Transformation rarely fails at the strategy.It fails at the process nobody measured.
We map one process the way it really runs, not the way it is written down. The actual numbers: how long things take, where they jam, what one pass through it costs. Plus real conversations with the people inside the process and the customers on the other end of it.
Where systems are involved we map those too — which system touches which step, where the handoffs are, where the data breaks. Then we lay out the options honestly. Sometimes the answer is a redesign. Sometimes it is a system change, sometimes automation or AI on two specific steps, and sometimes it is leaving most of it alone and fixing one handoff.
The craft underneath is service design: blueprinting a process end to end with the user and customer reality built into the map rather than appended to it. That is what stops a process map from becoming a diagram that gathers dust.
Where systems are involved we map those too — which system touches which step, where the handoffs are, where the data breaks. Then we lay out the options honestly. Sometimes the answer is a redesign. Sometimes it is a system change, sometimes automation or AI on two specific steps, and sometimes it is leaving most of it alone and fixing one handoff.
The craft underneath is service design: blueprinting a process end to end with the user and customer reality built into the map rather than appended to it. That is what stops a process map from becoming a diagram that gathers dust.
Three questions about a process you already run: what does one pass through it cost, how long does it really take end to end, and who handles the exception? If nobody can answer in a minute, that is the process to look at.
7×
Redesign beats acceleration. Among 152 CEOs of companies over $500M in revenue, the high performers were seven times more likely to have redesigned how work gets done end-to-end than to have made the existing steps faster. (BCG, 2026)
10→1
Faster task, same waiting time. One company cut a ten-day task down to a single day, and its customers still waited ten days for an answer, because the process around that task had not changed. (BCG, 2026)
26%
And then it costs more than agreed. More than a quarter of organisations exceeded the budget on their last major system project, most often because further technology turned out to be needed. (Panorama Consulting, 2026 ERP Report)
Sound familiar?We hear this a lot. We also fix these ever day.
Find out. Decide. Build.In that order, whether or not a system is involved.
What you getThree things you walk away with (and one decision you can actually make).
The Map.
How the process actually works today, blueprinted end to end — the real version, not the one in the handbook. Every step, every handoff, and every exception people have quietly built around.
How the process actually works today, blueprinted end to end — the real version, not the one in the handbook. Every step, every handoff, and every exception people have quietly built around.
Core Insights.
The operational numbers and the human reality sitting inside that map: how long each step really takes, where it jams, what one pass through it costs — what the people running it and the customers on the other end actually experience, and, where systems are involved, where the data and the handoffs break. Built in, not appended at the end.
The operational numbers and the human reality sitting inside that map: how long each step really takes, where it jams, what one pass through it costs — what the people running it and the customers on the other end actually experience, and, where systems are involved, where the data and the handoffs break. Built in, not appended at the end.
Roads Ahead.
Your real options from here, with what each one is worth and what it depends on. Sometimes one obvious move, sometimes a few worth weighing. Specific enough to take to a board or a budget owner and decide on.
Your real options from here, with what each one is worth and what it depends on. Sometimes one obvious move, sometimes a few worth weighing. Specific enough to take to a board or a budget owner and decide on.
Fixed price, fixed scopeNo open-ended bills, no surprises.
3–6wk
Three to six weeks from kickoff to an answer you can act on. No open-ended engagement.
€15K
Small enough to approve without a procurement round, specific enough to take to whoever holds the budget.
0
No obligation to continue. You are paying for the answer, and if it points to a build we can do that, but it gets shaped by what we found rather than sold up front. Plenty of clients take the map and carry on themselves.
Oh... FAQWe hear this a lot.
We already have a transformation programme. Where does this fit?
Underneath it. A programme sets direction; Waypoint measures one process inside it and tells you what changing that process is worth. It is the evidence layer the programme usually lacks, and it takes weeks rather than quarters.
We're already mid-procurement. Is it too late?
Usually not, and it is often the best moment. The requirements are being written right now, and requirements written from the documented process rather than the real one are exactly what turn into change requests later. A few weeks here is cheap against that.
How is this different from a management consultancy's assessment?
Most produce a framework, a maturity score or a trends deck with your logo on it. Waypoint maps your actual process, with your numbers, and ends in options you can decide between. You leave with a decision rather than a scorecard — and the people who diagnosed it can build the fix if you want them to.
We already have process documentation. Why isn't that enough?
Documentation describes how the process is meant to work, not how it really does. The gap between the two is where the cost, the delay and the risk sit. Waypoint maps the real thing, and the gap is usually the finding.
Where does AI fit into this?
Wherever the map says it does, and nowhere else. Some steps in some processes get materially cheaper with automation or agents, and most don't. Which is which comes out of the diagnosis, and that is the only basis we will use for spending your money on it.
What do I actually take to the board?
What one pass through the process costs today, where that cost is created, what the realistic options are and what each one is worth. That is a business case, not a status update.
How much of our people's time does this take?
A handful of interviews and one or two workshops, plus access to whatever operational data already exists. We do the gathering and the synthesis. Nobody on your side has to run a project to make it happen.
What happens after? Do we have to commit to a big build?
No. The diagnosis stands on its own. If the options point to building something we can do that, but it gets shaped by what we found rather than sold up front. Plenty of clients take the map and carry on themselves.
Underneath it. A programme sets direction; Waypoint measures one process inside it and tells you what changing that process is worth. It is the evidence layer the programme usually lacks, and it takes weeks rather than quarters.
We're already mid-procurement. Is it too late?
Usually not, and it is often the best moment. The requirements are being written right now, and requirements written from the documented process rather than the real one are exactly what turn into change requests later. A few weeks here is cheap against that.
How is this different from a management consultancy's assessment?
Most produce a framework, a maturity score or a trends deck with your logo on it. Waypoint maps your actual process, with your numbers, and ends in options you can decide between. You leave with a decision rather than a scorecard — and the people who diagnosed it can build the fix if you want them to.
We already have process documentation. Why isn't that enough?
Documentation describes how the process is meant to work, not how it really does. The gap between the two is where the cost, the delay and the risk sit. Waypoint maps the real thing, and the gap is usually the finding.
Where does AI fit into this?
Wherever the map says it does, and nowhere else. Some steps in some processes get materially cheaper with automation or agents, and most don't. Which is which comes out of the diagnosis, and that is the only basis we will use for spending your money on it.
What do I actually take to the board?
What one pass through the process costs today, where that cost is created, what the realistic options are and what each one is worth. That is a business case, not a status update.
How much of our people's time does this take?
A handful of interviews and one or two workshops, plus access to whatever operational data already exists. We do the gathering and the synthesis. Nobody on your side has to run a project to make it happen.
What happens after? Do we have to commit to a big build?
No. The diagnosis stands on its own. If the options point to building something we can do that, but it gets shaped by what we found rather than sold up front. Plenty of clients take the map and carry on themselves.
Selected work from across DigitalistDifferent domains, same starting point.
Otava Learning
A customer experience strategy for 2025–2028, built from a current-state analysis, co-creation workshops and scenario work — with the operating model and the metrics defined so that it doesn't stay a document.
Viking Line
A future-proof digital platform and an onboard app, built around how passengers actually move through the journey rather than around the existing systems.
Forterro
Over 15 product websites consolidated onto one composable multisite platform: Drupal behind, Next.js in front, a shared component system, and one place to manage content that had been scattered across a dozen separate sites.
Let's
talk
!
Reach
out!
Send us one process & we'll get back to youHonestly, we want to hear your problems.
Thank you! Your message has been received!
Oops! Something went wrong while submitting the form.
Find out.
Two to three weeks on one process: interviews with the people who actually run it, whatever operational data already exists, and — when systems are in play — a walk through the landscape it touches. We measure the current version rather than argue about it.
Two to three weeks on one process: interviews with the people who actually run it, whatever operational data already exists, and — when systems are in play — a walk through the landscape it touches. We measure the current version rather than argue about it.
Decide.
You get the map, what the process costs today, and the options, with what each one is worth and what it depends on. This is also the point where the honest answer can be that nothing should be built yet, and we will say so.
You get the map, what the process costs today, and the options, with what each one is worth and what it depends on. This is also the point where the honest answer can be that nothing should be built yet, and we will say so.
Build.
If you decide to change something, the same people carry it into the work: process redesign, integrations, modernisation, automation on the steps where it pays. Shaped by what we found rather than by what was in the original specification.
If you decide to change something, the same people carry it into the work: process redesign, integrations, modernisation, automation on the steps where it pays. Shaped by what we found rather than by what was in the original specification.
Process before techWhen a system, an integration or an AI decision is already on the table, the map covers the technical side too. This is where process work and engineering meet, and it is the part most process consultancies leave out.
The system landscape, step by step.
Which systems touch each step, where the handoffs are, and which of them are actually manual. Most of the cost in an operational process sits in the seams between systems rather than inside them — and those seams are rarely on anybody's architecture diagram.
Which systems touch each step, where the handoffs are, and which of them are actually manual. Most of the cost in an operational process sits in the seams between systems rather than inside them — and those seams are rarely on anybody's architecture diagram.
Where the data lives, and what state it is in.
Which steps produce data, which consume it, where it gets re-entered by hand, and how reliable it is. This is also the honest answer to whether automation or agents are feasible here at all. MIT found that 95% of enterprise GenAI pilots produced no measurable bottom-line impact; the process and the data underneath are usually why.
Which steps produce data, which consume it, where it gets re-entered by hand, and how reliable it is. This is also the honest answer to whether automation or agents are feasible here at all. MIT found that 95% of enterprise GenAI pilots produced no measurable bottom-line impact; the process and the data underneath are usually why.
What a change would really cost in this architecture.
Which changes are configuration, which are integration work, and which mean touching something nobody wants to touch. You end up with a technical baseline you can hand to a supplier or attach to a tender — including the parts you were about to procure and shouldn't.
Which changes are configuration, which are integration work, and which mean touching something nobody wants to touch. You end up with a technical baseline you can hand to a supplier or attach to a tender — including the parts you were about to procure and shouldn't.
Two things we won't doWorth saying out loud, because it costs us work sometimes.
We don't produce slides we won't build ourselves.
Consultancies sell the analysis and hand delivery to someone else. We take the same work into the code and stay responsible for it afterwards.
Consultancies sell the analysis and hand delivery to someone else. We take the same work into the code and stay responsible for it afterwards.
We don't build what was ordered if what was ordered is wrong.
Software houses take the specification and build it. We check first whether there is a process behind it worth copying into software, and sometimes the answer is not yet.
Software houses take the specification and build it. We check first whether there is a process behind it worth copying into software, and sometimes the answer is not yet.
This is a standard, not a promise.
We don't win this argument every time, including with clients. It is still where every project starts, and it is the main reason the ones that go well go well.
We don't win this argument every time, including with clients. It is still where every project starts, and it is the main reason the ones that go well go well.