Skip to main content

How we price software projects.

We don’t publish package prices, because the same request can describe very different amounts of work. Instead, here is exactly how we scope and quote, what moves the number, and how to get an accurate estimate quickly.

From enquiry to quote

How a quote comes together.

  1. Step 1

    Conversation

    You tell us what the business needs and where it hurts today. We ask about users, volumes, systems you already run and deadlines.

  2. Step 2

    Scoping

    We turn that into a written scope: the features, integrations, data to migrate and anything we recommend leaving out of the first release.

  3. Step 3

    Proposal

    You receive a proposal with the scope, a delivery plan with clear milestones, and the price. Hosting and support are listed separately.

  4. Step 4

    Changes

    If priorities change during the project, we agree the change and its effect on time and cost before the work is done, not after.

What moves the number

What drives the cost.

These are the factors we price against. Knowing them up front is the fastest way to a realistic budget.

What the system has to do
The number of workflows, user roles and screens is the biggest single factor. A booking form and a booking engine with supplier inventory are different projects, even if both are called "booking".
Integrations
Every connection to another system (accounting, ERP, payment gateways, WhatsApp, government portals, suppliers) adds design, build and testing work, and some third-party APIs are far harder to work with than others.
UAE compliance
VAT-correct invoicing, readiness for the UAE e-invoicing programme, and personal-data handling under the PDPL all need to be designed in. They are cheaper to build in at the start than to retrofit.
Platforms and languages
Web only, or web plus iOS and Android. English only, or a full bilingual English and Arabic build with right-to-left layouts.
Data migration
Moving years of records out of spreadsheets or an old system, cleaning them and proving the numbers reconcile is real work, and it is often underestimated.
Design depth
A clean interface built on a proven component system costs less than bespoke design with extensive user research, prototyping and testing.
Hosting and support after launch
Cloud hosting, monitoring, backups and ongoing improvements are recurring costs. We quote them separately so the build price is not hiding them.

Cost guides

Typical costs, by type of project.

Our guides explain what shapes the budget for each kind of build, and where projects tend to overspend.

Already running a system? Ongoing work is covered under software maintenance and support.

Questions

Pricing, specifically.

Because two projects with the same name can differ several times over in scope. A fixed package would either overcharge simple projects or under-deliver complex ones. We would rather understand what you need and give you a number we can stand behind.

Send a short brief: what the system must do, who will use it, which systems it connects to, and your timeline. Our guide to writing a software requirements brief shows what to include.

Often, yes. If a packaged product or a configured system such as Muhasib covers your process, that is usually the faster and cheaper route, and we will tell you so. Custom builds make sense where your workflow is distinctive or nothing on the market fits.

No. They are ongoing costs, so we quote them separately. That keeps the build price honest and lets you see the full cost of running the system.

Our invoices follow UAE VAT rules for tax invoices. The proposal states clearly whether figures are shown before or after VAT.

Let’s scope your project.

Tell us what you are building. We reply within one business day.