MVP development: what it costs in 2026 and what the first version includes

Include what the user needs to reach the main result: sign-in, one main scenario from start to finish, a minimal admin panel, a server and a database, and store publishing for an app. Leave for later: extra scenarios, payments and subscriptions if you are testing demand, complex reports, and roles you do not need for the first test.

Start with screens: sketch them in Maketa (maketa.pro) and send the link. Pick one user type first. Postpone in-app payment. Pay in stages, so you see a result before each next payment. Check demand with a cheaper format when a bot or a web version can answer the question.

MyPulso is our own product: a client finds a personal trainer and books a session. We built two Flutter apps, one for clients and one for trainers, with a server behind them. Both are published on the App Store and Google Play. The public versions have no payments or subscriptions; in-app payment for sessions is in testing. That is an MVP: the main scenario works in the stores, and monetisation comes after the first checks. Case: /en/cases/mypulso.

Scope sets the price: screens, roles, integrations, a backend, offline mode. We make a process diagram and a screen list first. The estimate is free. We work under a contract, without VAT, in stages, with the rest paid after each act. You receive the code and documentation. A three-month warranty follows acceptance. We name the delivery date together with the price.