How we work
Five stages, one contract
Scope, prototype, build, launch, run — the same shape on every project, quoted against your scope and run to your deadline.
- Brief to a fixed quote
- 48hBrief to a fixed quote
- Demo and check-in cadence
- Your callDemo and check-in cadence
- Code and accounts you own
- 100%Code and accounts you own
The engagement model
The shape of every build
Each stage ends with something you can open, read or click — and a decision that is yours to make.
01
Scope
We turn a rough idea into a scope with a number against it.
02
Prototype
You click the thing before we write production code.
03
Build
Short cycles, each one ending in something you can hold.
04
Launch
Performance, accessibility and security work, then go-live.
05
Run
Thirty days of warranty, then a care plan if you want one.
Stage by stage
What each stage actually produces
Stage 01
Scope
Before anything is priced
We turn a rough idea into a scope with a number against it.
It ends in a fixed quote, or an honest reason not to build.
You end up holding
- Scoped brief
- Architecture sketch
- Fixed quote
- In and out of scope
Your call — Go ahead, or keep the brief and walk.
Stage 02
Prototype
Before production code
You click the thing before we write production code.
Disagreements are cheap on a prototype and expensive in a codebase.
You end up holding
- Clickable prototype
- Acceptance criteria per screen
- Content model
- Arabic layout check
Your call — Sign off screen by screen, or change it.
Stage 03
Build
On your cadence
Short cycles, each one ending in something you can hold.
You pick when the demo lands and how often it comes round; we agree the cycle's scope in writing before it starts.
You end up holding
- Staging build
- Written changelog
- Open defect list
- Test coverage
Your call — Reorder the backlog at the top of any cycle.
Stage 04
Launch
On a date you choose
Performance, accessibility and security work, then go-live.
Nothing ships without a rehearsed rollback path, and nothing ships on a day nobody is around to watch it.
You end up holding
- Runbook
- Accounts and DNS handed over
- Recorded training
- Launch checklist
Your call — You pick the date and the rollback line.
Stage 05
Run
After go-live
Thirty days of warranty, then a care plan if you want one.
Monitoring, patches and the next release, on the same rhythm the build ran to.
You end up holding
- 30-day warranty
- Monthly report
- Agreed response times
- Quarterly roadmap
Your call — Renew, resize or cancel with 30 days' notice.
Quotation
How we price it
Every build is quoted on its own scope. You pick the pieces you need, tell us the deadline you are working to, and one itemised quotation comes back — no bands to guess between and nothing to ask twice for.
- Free to ask for, always
- Itemised line by line, in writing
- Shaped to your deadline and budget
- Held for thirty days once sent
What we quote against
Landing page
One page, one goal, copy and analytics included.
Corporate website
Five to fifteen pages, CMS, SEO structure, bilingual-ready.
E-commerce
Catalogue, UAE payment rails, delivery and VAT handling.
Custom system / CRM
Roles, workflows, integrations, reporting, migration.
Mobile app
iOS and Android, backend, store submission.
AI implementation
Data pipeline, retrieval, evaluation, human review loop.
Support & care
Monitoring, patching, small changes, agreed response times.
Pick as many as apply — most builds are two or three of these, and the quotation prices them as one scope rather than as separate jobs.
Quoted separately
- Third-party licences and subscriptions
- Content writing, translation and data entry
- Paid media, ad spend and creative production
- Hardware, on-site cabling and network gear
No price on this page
Because we would rather quote your scope than a category you fall into.
Tick what you need, say how fast you need it, and one itemised quotation comes back inside two business days.
In the contract
What we put in writing
Six clauses, in every agreement we sign. None of them is negotiable downward.
A fixed quote in 48 hours
A scoped brief and one itemised quotation, inside two business days of the call.
Full repository handover
Every milestone hands over the whole repository — history included, nothing held back.
100% IP ownership
You own the source, the designs and the infrastructure accounts. Always.
Milestone payments
You pay against delivered, reviewable milestones — not calendar dates.
30-day post-launch warranty
Defects found in the first 30 days after go-live are fixed at no cost.
NDA on request
Send yours or use ours. Signed before the first technical conversation.
Questions
Before you ask
The eight that come up in nearly every first call.
Who writes my code?
In-house engineers, employed here rather than sourced per project, and named on the proposal before you sign it. The engineer who scopes your system is the one who builds it and runs the demos — there is no handover to a cheaper team after signature, because there is no cheaper team.
How much will it cost?
Whatever your scope costs, quoted in writing before anything starts. We do not publish bands because a band is a guess you have to fit yourself into: pick the pieces you actually need on the quote form and one itemised quotation comes back within 48 hours. Asking costs nothing and commits you to nothing.
What do I actually end up owning?
All of it — the source, the commit history, the designs, the schema and the infrastructure accounts. The whole repository is handed over at every milestone rather than transferred at final payment, so you hold a complete, buildable copy of the work long before the last invoice, and nothing is withheld at the end as leverage.
What is outside the quotation?
The quotation states the in-scope and out-of-scope lists on one page. Licences, content entry, translation, migration, paid media and training are quoted separately or excluded in writing before you sign anything.
Is it a bug or a change request?
If it contradicts the written acceptance criteria, it is a defect and we fix it at our cost. If it changes them, you get an estimate and you decide. That test is written into the contract so neither of us argues it later.
Can you work with our existing team?
Yes. We join your board, your standups and your review process, and we write the same acceptance criteria either way. Roughly half of what we do sits beside an in-house team rather than replacing one.
How do payments work?
Against delivered milestones, not calendar dates. The quotation names each milestone and what it has to contain to be one. After that you pay when something reviewable lands, which keeps the incentive on shipping rather than on invoicing.
What happens after launch?
Defects present at go-live are fixed free for 30 days. After that there is an optional care plan covering monitoring, patching, small changes and an agreed response time, quoted monthly against the system you actually have. It is cancellable with 30 days' notice.
Start with the quote you can walk away from.
Pick the pieces you need. The scope, the plan and the number come back in writing, and they are yours either way.