Services
What we build.
Most projects use three or four of these at once. A mobile app needs a backend, a brand, and somewhere to send the invoices. You brief all of it once, to the same people.
How an engagement runs
Four stages, whichever service you start with. You finish each one holding something real.
Scope
What we are building, when it is needed, and what we are leaving out on purpose. You get a written list and a date before any code exists.
Prototype
Built in real code, so you click the real thing instead of approving a picture of it.
Build
The long stage. It reaches you piece by piece, every week, rather than in one reveal at the end.
Ship & maintain
We launch, watch what people actually do with it, and stay on afterwards. Everything we have built, we still look after.
How it is priced
Scoping comes first. We work out what you need, then send a fixed price for a fixed scope, or a monthly rate if the work is ongoing and its shape will keep changing. You see the number before anything starts.
If you change your mind halfway, we tell you what it means in time and money before we do it. Code, accounts, domain and data are yours from the first week, and they stay yours if you ever walk away.
first
Questions, answered
The things people ask before we start.
It depends on scope, so we work the scope out first, at no cost: one or two calls and a written list of what we are building. Then you get a fixed price for that list, or a monthly rate if the work is ongoing. No number is a surprise, and nothing starts before you have agreed to one.
Either. Some clients hand over the whole thing, from the brand through to the app on the store. Others already have a designer, or an existing system, and need one part built properly. We are used to arriving in the middle of something and reading someone else's code.
The people you speak to. The developer who joins your first call is the one writing the code, and the designer in that call is the one drawing the screens. Nothing is passed to a junior after you sign, because there is no second tier to pass it to.
Most of our work is remote, and we run projects across time zones as a matter of routine. Calls in your working hours, written updates every week so nothing depends on catching each other live, and everything in English or Arabic.
Scope first, always. A written list of what we are building and when, before any code. Then a fixed scope or a monthly agreement, depending on the work. If you want to change something, we tell you what it means before we do it.
Less than you think. A rough description of the problem, one person on your side who can make decisions, and whatever already exists: a spreadsheet, an old system, a competitor you like. You do not need a specification. Writing that is our job, and it is the first thing we do.
Yes. Launch is when the real users arrive, not when the work stops. Nothing we have shipped has been handed off and forgotten, and when you need a change you message the developer who wrote it rather than opening a ticket. If you would rather move it to your own team one day, it is built so you can.
All of it. Code, accounts, data, in your name from the first week rather than handed over at the end. Everything is documented and written to be picked up by another developer, and we will help with the move if you ever make one.
Two working days for a new project, from a person who has read it properly. Faster once we are working together, and the WhatsApp number on the contact page reaches someone the same day.
Pick a starting point
Not sure which one you need?
Describe the goal and we will tell you what it takes and which parts you can skip.
Start a project→