How we work
Our Process
No three-month silence between the kick-off and a reveal. You get a weekly demo of the real thing, because working software is the only honest progress report.
The shape of an engagement
Four stages, each of which ends in something you can hold: a document, a screen, a release, a number. You can stop after any of them and still own everything produced up to that point.
Discover
A paid two-day workshop that produces a scope, a real estimate and a recommendation — including "do not build this" where that is the answer.
You leave withA written scope and a priced plan you own, whoever builds it
Design
Flows and interfaces tested with real users before anything is built, in Arabic and English from the first screen.
You leave withSigned-off screens in both languages, and the architecture behind them
Build
Two-week cycles with a demo at the end of each. Small team, senior engineers, and the architecture reviewed before a line is written.
You leave withWorking software every fortnight, in your repository from the first commit
Grow
Launch is the start. The same team runs the marketing, measures against revenue, and stays on an SLA afterwards.
You leave withMonthly numbers tied to revenue, and a response time in writing
The cadence
What a fortnight actually looks like
The build stage is not one long stretch with a reveal at the end. It is the same two weeks repeated, and the last day of each one feeds the first day of the next — which is why a correction you raise in a demo lands in the following cycle rather than in a change request after launch.
Plan
We agree what the fortnight contains, in writing, before it starts. Nothing enters a cycle mid-flight.
Build
Senior engineers only, reviewing each other. Progress is visible in your portal continuously, not summarised weekly.
Demo
Working software, on a real environment, that you use yourself. Not a slide about what was done.
Adjust
What you said in the demo changes the next plan. This is the step that makes the loop worth drawing.
Where it starts
Two days that decide whether the rest happens
Discovery is paid, and it is the only part of an engagement you can buy without committing to the build. Two days with the people who own the problem, then a written document — which is yours whoever ends up building the thing, including nobody.
- A written scope, in language your finance team can read
- A real estimate, priced per phase, with what is excluded stated
- An architecture recommendation — including "do not build this"
Our side
What you get from us, every time
A demo at the end of every cycle
Software you operate yourself, not a status report. If there is nothing to show, we say that and explain why.
A portal, so nothing needs a meeting
What shipped, what is next, what is blocked and every invoice — visible without asking anyone.
Estimates we stand behind
Priced per phase, with an explicit list of what is not included. When we are wrong about an estimate, we say so early rather than at the invoice.
A named person to escalate to
You have the direct contact of the person accountable for the work, not a shared inbox.
Your side
What we need from you for this to work
Someone who can decide
One person with the authority to settle a question in the room. Decisions that need a committee are the single biggest cause of a slipped date.
Access to the people doing the work
An hour with the person who actually runs the process we are automating is worth a week of specification.
Feedback inside the cycle
Reactions to a demo within a few days, while the code is still warm. Feedback three cycles later costs several times more to act on.
The real numbers
Revenue, margin, conversion and churn as they are, not as the board deck has them. We cannot optimise against a figure we cannot see.
Stage by stage
1. Discovery
We start by understanding the business outcome you are buying, not the feature list. One or two sessions with the people who own the problem, then a written summary of what we heard — so any misunderstanding surfaces before it costs anything.
2. Scope and estimate
You get a phased scope with a fixed price per phase, and an explicit list of what is not included. Phases are sized so you can stop after any one of them and still have something usable.
3. Design
Interface design and technical architecture happen together, reviewed with you before a line of production code is written. Changing a screen at this stage costs hours; changing it after launch costs weeks.
4. Build
Two-week iterations, each ending in something you can actually click. You see progress in your client portal continuously — no status meetings required to find out where things stand.
5. Launch
We handle deployment, monitoring, analytics and handover documentation. You own the code and the infrastructure from day one.
6. Growth
This is where most agencies leave. The same team then runs SEO, campaigns and conversion work against the product they built — so the people optimising it already understand how it works.
Last updated September 7, 2026
Start with the discovery workshop
Two days, paid, and it ends in a scope and an estimate you own — including the recommendation not to build it, where that is the honest answer.