A holding company that builds
Aakam is a technology holding company. We build SaaS products, we own them, we operate them, and we grow the ones that earn it. Each is a product rather than a feature — and each is built to understand a business, find what needs to happen inside it, and act on it, rather than to sit and wait for an instruction.
We build more than one because each of these problems is deep enough to deserve full attention. A dedicated team, product and roadmap can go further into one problem than a shared roadmap can go into several — so the portfolio is how we buy depth, not how we avoid building things together.
What connects the products is not a shared backend — there is none — but a shared conviction: that the value a business earns from customers it already has is the value most worth engineering for, and that the impact has to be provable in the customer’s own numbers rather than in our deck.
The portfolio starts in commerce because the problems there are sharp, measurable and already solved by products running today. The problems themselves are not particular to commerce, and neither is where the portfolio goes next — but a sector does not become ours without a product working in it and proof we can publish.
Personalize
Retain
Measure
A small team running three products in production. That means a wider scope of responsibility than usual, a shorter distance to a decision, and work that reaches real customers in days rather than quarters.
Today that work is bounded by the rules and reviews of the platforms the products are deployed on — a real engineering constraint that teaches more discipline than a blank canvas does. Product and content are written in Arabic first, not translated into it.
A problem worth solving deserves a product. Someone has to build it.
Three founders, three products running in production, and no layer in between. The distance from noticing a problem to shipping against it is short because the people at both ends are the same people.
Four things we do the same way every time.
Four problems that belong to any business with customers
A customer decides, comes back or does not, gets measured or does not, and is worth going back to. Those things happen in a restaurant, a clinic and a subscription service as surely as in a store — and each is a different problem needing a different product. Commerce is where we started, not the shape of the question.
A problem deep enough to deserve a product
Three beliefs govern what gets built. A problem worth solving rewards depth, and depth is what a dedicated product can give it. Growth from a customer a business already has is the only growth that compounds. And impact has to be provable in the customer’s own numbers.
Where the work already happens, and from the server
A product should install where its customer already works rather than beside it. Today that means approved applications inside the commerce platforms the products run on: installed from the platform’s own app store, reading its events under scoped permissions, with no custom development. And measurement is captured at the server rather than the browser, so a blocker never decides what gets counted.
More products, on evidence rather than intent
The portfolio grows when a problem earns a company, not when a category looks empty. That is slower than announcing a roadmap and it is the point: a sector does not become ours without a product working in it and proof we can publish.
One meaningful problem deserves its own product
The rules we do not break
- Proof gates claims — no number without a source, no capability that is not built
- Omission over pretence — a module without content does not render
- Focus beats breadth — each product earns its place alone, or does not exist
A small team,three products in production
We do not list roles that do not exist. There are no advertised openings right now — if your work intersects with how we build, write to us about what you have built.
Two tracks, each going where it should
We do not show a contact form before a real destination exists for it.