The $3,500 planning sprint counts towards your first development payment if you build with us.
You need an MVP when it is time to test the idea on real users instead of in meetings. An MVP is the first working version of a product with only the features the test cannot run without: a person goes through the key scenario end to end and shows by their behaviour whether they need the product. Everything else waits until it is clear what gets used and what does not.
We build web products: applications that open in a browser on desktop and mobile, without separate native apps. We design the MVP so it does not have to be rewritten after the first hundred users. The first version has few features, but the data structure and architecture are laid out for growth, so the next capabilities are added to a system that already works.
Who it is for
Book a 20-minute callMost often an MVP is ordered by startup founders who have an idea and a budget to test it but no technical partner, and by companies that need to show an investor or their first clients a working product instead of a deck. The second common case is a process that already lives in spreadsheets and messengers: order tracking, calculations, dealer requests. That process moves into a system, and the first version covers exactly it, with no extra sections.
If an off-the-shelf tool covers the job — a CRM, a website builder or a plugin — we will say so on the first call. The same goes for cases where what you need is a website: a landing page, a catalogue or an online store costs less and takes less time than an application.
What MVP development includes
The work covers everything needed for the product to run for your users:
MVP or an off-the-shelf tool? We will tell you in 20 minutes
Leave your number — we will call back within one business day, go through your idea and tell you whether you need development or a CRM, a builder or a plugin already covers it.
How we work
01.Call and planning sprint
We start with a free 20–30 minute call: you describe the idea, we ask about users, processes and constraints and say whether we take it on. Next comes the planning sprint — two weeks, $3,500 — after which you hold the specification, the architecture, the development plan and a fixed estimate.
02.Development and handover
Development runs in sprints. Every week we show a 30-minute demo, and on Friday we send a written report: what is done, what is next, what is in the way. At the end we hand over documentation and access, and since the code sits in your repository the whole time, no separate handover procedure is needed.
What it costs
Planning sprint
We name the development price after the planning sprint: before it any figure would be made up, because the scope is not described yet. The sprint costs $3,500 and counts towards your first payment if you order development from us. Development itself is paid in three instalments: 40% at the start, 40% after the mid-project demo and 20% at handover.
The closest example by approach
Questions we hear most often
How is an MVP different from a full product?
By the number of features. An MVP includes what the hypothesis cannot be tested without. The code and the architecture are the same, so later features are added to a foundation that already works.
How long does MVP development take?
You see the exact timeline in the plan after the planning sprint, together with the price.
Can we start with planning and design and order development later?
Yes. After the planning sprint you keep documents any team can work from. That is what happened with the tyre and wheel marketplace: we did the planning and the design, and another team built it.
Who owns the code?
You do. The repository is in your name from day one, and the rights to the code transfer once the work is accepted.
What do you build with?
We choose the stack for the project and name it before the contract is signed. We use mainstream tools so any team can pick the code up.
