No black boxes, no surprise invoices
Five stages, a demo every two weeks, and one person who knows the answer to your question. Here is exactly what happens and what you get at each point.
Discovery
A working session with the people who do the job today. We map the process, the systems it touches and the constraints nobody wrote down.
What you get
- Written scope document
- Systems and data map
- Risks and assumptions
- Estimate and timeline
Design
Wireframes, then a clickable prototype. Stakeholders react to something real while changes are still cheap.
What you get
- Clickable Figma prototype
- Screen inventory
- Design system basics
- Signed-off scope
Build
Two-week sprints. Each ends with a demo of working software and a short note on what is next.
What you get
- Working software each sprint
- Sprint demo recordings
- Code in your repository
- Weekly progress note
Test
QA across devices, browsers and edge cases, plus a session with your actual users before anything ships.
What you get
- Test plan and results
- Bug list with severity
- User testing findings
- Go/no-go report
Run
Launch, handover and support. The relationship does not end when the invoice does.
What you get
- Deployment and monitoring
- Written documentation
- Team training session
- Support window
Three ways to engage
Same process, different commercial shape.
Fixed price
Best when the scope is clear
One price agreed after discovery, with milestones and a change process in writing.
- Defined deliverables and dates
- Milestone-based payments
- Changes quoted before they start
- Support window after launch
Dedicated squad
Most popular for products
A monthly team — developers, QA and a lead — working only on your roadmap.
- Two-week sprints with demos
- Scale the team up or down monthly
- Your repository, your IP
- Direct access to every member
Hourly
Best for changes and support
A block of hours for improvements, fixes and small features on an existing system.
- No minimum commitment
- Monthly statement of hours used
- Same engineers each time
- Priority response option
How we behave when things go wrong
What if the scope changes mid-project?
We quote the change before doing it. Absorbing scope quietly is how projects slip, so we would rather have the awkward conversation in week five than the very awkward one in week twelve.
What if we are unhappy with progress?
Escalate to your point of contact. Fixed-price work has milestone exits, and retainers run month to month — you are never trapped in a bad engagement.
What if a deadline is at risk?
You hear about it in the weekly note, with the options: cut scope, add people, or move the date. Never a silent slip discovered at the demo.
Who owns the code and accounts?
You do. Work happens in your repository under your cloud accounts from the first commit.
Start with a discovery session
You keep the written scope even if you never hire us. It is a reasonable way to find out whether we are worth the money.