- Steps
- 5, always in order
- Typical project
- 6–16 weeks
- Progress
- Every Friday
- Surprises
- None, by design
A typical 12-week project. Yours gets its own schedule after the planning week.
Step by step, in order.
1 of 5
Step 1 · 1 week
Understand
We get to know your business before we build anything: who your customers are, what is slowing you down, and what success looks like. Most failed projects go wrong here, so we take it seriously.
You get a written plan and a fixed price
Step 2 · 2 weeks
First version
Two weeks later you can click through a first working version — not slides, not a mock-up. It answers the biggest question early, while changing direction is still cheap.
You get a first version you can try
Step 3 · 4–12 weeks
Build
We build in one-week steps. Every Friday you see what is new and get a link to try it. No months of silence, no big surprise at the end.
You get visible progress every Friday
Step 4 · Every week
Check
Speed, security, ease of use and correctness are checked every week, not left to the end. If something is not good enough, it does not go out.
You get software that does what we promised
Step 5 · Launch + 30 days
Launch & look after
We launch, watch how real people use it, and fix what they find. Then we hand over cleanly to your team — or keep looking after it for you.
You get a live product, and people who know it
Checked every week, not at the end.
Speed
Every screen is timed. If it opens slowly on an ordinary phone, it is not finished.
Works for everyone
Readable, usable with a keyboard or screen reader, and comfortable on any size of screen.
Safe
Logins, payments and personal data are reviewed every week, not just before launch.
Does what it should
Automatic checks run on the parts that matter most, so a fix never breaks something else.