MVP build: a first version real users can try
For founders and teams with a product idea who want a first working version in front of real users, without building everything at once.
An MVP, or minimum viable product, is the smallest version of a product that does its main job well enough for real users to try. An MVP build at Vyorde covers the scope, design, build and launch of that first web or mobile app, typically in 6 to 12 weeks, on accounts in your name.
- Typical timeline
- 6 to 12 weeks. The exact dates are in your quote.
- Quote
- A written quote after a short, free call
What you get
A scope on one page
What goes into the first version, and the longer list of what waits. Agreed before we start.
Design
The main flows and screens, including the empty and error states nobody remembers.
The build
A working web or mobile app, built in stages you can click through as we go.
Launch
Live on hosting and app store accounts opened in your name.
The basics done properly
Logins, backups and error tracking from day one, so the first users don't find out the hard way.
A clean handover
Code you own once it's paid for, plus notes for whoever works on it next.
How it goes
We cut the scope.
The first version needs to answer one question: will people use this?
You see it early.
Rough screens first, while changing your mind costs an afternoon.
We build in pieces.
Short updates and a test version you can use, instead of a big reveal at the end.
It goes live.
We launch, watch what real users do, and fix what they trip over.
Every project follows the same five steps. See the full process.
What's not included
- Everything on the long list. What waits is written down, and gets its own scope later.
- A brand identity. If you need a logo and guidelines, that is Brand Identity, scoped separately.
- Marketing, advertising and app store promotion after launch.
- Fees charged by others, such as hosting, app stores and payment providers. Those are billed to your own accounts.
- Looking after it month after month. That is a support agreement, if you want one.
Before you start
- One sentence on who it is for and what they do with it
- The long list of everything you would like, so we can cut it together
- Anything it must connect to on day one: payments, logins, another system
- A date that matters, if there is one, and why
- One person who can decide for your side
You don't need all of it for the first call.
Questions about the MVP Build
What if we want to add something halfway through?
We talk about it. Either it swaps out something of similar size, or it goes on the list for the next version. You hear the effect on the dates before anything changes.
Is an MVP just a cheap, rough version?
No. It's a small version. What's in it should work properly. What's left out simply isn't there yet.
What happens after launch?
Your call. We can keep building under a new scope, look after it under a support agreement, or hand it to your own developers.
What do you need from us to start?
One person who can decide, the long list of what you would like, and time for a few calls in the first week. You don't need a specification. We write the one-page scope together.
Who owns the code and the accounts?
You do. The code and designs are yours once the work is paid for, and the contract says so before we start. Hosting and app store accounts are opened in your name from the first day. More on How we work.
How is this different from your custom software service?
An MVP Build is one first version with a clear end. Custom software is the wider service: larger systems, internal tools and integrations, built in stages. Many projects start as the first and carry on as the second.
What does it cost?
It depends on the scope we agree. You get a written quote after a short, free call, with the scope and the dates next to it.
More questions are answered on the FAQ page.
From Insights
The other two packages
- 01Technical AuditTypically 1 to 2 weeks
- 03Fractional CTOTypically 2 to 3 weeks to get up to speed, then month to month
Last updated