Process
From first call to long-term support
Every project runs through the same 5 steps. Here is what happens in each one, and what you have in hand when it ends.
The steps
You see working software at the end of every sprint, and you always know what happens next.
Step 1: Discover
We learn your goals, users and constraints, and write them up as a scope you can check.
What you get
- A written scope
- A rough timeline and budget range
- The open questions, listed
Step 2: Design
Wireframes first, then screens you can click through, revised with you before the build starts.
What you get
- Wireframes
- A clickable prototype
- Screens you have signed off
Step 3: Build
Short sprints, each ending in a demo, with code that is tested and documented.
What you get
- A demo at the end of every sprint
- Working software you can click through
- Code reviewed by a second developer
Step 4: Launch
We deploy, hand over access and documentation, and stay close for the first weeks.
What you get
- Your software, live
- Access and logins handed over
- Documentation
Step 5: Support
Fixes, updates and new features for as long as you need them.
What you get
- Fixes and updates
- New features when you need them
- The same team that built it
What holds in every step
We are a small, senior team. Everyone talks to clients, everyone reviews code, and everyone looks after what they build once it is live.
Demos every sprint
Each sprint ends with working software you can click through.
Straight answers
We tell you what something will cost and how long it will take, and we tell you early when that changes.
Reviewed code
A second developer reviews every change before it ships.
New tools, used with care
We pick up new technology early, AI included, when it makes the product better for the people using it.
Three ways to work with us
Compare themFixed scope
An agreed scope, price and launch date. Our team takes it from brief to launch.
When it fitsDedicated team
Developers who work only on your product, inside your tools, sprints and standups.
When it fitsTime and materials
You pay for the time worked, so the scope can change as you learn.
When it fits
Questions, answered
How long does a project take?
It depends on the scope. Send a brief and we reply within one working day with next steps, a rough timeline and a budget range.
Will I see the software before it's finished?
Yes. Every sprint ends with a demo of working software you can click through, so you see progress every couple of weeks, not only at launch.
Who will I talk to during the project?
The people who design and build it. One in-house team handles your project from the first call to support after launch.
What happens after launch?
We stay close for the first weeks, then keep fixing, updating and extending the software for as long as you need it.
Tell us what you’re building.
We reply within one working day with next steps, a rough timeline and a budget range.