Skip to content
Free tool

How long will your project take to build?

Pick your kind of project, answer a few questions and see a realistic timeline, phase by phase, and the team it takes — based on our own projects, not industry averages.

01What kind of project is it?

We fill in the usual answers for that type — change anything below.

02What do you need built?

Pick everything that applies.

03How many types of user?

For example: customer, sales rep, supplier, admin.

04Which features does it need?

Only what the first release needs.

05In which languages?
06Where is the design?
07Where are we starting from?
Estimated timeline

11–15 weeks

About 2.5–3.5 months from first workshop to launch.

  • Requirements & discovery2 wk
  • UI/UX design2 wk
  • Design revisions after your feedback1 wk
  • Build6 wk
  • Testing & launch2 wk
The team
  • Solution architectPart-time, throughout (~25%)
  • Product managerPart-time, throughout
  • UI/UX designerDesign phase, then on call during build
  • 2 × Mobile engineer (Flutter)Build
  • Web engineerBuild
  • Backend engineerBuild
  • QA engineerTesting, and alongside the build

Timelines reflect our AI-assisted delivery. This is a range, not a commitment — discovery sets the real plan.

Price depends on your market, so we send it to you directly with the breakdown.

Get the price for your market
How we got here
PhaseItemWeeks
Requirements & discoveryStarting point+2
UI/UX designStarting point+2
Design revisions after your feedbackOne round of feedback+1
BuildMobile app (iOS + Android)+2.5
Admin panel / dashboard+1.5
Sign-up, login & profiles+0.5
Catalogue, cart & ordering+1
Notifications (push, SMS, WhatsApp)+0.5
Testing & launchA third of the build time+2
How the estimate works

No black box.

  • It starts from real projects

    A typical project of ours — an iOS and Android app with an admin panel, two types of user, Arabic and English — takes about 13 weeks: two for requirements, three for design and revisions, six for the build and two for testing. Every answer you give moves that baseline up or down.

  • Every addition is shown

    Nothing is hidden behind a "calculating…" screen. The table under the result lists each platform and feature and the weeks it adds, so you can see what to move to a second release.

  • Time and team, not price

    The effort a project takes is the same wherever you are. Price depends on your market, so we send it to you directly with a written breakdown instead of guessing at it here.

  • A range, not a promise

    The estimate is shown as a range because it has to be. A paid discovery phase turns it into a real plan with a fixed scope.

Common questions

About time and price.

How long does it take to build an app?
For a typical business app — iOS and Android plus an admin panel, two types of user, Arabic and English — about 11 to 15 weeks from the first workshop to launch. Payments, integrations, extra user types and AI features add to that; launching with fewer features takes less.
Does AI make development faster?
Yes, mainly during the build: our engineers use AI tools for routine code, tests and documentation, and these timelines already reflect that. It does not shorten requirements, design approvals, third-party integrations or app-store review, which is why we do not promise a dramatic multiplier.
Why don’t you show a price?
Because the same project is priced differently in Egypt, the Gulf and the US, and a number shown out of context helps nobody. Send us the estimate and we reply with the price for your market and what it includes.
What happens after I send the estimate?
We reply within one business day with the price for your market and a short list of questions. If it fits, the next step is a paid discovery phase that ends in a scoped plan you own, whether or not you build with us.

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.