Screens are not a unit of cost
A plain form that everyone can see and edit is cheap. The same form seen by four roles with different permissions, routed through two approvals, and pushed into your accounting file, is a different project. The difference is not the design. It is the number of rules that must be written, tested and kept working.
Before requesting a quote, write one page: who uses the system, what decision each person makes, and where the data lives today. That page sets the number. The drivers are finite:
- Roles and permissions: every extra role adds view and edit rules, and a test for each.
- Workflows and approvals: three approval stages need states, notifications and an audit trail.
- Integrations: payments, WhatsApp, accounting, e-invoicing, national sign-on. Each is its own line.
- Reporting: an exportable table is one cost; a live dashboard is another.
- Mobile use: a field employee on a patchy connection changes the architecture.
- Data migration: years of untidy spreadsheets is a project with its own budget.
- Hosting and support: a recurring monthly cost, not a one-off line.
The services page separates a brochure website brief from an operational system.
Roles and approvals are usually the heaviest line
Most owners are surprised that who sees what costs more than how it looks. The accountant sees prices. The rep sees only their own customers. The manager approves discounts above a threshold. Every sentence like that becomes a rule in code, a test case, and a mistake to prevent.
List the roles by their real job titles. Next to each one write what they create, edit, approve, and must never see. If you cannot fill in that table, the system is not ready to be priced, and any number you hear is a guess.
Approvals need the same detail. What if the manager does not respond in two days? Can somebody sign on their behalf? Can an approved record be reversed? Deciding later means rebuilding later. Define one simple approval chain for the first release and postpone the exceptions.
Price every integration separately
An integration is not a button. It is an agreement between two systems, each with its own rules and failure states. Insist every integration appears as its own line in the quote.
- Payment gateway: the cost is not the pay button. It is pending transactions, refunds, and reconciling payments against orders.
- WhatsApp: a click-to-chat link is trivial. Automated notifications through the WhatsApp Business API need an approved account, message templates, and an ongoing per-message cost.
- Accounting: first ask whether your accounting software has an API. If not, the fallback is file export and import: cheaper, but not real time.
- E-invoicing: ZATCA regulates e-invoicing in Saudi Arabia in phases, and requirements and dates depend on how your business is classified. Check the current official guidance to confirm what applies to you, then have it priced. See the e-invoicing integration guide.
- Nafath: national digital identity sign-on is an official service, not a library you drop in. Eligibility and onboarding are set by the operating authority, so verify the requirements before putting it in phase one. See the Nafath single sign-on guide.
Every integration needs a test environment, an account, and somebody on your side to approve it. Waiting on a third-party account is a common delay, outside the developer's control.
Reporting, mobile use and offline reality
A request for reports cannot be priced. Ask your team to name three reports that will drive a real decision this month, and for each note who reads it, how often, and what changes as a result. Often one filterable, exportable table replaces a dashboard in the first release.
Mobile use is an architectural decision, not a cosmetic one. A system that works well in a phone browser is enough for most office work. A field employee recording data on site with a weak connection needs offline handling and later synchronisation, which visibly raises the cost.
If your team genuinely needs a separate app from the stores, that is a distinct budget with its own accounts, reviews and update cycle. Read the mobile app cost guide for Saudi Arabia before merging both requests into one project.
Data migration, hosting and life after launch
Data migration is the line that gets forgotten and then paid for twice. Ask how many spreadsheets you have, whether names are consistent, how many duplicates exist, and who decides which version is correct. Cleaning data is your team's decision; the developer only executes it. The cleaner the file arrives, the lower the cost.
Hosting and support are permanent monthly expenses. A live system needs backups, security updates, uptime monitoring and somebody who answers when it stops. In the packages, a basic care plan starts from 300 SAR per month, and an extended plan from 750 SAR per month with content changes, priority support and a monthly report. Any quote that does not state the recurring cost is incomplete.
If the system holds personal data about customers or staff, decide early where it is hosted, how long it is kept, who can access it, and how it is deleted on request. Personal data in Saudi Arabia falls under the Personal Data Protection Law, and detail changes, so check the current official guidance. Start with the PDPL compliance guide.
A free prototype removes the most expensive risk
The costliest mistake is not the hourly rate. It is building a whole system, then discovering the team does not use it, or that the workflow on paper is not the one in practice. A prototype settles that before you sign a large scope.
At Tech Corners we start with a free prototype of the main journey: one or two screens showing how a request moves through the system. Sit a real employee in front of it so they can tell you a field is missing, or that a step works differently here. A change now costs minutes. After the build, it costs weeks. A prototype tests the idea, not production, and does not replace a written scope.
Fictional example, not a client result: a Jeddah supply business asked for an order system with four roles, two approvals, an accounting link and a field app. One prototype session showed the second approval happens once every two months, and the reps work from their desks. The field app left phase one; the approval became a notification.
What a written quote must itemise, and who owns what
Do not accept a single figure in a message. Ask for a written scope separating:
- The roles, and the permissions attached to each.
- Workflows and approvals, with their states from creation to closure.
- Each integration on its own line, with who supplies accounts and test environments.
- Reports included by name, and what is out of scope.
- Data migration: the source, the volume, and who cleans it.
- Hosting and the recurring monthly or annual costs.
- The warranty period, and what counts as a bug fix versus a new request.
- Training and handover: who trains your team, and which documents you receive.
Then put ownership in writing, the clause most often skipped. Who owns the source code after final payment? Who owns the data, and how is it exported if you move? Who owns the domain, hosting, repository and third-party accounts? All of these should be registered in your company's name, with the developer granted access, not the other way round.
Phase it, then choose fixed scope or retainer
Make the first release deliberately small. Pick one process that hurts today — orders, bookings, chasing collections — and build it until it works. One working process beats five half-finished ones, and it prices phase two for you.
In the packages, a custom web system or app MVP starts from 15,000 SAR, with a planning window of 6 to 12 weeks depending on scope. If the process itself is not yet clear, a digital transformation assessment starts from 3,000 SAR: a two-week audit of processes and tools ending in a roadmap report.
Fixed scope suits stable, written requirements and gives you a defined figure and date, but every change needs a written addendum. A retainer suits life after launch, when the need becomes continuous improvement. For most SMEs: fixed scope first, then a retainer.
Every project starts with a one-page written scope, a quote within 48 hours, and two payments: 50% to start and 50% before go-live. Tech Corners is a software studio in Jeddah working with SMEs across Saudi Arabia.
Still deciding between a website and a system? Read website or custom system. If the problem is wider than one system, start with digital transformation for a Saudi SME, or discuss your scope.