By Danijel Balog, Founder, Fragon Studios · Last updated: 2026-11-13
MVP development in 12 weeks
The smallest version of your product that real users work with. For startups and small and medium-sized businesses (SMEs) that want to test an idea on the market before committing a large budget. Developed in Linz, with meetings in person possible.
- 30 minutes
Initial consultation
Then a price and time range within one business day.
- 2 weeks
Discovery
The analysis before the build.
- around 6 weeks
Build
A demo every week.
- after 8 to 12 weeks
Go-live
An app MVP is in the store.
In short
- An MVP is the smallest version of your product that real users work with.
- A lean MVP costs €15,000 to €25,000, an app with login, backend and store submission typically €25,000 to €40,000, net.
- Live after 4 to 12 weeks, usually at a fixed price once the discovery phase is done.
- Below €15,000, an architecture workshop from €1,500 is the more honest start.
What is an MVP, and what is it not?
The smallest version of a piece of software that solves a clear problem and is used by real users.
In the MVP
- one core feature that solves the problem
- two to three core screens
- login, where the product needs it
- a connection to a backend or an existing system
- operation with real users
In the next version
- secondary features and edge cases
- elaborate animations and polish
- finely graded roles for every department
- integrations with every tool in the company
- optimisation for load peaks that do not exist yet
An MVP goes live and delivers data for the next version.
An MVP (minimum viable product) is not a clickable mock-up and not a demo for a pitch. It goes live: to the App Store, onto the web or to the team that works with it. It delivers data for the next version. Anything that does not contribute to that comes later.
How much does an MVP cost?
A lean MVP €15,000 to €25,000, an app with login, backend and store submission for iOS and Android typically €25,000 to €40,000.
The range depends mainly on the number of integrations, less on the number of screens.
| Scope | Price | Typical content |
|---|---|---|
| Lean MVP | €15,000-25,000 | one platform or a simple app, few integrations, no login |
| App with backend | €25,000-40,000 | login, iOS and Android, store submission |
| MVP project with discovery and several integrations | €30,000-45,000 | 2 weeks of discovery, 6 weeks of build, around 250 hours, operation on Fragon Cloud |
A small internal tool starts at €5,000 (custom software for SMEs). The app cost calculator gives you a first range for apps.
How long does it take to develop an MVP?
Between 4 and 12 weeks, and an app MVP for iOS and Android is in the store after 8 to 12 weeks.
The 12 weeks are realistic for a tightly scoped project, but not a promise for every idea.
If the scope grows, we cut back together instead of stretching the schedule.
A typical project starts with two weeks of discovery, followed by around six weeks of build. If the feature list grows beyond that frame, there is usually still too much in it.
Typical scenario: an app for the field team
An industrial business records orders in the field on paper and types them up in the office in the evening. The MVP for this takes eight to ten weeks, with login, order list, photo upload, offline sync and a connection to the existing ERP. Not a customer project, but a case that comes up again and again.
How does an MVP project work?
In five steps from the initial consultation to go-live.
Initial consultation, 30 minutes
No obligation, in person in Linz or by video.
Discovery
Two to ten working days at the day rate of €1,100.
Quote
Usually a fixed price. If the work is genuinely open, time and materials with a fixed weekly cap.
Build with weekly demos
Feedback within the agreed scope costs nothing extra.
Go-live
On Fragon Cloud at Hetzner in Germany and Finland, apps with store submission.
New features get a written price before we build them.
- In the initial consultation we listen and check whether we can seriously deliver the project.
- In discovery we cut the scope back to what is necessary and translate it into effort.
- For a clearly defined MVP we usually offer a fixed price. If the work is genuinely open, we say so and bill time and materials.
- Every week you see what has been built. New features go through a written change request with a price before we build them.
- Go-live includes deployment to Fragon Cloud and, for apps, store submission. After that we train your team.
How the day rate, the fixed price and changes fit together is explained on How we price.
Who builds your MVP?
Danijel Balog, founder and lead engineer, from architecture to deployment.
The handover is written for a developer you do not know.
Danijel is your direct contact. Fragon Studios is a small studio in Linz. So that your MVP does not depend on one person, every commit lands in your Git repository if you buy. The handover includes an architecture document, a runbook and an onboarding guide. More on About Fragon Studios.
What happens after the MVP?
You evaluate what real users do and then decide on the next version.
If you buy, the source code is yours, and you can carry on with us, with another team or in-house. In the instalment model the code stays with Fragon Studios, and you get an export of your data and a regulated exit.
We fix bugs under the warranty, and maintenance is optional.
- We fix defects in what we delivered under the statutory warranty of Austrian law.
- Updates, monitoring and further development are covered by an optional maintenance contract or billed at the day rate.
- The next stage starts with a new discovery phase based on real usage data.
- A switch to another team includes a joint code walkthrough, the operations manual (runbook) and all access credentials.
When is it too early for an MVP?
When the requirements are unclear or the budget for an app or product MVP is below €15,000.
Architecture workshop, from €1,500
One day, on site or remote, with an architecture sketch and next steps.
Feasibility analysis, from €3,000
One to two weeks, with an effort estimate and a stack recommendation.
An off-the-shelf tool instead of a custom build
If a SaaS product covers your case, that is almost always cheaper. Read the guide Custom or off-the-shelf software.
The feasibility analysis clarifies whether the idea works technically.
- At the end of the architecture workshop you have a written architecture sketch, a risk assessment and prioritised next steps.
- The feasibility analysis is a technical assessment of one to two weeks with an effort estimate and a stack recommendation. Useful when it is still open whether the idea works technically.
- If an established SaaS product covers your case, that is almost always cheaper and faster.
No serious MVP can be built for less than €15,000. We would rather say so before the first meeting than after the third.
Frequently asked questions
What is the difference between an MVP and a prototype?
A prototype shows what something could look like. An MVP runs in production.
An MVP has real users and delivers data for the next version.
Do we get a fixed price for the MVP?
After discovery, usually yes.
For well-defined MVPs, a fixed price is our standard. Only if the work is genuinely open do we bill time and materials, with a fixed weekly cap.
Who owns the MVP's code?
If you buy, you do, in full.
Every commit lands in your Git repository, and you also get the rights of use and the documentation. In the instalment model the code stays with Fragon Studios, and you get the running application, an export of your data and a regulated exit.
Do you only build MVPs as apps?
No. An MVP can also be a web application or an internal tool.
We build apps with React Native and Expo for iOS and Android, web applications with Next.js 16 and the backend with .NET 10 and PostgreSQL.
Can an MVP get funding in Upper Austria?
That depends on the product.
DIGITAL.PLUS 26 excluded product development, apps for sale in the App Store and applicants who themselves offer IT solutions in the area applied for, and only funded internal company tools. According to the programme page, the application deadline ended on 2 November 2026. For a product with real technical risk, the FFG Basisprogramm or the FFG Kleinprojekt may fit, with ongoing submission until 31 December 2026. Details in the guide Funding for software in Upper Austria.
Further reading
Let's talk.
An MVP idea on the table?
Tell us about it in 30 minutes. You will get a price and time range within one business day.