Skip to content
Colour theme

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.

Schedule a discovery call →See how we work

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.

Every engagement in the Kingdom carries the same regulatory ground regardless of city: ZATCA e-invoicing, PDPL data protection and a written scope agreed before anyone prices the work.

  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

    Fatoora integration built to the Phase 2 requirement: UBL 2.1 XML, a cryptographic stamp and a QR code, for whichever wave your revenue falls into.

    Phase 2 · Fatoora

  3. PDPL-ready data handling

    Controller and processor roles set out in writing, with approved safeguards for any personal data that needs to leave the Kingdom.

    Article 29 · SCCs

  4. CRM and reporting tools

    Systems shaped around how a Saudi sales or operations team actually works, not a generic pipeline bent to fit.

    Custom fields · live data

  5. Cloud and DevOps

    AWS infrastructure, staged releases and a rollback path, so a system five cities depend on does not run on one laptop.

    AWS · Docker · CI/CD

  6. Dedicated product teams

    A standing pod that becomes the engineering function behind a Saudi product, 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

    Saudi Arabia and Kuwait share the same UTC+3 offset our Ahmedabad team already keeps Gulf hours for, so most of your working day overlaps ours in real time.

  • We say what we are not

    No Saudi office, no local entity, stated upfront. What you get instead is a written scope, a named engineer and a straight answer on ZATCA and PDPL before anyone prices the work.

  • You keep the code and the access

    The repository lives in your account from day one. If the engagement ends, you keep a working system, not a dependency on us.

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 the current workaround and what a first release needs to replace, wherever in the Kingdom the work sits.

    Week 1

  2. Design & validate

    A clickable prototype reviewed with the people who will use it, before we write production code.

    Weeks 2-3

  3. Build in sprints

    Working software every two weeks, demoed live rather than reported in a status deck.

    Sprint by sprint

  4. Launch & stabilise

    A rollout plan, data migration from whatever it replaces, and a rollback path.

    Launch week

  5. Improve & extend

    Monitoring and the next slice of roadmap once the system carries real operational data.

    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

    A defined first release with a written scope and a fixed set of exclusions.

    Fixed price · 6-14 weeks

  2. Dedicated product team

    A standing team that becomes the engineering function behind your systems, scaling with the roadmap.

    Monthly · 30 days notice

  3. Staff augmentation

    Engineers who join your existing team and process directly.

    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

    Dashboards and portals built for people who use them every day, not once.

  2. 02

    Application

    Where the rules live

    Business logic written so the next engineer can read it without you in the room.

  3. 03

    Data

    What you cannot afford to lose

    Backups and access control designed before the first row is written.

  4. 04

    Delivery

    How it reaches production

    Staged releases and a rollback path on every deploy.

Already running something else? We extend what works rather than rewriting it for the sake of a stack preference, whichever city the system runs in.

Review my stack →

Case studies

Case studies closest to Saudi engagements.

Booking and payments at volume, and a centralised scheduling system replacing spreadsheets: production work closest in shape to what the five Saudi cities need. Full write-ups are available on request.

    Start here

    Discuss your Saudi Arabia project.

    Tell us which city, what the system needs to replace and 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.
    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 a full Sunday-to-Thursday working day in common rather than a narrow overlap window, regardless of which 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.
    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.
    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

    Each city page carries its own sector detail and its own systems. This is the short version of what makes each one different.

    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.

    Request a free consultation

    Keep exploring