How we work
Four stages. Each one ends with something you can keep.
01Stage by stage
Every stage ends with something concrete in your hands. By launch you hold all four.
01 / 04
We learn how the work happens today, who is involved and what needs to change. Short conversations, not lengthy questionnaires.
What happens
You keep
You decide
Whether the problem is worth solving now, and with us.
02 / 04
We shape the solution: what to build first, how it fits with your existing tools, and what it will take.
What happens
You keep
You decide
Whether to start the first phase, as proposed or adjusted.
03 / 04
Work happens in short cycles with regular demonstrations, so you see progress early and can steer it.
What happens
You keep
You decide
What the next cycle focuses on, and when it is ready to release.
04 / 04
We test thoroughly, release carefully and hand over properly. Ongoing support and improvement are available when you need them.
What happens
You keep
You decide
What support you want, and what to improve next.
02Your decisions
Every stage ends at a gate. You see what was made, then decide to go on, change course or stop. Nothing commits you to the whole project up front.
01
Understand
How your work runs today, and what must change.
02
Define
What to build first, how it fits, what it costs.
03
Design & build
Short cycles and regular demos, so you can steer.
04
Launch & improve
Tested, released carefully, handed over. Then we keep improving.
01
Work is split into phases. You agree to the next once you’ve seen the last one working.
02
A demo at the end of every cycle, so progress is something you can try, not a report.
03
Scope, timeline and cost before you commit, and decisions recorded as they’re made.
04
Readable code, documented decisions and a proper handover, so any team could carry on.
03FAQ
Straight answers on cost, time, ownership and what happens after launch.
Still unsure?
Ask us directlyIt depends on scope, integrations with your existing tools, and the number of platforms. Every project starts with a written proposal that sets out scope, timeline and cost before you commit to anything. We can share typical ranges on the first call.
It depends on what is built first. We plan work in phases, so a focused first release reaches your team early and the rest follows in short cycles. The proposal gives a timeline for each phase.
Ownership is set out in the proposal before work starts. We build so another team, including your own, could pick the work up: readable code, documented decisions and a proper handover.
Yes. Most projects connect to software a business already uses, and we work alongside in-house teams when there is one. We start by learning how the work happens today.
No. Work is split into phases, each ending with something concrete in your hands. You decide on the next phase once you have seen the previous one working.
We test thoroughly, release carefully and hand over documentation. Ongoing support and improvement are available when you need them.
Yes. We are happy to sign a reasonable NDA before you share details of your business or product.
They are held to the same standard. Building and running products of our own keeps us honest about what it takes to make software last, and that experience goes into client work.
04Contact
A few sentences are enough. We’ll take it from there.
About 2 minutes
