Most questions about software cost are really questions about scope, risk and who carries which decision. Published price lists rarely help, because two systems described in the same sentence can differ by an order of magnitude once integrations, permissions and compliance enter the picture.
This article sets out what actually drives custom software development cost in Dubai and the wider UAE, how engagement models change the commercial shape of a project, and what to prepare so that the first quotation you receive is a number you can plan against rather than a placeholder.
Why published price lists rarely help
A supplier can only price what has been described. Where a brief is silent, the gap is filled either with assumptions or with contingency, and both are guesses made at the least informed moment of the project.
That is why the same requirement produces quotations that differ by a factor of three. The difference is rarely day rate. It is what each supplier believes is included: whether roles and permissions were assumed, whether data migration was assumed, whether testing was assumed, and whether the integration work was estimated from the vendor's documentation or from experience of that vendor's actual behaviour.
Compare proposals on what they include, not only on the total.
The kinds of system and what each demands
Six categories cover most of the enquiries we receive. They differ far less in visible interface than in what sits underneath.
| System type | What drives the work | Typical delivery shape | Where budgets usually go wrong |
|---|---|---|---|
| Simple business application | One core workflow, a handful of screens, one or two integrations | Focused build, measured in weeks | Assumed to need no permissions, reporting or audit trail |
| Custom CRM | Sales and service data model, roles, pipeline logic, email and telephony integrations | Multi-phase, with data migration | Existing data quality discovered late |
| SaaS platform | Multi-tenancy, entitlements, subscription billing, administration | Product-shaped, released in stages | Billing and admin tooling treated as post-launch tasks |
| Enterprise management system | Several modules, approval chains, finance and operations integration, migration | Programme with phased rollout | Legacy process exceptions that must be preserved |
| B2B marketplace | Two-sided onboarding, catalogue, matching, payments, verification, dispute handling | Platform plus operational tooling | Settlement and verification logic underestimated |
| Integrated ecosystem | Several systems and organisations exchanging data, shared identity, common rules | Architecture-led programme | Participant onboarding and governance assumed to be simple |
The category sets the foundation, not the interface. A CRM with excellent screens and no reporting model is a spreadsheet with better fonts, and it will be rebuilt within two years.
The cost drivers, in the order they appear
| Driver | What it covers | Why it moves the number |
|---|---|---|
| Product discovery and planning | Process mapping, requirements, scope definition, acceptance criteria | Cheapest stage, and the one that most determines the rest |
| UX and UI design | Workflow design, interface system, empty and error states | Redesigning after build starts is expensive; designing before it is not |
| Backend architecture | Data model, service boundaries, tenancy, background processing | Decisions here are the hardest to reverse |
| Frontend development | Screens, forms, dashboards, role-specific views | The number of distinct user states matters more than page count |
| User accounts and permissions | Identity, single sign-on, roles, approval rights | Enterprise requirements expand this substantially |
| Multi-tenant functionality | Tenant isolation, per-tenant configuration, data export | Essential for products, avoidable for single-company systems |
| APIs and integrations | Third-party systems, webhooks, reconciliation, error handling | Each integration carries mapping, failure handling and support cost |
| Security and compliance | Access control, encryption, audit logging, data residency, testing | Regulated data adds assessment and evidence work |
| Testing and deployment | Automated tests, environments, release process | Determines the cost of defects after launch |
| Hosting and infrastructure | Environments, monitoring, backups, scaling | Usually operating cost, sometimes mistaken for build cost |
| Ongoing maintenance | Fixes, dependency updates, small changes, monitoring | Continues for the life of the system |
An integration is rarely one connection. It is mapping, authentication, failure handling, retry logic, reconciliation and someone to answer the phone when the vendor changes a field name. A brief that lists eight "simple" integrations has described a substantial part of the programme.
How engagement models change the numbers
| Model | How pricing works | Best fit | What it optimises |
|---|---|---|---|
| Fixed-scope project | Agreed price per phase against written acceptance criteria | Well-specified work with stable requirements | Budget certainty for a known scope |
| Time and materials | Paid for effort against a prioritised backlog | Evolving requirements and discovery-heavy work | Flexibility, at the cost of budget certainty |
| Dedicated development team | Monthly capacity for a named team | Long-lived products needing continuous delivery | Continuity and delivery speed |
| Strategic technology partnership | Retained team plus architecture and roadmap ownership | Multi-year platform programmes | Coherence across releases |
Most first builds work best as fixed scope for the first phase, then a decision once the shape of the product is visible. Fixed price across a whole programme assumes the later phases are knowable in advance, and they usually are not.
UAE-based and offshore development
Geography changes rates and coordination cost. It does not determine quality, and a proposal is not better because the team is closer or cheaper because it is further away.
What actually differs is the seniority mix available at a given rate, overheads, time zone overlap, contractual enforceability and how quickly feedback travels. An offshore team can be cheaper per hour while costing more per delivered increment if review cycles take days. A local team costs more per hour and shortens the distance between a decision and a working change.
Two constraints sit outside price: data residency, since the regime that applies to you may limit where work happens and where test data lives, and accountability, since a rate advantage is consumed by rework when the architect is not involved in delivery.
Illustrative budget scenarios
The figures below are illustrative planning bands prepared by Sardo Group for this article. They are order-of-magnitude ranges for budget preparation, not market research, not a quotation, and not a substitute for scoping your requirement. They exclude VAT, hosting, third-party licences and ongoing support.
| Scenario | Scope assumptions | Illustrative first-release band (AED) | Indicative duration |
|---|---|---|---|
| Single-workflow application | One process, two roles, one integration | 80,000 to 200,000 | 8 to 14 weeks |
| Custom CRM with migration | Sales and service model, roles, email and telephony integration, data migration | 220,000 to 450,000 | 4 to 6 months |
| Multi-tenant SaaS first release | Tenancy, entitlements, billing, administration, one external integration | 400,000 to 900,000 | 6 to 9 months |
| B2B marketplace | Two-sided onboarding, catalogue, payments, verification, operations tooling | 600,000 to 1,500,000 | 9 to 14 months |
| Enterprise system with ERP integration | Several modules, approvals, finance integration, migration, phased rollout | 900,000 to 2,000,000 | 12 to 18 months |
The band widens as integration count rises, and the largest determinant of where a project lands within its band is how much of the current process must be preserved rather than redesigned.
The cost after launch: total cost of ownership
Build cost is the visible number. The one that decides whether the investment holds up is the running cost.
| Item | Typical basis | Why it matters |
|---|---|---|
| Hosting and infrastructure | Monthly consumption, scaled to traffic and data | Grows with success, so model it |
| Maintenance and fixes | Reserved capacity or a support agreement | Without it, small defects accumulate |
| Dependency and security updates | Scheduled work each cycle | Framework and library updates are not optional |
| Third-party services | Per-transaction or per-seat fees: payments, messaging, maps, model usage | The largest surprise in AI-enabled systems |
| Support and service levels | Response commitments by severity | Defines what happens at 2am |
| Enhancement budget | Quarterly or annual allocation | The difference between a maintained system and a decaying one |
| Technical debt | Deliberate remediation work | Interest paid on shortcuts, either now or later |
| Compliance reviews | Periodic assessment and evidence | Required where personal or regulated data is processed |
As a planning heuristic, organisations commonly provide for maintenance in the region of 15 to 20 per cent of initial build cost per year, before enhancements. Treat that as a budgeting convention to be replaced with your own measured figures, not as a rate.
What to prepare before requesting a quotation
A brief that answers these questions produces comparable proposals. Its absence produces ranges that cannot be compared.
- The commercial outcome: what changes in the business if this works, and how it is measured
- The users: who they are, how many, and what each is permitted to do
- The current process: what happens today, including the exceptions people work around
- The systems involved: what must be read from or written to, and who owns each system
- The data: what must be migrated, in what condition, and who is accountable for its quality
- Constraints: regulatory position, data residency, procurement rules, deadline drivers
- The first release: what is in it, and explicitly what is not
- Budget expectation and decision process, shared honestly with shortlisted suppliers
- Internal ownership: who will be the product owner and who signs off acceptance
How Sardo Group approaches development projects
Discovery establishes the commercial outcome, the process reality and the scope of a defensible first release. Technical architecture then fixes the decisions that are expensive to reverse: data model, tenancy, identity, integration boundaries and hosting approach.
Build follows in increments with demonstrable output at each stage, integrations run as their own workstream with dedicated testing and failure handling, and launch covers onboarding, instrumentation and the handover that lets your team operate the system.
The work sits across our custom software development practice, with architecture and independent technical assessment from technology and business consultancy and product builds through platform development.
Common mistakes that increase cost
- Requesting quotations before the requirement is written down, then treating the cheapest as the benchmark.
- Omitting migration, testing and deployment from the scope in the hope they are included.
- Changing the data model after build starts, which touches every screen and every report.
- Treating permissions and administration as features to add later.
- No internal product owner, so decisions wait for meetings.
Frequently asked questions
How much does custom software development cost in Dubai?
There is no meaningful single figure. Cost follows the type of system, the number of integrations, the permission and compliance requirements, and how much existing process must be preserved. The illustrative bands above show the order of magnitude for common categories; a real quotation comes from scoping your requirement.
Why are two quotes for the same brief so different?
Because the brief is rarely the same to both suppliers. Differences usually come from what each has included, whether migration and testing were costed, and whether the estimate was based on vendor documentation or previous experience of that integration.
Is offshore development cheaper?
The hourly rate usually is, but the delivered cost is not automatically lower: coordination, review cycles and rework consume the difference, and the deciding factor is who is accountable for delivery.
How long does a custom software project take?
A focused application runs to weeks, a CRM or marketplace to months, and an enterprise programme with migration and phased rollout to quarters. Duration follows scope and integration count more than team size.
What does maintenance cost after launch?
Plan for hosting, third-party service fees, dependency updates, support and a small enhancement budget. The 15 to 20 per cent convention is a starting point for planning, to be replaced by measured figures once the system is live.
Can we start with a smaller first release and add later?
Yes, and it is usually the better commercial decision, provided the foundation is designed for what comes next. A restricted first release with a data model built only for that release is not a saving; it is a scheduled rebuild.
Key takeaways
Cost is determined by the type of system, the integration surface, the permission and compliance requirements, and how much of the existing process must be retained. Compare proposals on what they include, budget for running costs from the outset, and prepare a brief that a supplier can price without inventing assumptions.
Discuss Your Software Development Project
If you have a requirement, a budget range and an outcome in mind, we will tell you what a defensible first release looks like, what it would take, and what we would leave out. Start with our custom software development solution, review how to choose a development partner, or start your software development project and we will respond with a phased proposal against your brief.