Cairo · Software studio · Est. 2024Cairo · Est. 2024
Cubitan old unit of length taken from the forearm — so no two were ever quite the same
We measurebefore we build.
Two of us, in Cairo. We never start from a template, because a template has already decided the shape of your business before anyone asked what it is. We start with meetings — then build something cut to fit.
Two of us, in Cairo. We never start from a template — a template has already decided the shape of your business before anyone asked what it is.
01 — Selected work
Three projects. Three different structures.
A café with a yard, a furniture workshop and a student club do not want the same website. Nothing structural is shared between these three. That is the entire point, and the evidence is below.
Yard Club
A week-first site for a café, bike workshop and event yard in Maadi as-Sarayat. Replaced a WordPress site that read like a bike shop.
Read the case study
Art of Nature
A gallery, deliberately not a shop. We talked the client out of e-commerce across three meetings and built an inquiry path instead.
Read the case study
Enactus SAMS
A site and a management platform for the Enactus chapter at Sadat Academy in Maadi. Recruitment, a year’s project and six teams — run by a board that changes every year.
Read the case study
02 — The evidence
Same studio. No two of these share a skeleton.
Yard Club
Organising principle
The week
Events are the spine. The café menu sits a level down, because nobody drives to Maadi for a menu — they come for what is on.
What it did not need
A CMS. Two people update it weekly; an admin panel would have been furniture.
Art of Nature
Organising principle
Material & room
Every piece is a one-off, so the site reads as a gallery indexed by room and timber — not a catalogue with prices it cannot honour.
What it did not need
A cart. It would have produced orders the workshop must refuse.
Enactus SAMS
Organising principle
The season
Everything follows the academic year: recruitment opens and closes, one project is told in full, and the board that runs it all hands over at the end.
What it did not need
A framework on the public page. It is read on phones over campus data, so it ships as plain HTML.
If we had one skeleton, you would be looking at three versions of the same website right now.
Read the case studies03 — How it goes
Meetings first. Always.
- 01
Listening
Two or three sessions before anything is designed. How the business actually runs, who updates what, what happens on a Friday night.
- 02
Shaping
Structure before pixels. We agree what the spine of the thing is, and what we are deliberately leaving out. This is where we argue.
- 03
Building
In the open, in short passes you can look at. Stack chosen per project — the lightest thing that solves it, never the fashionable one.
- 04
Handing over
You own the code and the accounts. We stay on for hosting and maintenance if you want us to, and you can leave whenever.
Tell us how your business actually works.
First meeting costs nothing and has no deck in it. Bring the messy version — the spreadsheet, the WhatsApp group, the thing you keep meaning to fix.