Table of Contents
Frequently Asked Questions
How many payment milestones should a fixed-scope software project have?
There is no legal number. Most fixed-scope projects use four to six stages, such as a deposit, design sign-off, a working build, user testing and final acceptance. Each milestone should map to a deliverable that both sides can verify, and the split should reflect the cash-flow risk each party carries.
Is it normal for a developer to ask for a deposit before starting work?
Yes. A deposit on signing is a common way to secure the developer's capacity and cover early costs. Its size is a negotiated commercial term, not a fixed rate. Founders often balance a smaller deposit with shorter intervals between later payments.
Can a developer keep the source code until the final payment clears?
Yes, if the contract says so. A common approach is to give the client a limited usage right for testing and transfer full ownership only after the final milestone is paid. Without a written intellectual property clause, ownership of the code can become a dispute.
What can a developer do if a client will not approve a milestone?
The contract should answer this in advance. Useful terms include a defined review window, a written defect list requirement, and deemed acceptance if the client does not respond in time. Where the client names a defect, the developer corrects it and resubmits. Unresolved cases follow the dispute resolution steps in the agreement.
Do milestone invoices have to include VAT?
They must if the supplier is VAT-registered. The standard UAE VAT rate is 5%, and the Federal Tax Authority sets the mandatory content of a tax invoice. The contract should state whether prices include or exclude VAT, so the invoice matches the agreed amount.
How should a developer price a mid-project change request?
Issue a written change request that states the added work, its cost and its effect on the timeline. The client signs it before development starts. The change then either adjusts the value of an existing milestone or becomes a new one. Instructions given only on calls or in chat messages are hard to enforce.
Can a Meydan Free Zone software company support milestone payments through its bookkeeping and banking setup?
Yes. Meydan Plus (mPlus) brings together Meydan Free Zone’s business support offerings, including mAccounting for bookkeeping, VAT, Corporate Tax and payroll, which helps a company record each milestone receipt against its invoice. mCore provides business bank account support, while account approval stays with the bank.
Topic Summary
What Payment Milestones Mean in a Software Development Contract
A payment milestone is a defined stage of a project that triggers a set payment once agreed conditions are met. In a software development contract, milestones link money to deliverables such as a signed specification, a working prototype, or an accepted release, so both sides know what each payment covers.
How to Structure Milestones in a Software Development Contract
Divide the project into stages that each produce a verifiable deliverable, then assign a share of the fee to each stage. Keep early payments proportionate so neither party carries disproportionate risk.
Handling Scope Changes and Late Payments
Scope changes need a written change request that states the added work, cost and timeline before development starts. Late payments need a defined remedy, such as a grace period followed by paused work.
Five Clauses That Protect Milestone Payments
Five clauses protect payments in a software development contract: a deliverables schedule, acceptance criteria, a change request process, an intellectual property transfer tied to payment, and a dispute resolution mechanism.
Invoicing Each Milestone Correctly
Each milestone invoice should reference the software development contract, name the deliverable, show the amount in AED, and include VAT where the supplier is VAT-registered. Issuing invoices on acceptance, not on delivery, keeps the payment trail consistent.
What Founders Should Settle Before Signing
Before signing, confirm the scope, the milestone split, who approves deliverables, how change requests are priced, and which entity holds the license for the services. A software development contract works best when commercial terms match the company's licensed activity.
Conclusion
A software development contract works when each payment is tied to a deliverable both sides can verify. Clear milestones, written change control, correct invoicing and a matching license prevent more disputes than any negotiation tactic. Before the next proposal goes out, map each deliverable to an acceptance test and a payment, then confirm your licensed activity covers the work.
Payment Milestones in UAE Software Development Contracts
Most software projects in the UAE run into trouble over money, not code. A client pays a deposit, the developer starts building, and nobody has agreed what finished means. A software development contract is where that gap closes or stays open. This guide is for founders structuring a software business before applying for a business license with Meydan Free Zone.
What Payment Milestones Mean in a Software Development Contract
A payment milestone is a defined stage of a project that triggers a set payment once agreed conditions are met. In a software development contract, milestones link money to deliverables such as a signed specification, a working prototype, or an accepted release, so both sides know what each payment covers.
Milestones Versus Time-Based Billing
Milestones pay for outcomes. Time-based billing pays for hours. Fixed-scope builds suit milestones, while open-ended work suits time and materials.
Many agreements mix both. Picture a Dubai e-commerce founder who hires a developer for a fixed-scope web store and pays by milestone, then moves to hourly billing for post-launch tweaks.
Typical Milestone Structure for a Fixed-Scope Software Project
| Stage | Illustrative Share (Negotiated) | What Triggers Payment |
|---|---|---|
| Deposit on signing | 20% to 30% | Signed agreement; secures the developer's capacity |
| Specification or design sign-off | 15% to 20% | Written approval of the specification by the named client approver |
| Working build delivered | 25% to 30% | Build deployed to a test environment with core features running |
| User acceptance testing passed | 15% to 20% | All agreed test cases passed, or a defect list cleared |
| Go-live and final acceptance | 10% to 15% | Production release and written final acceptance |
Why the Structure Matters Commercially
Milestones decide who funds the project between payments. Vague ones are the most common source of payment disputes. A developer finishes a module, the client calls it incomplete, and no clause defines completion. Written terms give you a clear basis if a claim reaches court or arbitration.
How to Structure Milestones in a Software Development Contract
Divide the project into stages that each produce a verifiable deliverable, then assign a share of the fee to each stage. Keep early payments proportionate so neither party carries disproportionate risk.
Common Milestone Stages
- Deposit on signing to secure capacity.
- Specification or design approval.
- Working build or beta release.
- Final acceptance and go-live.
A mobile app agreement often follows exactly this pattern. If you are building the business behind it, the software development business guide covers the licensing side.
Balancing Deposit and Final Payment
A large final payment protects the client. A large deposit protects the developer. Treat the split as a negotiated position, not a standard rate.
Avoid back-loading so heavily that the developer funds the whole build. One workable compromise is a smaller deposit with shorter payment intervals, which keeps cash flow stable on both sides.
Tying Payments to Acceptance Criteria
Define pass or fail tests for each deliverable. Name who has authority to sign off for the client. Set a review window and state what happens if the client stays silent.
Deemed acceptance is the clause worth fighting for. If no written defect list arrives within the review period, the deliverable counts as accepted and the invoice falls due.
Handling Scope Changes and Late Payments
Scope changes need a written change request that states the added work, cost and timeline before development starts. Late payments need a defined remedy, such as a grace period followed by paused work.
Change Request Process
Use a written request, a priced response and a signed approval. Changes either adjust a milestone value or add a new milestone. Chat messages and calls are not a substitute. If a client asks for an extra payment gateway integration on a call, issue a priced change request before touching the code.
Remedies for Delayed Payment
- A grace period, then a right to suspend work.
- Interest or late fees only if agreed in writing.
- Source code and license rights stay with the developer until payment clears.
- Hosting credentials held until the final invoice is paid.
Five Clauses That Protect Milestone Payments
Five clauses protect payments in a software development contract: a deliverables schedule, acceptance criteria, a change request process, an intellectual property transfer tied to payment, and a dispute resolution mechanism.
Deliverables Schedule and Acceptance Criteria
- List each module against its payment value.
- Attach measurable test conditions to every module.
- Record the named approver for each deliverable.
Intellectual Property Transfer on Payment
- Ownership passes after full payment, not on delivery.
- Grant a limited usage right for testing before that point.
- State that the right ends if payment defaults.
Change Control, Remedies and Dispute Resolution
- Repeat the change request and late payment terms in one place.
- Choose governing law and forum deliberately. A Meydan Free Zone company sits under Dubai Courts jurisdiction, so name the Dubai Courts or an agreed arbitration forum.
- Require a short negotiation period before formal proceedings.
Invoicing Each Milestone Correctly
Each milestone invoice should reference the software development contract, name the deliverable, show the amount in AED, and include VAT where the supplier is VAT-registered. Issuing invoices on acceptance, not on delivery, keeps the payment trail consistent.
VAT and Tax Invoice Content
The standard UAE VAT rate is 5%, and registration is mandatory when annual taxable supplies exceed AED 375,000. VAT-registered suppliers must issue tax invoices that meet FTA content rules. State in the agreement whether prices include or exclude VAT. The UAE tax invoice requirements article lists the mandatory fields.
Bookkeeping Support for Free Zone Companies
Meydan Plus (mPlus) brings together Meydan Free Zone’s business support offerings, including mAccounting for bookkeeping, VAT, Corporate Tax and payroll, and mCore for business bank account support. A software company can record each milestone receipt against its invoice for VAT returns, while bank account approval stays with the bank.
Match every milestone receipt to its invoice with mAccounting, part of Meydan Plus (mPlus).
What Founders Should Settle Before Signing
Before signing, confirm the scope, the milestone split, who approves deliverables, how change requests are priced, and which entity holds the license for the services. A software development contract works best when commercial terms match the company's licensed activity.
Match the Contract to Your Licensed Activity
The contracting entity should hold a license covering the services it sells. Review the IT and software agency guide before applying for your business license with Meydan Free Zone, not after the first client signs.
Pre-Signing Checks Worth Making
- Confirm payment currency, bank details and invoice recipient.
- Agree acceptance authority and the review window.
- Walk through each milestone's acceptance test with the client.
- Have a qualified UAE lawyer review dispute and governing law terms.
Conclusion
A software development contract works when each payment is tied to a deliverable both sides can verify. Clear milestones, written change control, correct invoicing and a matching license prevent more disputes than any negotiation tactic. Before the next proposal goes out, map each deliverable to an acceptance test and a payment, then confirm your licensed activity covers the work.
Ready to Launch Your Business in Dubai?
Let's Connect
