The uncomfortable truth about build timelines: coding is ~45% of the calendar
Every time someone asks "how long will it take to build this app?", the answer they expect is a coding estimate. But if you have shipped a few products, you know the calendar is dominated by everything around the code. Here is the breakdown we actually see on India-based builds, and why the estimate you were given keeps slipping.
The headline numbers (once the team is building)
| Project type | Realistic timeline |
|---|---|
| Landing page | 5-10 days |
| Business website | 2-3 weeks |
| Ecommerce site | 3-8 weeks |
| Simple app (few screens, 1-2 integrations) | 4-6 weeks |
| Mid-complexity app (accounts, payments, admin) | 8-16 weeks |
| SaaS MVP | 10-24 weeks |
| Complex platform / marketplace | 4-7 months |
These assume a competent team is already onboarded. The "hire" and "spec" time sits before this clock starts.
Where the calendar actually goes
This is the part that surprises non-technical stakeholders. For a typical app, the phase split looks like:
| Phase | Share of calendar |
|---|---|
| Discovery & specs | ~10% |
| UI/UX design | ~20% |
| Development (the "coding") | ~45% |
| Testing & bug-fixing | ~15% |
| Deployment & store review | ~10% |
Coding is under half the timeline. So when a vendor promises "your app in 3 weeks", the honest question is: which of these phases are you dropping? It is almost always testing — and you pay that debt back with interest in month two.
The real reason projects run late (it is not the developers)
In my experience the single biggest source of slippage on Indian projects is scope creep and slow client approvals, not slow engineering. Mid-build feature changes and multi-day sign-off delays on designs routinely add 2-8 weeks. That clock lives entirely on the client's side.
Things engineers can predict but clients rarely budget for:
- Native iOS + Android in parallel is materially slower than one Flutter / React Native codebase.
- App Store / Play review adds anywhere from a few days to a couple of weeks, and it is out of your hands.
- India-specific integrations — Razorpay/PayU, Aadhaar/DigiLocker KYC, GST invoicing — tend to need extra compliance rounds that never show up in the naive estimate.
How to actually hit the estimate
- Freeze scope before development starts. A locked spec is worth more than an extra developer.
- Assign one decision-maker on the client side who can approve designs within a day.
- Keep testing in the plan. If it is not a line item, it is not happening.
- Sequence, don't parallelize blindly — a shared codebase beats two native teams for most products pre-scale.
Disclosure: I work with ZoopCoder, an India-based development agency, so treat the agency framing accordingly — I have tried to keep the phase math and timelines honest and vendor-neutral. We published the full version of this, with the timeline-and-price table by project type and a ranked list of what causes delays, here: How Long Does It Take to Build an App or Website in India?
SOCIAL SHARE CARD GENERATOR