Skip to content
QuickshipTechnologies

AppsUAE & KSA7 min read

Fixed Price vs Time and Materials for App Projects

Fixed price vs time and materials for app projects in the UAE and KSA: how to choose, what VAT and contracts change, and a checklist to compare quotes.

By · Published

Looking for the software itself? See our app development company Dubai.

Fixed price vs time and materials comes down to one question: how well do you know the scope today? If you can list every screen, user role and integration, a fixed price protects your budget. If the scope will change as you learn, time and materials (T&M) with a cap is usually the safer way to pay.

Most app quotes you compare in Dubai, Abu Dhabi or Riyadh will use one of these two models, or a mix. They look similar on a spreadsheet. They behave very differently once the project starts.

What is the difference between fixed price and time and materials?

Under a fixed price contract, you pay an agreed sum for an agreed scope. Under time and materials, you pay for the hours the team actually works, at agreed rates, plus any agreed costs.

That means the risk sits in different places:

  • Fixed price: the vendor carries the risk of the work taking longer than planned. You carry the risk that the scope was wrong.
  • T&M: you carry the risk of the work taking longer. The vendor carries less risk, so you get more room to change direction.

A fixed price cannot make an unclear product clear. If the brief says "a delivery app like the big ones", the vendor will either add a large buffer or write a narrow scope and bill every extra. Neither is what you wanted.

Fixed price vs time and materials: which one fits your project?

Pick by certainty of scope, not by which number looks lower. Here is a side-by-side view.

Fixed price Time and materials T&M with a cap
Best when Scope is written and stable Scope is unclear or will change You want flexibility and a ceiling
Budget certainty High, for the agreed scope Low Medium to high
Changes Change request, usually billed extra Absorbed in the backlog Absorbed until the cap
Your effort Heavy upfront, light later Steady involvement Steady involvement
Main risk Wrong scope, or a padded price Costs drift with no limit Cap set too low or too high
Good fit Brochure app, simple internal tool New product, complex integrations Most first versions

A few rules of thumb:

  1. Fixed price fits a small, well-defined app. Think of a staff leave request app with three screens and one approval flow.
  2. T&M fits a product you are still discovering, or one with technical unknowns such as a new integration with an ERP or a courier API.
  3. Hybrid fits most others. Pay for a short discovery phase first. Then fix the price per milestone or for the build.

A worked example (hypothetical)

Say a Dubai trading company wants a mobile app for its field sales team. Reps will take orders, check stock and collect payment details. The company also wants it to connect to its accounting system, but the vendor has not seen that system yet.

A fixed price for the whole thing is risky. The integration is unknown, so the vendor either pads the price or excludes the integration and bills it later.

A better route:

  • Phase 1, discovery (T&M, short): workshops, screen flows, a list of integrations, a backlog. The company owns the output.
  • Phase 2, build (fixed price per milestone): order taking first, stock view second, accounting integration third. Each milestone has acceptance criteria and its own price.
  • Phase 3, support (monthly): bug fixes and small changes, agreed separately.

The company knows what it pays at each step and can stop after any milestone.

How do you control a T&M contract?

You control T&M with a cap, a forecast, a visible backlog and the right to pause. Without those four, T&M is a blank cheque.

  • Not-to-exceed cap. Say the vendor estimates 600 hours. You might set the cap at 700. Work beyond it needs your written approval.
  • Short forecasts. Ask for a forecast every sprint or every two weeks, not just at the end of the month.
  • Visible backlog. You should see what the team is working on and what comes next, in a tool you can open yourself.
  • Right to pause or stop. Check the notice period and what you pay for work in progress.
  • Timesheets or sprint reports that match the invoice. If you cannot trace an invoice line to work done, ask before you pay.

What should a GCC app contract cover?

It should cover scope, change, payment, handover and termination in writing. The law fills gaps if you do not, and you may not like how.

On the UAE side, the official UAE Legislation page for the Civil Transactions Law covers the contract for work (muqawala). It says a contractor may supply all or part of the materials as well as the work, and must finish the work under the contract terms and within the agreed period. Law firm commentary reports that a new Civil Transactions Law came fully into force on 1 June 2026, replacing Federal Law No. 5 of 1985. Check that you are reading the current text.

Mayer Brown notes that the muqawala provisions are mostly non-mandatory default rules that apply when the parties have not agreed otherwise. That is the practical point. If your contract is silent on changes, delays or termination, default rules decide. We have not verified whether software work counts as a contract for work under that law, so ask your lawyer. The same goes for Saudi contracts: take legal advice before you sign.

Here is a checklist for the contract, whichever model you choose:

  1. Scope document with screens, user roles, integrations and what is out of scope.
  2. Languages. If the app needs Arabic and English, say so. Include right-to-left layout, Arabic content entry and who translates the text.
  3. Acceptance criteria for each milestone, so "done" is not a matter of opinion.
  4. Change process. Who requests, who estimates, who approves in writing.
  5. Payment schedule tied to milestones (fixed) or to approved timesheets (T&M).
  6. Source code and design files handed over to you on payment.
  7. Accounts in your name. Register the Apple Developer and Google Play accounts, cloud hosting and domain under your company. Add the vendor as a team member.
  8. Termination terms, including what you pay for work done and how the vendor hands over.
  9. Support period after launch, and what counts as a bug versus a new feature.

How do VAT and currency affect the quote?

They change the number you actually pay, so ask every vendor to state whether the quote includes VAT. If the vendor is VAT-registered in the UAE, the FTA gives the standard rate as 5%. A fixed fee or a monthly T&M invoice would normally carry that on top.

In Saudi Arabia, ZATCA's invoicing guideline says taxable supplies carry the 15% standard rate added to the final selling price. It also says invoices must state that the consideration includes VAT at 15%, in Saudi Riyals. If you compare a Riyadh vendor with a Dubai vendor, compare them on the same basis: same VAT treatment, same currency, same scope.

Two more points for T&M. Ask which currency the hourly rate is in. Ask whether the rate is fixed for the contract or can change after a set period.

Common mistakes when comparing app quotes

  • Comparing totals, not scope. A lower fixed price often means a narrower scope. Put the quotes side by side against your own scope list.
  • Treating T&M as "no budget". Set a cap before the first sprint.
  • Skipping discovery to save a few weeks, then paying for the wrong scope.
  • No owner on your side. Someone must answer questions within a day or two. Slow answers raise cost under T&M and delay milestones under fixed price.
  • Letting the vendor hold the app store accounts. It is hard to undo later.
  • Forgetting post-launch. Hosting, bug fixes and OS updates are usually not part of the build price.

How to choose in five steps

  1. Write your scope in a page or two: users, screens, integrations, languages.
  2. Mark each item as known, partly known or unknown.
  3. If most items are known, ask for a fixed price. If many are unknown, ask for paid discovery, then T&M with a cap or milestone pricing.
  4. Ask each vendor the same questions on change process, VAT, handover and account ownership.
  5. Compare quotes on scope and terms first, price second.

If you want a second opinion on a quote, Quickship's team can review your scope and discuss options for mobile app development or custom software. Pricing for both is on quote, because it depends on your scope.

Frequently asked questions

Is a fixed price quote always cheaper than time and materials?

No. A fixed price gives you a known number, not a lower one. Vendors usually price in the risk of unclear scope, and every change request is billed on top. Time and materials can cost less when the scope is small or still forming, but only if you set a cap and review progress often.

Can I start with time and materials and switch to fixed price later?

Yes, and it is a common way to work. You pay for a short discovery phase on time and materials, end up with screens, a backlog and acceptance criteria, then ask for a fixed price on the build. Write the switch into the first contract so the vendor does not have to re-quote from zero.

Who should own the Apple and Google developer accounts?

Your company should. Register the accounts under your legal entity and add the vendor as a team member. If the vendor holds the accounts, moving the app to another team later becomes a negotiation. Put account ownership and source code handover in the contract.

Do I pay VAT on app development in the UAE and Saudi Arabia?

If the vendor is VAT-registered, the UAE standard rate is 5% according to the FTA, and the Saudi standard rate is 15% according to ZATCA. Ask every vendor to say whether their quote includes or excludes VAT. Your accountant can confirm how it applies to your situation.

What should a change request process include?

It should say who can ask for a change, how the vendor estimates it, and who approves it in writing before work starts. Each change should show its effect on cost and delivery date. Without this, both models drift into arguments.

Sources

  1. UAE Legislation: Civil Transactions Law (contract for work, muqawala)
  2. Lexology: new UAE Civil Transactions Law in force 1 June 2026
  3. Mayer Brown via Mondaq: muqawala contracts under the new UAE Civil Code
  4. ZATCA: invoicing guidelines

Rules and fees in the UAE and Saudi Arabia change. This guide reflects the sources above on 20 November 2026. Check the official source before acting on it.

App Development

Mobile and web apps built to your requirements.

Get a quote

Related guides

Instant quote