An Ullage MVP is working software in production, not a prototype. Week one is scope and architecture, weeks two to five are build cycles with something usable at the end of each, and week six is deployment and handover. You own the repository, the infrastructure and the documentation from the first commit.
Something real users can use for a real task, deployed on infrastructure you control. Not a clickable prototype, not a design file, not a demo that only survives the happy path. The point of a minimum viable product is the viable part: it has to be able to be wrong in public, which a prototype never is.
We write down what is being built, what is deliberately left out, and the one metric that will tell us it worked. Most of the risk in a six-week build lives in this document, which is why it exists before any code does — and why you keep it even if you decide not to go ahead.
Each week ends with software you can actually use, deployed. That cadence is not a ceremony; it is how scope stays honest. When a feature turns out to matter less than it looked, you find out in week three with time to trade it for something better, instead of in week six with nothing to trade.
Deployment, documentation, a walkthrough with whoever will carry it, and access to everything: repository, infrastructure, keys. You leave able to continue with your own team, another vendor, or us. An engagement that only works while we are still in it is not a service, it is a hostage situation.
Some problems are not MVP-shaped: heavily regulated flows, deep integrations with systems nobody can get access to in time, or products whose entire value is a data set that does not exist yet. When that is the case we say so on the first call and tell you what we would do instead.
A fixed part for the build plus a variable part tied to one metric you choose. The fixed part depends on scope and lands at roughly a fifth of what the same build costs at market rates; you get the number in writing after the first call, before anything starts.
You do, from the first commit. The repository is yours, the infrastructure is in your accounts, and the documentation is written for someone who was not in the room. There is no license, no runtime fee and nothing to buy out at the end.
Most clients carry it themselves, which is the point. If you want us to keep going, we scope another short engagement the same way. There is no retainer, and nothing about the handover assumes we will be back.
Thirty minutes and you leave with a written scope for the six weeks — free, and yours either way.