MVP: test the idea in two months, not a year.
We build the first version of your product, one you can put in front of users and charge money for. We cut everything unnecessary, keep the core scenario and set up analytics. That is how we launched our own products, and we know which features can wait.
Who it is for
- Founders with an idea and first customers who need a product to test demand and talk to investors.
- Established businesses launching a new line or a service for their customers.
- Teams with a prototype in Figma or no-code that has hit its limits.
- Corporate projects that need to show a working version quickly before securing a large budget.
What you get.
Together we define one core scenario and cut the rest. The result is a list of 5–10 features, not 50.
Scenarios, screens, data structure, stack choice. 1 week, then an exact estimate.
A prototype and a design system: neat, fast, no 'unique' illustrations at this stage.
Next.js and Node.js for the web, Flutter for mobile: whatever gets to release fastest.
Kaspi Pay or subscriptions through Apple and Google from the first version: an MVP has to be able to take money.
Events, funnels, cohorts. Without data an MVP is pointless.
Servers, backups, monitoring, one-command deploy. Costs next to nothing at the start, scales later.
Domain, the stores if needed, a landing page to attract the first users.
After launch: weekly sprints driven by data and feedback. Support by subscription or in stages.
What we cut from an MVP, and why.
An admin panel with charts becomes a database table and Metabase. A role system becomes two roles. Notifications across every channel become one Telegram bot. A personal account with settings becomes a single page. Multiple languages become one. Integrations with ten services become one, the one you cannot do without.
All of that is added later, once it is clear the product is needed. Until then, every extra feature is weeks and money spent on something that, quite possibly, nobody will open.
We went through this with 1Study: the first version was an app for a single school, with no white label, subscriptions or SEO storefronts. All of that came when the schools numbered in the dozens.
How we work with startups.
Payment in stages: discovery, design, development, launch. Payment per sprint is possible so that your money is not tied up. The code and infrastructure are yours from day one, with no lock-in to the studio.
After launch we can stay on as your technical team by subscription, which is cheaper than hiring developers in-house before the first revenue. Or we hand the project over to your team with documentation.
We do not take equity in projects and do not work 'for a share': only a clear estimate.
From enquiry to result.
- 1Scope
Half a day with the founder: the core scenario, who pays and for what, what gets cut. Free of charge.
- 2Discovery
1 week: prototypes, data structure, stack, estimate. Paid separately; the output is yours.
- 3Development
4–6 weeks in sprints, a demo every Friday. The first working scenario in 2 weeks.
- 4Launch
Infrastructure, analytics, first users. You start selling.
- 5Iterations
We review the data, fix and add. Weekly sprints by subscription or in stages.
What affects the price.
A web MVP with authentication, one core scenario, payments and analytics is ₸1,200,000–2,500,000 and 4–6 weeks. A mobile MVP on Flutter with a back-end is ₸2,500,000–4,000,000 and 6–8 weeks. Discovery is from ₸200,000 and is deducted from the estimate if you continue.
Subsequent iterations are per sprint from ₸300,000 a week, or by subscription to a technical team.
We do this for ourselves too.
The studio's three products, 1Study, 1Work and 1Ticket, each started as an MVP for a single client. Today they serve 71 organisations with ₸1.82bn in turnover. For clients we have built MVPs of a loyalty platform for fitness clubs and an HR platform. See our case studies.
The short version.
How much does an MVP cost?
From ₸1,200,000 for a web version and from ₸2,500,000 for mobile. That is the price of a first working version with payments and analytics, not a prototype.
How fast can you deliver?
4–8 weeks from the start of development. Plus a week of discovery before that.
What if we have a no-code prototype?
Excellent, it will speed up discovery. We move what works into code once no-code hits its limits on speed, payments or integrations.
Do you take equity in the project?
No. We work by estimate and contract. It is fairer for both sides.
What if everything has to be rewritten after the MVP?
We choose the stack so that the MVP grows into a product without a rewrite: the same Next.js, Node.js and PostgreSQL that run our own products for thousands of users.
Have an idea? We will scope the MVP in half a day, free of charge.
Tell us what the product is, who will pay for it and what you already have: a prototype, customers, a team. We will suggest where to start.