HOW IT WORKS

You do not need 45 pages to start.

Nobody arrives with a finished brief. We build in stages, so you see it working early and nothing big is locked in before you have had your say.

01 / UNDERSTAND

01

Understand

The first stage is about understanding the problem properly, before anyone talks about what to build.

What happens

We talk through the problem, the workaround you are using now, and who it affects. Usually that means sitting with the people doing the work, not just the person who called us.

What you see

A written summary of what we heard, in plain English. It is there so you can correct us early, while correcting us is free.

What you decide

Whether the problem is worth solving with software at all. Sometimes the honest answer is that a change to the process gets you most of the way there.

02 / PLAN

02

Plan

Once we know the problem, we work out what to build and in what order. How much planning that takes depends on how complicated the build is.

WHAT HAPPENS

We map the build: what it does, how it fits with the tools you already use, and what comes first. On a straightforward project that sits inside the work. On a complex one, the scope is worth designing properly on its own before anyone commits to building, so we quote that as a separate piece of work and you get a finished plan out of it either way.

WHAT YOU SEE

A plain-English plan with scope, priorities and costs, before anything gets built. Not a technical document you need somebody to translate for you.

WHAT YOU DECIDE

Whether to build, change the order, or stop. If the project is complex enough to need its own scope design first, you decide that here, before there is a build cost attached to anything.

03 / BUILD IN STAGES

Build in stages

This is the part most people worry about, because it is where a build tends to go quiet. We work in stages so that does not happen. Each stage produces something you can open and use.

WHAT HAPPENS

We build in stages rather than disappearing for three months. Each one delivers a working piece of the system, not a progress report about one.

WHAT YOU SEE

Working software early, not pictures of it. You use it the way your team would use it, on a real browser or a real phone.

WHAT YOU DECIDE

What changes at the end of each stage, while changing it is still cheap. Nothing large gets locked in before you have had a chance to use it.

04 / LAUNCH & IMPROVE

04

Launch & Improve

Launch is not the end of the work. The first few weeks of real use tell you things no amount of planning will, so we treat that as part of the job rather than as a surprise.

WHAT HAPPENS

We get it live and help your team settle into using it. That usually means being around more in the first few weeks, not less.

WHAT YOU SEE

The system running on real work, with the rough edges getting sorted as they turn up.

WHAT YOU DECIDE

What gets improved next, once you have used it properly and know what actually matters.

05 / THE PRACTICAL BITS

The questions that actually

hold people up.

01

Cost and scope

You get an agreed plan with scope, priorities and costs before the build starts, so the number is not a surprise at the end.

02

Who owns it

What we build for you is yours. Where a build uses third party platforms or licensed components, those keep their own terms, so the agreement sets out exactly what transfers and what is licensed.

03

After launch

Support continues as the system changes and grows. A business that is working will keep finding new things it needs, and that is normal rather than a sign something went wrong.

06 / Questions

Questions

01 / How involved do we need to be?

Most of the work is ours. We need you at the start and end of each stage, to look at what exists and tell us what to change. Between those points you should be able to get on with running the business.

02 / How long does a build take?

It depends on the scope, so the honest answer is that we can give you a range once we understand the problem. What we can say is that you will not be waiting until the end to see something. Each stage delivers a working piece rather than a progress report.

03 / Can you work with our existing systems?

Often, yes. We look at what is worth keeping and connecting before suggesting anything gets replaced. Replacing software that already works is expensive and rarely necessary.

04 / What if priorities change mid-build?

That is part of why we build in stages. Priorities get set again at the end of each stage, before the next one starts, so a change of direction costs you a stage rather than a project.

NEXT STEPS

Bring the problem.
We will help define what to build.

A 30 minute conversation about what is happening now and what a better system could look like. You do not need a technical brief.

Copyright 2026. Designed For Results. All Rights Reserved.