A software team in Giza that ships its own product
This is home. We are based in Giza and work with Egyptian businesses on web applications, mobile apps, internal systems and SaaS products — the same engineering we put into our own product, with the advantage that we can sit in the same room.
Egyptian businesses are digitising the hard parts now
The easy digitisation already happened: a website, a page on social media, maybe an accounting package. What is left is the difficult half — the operational process still running on a spreadsheet, a WhatsApp group and one person’s memory.
That work is unglamorous and genuinely valuable. It is also where a badly chosen supplier does the most damage: a system built to a fixed price by a team that will not be reachable in a year, with data nobody else can get out.
We build these systems the way we built our own product, and we hand them over so completely that you could replace us. Local rates, local language, and the option of meeting in person when a conversation needs a whiteboard.
What working with us actually looks like
Every item here is something we built and still run ourselves — not a service line we have only read about.
You can actually meet us
We are in Giza. For a project that needs a room, a whiteboard and the people who do the work, that is an option — not a video call standing in for one.
Arabic as the working language
Requirements, documentation and training in Arabic where that suits your team, and interfaces written in Arabic rather than translated into it.
Local payment integration
Card and mobile-wallet checkout through Paymob — the Intention API integration running in production on our own product, webhook verification included, not a first attempt on your project.
Replacing the spreadsheet
Attendance, scheduling and payroll — the operational systems most Egyptian businesses still run on a shared file, rebuilt the way they are in our own product: role-based permissions and an audit log of who changed what.
Products built for export
If you sell beyond Egypt, multi-language, time-zone and currency handling are architecture decisions, not later features: our own product ships twelve locales with full right-to-left, stores a per-user time zone, and denominates every stored amount in an explicit currency.
Realistic infrastructure
Cloud bills arrive in dollars and Egyptian budgets do not, so the size of the machine is a real design decision here — usually one well-run server rather than a platform priced for someone else's scale. Monitoring, encrypted off-site backups and a rollback path, in your accounts.
Your team trained on it
Handover includes sitting with the people who will use it and the people who will run it, until neither group needs us on speed dial.
Yours, including the data
Source, infrastructure, accounts and documentation. No arrangement where your data is easier for us to reach than for you.
How we start with an Egyptian client
The same sequence on every engagement, whatever the stack.
1. A conversation, in person if useful
For internal systems especially, an hour watching the real process is worth more than a week of written requirements.
2. A written scope and estimate
In Arabic or English. What we build first, what waits, and what it costs — before any commitment.
3. Build, train, hand over
Delivered into your accounts with your team trained to operate it, not dependent on ours.
Straight answers
The questions that actually come up on a first call.
Giza. For a serious engagement we are happy to meet in person, and for internal-systems work we usually recommend it at least once — watching the real process in the room surfaces requirements no document captures.
Yes, provided the project makes sense. The test is whether custom software is the right answer at all: if an existing product plus a small integration would serve you, we will tell you that rather than quote a build.
Yes. Our own product runs a Paymob integration in production: the Intention API flow, HMAC-verified webhooks, and idempotency keys with claim-before-charge so a lost or replayed response cannot charge twice. Other local gateways follow the same patterns.
That is a normal and healthy outcome, and the way we build is meant to allow it: a conventional stack you can hire for, documentation a new developer can start from, and everything already in your accounts.
Let’s talk about what you are building
Describe the problem — a paragraph is enough to start. You get a written scope back, and an honest answer if the right move is to buy something instead.
Every project starts with a scoping conversation and a written estimate before any code is written. No retainer required to talk.