How we scope an MVP for a UK founder
The first week of an engagement: what we ask, what we write down, and what we refuse to put in version one.

- Written by
- Jareer Zeenam, Technical Lead
- Published
- Reading time
- 1 min read
Week one is not a workshop theatre
An MVP usually takes us 4 to 5 weeks, and a larger build 10 to 12. The first week is a call, a written scope, and a number. That is the same process described on how we work and on MVP development.
What we ask
- Who is this for, in one sentence.
- The two or three flows that must work on day one.
- What you will do after launch, sell, raise, or run it yourself.
- Who will answer questions during the build.
What we leave out
Admin for every future role. Native apps before you have users. Integrations you cannot name a vendor for. If it is not needed to get a customer in front of the product, it waits.
What you get in writing
What is in, what is out, a timeline, and a price. Website work starts from the packages on pricing. Custom product work is quoted after a free call. If you want that conversation, book a call.


