- Market
- Saudi Arabia
- Written for
- Founder, Procurement
- Decision
- Compare mobile app quotes and understand why they differ
- Languages
- EN · AR
Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
What a quote assumes
The assumptions that set a mobile app figure before anyone builds
Each driver below is a question a supplier answers on your behalf when they hand you a number. Where two quotes diverge, the difference is almost always here rather than in a difference of skill.
| Variable | Effect on price | Why |
|---|---|---|
| Whether the backend already exists | The largest hidden swing | An app over an adequate existing backend is mostly a client. An app that needs its own server, accounts, real-time updates or offline synchronisation is two products, and the invisible half is often the larger one. A quote that assumes a backend exists, when it does not, is the single most common reason a figure doubles after signing. |
| The platform strategy | Native both platforms costs most | Native iOS and Android are close to two builds; a cross-platform codebase makes the second platform a smaller increment; launching one store first defers the rest. A supplier who assumed cross-platform will quote below one who assumed native for the same brief, and both are answering a question you have not yet settled. |
| Number and maturity of integrations | Each adds work, some add risk | Payments, maps, identity, messaging and links to your own systems each carry integration, testing and edge-case work. An integration with a documented, mature service is modest; one with a legacy internal system whose behaviour nobody wrote down is where a timeline and a figure move together — and it is the item quotes most often omit. |
| Feature depth, not screen count | Depth multiplies, counting misleads | A screen that lists records is cheap; the same screen with search, filters, offline edits and role-specific behaviour is several times the work. A quote built by counting screens flatters a complex app and penalises a simple one, so a page count is the least useful thing to compare two quotes on. |
| Arabic, right-to-left and local payment | A requirement here, not an add-on | For a Gulf audience, Arabic and a right-to-left interface are part of the build, and payment goes through the methods people here use. A quote that treats these as optional extras has priced an app for a different market, and adding them after launch costs more than including them from the start. |
| What happens after launch | A recurring line, easily hidden | An app is not finished at launch. Operating-system releases, store policy changes, fixes and the features real usage reveals are an ongoing line, and a quote that shows only the build hides the cost of keeping the app alive. A figure without a maintenance line is a figure for a product that stops the day it ships. |
Ask any supplier quoting this
- Does your figure assume our backend exists and is adequate, or does it include building one?
- Is this native, cross-platform, one store or both — and which did you assume for this number?
- Which integrations are in scope, and which of them have you built against before?
- Are Arabic and right-to-left support inside this figure or priced separately?
- What is the monthly cost of running and maintaining the app after launch?
- What is explicitly excluded here that we might reasonably assume is included?
Reading the gap
A cheaper mobile app quote is usually a narrower one
When one quote comes in far below the others, the instinct is to treat it as a bargain and the rest as padding. Occasionally it is. Far more often the low quote has quietly excluded the backend, assumed cross-platform where you wanted native, counted a legacy integration as trivial, or left maintenance off the page entirely. The gap is not efficiency; it is a smaller app answering the same brief, and the difference reappears as change requests once the work is under way.
The way to compare is to force every supplier onto the same assumptions before you look at a number: the same backend position, the same platforms, the same named integrations, the same treatment of Arabic and maintenance. Once the briefs are identical the figures become comparable, and a genuine difference in price starts to mean a difference in how the work would be done rather than a difference in what was quietly left out.
A complete quotation
The line items a mobile app quote has to name to be trusted
A quote you can rely on states each of these rather than folding them into one number. A blank in any row is the question to ask before you sign, not after.
Backend build or backend assumed
It is the largest variable in the whole figure, so it cannot sit inside an unlabelled total.
What a blank here hides: A doubling of scope that surfaces as the first major change request.
Platforms and framework
Native versus cross-platform and one store versus both change the build size directly.
What a blank here hides: A second platform the buyer expected but the price never covered.
Named integrations
Each integration is a discrete piece of work with its own testing and edge cases.
What a blank here hides: A legacy connection costed as trivial that turns out to carry the risk.
Arabic and right-to-left
For this market it is a requirement, and retrofitting it after launch costs more.
What a blank here hides: An app built for a different market that has to be reworked for this one.
Post-launch maintenance
Operating systems and store policies change, and the app has to keep working through it.
What a blank here hides: A running cost the budget never planned for.
Our role
What we settle before we put a number on a mobile app
- 01
The assumptions, made visible
We resolve the backend, platform, integrations and market requirements into an explicit brief before quoting, so the figure attaches to a specific app rather than to a set of guesses no one can see.
- 02
A figure with its exclusions named
We quote a fixed figure against the agreed brief and state what sits outside it, so the number you budget is the number the work costs and the surprises are decided in advance rather than discovered.
- 03
A quote you can hold others to
The brief we produce is one you can put to any supplier, so a comparison measures how the work would be done rather than which supplier hid the most, whether or not the work comes to us.
Which app you actually want, and how much you will spend before it is proven, are yours to decide; we make the assumptions explicit so competing quotes describe the same product and the figure you choose means what you think it means.
Common questions
What buyers ask
One quote is a third of the others — is it too good to be true?+
Usually it is a narrower app rather than a better deal. Before deciding, line the low quote up against the others on the same assumptions: does it include the backend, both platforms, the named integrations, Arabic support and maintenance, or has it quietly excluded some of them. Occasionally a supplier really is more efficient, but far more often a third of the price is a third of the scope, and the missing two thirds return as change requests once the work is under way. Force the briefs to match and the comparison becomes honest.
How do we compare quotes from suppliers who scoped the app differently?+
You cannot compare them until you rewrite the brief so it is identical for all of them, which is the single most valuable thing you can do before signing. Fix the backend position, the platform strategy, the exact integrations, the market requirements and the maintenance expectation, then send the same brief to every supplier and ask them to quote against it. Any difference that survives that is a real difference in how the work would be done, which is what you actually want to be choosing between, rather than a difference in what each supplier assumed.
Which part of an app quote is most often wrong?+
The backend, because it is the part a buyer does not picture. The screens are visible and get estimated carefully; the server that keeps them in sync, the accounts, the real-time updates and the connection to an internal system nobody documented are invisible in a mockup and can be the larger half of the work. The second most common is maintenance treated as free. A quote that shows only the build and assumes a backend already exists will look competitive and then move the most after signing, which is exactly why those two rows deserve a direct question early.
In this cluster
A scoping session that turns competing quotes into like-for-like comparisons, so the figure you choose reflects the same app rather than the supplier with the smallest hidden scope.
Make your quotes comparable