Skip to main content

The Hashtech

What Should a Mobile App Development Proposal Include in Saudi Arabia?

Published Date
9 November, 2026
What Should a Mobile App Development Proposal Include in Saudi Arabia?

A strong mobile app development proposal in Saudi Arabia should cover 12 things: business goal and scope, deliverables and exclusions, SAR pricing with VAT, milestones and payments, timeline, team, technical approach, Arabic and integrations, PDPL and security, IP and source-code ownership, support and SLA, and exit terms. If a proposal skips any of them, ask for the missing section before you sign.

This guide is a buyer’s checklist for founders, CTOs, and procurement teams. It shows what to look for, which red flags to watch, and how to compare vendors fairly. It is general information, not legal advice. Have Saudi counsel review your final contract.

Why Proposals Fail Saudi Buyers

Most proposal problems are not technical. They are gaps that appear later as disputes, delays, and surprise costs.

  • A single price with no breakdown. You cannot compare it or negotiate it.
  • VAT missing. The real cost is 15% higher than the headline number.
  • No Saudi compliance section. PDPL, hosting, and Arabic UX appear only after signing.
  • Vague ownership terms. You pay for the app but cannot move the code.
  • No exit plan. Leaving the vendor becomes a project in itself.

A good proposal answers these questions before you ask them.

The 12-Point Proposal Checklist at a Glance

# Section What good looks like Red flag
1 Goal and scope Business goal, users, and success measures Feature list with no goal
2 Deliverables Named outputs and clear exclusions “Everything needed” wording
3 Pricing SAR, itemized by phase, VAT shown One bundled number
4 Milestones Payments tied to accepted deliverables Large upfront payment, no milestones
5 Timeline Phases with dates and dependencies One end date
6 Team Named roles, seniority, availability “Our team” with no names
7 Technical approach Platform and stack with reasons Stack chosen for the vendor’s comfort
8 Arabic and integrations RTL, bilingual QA, listed integrations Arabic as a final step
9 PDPL and security Data map, hosting, processor terms “We are secure” with no detail
10 IP and handover Ownership, repositories, accounts, docs Silent on source code
11 Support and SLA Severity levels and response targets “Ongoing support” with no terms
12 Legal and exit Governing law, disputes, transition help No termination terms

1. Business Goal and Scope Summary

The proposal should start with your goal, not the vendor’s features. It should name the problem, the target users, and how you will measure success. For example: reduce order-handling time, increase repeat bookings, or replace a manual process.

Look for a short scope statement and a list of assumptions. If the vendor never asks about your users or goals, the quote rests on guesses.

2. Deliverables, Features, and Exclusions

List every deliverable by name: design files, mobile apps, admin panel, backend, documentation, and test reports. Then check the exclusions. This is where many budgets break.

Typical exclusions to confirm:

  • Content and translation work
  • Third-party licenses and subscriptions
  • Store account fees
  • Extra platforms or languages
  • Data migration
  • Training and marketing

A clear exclusions list protects both sides. It turns “I thought that was included” into a written answer.

3. Pricing in SAR, With VAT Shown

Saudi buyers should expect pricing in Saudi riyals with the 15% VAT shown as a separate line. Standard VAT has been 15% since July 2020. Invoices from VAT-registered Saudi suppliers also follow ZATCA e-invoicing rules, which include Arabic invoices and the seller’s VAT registration number. Ask your vendor to confirm how they invoice.

Itemize the price by phase: discovery, design, development, QA, launch, and support. Our guide to mobile app development cost in Saudi Arabia explains what drives each line.

Pass-Through Costs to Clarify

Some costs sit outside the development fee. Ask who pays for each.

  • Cloud hosting and backups
  • Maps, SMS, email, and push services
  • Payment gateway fees
  • Apple and Google developer fees
  • Third-party SDK licenses
  • Security testing by an outside party

Pricing Models

The proposal should state the pricing model and why it fits.

Model Suits Main risk What the proposal must show
Fixed price Clear, stable scope Change requests add cost Frozen scope and change process
Time and materials Scope that will evolve Budget drift Rate card, estimates, monthly cap
Dedicated team Long-term product work Ongoing commitment Team roles, ramp-up, notice period
Build-operate-transfer Build first, then hand over Transfer complexity Transfer plan and conditions

Choose the model that matches how clear your requirements are. A fixed price on shifting requirements creates the most friction.

4. Milestones and Payment Schedule

Tie each payment to an accepted deliverable, not to elapsed time. A milestone should say what you will receive, how you will test it, and who signs it off.

Watch for a large upfront payment with vague stages afterward. Also check what happens when a milestone slips because of the vendor, and what happens when it slips because of your feedback delay.

5. Timeline and Dependencies

A useful timeline lists phases, dates, and dependencies. Dependencies include your content, API access, approvals, and third-party onboarding.

If your project depends on outside approvals, such as SAMA requirements or government integrations, the proposal should say so. Those steps run on someone else’s schedule. Our guides on how long it takes to build an app in Riyadh and in Jeddah show where time usually goes.

6. Team, Roles, and Availability

Ask for named roles: project manager, designer, developers, QA, and technical lead. Then check three things.

  • Seniority. Who writes the code, and who reviews it?
  • Location and overlap. Where does the team sit, and how many hours overlap with your day?
  • Replacement. What happens if a key person leaves?

Ask about on-site availability for workshops and demos. Many Saudi buyers value face-to-face sessions at key milestones.

7. Technical Approach

The proposal should explain the platform and stack, and give reasons tied to your needs. Native, Flutter, and React Native each fit different cases. A vendor should recommend one based on performance, budget, and integrations, not habit.

Check for these items:

  • Architecture overview and main components
  • Environments: development, staging, and production
  • Release process and version control
  • Monitoring and error tracking
  • A list of integrations, such as payments and identity

For payments, see our guide on how to add Apple Pay and STC Pay. For national identity sign-in, see how to add Nafath login to a mobile app.

8. Arabic, RTL, and Localization

For Saudi users, Arabic is part of the product. The proposal should state whether the app is Arabic-first, bilingual, or English with Arabic added later. It should also cover RTL layouts, Arabic fonts, numerals, Hijri dates where needed, and bilingual QA.

Adding Arabic late costs more than planning it from the start. Read our guide to Arabic app development and RTL design for what to ask.

9. PDPL, Security, and Data Hosting

If your app handles personal data about people in Saudi Arabia, PDPL applies. The proposal should name the data the app collects, the legal basis, where data is hosted, and which vendors touch it.

Look for:

  • A data map. What data, why, and where it flows.
  • Role clarity. You are usually the controller, and the vendor is a processor. A written processor agreement should follow.
  • Breach process. PDPL requires notifying SDAIA within 72 hours of becoming aware of a breach that may cause harm.
  • Hosting and transfers. Where servers sit, and how any data leaving the Kingdom is handled.
  • Security controls. Encryption, access control, logging, and test data practices.
  • SDK list. Every third-party SDK and what it collects.

Our guide on how to comply with PDPL in Saudi Arabia covers each duty in detail.

10. IP Ownership and Source-Code Handover

This section decides whether you can switch vendors later. The proposal should say who owns each item.

  • Source code and repositories
  • Design files and brand assets
  • Documentation and test cases
  • App Store and Google Play accounts
  • Cloud accounts and credentials
  • Domains and certificates

The contract should separate pre-existing vendor tools from new deliverables built for you. It should also list third-party and open-source components with their licenses.

Saudi copyright law has features that affect drafting. A global legal guide notes that the law recognizes moral rights and restricts assigning future works. So do not rely on a generic “we assign everything” sentence. Ask Saudi counsel to draft the IP clause for your deliverables.

The Handover Package

Ask the vendor to list what you receive at the end:

  • Complete source code, with build instructions
  • Technical and API documentation
  • Test accounts and test data
  • Environment and deployment guides
  • Store listing assets and account access
  • A walkthrough session with your team

For critical systems, ask about source-code escrow as an extra safeguard.

11. Testing, Acceptance, and Warranty

Define “done” before work starts. The proposal should describe the test types, the acceptance process, and the warranty period for defects.

Check these points:

  • Functional, device, performance, and security testing
  • User acceptance testing: who tests, with what data, and for how long
  • Defect severity levels and fix commitments
  • A warranty period after launch for bugs in delivered work

12. Support, SLA, and Maintenance

“Ongoing support” means nothing without terms. A real service level agreement (SLA) defines:

  • Severity levels, such as critical, major, and minor
  • Response and resolution targets for each level
  • Support hours and contact channels
  • Backend uptime commitments, where relevant
  • What maintenance covers: bug fixes, OS compatibility updates, security patches, and monitoring
  • What counts as new feature work and how it is priced

Apple and Google update their platforms every year, and those updates can break apps. Ask whether OS compatibility work sits inside the support fee.

13. Change Requests, Assumptions, and Risks

Every project changes. The proposal should explain how. It should state who can request changes, how they are estimated, and how approval works. It should also list key assumptions and risks, such as late content, slow approvals, and integration delays.

A vendor that names risks honestly is easier to trust than one that promises none.

14. Legal Terms and Exit

Your final contract should cover these points. Have counsel review each one.

  • Governing law. State the law that applies.
  • Language. Saudi private contracts are often bilingual. A bilingual contract needs a clause that says which language prevails. Saudi courts require Arabic, or a certified Arabic translation of foreign-language documents.
  • Dispute resolution. Arbitration agreements must be in writing under Saudi law. A clear clause names the institution, seat, language, number of arbitrators, and governing law. The Saudi Center for Commercial Arbitration (SCCA) publishes model clauses.
  • Confidentiality. Sign an NDA before you share details.
  • Termination and exit. Define notice periods, final payments, and transition help.

Transition help matters most. A good vendor commits to hand over code, documents, and access in a set period, so you are never locked in.

How to Compare Proposals Fairly

Do not compare price alone. Use a simple scorecard. The weights below are an example. Adjust them to your priorities.

Criteria Example weight Questions to ask
Scope clarity 20% Are deliverables and exclusions named?
Price transparency 15% Is it itemized in SAR with VAT shown?
Saudi compliance 20% Are PDPL, hosting, and Arabic covered?
Team and delivery 15% Are roles, names, and availability clear?
IP and exit terms 15% Can you own and move your code?
Support and SLA 15% Are response targets written down?

Score each vendor from 1 to 5 on every row, multiply by the weight, and compare totals. Then discuss the lowest-scoring rows with each vendor.

Also read our guide on how to choose a mobile app development company for the selection questions to ask alongside this checklist.

Red Flags in a Proposal

  • A price with no phase breakdown
  • No mention of VAT, or of who pays pass-through costs
  • No named team members
  • Fixed price on a vague scope
  • No PDPL or data hosting section
  • Silence on source-code ownership
  • No acceptance criteria or warranty
  • “Unlimited” support or revisions
  • No exit or transition terms
  • Pressure to sign before you receive these answers

One flag deserves a question. Several flags deserve a different vendor.

How We Structure a Proposal at The Hashtech

Our process follows six stages: requirement analysis, UI/UX design, engineering, quality assurance, launch, and post-launch support. Our proposals follow the same order, so each stage has its own scope, deliverables, and price line. We offer fixed-price, time-and-material, dedicated team, and build-operate-transfer models, and we state which one fits your project and why.

For delivery, we work in short sprints with regular demos, so you see working software during the build. If you want to compare our approach with other vendors, use the checklist above on our proposal as well. Our mobile app development team expects that comparison.

Building enterprise platforms alongside the app? Our software development company in Saudi Arabia can scope the backend and integrations in the same proposal.

Final Thoughts

A good mobile app development proposal makes decisions easier. It shows what you get, what you pay, who does the work, how you stay protected, and how you can leave. It treats Saudi requirements such as VAT, Arabic, PDPL, and hosting as core scope, not as add-ons.

Use the checklist before you sign. Ask for the missing sections. Compare vendors with a scorecard. And have counsel review the contract. The best time to find a gap is before you pay for the work.

Frequently Asked Questions

What should a mobile app development proposal include?

It should include the business goal and scope, deliverables and exclusions, itemized pricing with VAT, milestones and payments, timeline, team, technical approach, Arabic and integrations, PDPL and security, IP and handover, support and SLA, and legal and exit terms.

Should app development pricing in Saudi Arabia include VAT?

The proposal should show VAT as a separate line. The standard rate is 15%. Ask the vendor how they invoice, since Saudi e-invoicing rules require Arabic invoices with the seller’s VAT registration number.

Who owns the source code after development?

It depends on the contract. Ask for a written clause that names who owns the code, designs, and accounts, and what the vendor keeps. Because Saudi copyright law has specific rules, have Saudi counsel draft the IP clause.

Does a contract have to be in Arabic?

Generally no, except in some cases such as contracts with the government. But Saudi courts require Arabic, or a certified Arabic translation. Bilingual contracts should say which language prevails.

How should payments be structured?

Tie each payment to an accepted deliverable. Avoid large upfront payments with vague stages. Define acceptance criteria in the proposal.

What is an SLA in an app proposal?

A service level agreement sets severity levels, response and resolution targets, support hours, and what maintenance covers. Without it, “support” has no measurable meaning.

How many proposals should I request?

Request three, and give each vendor the same brief. Then compare them with one scorecard.

This article is general information, not legal advice. Facts about VAT, e-invoicing, contract language, arbitration, and copyright come from public legal and tax guidance. Rules change, so confirm current requirements with ZATCA and qualified Saudi counsel before you sign a contract.

Want a Proposal That Passes This Checklist?

Send us your goals, users, and timeline. Talk to our team, and we will prepare a proposal with scope, SAR pricing, PDPL, handover, and support terms laid out clearly.

 

Lara Hawkins
Lara Hawkins is a Senior Content Writer Specialist with expertise in creating clear and SEO-focused content. She specializes in technology, mobile app development, business, and education topics, helping brands communicate complex ideas in a simple and reader-friendly way.