Services · MVP
From an idea to a first version real users can try.
You bring the idea and know who it's for; I turn it into the smallest product that proves it — scoped in writing, built end to end (frontend, backend, database, deployment), and launched on the web, in the App Store and Google Play, or both. You don't need the technical vocabulary: every choice is explained in plain language, and the code is yours.
Pricing
from $3,500
Web App: from $3,500 · Mobile App: from $5,000 · starting price · negotiable by scope
Is this you?
- You have an idea for an app or platform and don't know where to start technically.
- You need something real in front of users — not a slide deck or a clickable mock-up.
- You're not sure whether it should be a web app, a mobile app, or both, and want an honest recommendation.
- You'd rather work with one accountable engineer than coordinate a designer, two developers and a DevOps contractor.
What you get
- A written scope for version one: what's in, what waits, and why
- A working product — web app, mobile app for iOS and Android, or both — on the architecture it will grow on
- Sign-up and login, the one core workflow, payments if it charges from day one, and an admin view to run it
- Deployed to production, or published to the App Store and Google Play in your own accounts
- Analytics from the first release, so you see what users actually do
- Documentation and a clean handoff — the code is yours, whether you keep building with me or not
How I build it
- Scope before code: version one is cut down to the workflow that proves the idea, and the rest is written down for later.
- Real data and a real deployment from the first milestone — you use the product while it's being built, not at the end.
- Built to grow, not to throw away: the same clean architecture as the production apps on this site, sized for a first version.
- A demo of what shipped every week and a written summary at every milestone.
What this looks like in practice
- Xera Laba dental X-ray lab's case workflow built from zero as one platform: customer portal, admin dashboard, Node.js API, PostgreSQL and deployment, by one engineer.
- Jaweban informal two-team quiz night turned into a mobile game that referees itself, scores automatically and takes payments, designed and built solo.
- Ezhala car-service platform as three role-specific Flutter apps, with live technician tracking and MyFatoorah, Stripe and Apple PassKit.
- FasTapan NFC business card: a Flutter app that writes profiles to cards, and a web profile page for tap-to-share links.
Technologies
Case studies
How a project runs
Intro call
A free call. You describe the product and what's blocking you; I tell you honestly whether and how I can help.
Written proposal
Scope, price, timeline and payment phases — all in writing before any code is written. You approve it, then we start.
Milestone delivery
You get working, testable software at every milestone, not a status update.
Handoff
Deployment, documentation and a codebase the next engineer can maintain. The code is yours.
Questions about this service
How much does it cost to build an MVP?
An MVP is priced as the product it becomes: a web MVP starts from $3,500 and a mobile MVP for iOS and Android from $5,000. The final price depends on the workflows, user roles and integrations in version one, and it goes in a written proposal — with the timeline and payment phases — before any work starts. The first call is free.
How long does it take to build an MVP?
It depends on the scope, so the timeline is set per proposal rather than quoted up front. What doesn't change: you get the timeline and milestones in writing before we start, and working software at every milestone — not a big reveal at the end.
Should my MVP be a web app or a mobile app?
It depends on how people will use it. If they'll use it daily on the go, need notifications, the camera or location, or expect to find it in an app store, start with mobile — Flutter covers iOS and Android from one codebase. If it's used at a desk, needs to be found through search, or has to reach people without an install, start with the web. Most products need both eventually; version one usually needs one. Not sure? Say so in the brief and I'll recommend one, with the reasons.
I'm not technical. Can I still work with you?
Yes. Describe the product the way you'd explain it to a customer — who uses it and what they do with it. I turn that into a written scope, explain the choices in plain language, and show you working software every week. You approve the proposal before any work starts.
What happens after the MVP launches?
You own the code, the accounts and the deployment, with documentation the next engineer can pick up. If you want to keep building with me, the next phase is scoped and priced the same way; ongoing maintenance after handoff is agreed separately.
Ready to scope it?
Tell me what you're building — in plain words, no technical brief needed — or book a free call. You'll get an honest answer and, if it fits, a written proposal with the price and timeline.