This article is for the owner or managing director with a few quotes on the desk and no way to tell which one is fair. You might run a contracting firm in Musaffah or Al Quoz, a trading company in Deira, or a facilities and services company across Dubai. By the end you will know what moves the price, what a fair quote must list, and whether you should build an app this year at all.
Where you probably are right now
Site supervisors send progress photos on WhatsApp. Someone in the office types delivery notes into Excel, and the accountant re-enters them into the accounting software at month end. Technicians call in to ask which job is next, and nobody can tell you today which projects are over budget until the quarter closes.
So you asked for an app. The quotes came back, and they look nothing alike. That is normal, and it is fixable.
Why your quotes look nothing alike
The vendors are rarely quoting the same thing. A low quote often covers the screens your team sees and nothing behind them: no admin panel for the office, no proper backend, no Arabic, no testing on the older Android phones your site staff actually carry. A high quote often includes discovery workshops, a full design system, and a project manager you will talk to more than the developers.
Neither is lying. They are pricing different products and calling both of them "the app."
The seven things that move the price
Scope of the first version. This is the biggest lever by far. An app that lets site supervisors log daily progress with photos is a different project from one that also handles material requests, approvals, subcontractor payments and client sign-off. Every extra workflow adds screens, rules, and testing. The cheapest version is the one that solves one painful problem completely.
One codebase or two native apps. You can build separate apps for iPhone and Android, or build once with a cross-platform framework like Flutter or React Native. For most SMEs, building once is the right call because one cross-platform codebase usually costs less to build and maintain than two separate native apps, and your staff and customers will not notice the difference. Two native apps make sense only for heavy offline work, complex camera or GPS features, or very high performance needs.
Arabic, done properly. Right-to-left is not a translation job. Every screen has to be mirrored, every table and form retested, and mixed Arabic and English text (a customer name in Arabic next to an invoice number) has to display correctly. If half your drivers or site foremen read Arabic first, budget the hours for it honestly rather than bolting it on later.
Integrations with your accounting software or ERP. This is where small apps quietly become medium ones. Most cloud accounting packages and modern ERPs have clean APIs. Desktop accounting software is different: it usually runs on a machine in your office, so syncing with it often needs a small connector installed on that PC, and the app is only as reliable as that machine staying on. Ask every vendor how they plan to handle this, because the ones who have not done it before will not raise it.
Payment gateways. Taking card payments through a local payment gateway means extra screens, reconciliation logic, failure handling and gateway approval paperwork. A trading company collecting from retail customers needs this. A contractor whose clients pay by bank transfer against a certified invoice probably does not.
Staff roles and permissions. A site engineer, a project manager, a procurement officer and the finance team should each see something different. Every role you add means its own screens, its own rules about who can approve what, and its own testing. Three roles is a modest app. Eight roles with approval chains is a serious one.
Reporting. A simple list of today's jobs is cheap. Live dashboards showing cost against budget per project, stock by warehouse, or technician utilisation by week take real work, especially when the data comes from more than one system.
What a fair quote must list
A quote you can trust names its assumptions. Before you compare numbers, make sure each one spells out:
- The exact features and user roles in version one, and what is explicitly out of scope
- Whether it is one cross-platform codebase or two native apps
- Whether full Arabic right-to-left is included
- Every integration (accounting software, ERP, payment gateway) and how each one will work
- Who owns the source code and the store accounts (it should be you)
- Testing on real devices, including older Android phones
- Hosting, monitoring and support after launch, with a clear monthly or yearly line
- Whether the figure includes 5 percent VAT
If a quote cannot answer these, it is not cheaper. It is incomplete.
The costs that arrive after launch
The build is the visible part. The running costs decide whether the app survives its second year.
- Apple Developer account: USD 99 per year
- Google Play account: USD 25, one time
- Hosting and services: scales with users, file storage (site photos add up fast), and SMS or WhatsApp notifications
- Maintenance: 15 to 20 percent of the build cost per year, a common industry rule of thumb, covering OS updates that break things, security patches and small fixes
Take that maintenance line seriously. Apple and Google release major updates every year, and an app nobody touches for eighteen months will start failing on new phones.
Where app budgets go wrong
The cheapest quote is usually the most expensive decision. Failed app projects are rarely about the original price. They come from unclear ownership of the source code, a developer who disappears after launch, or an app rejected by Apple because nobody read the review guidelines.
The bigger risk is building an app your team will not use. If your site supervisors are happy on WhatsApp, a WhatsApp Business API flow that drops their updates straight into a structured sheet might do most of the job with far less build. Fix the data flow first. The app can come after.
For a 50-person contractor or trading company, the advice is simple. Start with a web app that works well on phones, prove your team uses it for three to six months, then wrap it as a store app once usage justifies it. You give up some polish and push notifications early on, but you stop paying for guesses.
Do it yourself, or bring someone in
If your need is simple job scheduling, a basic stock list or a form your technicians fill in, try an off-the-shelf tool first. Many field service and inventory apps can be set up in a weekend. If one covers your process, you do not need custom software.
If your business works differently from the template (your BOQ structure, your approval chain, your multi-warehouse stock, your accounting sync), that is where custom work earns its cost. How long the first version takes depends mainly on scope, and accounting or ERP integration and full Arabic each add time. Pick a team that will still answer the phone in year two; that build-and-stay model is how Hadiati works, with 20+ apps and platforms shipped and 50+ automations running in production.
Questions owners ask
How long does it take to build a business app in Dubai? The time depends mainly on scope. Integrations with your accounting software or an ERP and full Arabic support each add time.
Is it cheaper to build one app for iPhone and Android? Yes. A single cross-platform codebase built with Flutter or React Native usually costs less to build and maintain than two separate native apps, with no visible difference for most business users.
Can a custom app connect to desktop accounting software? Yes, but desktop accounting software usually runs on a local office machine, so the connection often depends on a connector installed there. Ask how the vendor handles sync failures and what happens when that PC is switched off.
How much should I budget for maintenance? Plan on 15 to 20 percent of the build cost per year, plus Apple's USD 99 annual fee, Google Play's one-time USD 25, and hosting that grows with your usage.
When you are ready to talk through what your own app would involve, email hello@hadiati.ae.