Serious software, delivered without surprises.
Projects rarely fail on code. They fail on fuzzy scope, slow decisions and long silences. Everything about how we work is built to remove those three, from a fixed scope before we start to a working build every two weeks.
- Fixed quote
- before any work starts
- Every two weeks
- a demo you can click through
- Within the hour
- a reply to your messages
- Yours
- code, files and accounts
Five phases. Each ends with a decision you make.
Nothing moves forward on an assumption. Every phase finishes with something you can see, and a clear yes or no from you before the next one starts.
Discovery
Understand the problem before pricing the solution.
We talk to the people involved, look at what exists today and map how the work really flows, awkward exceptions included. For an existing product, we read the code and the data before suggesting anything.
- 01Stakeholder and user interviews
- 02Workflow and systems mapping
- 03Risks, assumptions and open questions
- Written scope
- Prioritised feature list
- Fixed, itemised quote
An hour or two with the people who do the work, and access to anything that already exists.
Ends when You approve the scope and the quote.
Design
See the product before any production code exists.
We design the key journeys as a clickable prototype, test it with real users where we can, and settle the edge cases on screen, where changing them is cheap.
- 01User flows and information architecture
- 02Clickable prototype of the key journeys
- 03Visual design and component system
- Clickable prototype
- Design system
- Build-ready screens
Feedback within a couple of days at each review, from someone who can make the call.
Ends when You sign off the designs for the first release.
Build
Working software every two weeks, not a big reveal at the end.
We build in two-week sprints on a staging link you can open at any time. Each sprint ends with a demo and a decision about what comes next, so priorities can shift without derailing the plan.
- 01Sprint planning against the agreed scope
- 02Development with code review and tests
- 03A demo on staging every two weeks
- Working build on staging
- Sprint notes
- Weekly written update
Half an hour at each demo, and quick answers when a question comes up.
Ends when You accept each sprint's work on staging.
Launch
A release you can roll back, to a team that knows how to use it.
We test across devices, move your data across, set up monitoring and roll out in stages. Your team gets trained, and nothing goes live without a way back.
- 01Testing and acceptance checks
- 02Data migration and go-live plan
- 03Monitoring, alerts and backups
- Live product
- Team training
- Rollback plan
Final acceptance testing, and the go-ahead on a launch date.
Ends when You give the go-ahead to launch.
Grow
Keep improving it, or hand it over cleanly.
Real users show what matters next. We look after the product on a monthly plan, from fixes and updates to new features, or hand it to your own team with everything they need.
- 01Monitoring and fixes
- 02Roadmap and feature releases
- 03Performance and security updates
- Monthly care plan
- Documentation
- Roadmap for the next release
A view of what your users and your business need next.
Ends when You choose ongoing support or a documented handover.
What a sprint looks like from your side.
Two weeks, three touchpoints, and a staging link that's always current. You always know what's done, what's next and what we need from you.
- Day 01PlanWe agree the sprint's goal with you, drawn from the agreed scope.
- Day 05UpdateA short written note: what's done, what's next, anything we need.
- Day 10Demo and decideYou see the work running on staging and decide what comes next.
Where projects usually go wrong, and what we do instead.
We've seen enough projects stall to know the usual causes. Each one has a fix built into the way we work.
- 01
The scope keeps growing
Each release is fixed in writing. New ideas go to a backlog and are priced for you to approve before anyone builds them.
- 02
Decisions take weeks
We agree one decision-maker on your side at the start, and every demo ends with a clear question for them.
- 03
A surprise at the end
You use the real product on staging from the first sprint, so nothing is unveiled at the last minute.
- 04
Long silences
A written update every week, a demo every two weeks, and replies within the hour.
- 05
Locked in to the agency
Code, accounts and documentation are handed over to you, so you're free to stay or to move on.
Questions
The things people
ask us first.
If yours isn’t here, send it over. We reply within 1 hour, guaranteed, and you’ll get a straight answer rather than a brochure.
How much of our time will the project need?
+
Most in discovery, when we need a few hours with the people who do the work. After that, around half an hour for each fortnightly demo, plus quick answers to questions as they come up. The single most useful thing is one person who can make decisions.
How do you report progress?
+
A short written update every week, a demo on staging every two weeks, and a staging link you can open whenever you like. We talk over Google Meet and WhatsApp or Slack, whichever your team already uses, and reply within the hour.
What if our requirements change mid-project?
+
They usually do, and that's fine. Small changes are swapped into a sprint where they fit. Anything bigger is written up and priced, and only built once you approve it, so the scope never moves without you knowing.
How do you make sure what you build is what we asked for?
+
Every phase ends with something you review and approve: the scope, the designs, each sprint on staging and the launch itself. Nothing moves to the next phase on an assumption.
Do you work alongside in-house teams?
+
Often. We can own the whole build, or take on design or a defined part of the engineering while your team handles the rest. We agree who owns what at the start.
Can you take over a project someone else started?
+
Yes. We begin with a short audit of the code, the designs and the accounts, then give you an honest read on what's worth keeping and what it takes to get releases moving again.
Where ambitious
ideas become reality.
We design, develop, and support digital experiences that turn ambitious ideas into meaningful products.