Loading...
What an MVP means for a non-technical Dubai owner: the one-screen test, what to cut first, the three things never to cut, and how to describe it on one page.
An MVP is the smallest version of your app that lets one real customer finish one real job, such as booking, ordering or paying, without you stepping in. It is not a cheap version of the full idea, and it is not a demo. If you can describe that one job in a sentence and sketch the screen where it ends, you already know most of what your MVP is. The rest of this guide is about cutting everything else.
I run ForgeApp, a one-person AI-native app studio in Dubai. Most of the owners I talk to are not technical, and the word "MVP" confuses them more than it helps. The examples below are illustrative, not clients, and there are no statistics here, only the way I think about scope after building small apps for small businesses.
MVP stands for minimum viable product. Each word does work:
The point is to find out, with real customers and real money, whether the idea works, before you spend on the version you dream about. For a small business in Dubai that usually means weeks, not months, and a budget you would not mind losing if the answer is no.
No, and this is the most common misunderstanding. A cheaper version of the full app is the full app with every feature done badly. An MVP is one feature done properly.
Think of a salon owner who wants an app. The full idea has bookings, staff rotas, loyalty points, product sales, gift cards, reviews and a marketing tool. A "cheap version" tries all seven at a basic level and none works well. An MVP does bookings only, but a customer can choose a service, pick a slot, pay a deposit and get a confirmation in Arabic or English. Everything else waits.
The MVP is narrower, not shallower.
This is the test I use with every owner, and it takes ten minutes with a pen.
If you cannot draw the final screen, the problem is not the budget or the builder. The idea is still too vague to build, and that is worth knowing before you pay anyone.
Here is the order I usually cut in, starting with the easiest wins:
| Cut first | Why it can wait | What to use instead for now |
|---|---|---|
| Admin dashboard with charts | You can read 30 bookings in a list | A simple list view or a spreadsheet export |
| Reports and analytics | You do not have enough data yet | A weekly look at the list |
| Loyalty points, referrals, gift cards | They reward repeat customers you do not have yet | A manual discount code |
| Multiple user roles and permissions | One or two people run things at the start | One admin login |
| Native apps in both app stores | Store reviews add time and cost | A mobile-friendly web app customers open from a link |
| Anything described as "later we could" | That sentence is a feature for version two | A note in a "later" list |
None of these are bad ideas. They are second ideas. Each one you remove makes the build faster, the bugs fewer and the first launch easier to judge.
Three things look optional on paper and are not, at least for most consumer-facing businesses here.
If the job involves money, the MVP should take the money, or at least a deposit. "Pay on arrival" in an MVP tells you whether people will click a button, not whether they will pay. Real payment is the strongest signal you can get, and it filters out the no-shows you would otherwise be counting as success. UAE payment gateways are a solved problem for a builder; the work is mostly setup and testing, not invention.
If a meaningful share of your customers prefer Arabic, the MVP needs Arabic, including right-to-left layout, not a translated button or two. Adding Arabic properly later means revisiting every screen. Doing it from day one costs much less than retrofitting it. If your customers genuinely all use English, skip it, but decide on purpose rather than by default.
In my experience, customers here will message before they fill in a form, and they will message again when something is unclear. An MVP without a visible WhatsApp link pushes those people away silently. You do not need automation. A "Questions? WhatsApp us" link that reaches a real person is enough for the first version.
You do not need a long document. Before you speak to any builder, write half a page in your own words:
If you can fill that in, you can have a sensible conversation about price and timeline with anyone. If you want to see how I package builds, my pricing page shows what is included, and a 20-minute call is enough to test your half page against it.
A minimum viable product is the smallest version of your app that a real customer can use to finish one real job, such as booking, ordering or paying. It is not a demo or a mock-up. If nobody can complete the job with it, it is not an MVP yet.
Sketch the single screen your customer must reach to finish the job, such as a confirmed booking. Everything needed to get there stays in the MVP. Everything a customer does after that screen, or never needs to reach it, is a candidate to cut.
Admin dashboards, reports, loyalty points, multiple user roles, a native app in both stores and anything you describe with the words "later we could". A spreadsheet export and a simple web app usually cover the first months.
Taking payment if the job involves money, Arabic where your customers read Arabic, and a WhatsApp route for questions. Cutting these saves little build time and often decides whether customers use the product at all.
Not sure what your one job is?
The salon example is illustrative and not a client. This guide reflects my own experience, not survey data.
Free 20-minute call
We review your idea, scope the first version and give you a fixed price and timeline on the call. No obligation, no sales deck.
Freelancer, agency, in-house hire or fixed-price studio in Dubai? An honest comparison on price clarity, timeline, code ownership, Arabic support and risk.
Build vs buy software for a UAE SME: honest math on an 18,000 AED custom app versus 300 AED a month subscriptions, with break-even for one tool, three tools and 12 seats.
What a UAE tax invoice needs: TRN, 5% VAT, sequential numbers, dates, parties and AED totals, plus why spreadsheets break and what an invoicing app must do.