Consulting · 05
Software product development
From discovery to MVP to a product your customers rely on.
01The problem
Most software projects go wrong before the first line of code.
- 1.1
Building the wrong thing.
Months go into features nobody asked for, because no one tested the idea with real users first.
- 1.2
Scope that never ends.
Without a clear first release, every week adds something and nothing ships.
- 1.3
Code no one else can maintain.
Clever, undocumented code ties you to the people who wrote it.
- 1.4
A launch, then silence.
The product goes live and nobody measures whether it’s working.
02What we do
Built to last, and to hand over.
The same team from first sketch to release, writing code your next team can work with.
- Product discovery
- Who it’s for, the problem it solves, and the smallest version worth building.
- UX and interface design
- Flows and clickable prototypes, tested with real users before we build.
- MVPs
- A first release in weeks, scoped to learn the most for the least.
- Web and mobile apps
- Fast, accessible apps that work on the phones your customers actually use.
- SaaS platforms
- Multiple customers, roles, billing and the admin tools to run them.
- Maintenance and support
- Updates, monitoring and improvements after launch.
03How it runs
From idea to first release.
About sixteen weeks for a typical MVP.
- 01Weeks 1–2
Discover
Users, the problem, and the scope of a first release.
- 02Weeks 2–4
Design
Flows and clickable prototypes, tested with users.
- 03Weeks 4–14
Build
Two-week iterations, each ending with a demo.
- 04Weeks 14–16
Launch
Release, monitoring and support for the first users.
- 05Ongoing
Grow
Improve from what real usage shows.
04What you get
You own all of it.
Code, designs and documentation, in your accounts from day one.
- DEV-01
Product brief
Who it’s for and what it must do.
- DEV-02
Clickable prototype
The product, before it’s built.
- DEV-03
Source code
In your repository, from the first commit.
- DEV-04
Architecture notes
How it fits together, and why.
- DEV-05
Test suite
Automated checks that run on every change.
- DEV-06
Runbook
How to deploy, monitor and fix it.
05Questions
What people ask us.
Who owns the code?
You do. It lives in your repository from the first day.
Fixed price, or time and materials?
Discovery and MVPs can be fixed in scope. Ongoing work is usually a monthly team. We’ll recommend what suits the risk.
Which technologies do you use?
Proven, widely used ones, so you can hire for them later. We’ll explain the choice for your product.
Can you take over an existing product?
Yes. We start with a review of the code and architecture, then agree a plan to stabilise it.
Build the right thing first.
A discovery conversation turns your idea into a scope and a plan.