Decide early, then move fast.
Every project runs through the same four stages. The first two settle what we are building; the last two build it, prove it and hand it to you.
Riyadh, Saudi Arabia
From first call to hand-over
Call
We begin with the outcome you want, the people it serves, the systems it has to touch and the date it has to be live. Bring whatever you already have: a brief, a spreadsheet, a screenshot of the current process. The aim of this stage is a shared picture of the goal.
You receive
- A first read on scope and timing
- A map of the systems and people the work involves
- The open questions to settle before scoping
Scope
The goal goes onto one page, in plain language, with the constraint that shapes it. We then mark what belongs in this phase, what is held for a later one, and what would change the price. That boundary is what lets the build move quickly.
You receive
- A one-page statement of the goal
- A written proposal with deliverables, timeline and fees
- A list of what is held for a later phase
Build
The data model and the access rules are built before any screen, because they are the costly part to change once real records exist. Screens come next, on top of them. Each feature is proven twice: by automated tests, then by a live run with your real systems and credentials.
You receive
- A data model and access rules, written down
- A test suite, including the cases each rule is meant to stop
- A live run against your own systems before launch
Launch and hand over
We launch into your environment and stay on while it settles in. Then everything moves to you: the code, the migrations, the documentation and the reasoning behind each decision, so your team, or any team you choose, can carry it forward.
You receive
- Source code, schema and migrations
- Technical and administrator documentation
- Training for the people who will run it
- A support window, with maintenance available on request
How we run a project
The costly choices come first
Data, access and scope are decided while every option is still open. Everything after that moves faster because of it.
Raised the day we see it
A risk, a gap in the brief or a cheaper route is flagged as soon as we spot it, so it becomes a decision we make together.
One reading of every requirement
When a requirement can be read two ways, we choose one, write it down and get your confirmation before building it.
Proven where it will live
A feature counts as finished once it works with your real systems, your real data and the limits you have set.
Tell us what you want to build.
One email is enough to start. We reply within two working days with a clear read on scope and timing.