A first version people can really useMVP · iPhone and Android app
Small on purpose. It does the one thing your idea depends on, properly.
New products · Founders and first-time product owners
Launch a product idea without a technical team
You have the idea, the market knowledge and maybe some designs. You do not have engineers. We act as your product engineering team: we help you decide what the first version must do, build it, put it in front of real users, and keep improving it. You own everything we make.
Already know the scope and want to hire an MVP team? The service page covers deliverables and how the engagement runs. MVP development service →
Who this is for: Founders and businesses launching a new product, with an idea, a spec or designs but no engineering team.
What you would get
The parts, in plain words.
Each part has a plain name and, underneath, what engineers call it. You never need the second one to talk to us.
Accounts, sign-in and payments if neededAuthentication · payment integration
The parts every product needs, built once and built properly.
The engine and your recordsBackend · database
Built so the next versions add to it rather than replace it.
A way to see what users doAnalytics · error reporting
So the next decision is made on evidence, not guesses.
A plan for what comes nextRoadmap
What we learned, what to build next, and what it would cost.
How it works
How it works, step by step.
- 01
We help you shrink the idea
The hardest part. We write down what the first version must prove, and cut everything that does not serve it.
You provide
Your idea, your market knowledge, any designs or notes, and honesty about what matters most.
We do
A one-page definition of the first version and the list of what waits.
- 02
You approve a plan and a price
The stages, what each delivers, and the price. For most first versions that is the Lean MVP package, with what is included written down.
We do
The plan, the price and the order of work.
- 03
We design the screens with you
Clickable screens you can show to people before any code is written. Cheap to change now, expensive later.
You provide
Reactions from a few people who might use it.
We do
The screens and the changes.
- 04
We build, you try it every two weeks
Preview versions on your own phone every two weeks.
You provide
Fifteen minutes every two weeks.
We do
The build, the testing and the fixes.
- 05
Launch
App in the stores, sign-ups working, errors watched. Store accounts are in your name.
We do
The release, the listings and the first weeks of watching.
- 06
Learn and improve
We look at what users actually did and plan the next version with you. Most ideas change here. That is good.
We do
Ongoing improvement under a separate agreement if you want it.
What affects the price
The questions that move the price up or down.
We price on scope, not guesswork. If you can answer these, we can give you a number quickly. If you cannot yet, we work them out together on the first call.
- 01How small can the first version be? Fewer screens is the biggest saving.
- 02One type of user, or several, such as customers and providers?
- 03Do users need accounts, payments or subscriptions in the first version?
- 04Do you have designs already, or do we design the screens together?
- 05Does it need to connect to other services, such as maps, messaging or a marketplace?
Packages
Packages that usually fit this goal
Starting prices for a written scope. The exact price follows the plan you approve.
You own the code. Everything we make for you is yours as soon as each stage is paid for, and you can see the code from the first day.
Prices for
- First version
Lean MVP
₹15,000 – ₹30,000 in India$2,500 – $5,000 outside India
A small, working first version of your app. It is built around one main task, done properly, with room to grow.
- For your business
Business App
₹40,000 – ₹2,00,000 in India$3,000 – $10,000 outside India
An app with a few types of user, a control screen for your team, and connections to the services your business already uses.
All packages, what each includes, and what is always extra →
Where it goes wrong
Quotes range wildly because nobody has agreed what the first version is. Freelancers come and go. A year later there is a half-built app, no documentation, and no users.
What you end up with
A first version that real users can sign up for and use, launched in the App Store and Google Play, with the code, accounts and documentation in your hands and a plan for the next three months.
What you need
Bring these and we can start.
- The idea, explained as a problem someone has today
- Any designs, notes or examples of products you admire
- A few people who might use it and will give honest reactions
- Store accounts in your company's name if it is a phone app (we help set them up)
- A decision-maker available every two weeks
What you get
What is included.
- A working first version in the App Store and Google Play
- Sign-in, accounts and payments if the product needs them
- The code, accounts and documentation, owned by you
- A plan for the next version based on what users did
What happens after you contact us
No sales calls. Here is the actual sequence.
- 01
An engineer reads your message and replies within one business day with two or three questions.
- 02
A short call about the idea and what the first version must prove.
- 03
A written plan with the first version's scope, the stages, and a price.
- 04
Work starts when you approve it. You sign an NDA with us first if you want one.
Technical detailsfor your technical advisor
A first version on the same foundations as the full product: a Flutter app, a managed backend with sign-in, and analytics and crash reporting from day one. The server technology is chosen per project and documented.
- The first version is built on the same API and data model the full product will use, so nothing is thrown away when it grows.
- Feature flags let us ship small and switch things on for groups of users.
- Repository access, CI and documentation are handed over from the first week, not at the end.
Stack
- Flutter app, iPhone and Android
- Managed backend with sign-in
- Database
- Payment provider tools, if needed
- Analytics and crash reporting
Questions we get asked
Frequently asked questions
How small should the first version be?
Small enough that a real user can get the main benefit, and nothing else. If you can describe it in one sentence, it is about right. We will push you to cut; that is part of the service.
Will you sign an NDA?
Yes, before you share anything sensitive.
What if I want to raise money first?
Clickable screens and a one-page definition are often enough to talk to investors. We can stop there if that is what you need, and continue when you are ready.
Can my own developers take over later?
Yes. Everything is in your repository with documentation from the first week. Handing over to an in-house team is a normal ending, not a problem.
Read first
Read before you decide
Plain guides on what to decide first, what moves the price, and what to ask any developer.
3 min read
How much does an app cost? Three examples, priced
Three example apps walked through our published packages: which package each fits, what pushes it into the next one, and what the app costs to run.
Read2 min read
What the Lean MVP package includes, and leaves out
Each part of our Lean MVP package explained in plain words: why it is in, why the rest is out, and how to add something without surprises.
Read3 min read
Flutter or native: trade-offs for a business app
When one Flutter codebase is the right choice for a business app, when native Swift and Kotlin are worth the extra cost, and how the two combine.
Read
Next step
Tell us where you are today.
An idea, a spreadsheet that hurts, an app that is stuck: describe it in your own words and an engineer will reply within one business day.
- No charge for the first conversation
- NDA on request before you share code
- Accounts, keys and listings stay yours