MVP Development en Manchester
How we work in Manchester
What gets rescued and what gets thrown away
With a half-built product you almost never keep everything or bin everything. Usually the product decisions and the design hold up and the code does not, or the other way round. It is decided piece by piece on technical grounds, never on what it cost: money already spent does not come back by building on top of it.
The first thing we write is tests
On someone else's code with no tests, nothing can be changed safely, because there is no way to know what broke along the way. Before touching any feature we cover what the product already does and genuinely matters. It is slower for a fortnight and considerably faster every week after that.
The users you already have cannot be reset
A half-built product usually has people inside it: accounts created, data piled up and some company genuinely using it. That removes the comfortable option of starting again clean. Data migration is planned at the beginning, because it is what ends up deciding how much of the model can change.
A date to decide whether it carries on
The risk with an inherited product is paying for it indefinitely because nobody wants to be the one who stops it. We set a date and a test: what has to be working and what has to have happened with real users to justify the next stage. If it does not, it stops, and having written that down beforehand is what makes it possible.
Answering your questions
What people ask us about MVP Development in Manchester.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
MVP Development: stack, process, use cases and FAQs