Mission
Not software that gets deployed and forgotten. Not software that solves a demo problem. Software that teams rely on, customers pay for without question, and operators are proud to run.
"We build operating companies, not products.— The Dal Dom Operating Principle
We understand markets by operating in them, not studying them.
We ship software that we depend on — and then we sell access to it."
In Practice
Maktabi wasn't built because someone read a market report. It was built because the people who built it managed properties, collected rent, handled maintenance, and negotiated with agents — and found every existing tool inadequate. The product came from operations, not observations.
Every Dal Dom product is a live, revenue-generating, customer-serving software company. We deal with production incidents, customer complaints, billing edge cases, and regulatory changes. This forces a quality standard that no freelance brief or sprint board can enforce. Pain is the best product manager.
Multi-tenancy, audit trails, proper queue architecture, ZATCA-compliant billing, Arabic-first design — these are expensive to build correctly and nearly impossible to retrofit. We pay the cost upfront. The products that result are harder to compete with, not easier to build.
Dal Dom is not a studio for hire. We don't build and hand over. When we engage externally, we structure it as a partnership, a joint venture, or a clearly scoped service — and we remain transparent about which it is. Our model requires us to be selective. We take fewer bets and go deeper on each.
Our software execution certification product, SATE, exists because we believe software must prove what it does — not describe it. We apply that doctrine internally. Our AI systems don't guess. Our APIs don't hallucinate. Our billing doesn't round incorrectly. When we say it works, we mean we have evidence.
The Saudi market has a specific regulatory environment, a specific language, a specific payment infrastructure, a specific trust culture, and a specific relationship between technology and business. We don't impose another market's assumptions. We design for what's actually in front of us.
What We Won't Do
Entering a new vertical requires operational experience in it first. We don't start with the code. We start with the problem.
Our products are not configurable professional services. They are opinionated systems built on a clear model of how the domain should work.
Working is the baseline. Predictable, provable, and operable at scale — that's the bar. We hold our own systems to the same standard we sell in SATE.
We don't optimize for vanity growth, DAU theater, or pitch-deck narratives. We optimize for product quality, customer retention, and long-term operational health.
Arabic-first means the product is designed in Arabic, tested in Arabic, and validated by Arabic-speaking users — not translated from English and declared done.
Why a holding structure? Why build and own rather than consult? What is the logic that unifies all four products?