Our strengths

The previous page argued why we beat the alternatives. This one is the inventory: what we hold today, so you can check it against what you need.

Experience you are actually buying

Every person who touches your work has run delivery before. There is no delivery pyramid here. The person who scopes your project is the person who builds it, and the person who answers the phone afterwards.

From the large firms	From small companies and our own products
Tests before code, a named human reviewing every change, documentation as a deliverable	How to cut a requirement down until it can actually ship in two weeks
Security review, release control, and what a regulated client asks for	How much of a specification is genuinely load-bearing, and how much is decoration
Systems used by thousands of people every day	Owning the thing at eleven at night, because there is nobody else

And you can check it rather than take it on trust. We built and own a booking and business-management platform, automation across CRM, analytics, payments and administration, and a real-time transcription and meeting-analysis product. Ask to open any of them in the first meeting.

We build with AI agents, under review

Our engineers work with AI agents through a defined method. It is the reason a one-month delivery is realistic and a fixed price is safe for us to quote.

It is also the question your IT adviser should ask us, so here are the answers before you ask.

Does AI write the code that ships?: AI drafts. A named senior engineer reads, tests and signs every change. Nothing reaches you without that signature.
Is it secure?: Automated security scanning runs on every change, and a human reviews the result. We will show you the method document before you sign anything.
Is it maintainable by our own people afterwards?: That is what the test suite and the documentation are for, and both are contractual deliverables rather than extras.
Who owns the result?: You do, in full.
Does our data go into a model?: No. We agree the data boundary in writing before we start, and we can name exactly which tools touch what.
Who is accountable?: A person, by name, on every release. A tool does not sign anything.

We will hand this method to your security reviewer as a document. Most firms using the same tooling cannot, and that difference is worth more to you than the speed.

Bilingual delivery, not bilingual marketing

Arabic and English in meetings, in written scopes, in the documentation, and in the software itself — including proper right-to-left interfaces built as right-to-left rather than mirrored at the end.

Anyone can translate a website. The test is whether the system your staff use every day reads correctly in Arabic on a phone, and whether the handover document your next engineer reads is in a language they work in.

A Saudi-owned company you can hold accountable

Founded and owned by Sami Alhamadah, a Saudi national. Registered in Riyadh, CR 7054801407. Saudi contract and jurisdiction, SAR invoicing, meetings in person, Sunday to Thursday.

This matters more than it sounds. A dispute with an offshore supplier is a letter into a void. A dispute with a company registered down the road is a conversation, and both sides know it, which is why it rarely gets that far.

We know the Saudi systems you have to connect to

Most integration pain in this market is not exotic. It is the same handful of national systems and the same handful of business platforms.

ZATCA e-invoicing (Fatoora) — Phase 2 clearance and reporting. Wave 25 was announced on 24 July 2026 with a threshold of SAR 187,500 and a deadline of 1 February 2027, so a further group of companies is now in scope.
Nafath and Absher — national sign-in for portals and customer-facing services.
Qiwa and Mudad — employment and payroll workflows.
ERP and finance — NetSuite, Dynamics 365, Odoo, SAP, and the local accounting packages mid-sized companies actually run.
PDPL obligations in practice — where personal data sits, who can reach it, and what crosses the border. Enforced, with penalties up to SAR 5,000,000 per violation.

Payments

Mada
SADAD · invoice-based
STC Pay
Apple Pay
HyperPay
Moyasar
PayTabs
Tap

Two things worth knowing before you choose. Your gateway must hold a SAMA licence — you do not need one, it does, and HyperPay, Moyasar, PayTabs and Tap all do. And Mada interchange is materially cheaper than international cards, so on a Saudi customer base the default card routing is worth arguing about.

Reaching people

WhatsApp Business API
Unifonic
SMS
National Address · SPL

Email is a rounding error in this market. If a message matters it arrives on WhatsApp, in Arabic, from a number the recipient recognises.

Where your software is allowed to run

In most markets hosting is a technical preference. Here it is decided first, by PDPL and by whatever your own client contracts say about where data may sit. So it is worth knowing what is actually available inside the Kingdom, as opposed to announced.

Region	Status	What that means for you
Google Cloud — Dammam	Live since November 2023	Our usual default. Full residency, and the AI services are in-region
Oracle Cloud — Jeddah	Live since 2020	The longest-established. Sensible where you already run Oracle
Oracle Cloud — Riyadh	Live since October 2024	Hosted in stc’s Center3, which some contracts specifically ask for
Microsoft Azure — Saudi Arabia East	Announced for Q4 2026	Eastern Province, three availability zones. Not a choice you can make today
AWS — Saudi region	Announced, not yet generally available	Same. We will not design around a date somebody else controls
stc, Sahara, NourNet, Mobily	Live	Local operators. Sometimes required by name in a government or defence contract

If a tender or a client contract names a provider, that decides it. If nothing names one, we will recommend the cheapest region that satisfies the residency requirement and tell you what it costs to move later.

Engineering practice that survives our departure

The measure of a supplier is what the system looks like a year after they stop working on it.

Source code in your repository, in your organisation account, from week one.
Automated tests, with the coverage level named in the contract.
Deployment that runs from a script, not from somebody’s laptop.
Cloud accounts in your name and billed to you.
Documentation aimed at the next engineer, in Arabic and English.
A written handover, and a free day of briefing for whoever comes after us.

Small enough to answer, big enough to finish

We are a small team, and we would rather say so than dress it up. We cannot run an unlimited number of projects at once, and if you ask when we could start we will give you the real date rather than the one you want.

What you get in exchange: the owner’s number, a reply the same working day, and a decision without a committee. When something goes wrong at 6pm on a Wednesday, there is nobody for us to escalate to either. That is a discipline of its own.

What we do not have yet

Listed here so that nobody has to discover it during due diligence.

Delivered client projects: None yet. Registered July 2026
Client references: None yet
ISO 27001 and similar: Not held
Local content certificate: Not held. It matters for government tenders, which are not our market yet
Delivery capacity: Limited, and we will tell you the real start date

If one of these is a hard requirement on your side, tell us in the first meeting. We will either say when we expect to have it, or tell you to use somebody else.