About
An engineering studio that turned toward AI, not an AI startup that learned to engineer.
Pountech has been building and running production software for over a decade — marketplaces, mobile apps, learning platforms, logistics tooling. The work that matters now sits on top of that, and needs the same discipline underneath.
What we believe
The model is the easy part.
Anyone can get a convincing demo out of a frontier model in an afternoon. The distance between that demo and something a business can depend on is where projects die — and that distance is made of ordinary software engineering: access control, error handling, cost ceilings, observability, and a plan for the times the model is confidently wrong.
We come at AI from that side. Our instinct is to ask what happens at three in the morning when it fails, before asking which model to use.
It also means we will tell you when AI is the wrong answer. A rule engine, a better query, or a redesigned form is often cheaper, faster and more reliable — and saying so costs us a project but keeps a client.
Working with the Gulf
Close enough to be in the room. Far enough to be affordable.
Our clients are in the UAE, Saudi Arabia, Qatar, Kuwait, Bahrain and Oman. We are engineered out of Alexandria — a two-hour time difference and a three-hour flight away.
- Working week Sunday to Thursday, on Gulf hours — not a European calendar with a Gulf phone number.
- Language Arabic and English throughout, in the product and in the room. Arabic-language AI is a first-class requirement here, not a translation task at the end.
- Data residency We architect for in-region hosting from the start, and will tell you plainly which parts of a design send data outside the region.
- On site We travel for discovery and for the milestones that need a room. The rest runs remote, which is what keeps the cost sensible.
- Engagement Fixed-price discovery, then a build contract with a named team. No open-ended retainers.
- Ownership Your repository, your cloud account, your models. We hand over documentation your team can actually follow.
How we work
Small team, named people, one project at a time.
You get the engineers who did the discovery, not a sales team followed by a handover to people you have never met. The team is small enough that everyone on it has read your codebase.
We work in short cycles with something running at the end of each one. If a direction is not working, we would rather find out in week two than in month five — and we would rather tell you than quietly absorb it.
Nothing we build is designed to keep you dependent on us. The end state of a good engagement is your team running the system without calling us.
Next step
Start with a conversation, not a brief.
You do not need a specification to talk to us. Describe what is slow, manual, or buried in documents, and we will work out the rest together.