How we work

Four stages, no surprises

Most projects fail in the first three weeks, not the last three. So we front-load the hard questions and keep you in the room while we answer them.

Discover & scope

1–3 weeks

We sit with the people who will actually use the system, map the real workflow — including the spreadsheet nobody admits to — and write down the constraints. You leave with a scoped plan, a fixed estimate and a list of the risks we found. If we think the project is a bad idea, this is where we say so.

Workflow mapping Compliance review Fixed estimate

Design & prototype

2–4 weeks

Interface and data model designed together, then put in front of real users as a clickable prototype before a line of production code exists. Changing a screen now costs an afternoon; changing it after build costs a fortnight.

Data model Clickable prototype User testing

Build & integrate

8–20 weeks

Two-week increments against an agreed backlog, with a working environment you can log into from day one. Integration work starts early rather than being saved for the end, because that is where the surprises live. Security review and PDPA controls are part of the build, not a phase after it.

2-week sprints API integration Security by design

Run & evolve

Ongoing

Go-live is the start of the relationship. Monitoring on the environment, support with a defined SLA, training for your team, and a quarterly roadmap review — with the same engineers who built it, not a ticket queue in another timezone.

Monitoring & SLA Quarterly roadmap Team training

What you get

Deliverables, stage by stage

Every stage ends with something you own and can take elsewhere if you decide not to continue.

Stage	You receive	You decide
Discover & scope	Scoped specification, fixed estimate, risk register, integration inventory	Whether to build at all
Design & prototype	Clickable prototype, data model, user test findings	Whether the design is right
Build & integrate	Working software every two weeks, test environment, release notes	Priority order of the backlog
Run & evolve	Production system, documentation, training, monitoring, SLA	The next quarter's roadmap

Process questions

The awkward ones

It usually does. Changes are priced as they arise against the fixed baseline, and you decide whether to add them now, defer them, or drop something else. What we avoid is discovering the change at the end.

Discovery is intensive — expect a few half-days from the people who know the workflow. After that, roughly two hours a fortnight for a sprint review, plus user testing sessions at the prototype stage.

Yes, and we prefer it. A scoped discovery or a single integration is a sensible way to find out whether we work well together before committing to a full build.

You keep everything produced up to that point — specification, design, code, data. There is no lock-in clause, because a client who stays out of obligation is not a reference.

Next step

Bring us the messy problem. We like those.

A 30-minute call, no deck, no obligation. Tell us what is breaking and we'll say honestly whether we're the right team to fix it.

Start a conversation WhatsApp us