Strategy

Know what you're building. Then build it.

We bring the problem, the intended outcome, existing systems and technical constraints together into a clear approach — with a scope, timeline and budget that hold up.

Discuss your project See our approach

Does this sound familiar?

Most projects don't stall on technology. They stall on a lack of clarity at the start.

Everyone means something different

Management, users and IT each hold their own picture of what should be built. That difference only surfaces during development.

Quotes vary wildly

Without a clear scope every supplier estimates something different, so prices are not comparable and the choice becomes a gamble.

The budget no longer holds halfway

Whatever was not agreed up front returns as extra work during the build — at the point where changing is most expensive.

There is an idea, but no plan

The direction is clear, but the translation into functionality, technology and phasing is still entirely missing.

What you get

Not a consultancy report, but a workable plan. You can act on it — with us or with another supplier.

Problem definition

What are we solving, for whom, and how will we know it worked.

Functional scope

What will and explicitly will not be built, and what moves to a later phase.

Technical architecture

Data structure, integrations, security and the choices that are hard to reverse later.

Visual design

The key screens and user flows, so everyone involved can see what they are getting.

Timeline and phasing

What comes first, what comes later, and which dependencies drive the order.

Budget and risks

A substantiated estimate, with the assumptions and risks it rests on.

Proven in practice

From question to workable plan

Projects where we first established the problem, the scope and the technical direction before anything was built.

Concept for an automated collection kiosk

A process involving drivers, administration and warehouse worked out into a single self-service flow.

Digital platform for complex applications

A fragmented application process rethought and translated into one case management environment.

Concept for connected roadworks signage

Electronics, connectivity and a web platform brought together into one feasible concept.

View all projects

Our approach

A few weeks of work, at a fixed price, with a concrete result. Offset against development if you continue with us.

Sharpening the problem

Conversations with management, users and IT. What does it cost today, what should it deliver, and how will success be judged.

Mapping the current situation

Which systems are running, where the data sits, which processes depend on them and which constraints are fixed.

Weighing the options

Off-the-shelf software, custom build, integration or a combination. We set out the options side by side with their costs, risks and consequences.

Making it visible

We map out the key screens and user flows, so the solution can be discussed through images rather than descriptions.

Fixing scope, timeline and budget

What will be built, in what order, at what cost, and on which assumptions and risks.

Deciding

You decide on the full picture: build, postpone or take a different route. The result is yours, including if you continue with another supplier.

Frequently asked questions

Are we obliged to build with you afterwards?

No. The engagement is set up so that you can decide freely afterwards. If you choose us, development follows on seamlessly.

Why not start building straight away?

Because changing something during development is far more expensive than changing it beforehand. The weeks invested here are recovered in avoided rework and rebuilding.

How long does this take?

Usually a few weeks, depending on the scale and the number of people involved. The duration is agreed up front.

What if off-the-shelf software turns out to be enough?

Then we say so. One of the possible outcomes is that building is not the best choice. That is a valuable result too.

Who from our organisation needs to be involved?

Someone who can decide, someone who knows the process day to day, and someone with a view of the existing systems. A few short sessions is usually enough.

Can we use the result for a procurement process?

Yes. A fixed scope, functional description and technical direction make quotes comparable and limit discussion later on.

What if the scope changes later anyway?

It happens. The difference is that you then know what is changing and what it costs — instead of discovering it halfway.