Custom software in Saudi Arabia is quoted per project rather than priced off a menu, because cost follows scope: user roles, integrations such as ZATCA, NPHIES or Mudad, and whether you need mobile apps too. Most first releases take eight weeks or more. A short paid discovery phase is the honest way to get a fixed number.
Why there is no price list for custom software
A website has a recognisable shape, so it can be priced from a starting number. Custom software does not. A quotation tool for a trading company and a patient portal for a clinic group are both custom software, and they share almost nothing except the label.
That is why we, and any agency being straight with you, quote software per project. Our published pricing lists it as quote only, with a typical timeline from eight weeks. Anyone giving you a firm number before understanding your workflow is either padding heavily or planning to charge you for change requests later.
What actually drives the cost
- User roles. An admin, a staff user and a customer are three different sets of screens and permissions.
- Integrations. ZATCA Phase 2 for invoicing, NPHIES for insurance claims, Mudad for payroll, or your existing ERP. Each is real engineering and testing work.
- Web only, or web plus mobile apps. Adding iOS and Android apps adds a second front end to build and maintain.
- Data migration. Moving years of records out of spreadsheets or an old system is often underestimated.
- Arabic and English. A properly bilingual interface with RTL layouts is more work than one language.
- Reporting. Dashboards that managers actually trust need clean data models, which take design time up front.
How long does custom software take?
A focused first release, such as an internal workflow tool or a customer portal, usually takes eight to twelve weeks. Systems with several integrations or a mobile app run longer. We recommend shipping a smaller first version that people use, then extending it, rather than a large release that arrives late.
How to get a quote you can rely on
Ask for a short discovery phase before the build quote. In it, the team maps your user roles, screens, integrations and data, and you get a written scope with a fixed price and timeline. It costs a little up front and saves a great deal of arguing later.
Compare quotes on scope, not on the total. Two quotes that differ by half usually describe two different systems.
If a quote has no list of screens, roles and integrations attached, you cannot compare it with anything.
