Your first version, live in the stores, in 6 to 8 weeks.
One paid discovery week to lock the scope. Then 6 to 8 weeks to a working iOS and Android app in the stores. You own the code on the day you make the final payment.
You own the source code, the designs and the accounts. Take them anywhere.
An MVP is not a demo and it is not a prototype. It is the smallest version of your product that a real stranger can download, use, and pay for, and the fastest honest way to find out whether anyone wants it. We build that version for founders and businesses who would rather learn from a hundred real users in two months than from a hundred slides in six.
Who you will work with
I have shipped 52 apps in seven years, and I have taken over enough half-finished ones to know exactly how a first version goes wrong. It is almost never the code. It is that nobody wrote down what ‘done’ meant.
So that is what the discovery week is for. At the end of it you have a document that says exactly what ships, what does not, and by when, and that document is yours, even if you take it to a different developer.
I am on every project. Not a salesperson, not an account manager. Me.
Before anything is built
One paid week. Fixed price, fixed length, and credited back in full against the build invoice if you go ahead.
| Day | What happens |
|---|---|
| Day 1 | We take your idea apart. Who is the one user, what is the one job they hire the app to do. |
| Day 2 | The feature list, split into three columns: ships, does not ship, phase two. |
| Day 3 | The core screens, drawn and clickable. |
| Day 4 | The technical shape: data, integrations, what is risky and what is not. |
| Day 5 | You receive the scope document, the estimate, and the delivery date. |
What you leave with: a document that names every screen, every exclusion, the price and the date. It is yours whether or not you continue with us.
Why it is paid: because a free version would be a sales pitch, and you would be right not to trust it. Charging for it is what lets us spend the week on your product instead of on winning you.
What an MVP is for
You are buying evidence that people want this, as cheaply as evidence can be bought. Every scope decision below is measured against that and nothing else.
The list nobody else publishes
| ✅ In the 6 to 8 weeks | ⛔ Not in the 6 to 8 weeks | → Scheduled as phase two |
|---|---|---|
| One user type | A second user type or role | Priced separately after launch |
| The core flow, end to end | A web version | → Web Apps & Admin Panels |
| iOS and Android | Offline mode | Phase two |
| Backend + basic admin screen | A full admin panel | → Web Apps & Admin Panels |
| One payment provider | Multiple payment providers, marketplaces, split payouts | → Backend, API & Integrations |
| One AI feature | A second AI feature | Phase two |
| Store submission, both stores | Migrating data from an old system | → App Modernization & Migration |
| Analytics | A custom design system | → UI/UX Design for Mobile |
| 30 days of post-launch fixes | Subscriptions, tenants, seats, billing logic | → SaaS Development |
Nothing in the middle column is refused. It is scheduled, after real users have told you which of it you actually need. That is the entire point of building a first version.
Your Android launch has a hidden queue
Since 13 November 2023, Google requires new developer accounts to run a closed test with 12 testers, enrolled for 14 continuous days, before the app can be promoted to production. It is not optional and it cannot be rushed.
Most teams find out in week sevenand tell the client it is Google’s fault.
The closed test runs alongside the final build week, not after it.
We recruit and brief the twelve testers in week one, not week seven.
Your app publishes under an established developer account, so the queue does not start from zero.
| Date | What changes | Who it affects |
|---|---|---|
| 2 Aug 2026 | EU AI Act Article 50: an AI feature that talks to a person must say it is AI, and AI-generated content must be machine-readably marked. | Any MVP with an AI chat or content feature, and any EU user |
| 1 Jan 2026 | Texas App Store Accountability Act in force; enforcement allowed to proceed from 10 Jun 2026. Age category and parental-consent duties, with Apple and Google compliance APIs. | Any app with US users. Utah and other states following |
| 31 Aug 2026 | Google Play target API level 36 (extension available to 1 Nov). | Any app being updated after this date |
Checked 12 August 2026. Sources: Google Play Console Help · artificialintelligenceact.eu · Apple and Google developer documentation.
Cost control, built in on day one
Real, documented, and none of it exotic:
A runaway loop on Google Cloud took one team from $5,000 to $72,000 in two hours. (The Register)
A forgotten public API key produced an $18,000 bill on a $7 budget, straight through a $1,400 spending cap. (Tom's Hardware)
Before your app goes live we set hard request limits, per-service budget alerts, key rotation and rate limiting, and we show you where the switches are. It takes half a day and it is the cheapest insurance in the project.
Full detail on Backend, API & Integrations.
Standards
Where AI actually helps
The most careful study of this so far took 16 experienced developers, working on codebases they already knew, and measured them with and without AI tools. (METR, July 2025, n=16, and the authors say themselves it is a small sample.)
So here is our honest position. AI genuinely speeds up the repetitive parts: boilerplate, test scaffolding, the fourth version of a form screen. It does not speed up the decisions: what to cut, what the architecture should be, why this screen confuses people. Those still take somebody who has shipped 52 apps.
That is why we sell six to eight weeks and not two. Anyone promising an MVP in ten days is selling you the AI and keeping the judgement.
Where we have shipped
| Industry | What we have built | Proof |
|---|---|---|
| Fintech & banking | Wallets, lending, KYC, crypto | QuickChain · Hindustan Loan · Fidex Wallet |
| Legal-tech | Case management, court data, auctions | Gavel Auctions |
| Retail & POS | Billing, inventory, small-business POS | Vencru POS |
| Hospitality | Discovery and booking | Tawla |
| Energy & utilities | Field operations at enterprise scale | Tata Power SolaRoof |
| Consumer & subscription | Content, habits, subscriptions | Pray the Bible |
| Healthcare & wellness | Open, no case study yet | No claim made |
Great work Anand on building this app from scratch. Looking forward to more projects with you.
He helped me develop a brand-new frontend for my mobile app in record time, delivering outstanding quality at a very reasonable price. His communication was clear, his attention to detail was impressive, and the final result exceeded my expectations.
Anand is highly technical… he has resolved our apps issues on time and made the apps live on Google Play and Apple App Store. He has shown his responsibility towards work.
Stack
Flutter is our core. It is not our limit. Where a project needs a technology we do not use every day, we bring in a developer for it and manage the delivery ourselves, you still have one team and one contract.
Proof
An honest note about these three. None of these was sold as an MVP. Every case study we own is a full build, so rather than relabel them we are showing you the three that are closest in shape, a first version that reached real scale, and telling you which part is comparable. Writing a proper MVP case study is on our own task list.
Shipped first, then scaled. 97% transaction success rate, settlement from 72 hours to under 60 seconds.
Comparable part: Getting a working first version into a hard market fast
An AI feature that people actually pay for, not a demo.
Comparable part: Shipping one real AI feature inside a first version
+45% booking conversion from one design decision.
Comparable part: A small, focused product that grew because the core flow was right
FAQ
From the day scope is locked at the end of the discovery week. Not from the day you sign.
Yes. Source code, designs, accounts, all of it, on final payment.
Because we would be guessing, and you would pay for the guess later. You get a fixed number at the end of the discovery week.
Google requires developer accounts created after 13 November 2023 to run a closed test with 12 testers for 14 continuous days before going live. We schedule it in parallel with the final build week.
We tell you the moment we know, not at the deadline, and we tell you which of the exclusions caused it. In practice the overrun is almost always a third party: a payment provider, an API key, a store review, and we name it rather than absorb it silently.
A prototype is a picture of an app. An MVP is an app: downloadable, usable by a stranger, able to take money. If a real user cannot complete the core job in it, it is not an MVP.
Because a free one would be a sales pitch. Paying for it means the week is spent on your product, not on winning you. It is credited back in full against the build.
You keep the scope document, the screens and the estimate, and you can take them to any other developer. That happens, and it is fine.
Partly. AI speeds up repetitive code. It does not speed up decisions, and the best measured study on this found experienced developers were 19% slower with AI while believing they were 20% faster (METR, 2025, n=16). We are fast because the scope is small and locked, not because of a tool.
There is a full table above, in the What is not in your MVP section. We publish it rather than argue about it in week five.
If you have EU users, yes. EU AI Act Article 50 has applied since 2 August 2026: the AI must disclose that it is AI, and AI-generated content must be machine-readably marked. We handle it in the build.
Yes. Flutter is our core, not our limit.
30 days of fixes included, then you choose: in-house, a maintenance plan, or phase two.
Most of our clients are not. Every weekly update is written in plain language and comes with a build you can install on your own phone, so you judge it by using it, not by reading a status report.
A short call, an honest answer on whether we are the right team, and a scope you can hold us to.
Start a project
