Skip to content

24.7°N 46.7°E · Serving the Kingdom

Custom Software Development Company for Saudi Arabia

Riyadh, Jeddah, Medina, Mecca and Dammam each run on their own mix of government, trade, visitor-services and industrial work. QalbIT builds the custom software behind all five: internal systems, backend platforms and CRM, engineered by one senior remote team on Saudi hours.

No office and no legal entity in the Kingdom, stated plainly on every city page below. What carries across all five is the ZATCA e-invoicing work, the PDPL data-protection position, and a written scope agreed before anyone prices a project.

Working overlap · a normal TuesdayBlue = live together

Saudi ArabiaLocal business hours, Sunday to Thursday
AhmedabadIndia standard time · our working day

Saudi Arabia and Kuwait share the same UTC+3 offset, so the working day we already keep for the Gulf covers all five Saudi cities in full.

8+

Years in custom software

120+

Projects delivered

50+

Clients worldwide

0

Subcontractors

What we build


Custom software for companies operating across Saudi Arabia.

In the Kingdom, invoices clear through ZATCA’s Fatoora platform and personal data answers to PDPL, overseen by SDAIA. That is the digital-government side of Vision 2030, and it reaches every city the same way.

  1. Custom software development

    End-to-end platforms, internal tools and B2B portals for Saudi companies replacing spreadsheets and licensed software that never fit the business.

    Laravel · Node.js · React

  2. ZATCA-compliant e-invoicing

    Phase 1 (December 2021) ended handwritten invoices. Phase 2 connects your system to Fatoora wave by wave: Wave 25 covers VAT-subject revenue above SAR 187,500 in any year from 2022 to 2025, live by 1 February 2027.

    Phase 2 · Wave 25

  3. PDPL-ready data handling

    PDPL reaches processors outside the Kingdom, us included. You stay the controller, and any personal data that leaves Saudi Arabia moves under Article 29 with SDAIA’s Standard Contractual Clauses, signed before the build.

    Article 29 · SCCs

  4. CRM and reporting tools

    Arabic and English in the same record, right-to-left screens and reports that read correctly in both, for sales and operations teams that work in two languages.

    Arabic · English · RTL

  5. Cloud and DevOps

    Hosting chosen around your data: inside the Kingdom where PDPL or a client contract requires it, regional where it does not. Every release is staged and can be reversed, wherever it runs.

    AWS · Docker · CI/CD

  6. Dedicated product teams

    A standing group of named QalbIT engineers running your product’s roadmap release by release, wherever in the Kingdom your team sits.

    Monthly · 30 days notice

Why us


Why Saudi companies choose one remote team across five cities.

A Saudi build succeeds or fails on the same things wherever in the Kingdom it runs: an honest office claim, a real overlap and a data-protection position settled before the first sprint.

  • One contract, one team, five cities

    The same engineers, the same written-scope discipline and the same PDPL position whether the work is in Riyadh, Jeddah, Medina, Mecca or Dammam.

  • A full working day, not a morning window

    The whole Kingdom keeps one clock, UTC+3, and a Sunday-to-Thursday week. Our Ahmedabad team already works Gulf hours, so demos and sign-offs land inside your week rather than ours.

  • We say what we are not

    No Saudi office, no local entity and no commercial registration. That rules us out of bidding on Etimad, where government tenders run, and we say so before anyone prices the work.

  • You keep the code and the access

    Your company owns the repository from the first commit, and the cryptographic certificates ZATCA issues for your invoicing are registered to you, not to us. End the engagement and nothing needs handing back.

Process


One process, run the same way in all five cities.

The city does not change how the work runs. What changes is the sector detail each city page covers.

  1. Discover & define

    We map today’s workaround, then confirm which ZATCA wave your revenue puts you in and what personal data the system will hold.

    Week 1

  2. Design & validate

    A clickable prototype, in Arabic and English where the product needs both, tested with the people who will use it before production code starts.

    Weeks 2-3

  3. Build in sprints

    Two-week sprints, each closing on a live demo booked inside the Saudi working week.

    Sprint by sprint

  4. Launch & stabilise

    Where the system issues invoices, its units are onboarded with ZATCA and pass compliance checks before go-live. Data comes across from the old system, with a rollback path ready.

    Launch week

  5. Improve & extend

    Once real Saudi transactions are flowing: monitoring, an alert on every invoice Fatoora rejects, and the next roadmap release.

    Ongoing

Engagement models


Fixed scope, staff augmentation or a dedicated team.

The same three models in every city we work in. The choice is made on scope and risk, not on which of the five cities the work sits in.

  1. Fixed-scope project

    One system, a fixed price and the exclusions listed. The usual fit for a ZATCA retrofit, where the wave deadline sets the end date.

    Fixed price · 6-14 weeks

  2. Dedicated product team

    A standing team for a product that keeps growing after launch, sized up or down as the roadmap changes.

    Monthly · 30 days notice

  3. Staff augmentation

    QalbIT engineers placed inside your own Saudi team, in your tools and your code reviews, for when you have a tech lead and need capacity.

    Per engineer · per month

Technologies


Four layers, chosen so the fifth engineer can still read them.

The same stack across all five cities, so a team built for Riyadh can pick up work in Dammam without relearning the architecture.

  1. 01

    Interface

    What your users touch

    Screens that work in Arabic and English, laid out right to left where they need to be, for staff who use them all day.

  2. 02

    Application

    Where the rules live

    VAT, approval and invoice rules kept in one place, readable by whoever maintains them next.

  3. 03

    Data

    What you cannot afford to lose

    What may leave the Kingdom and what must stay is decided before the first table exists.

  4. 04

    Delivery

    How it reaches production

    Staged releases, each with a rollback, timed around your Sunday-to-Thursday week.

Already on an ERP, an accounting product or an e-invoicing provider? We connect to it first, and suggest replacing it only when the connection costs more than the rebuild.

Review my stack →

Start here


Discuss your Saudi Arabia project.

Name the city, the system you want replaced, and whether a ZATCA wave date or a PDPL review is setting your timeline. You get a written scope, an architecture recommendation and a price range within 48 hours.

  • A written scope with the exclusions listed
  • An architecture recommendation, not a sales deck
  • The name of the engineer who would lead it
  • Free, and yours to keep either way

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

FAQs · Saudi Arabia


Frequently asked questions about working with QalbIT in Saudi Arabia

How one remote team covers five cities, and the regulatory questions that come up regardless of which one you are in.

Ask us directly →
No. QalbIT has no office and no registered entity in Saudi Arabia, on any of the five city pages this hub links to. Delivery runs remotely from our Ahmedabad office, on Saudi working hours, and we say so before any conversation about scope or price.
No. One scope, one contract and one team cover work across Riyadh, Jeddah, Medina, Mecca and Dammam. If your operation spans more than one city we combine the requirements into a single engagement rather than pricing each location separately.
Start with whichever city carries most of your operational headcount, then tell us about the rest on the discovery call. The five pages describe the sector angle we lead with in each city; the underlying engineering team and process are the same wherever the work sits.
Yes, once the data-protection position is set out properly. Under PDPL you remain the controller and we act as processor. Where personal data needs to leave the Kingdom, Article 29 permits it with approved safeguards, including Saudi Standard Contractual Clauses, agreed in writing before the build starts.
Yes, and the requirement does not change by city. Phase 2 requires direct integration with the Fatoora platform: UBL 2.1 XML, a UUID, a cryptographic stamp and a QR code, with standard invoices cleared before sending and simplified invoices reported afterwards. We confirm your specific wave and deadline directly with you rather than assuming one.
Phase 2 is the integration phase of Saudi e-invoicing. Phase 1, from December 2021, made invoices electronic; Phase 2 connects the system that issues them to ZATCA’s Fatoora platform, rolled out in waves by revenue. If your ERP raises your tax invoices and ZATCA has notified you of a wave, your ERP needs it. ZATCA notifies the businesses in each wave itself, at least six months before their integration date. If your invoices come from a separate accounting system or an invoicing service, that system is the one that must comply, and your ERP needs only a clean connection to it.
The whole Kingdom sits at UTC+3, the same offset Kuwait keeps, and it is the offset our Ahmedabad team already works Gulf hours for. That means four of your five working days overlap ours in full rather than in a narrow window, and the rest is covered by written updates, whichever of the five cities the work is in.
The product itself can ship fully bilingual, with correct right-to-left layout and Arabic invoice output. Day-to-day delivery, calls, documentation and written updates run in English across all five cities. If your stakeholder group needs Arabic-language delivery throughout, we will say so plainly rather than take on work we cannot serve well.
No, not for private-sector work. Your company needs its own registration to trade, but a vendor working from outside the Kingdom does not normally need a Saudi one: you can contract a software firm registered abroad as you would any overseas supplier. With us, your contract would be with QalbIT Infotech Pvt Ltd, which is registered in India. The vendor’s Saudi registration becomes a condition in government work, covered in the Etimad answer below, and some large buyers’ own vendor rules ask for one too. Payments to a supplier outside the Kingdom can attract Saudi withholding tax, so ask your tax adviser how it applies.
Not directly, in any city. Etimad tenders typically require a Saudi commercial registration held by the contracting party, which we do not have. Tell us at the first call if your procurement runs through Etimad and we will tell you immediately whether a workable structure exists.
It depends on scope, integration count and how much ZATCA and PDPL work the system needs, not on which of the five cities it runs in. We scope the first phase before naming a number, and the estimate is fixed once that scope is agreed.
It can be, on the engineering alone, but the hourly rate is not the whole cost. A vendor outside the Kingdom adds one piece of work a local firm does not: a PDPL transfer agreement, with safeguards, before any personal data reaches the team. And for government work through Etimad, it usually cannot be the contracting party at all. We will not put a Saudi rate beside ours without a source for it, and we have none. The fair test is two quotes against the same written scope, with the PDPL and hosting work included in both.
You do, in full, in your own repository, once project payments are complete. That is true whether the work was for a Riyadh headquarters, a Dammam plant or an operation spanning several of the five cities. No licence, no per-seat fee, and no restriction on hiring another team afterwards.

Cities we serve


Riyadh: HQ ERP and CRM · Jeddah: Red Sea trade · Medina: hospitality · Mecca: Hajj and Umrah · Dammam: Eastern Province industry

Next step


Start your Saudi Arabia project.

Two lines about your project and which city it is in is enough. You get a written scope, timeline and price range within 48 hours: free, and yours either way.