How a project runs, how we price it, and what you own at the end.
Clear phases, pricing that doesn’t come before understanding, and a handover that leaves everything in your hands.
From the first workshop to after launch.
Durations are for a typical project: an iOS and Android app with an admin panel, in Arabic and English. A solution architect stays with the project throughout.
- 01About 2 weeks
Requirements & discovery
Workshops with the people who will use the product, not only the people buying it. We map the flows, the integrations and the decisions still open, and agree what “done” means for the first release.
- 02About 2 weeks, plus 1 for revisions
UI/UX design
Screens in Arabic and English from the start, reviewed with you as a clickable prototype. Your feedback round is built into the plan rather than treated as a delay.
- 03About 6 weeks for a typical project
Build
Working software every week, not status decks. You see each release, test it on your own phone and steer while changes are still cheap.
- 04About 2 weeks
Testing & launch
Testing on the devices your users actually carry, in both languages, then App Store and Google Play submission, handled by us.
- 05Monthly, if you want it
Support after launch
Monitoring, OS and dependency updates, fixes and small features on a monthly plan — or a clean handover to your own team.
Three stages, each with a clear price.
1. Paid discovery first
We don’t quote a build before we understand it. Discovery is a short, paid phase with a defined output.
- A scoped plan for the first release
- Screens and flows for the key journeys
- A timeline and a price for the build
- Yours to keep, whether or not you build with us
2. Fixed-scope build phases
Each phase has an agreed scope and price. Anything new goes into a written change request or the next phase — no surprises on the invoice.
- First release first, then phase 2
- Weekly releases you can test
- Change requests in writing
3. Monthly support plans
After launch, a monthly plan sized in engineering days — from a few days a month for a stable product to a dedicated engineer for one that keeps growing.
- Monitoring and updates
- Fixes and small features
- One-off days for quick jobs
Everything. Whether we keep working together or not.
And we say so when the right answer costs us the work: build it in-house, keep your current vendor, or don’t rebuild it yet.
- The source code and the repository
- The cloud account it runs in
- The App Store and Google Play listings
- The documentation and the runbooks
About price and ownership.
- Do you give a fixed price?
- Yes — for a defined scope, after discovery. Before discovery we give a timeline range (our project estimator does it in a minute) and the price for your market, but not a fixed quote for something neither of us has scoped yet.
- What does discovery produce?
- A scoped plan for the first release, screens and flows for the key journeys, and a timeline and price for the build. You own it whether or not you build with us.
- Who owns the code?
- You do. The repository, the cloud account, the store listings and the documentation are yours, and they are handed over whether the engagement continues or not.
- Do you use AI to build faster?
- Yes, mainly during the build, for routine code, tests and documentation — our timelines already reflect it. Every change is still reviewed by an engineer, and AI doesn’t shorten the parts that depend on decisions: requirements, approvals, integrations with other companies’ systems and app-store review.
Have an RFP? Have an idea? Let's build it.
We reply to every inquiry within one business day. Tell us about your project, timeline, and what success looks like.