InterLAB references: a web app MVP is 2–5 million ₸ and 6–12 weeks, a turnkey product 5–15 million ₸ and 2–4 months, complex systems with many roles and integrations from 10 million ₸ and 4–8 months. The price is made up of user flows, roles and permissions, integrations, data and reporting requirements — not the number of screens. A web app avoids two cost lines familiar from mobile development: app store publication and a second platform — one codebase runs in every browser.
Contents
Budget and timeline references
Let's start with the numbers. These are InterLAB's public ranges — a sense of scale, not a price list: we give a fixed price after the brief, once the flows, roles and integrations are clear.
2–52–5
million ₸ — MVP, 6–12 weeks
5–155–15
million ₸ — turnkey product, 2–4 months
10+10+
million ₸ — complex systems, 4–8 months
22
weeks to a clickable prototype
Within a range the price depends on scope. A “customer account” can be three screens with an order status, or a system with payments, documents, chat and reports for managers. In an email they sound the same, but they are different projects.
What makes up the price
User flows
- Why it affects the price
- Every user path means screens, logic, validations and tests
- How to save without harm
- Keep one main flow, end to end, in the first version
Roles and permissions
- Why it affects the price
- Customer, manager and admin see and do different things — separate access logic
- How to save without harm
- Start with two or three roles, add fine-grained rights later
Integrations
- Why it affects the price
- 1C, Kaspi, payments, CRM, messengers — each has its own protocol and its own failures
- How to save without harm
- Limit the first release to one or two key integrations
Data and reports
- Why it affects the price
- Operation history, Excel import, exports and analytics need a well-designed data structure
- How to save without harm
- Basic reports first, complex ones on real demand
Design
- Why it affects the price
- Custom components take longer to draw and build than standard ones
- How to save without harm
- Rely on a design system and refine it where it matters
Reliability
- Why it affects the price
- Backups, an action log, load, security
- How to save without harm
- Do not save here: it is cheaper to build in from the start than to add later
How the budget differs from a mobile app
With the same business logic, a web app and a mobile app are priced on the same scale — InterLAB's ranges match. The difference is where the money goes.
Web app
- One codebase runs in any browser on any device
- An update reaches every user at once
- No developer accounts or store reviews needed
- The user opens the app via a link
Mobile app
- iOS and Android — two platforms or cross-platform code
- Updates go through App Store and Google Play review
- Annual and one-off developer account fees
- Deeper work with the camera, push notifications and offline mode
What usually goes into the first version
A good first version solves the main task completely rather than every task halfway. A typical web app MVP includes:
- Sign-in and two or three roles with different rights
- The main flow end to end: for example, request — processing — result
- An admin panel for operators and managers
- One or two integrations the process cannot work without
- Basic reports and data export
- Analytics of key user actions
- Backups and a log of important actions
Complex analytics, rare scenarios, automation of exceptions and a mobile app are usually postponed. They are easier to design once you can see how people use the first version.
Costs after launch
The launch budget is not the last line. Plan the recurring costs in advance so they do not come as a surprise:
- Server and database — they grow with the number of users and the volume of data
- Domain and certificate
- Third-party services: SMS, email delivery, maps, payment fees
- Support: updates, monitoring, bug fixes
- Planned development: new features after the first version
How to get an accurate estimate
Describe the flows
Who uses the app, what they do and what they get in the end. The brief generator helps you put this together in a few minutes.
Gauge the order of magnitude
The MVP complexity estimate shows the scale by flows, roles and integrations even before you talk to a contractor.
Brief
At the meeting we go through flows and constraints and clarify integrations and timelines.
Itemised estimate
We come back with an estimate by stage and a first-release scope that fits your budget.
The price of a web app is set by its flows and integrations, not by the number of screens.
