The approval-speed rule that actually sets your launch date, real 2026 timelines by project type, a phase-by-phase schedule of where the weeks actually go, the store and statutory clocks that run outside the build — and how to genuinely build faster without breaking the product.
Take whatever timeline your developer quotes and add one week for every three days you typically take to approve something — a normal Indian build has about six approval gates, so that arithmetic, not the code, is what decides your launch date. The same 3-week business website ships in 3 weeks for a client who replies within a day and in 7 to 8 weeks for a client who replies in a week, and the developer gets blamed for both. On next-day approvals, the 2026 baselines in India are: a business website 2–3 weeks, a simple mobile app 4–6 weeks, a complex marketplace app or SaaS platform 4–7 months, a landing page 5–10 days, an e-commerce store 3–8 weeks and a SaaS MVP 10–24 weeks.
A build timeline is not a property of the code, it is scope divided by your approval speed. The working rule: take the developer’s estimate, count the approval gates (design, content, staging, launch — usually six), and add one week for every three days you typically take to reply. A 3-week website with a client who answers in a day ships in 3 weeks; the same site with a client who answers in a week ships in 7 to 8 weeks, and the developer will be blamed for both. If you want it faster, the lever you control is not the price. It is your inbox.
We are the ones who get blamed when a project runs late, so treat this page as self-interested: an agency writing about delay has an obvious motive to point at the client. The rule above is offered as an arithmetic you can check against your own last project rather than as an excuse — and the store-clock section below is a delay that is genuinely nobody’s fault but is entirely plannable.
This is the deadline that catches almost every first-time Indian app owner, and very few agency timeline articles mention it. If your Google Play developer account was created as a personal account, Google requires you to run a closed test with at least 12 testers who stay opted in continuously for 14 days before you are even permitted to apply for production access. That is not review time and it is not negotiable — it is a hard fourteen-day clock that only starts once you have recruited twelve real people, and if testers drop out the clock effectively restarts. In practice it adds two to three weeks to the launch of a brand-new Android app. Organisation accounts (registered company, D-U-N-S verified) are exempt, which is a strong argument for registering the developer account as a company at the very start of the project rather than the end.
The other end-of-project clock is Apple. App Store review itself is fast — usually 24 to 48 hours — but first submissions are rejected far more often than they are approved, most commonly for a missing privacy policy, incomplete app privacy disclosures, sign-in that demands an account for no reason, or a demo login that does not work for the reviewer. Each rejection round trip costs a day or two. Budget one week for the App Store, not two days, and plan the first submission for a week before you need to be live.
Both of these sit entirely outside the development schedule. A developer can hand you a finished, tested app on the promised date and you can still be three weeks from being downloadable. Start the developer-account registration and tester recruitment in week one of the build, in parallel with development — it is free, it costs no engineering time, and it is the cheapest fortnight you will ever save.
Every agency timeline article stops at the store gates. There is a third clock, it is written into law rather than into a platform policy, it runs in parallel with the build if you start it on day one and in series with it if you do not, and getting it wrong costs real money rather than just days.
Under rule 9 of the CGST Rules a GST registration is granted within seven working days where Aadhaar authentication is successfully completed and the application is not flagged for risk. Skip or fail the Aadhaar authentication, or get flagged, and the application goes to physical verification of your place of business and the outer limit becomes thirty days — longer than the entire build of a business website. That alone is a reason to complete the Aadhaar step properly the first time.
The expensive part is rule 10, and this is what almost nobody buying software in India has been told. Apply within thirty days of becoming liable to register and your registration takes effect from the date you became liable, so the tax on the build invoice, the hosting, the domain and the foreign tooling all falls inside the registration period and the input tax credit is claimable. Apply after that window and the registration is effective only from the date it is granted — and there is no rescue, because section 18(1)(a) of the CGST Act grants transitional credit on inputs held in stock, which means goods, and a software build is a service. On a ₹2,00,000 build that is ₹36,000 of input tax credit thrown away by a filing delay that costs nothing to avoid. It is very probably the single most expensive scheduling mistake on this page, and it has nothing to do with your developer.
| Gate outside the build | Best case | Worst case | Start it in |
|---|---|---|---|
| GST registration — rule 9, CGST Rules | 7 working days (Aadhaar authenticated) | 30 days + physical verification of premises | Week 1 |
| Payment gateway onboarding (needs the GSTIN & business proof) | 2–5 working days | 2–3 weeks with document queries | As soon as the GSTIN lands |
| Google Play closed-testing gate (personal accounts) | 14 continuous days | 2–3 weeks, restarting if testers drop out | Week 1 |
| Apple App Store review | 24–48 hours | 1 week across rejection round trips | 1 week before go-live |
| Domain, SSL, business email | Same day | 2–3 days if the domain is being transferred | Week 1 |
Read that table as one instruction: every row except the App Store can be run in parallel with development, and every row that is not started in week one becomes serial time bolted onto the end of the project. The GST row is the one that also carries a price tag, which is why it is first. If you are building anything that takes money from Indian customers, the registration is upstream of the payment gateway, which is upstream of your launch — three queues in a row, all of them started by one form you could have filed on day one.
Current as at July 2026. General information about how these timelines work, not tax advice — confirm your own position with your CA. Note also that importing foreign developer services can itself trigger a registration obligation regardless of turnover under section 24(iii) of the CGST Act; we cover the reverse-charge mechanics in the React Native vs Flutter guide.
These are the same working windows ZoopCoder quotes from, alongside the honest price band for each. They assume a normal review pace — you giving feedback within a day or two — and a scope fixed in writing before the build starts.
| What you are building | Typical build time | Price band in India | What sets the pace |
|---|---|---|---|
| Landing page / one-pager | 5–10 days | ₹15,000 – ₹40,000 | Copy and one round of design |
| Business website (5–10 pages) | 2–3 weeks | ₹25,000 – ₹50,000 | Content readiness, page count |
| WordPress website | 2–4 weeks | ₹35,000 – ₹75,000 | Theme customisation, plugins |
| E-commerce store | 3–8 weeks | ₹50,000 – ₹2,50,000 | Catalogue size, payments, admin |
| Simple mobile app (Flutter) | 4–6 weeks | ₹50,000 – ₹1,00,000 | Screen count, one user role |
| Custom web app / portal | 6–16 weeks | ₹1,00,000 – ₹5,00,000+ | Roles, workflows, integrations |
| Medium app (logins + payments) | 8–14 weeks | ₹1,00,000 – ₹2,50,000 | Auth, payments, admin panel |
| SaaS MVP | 10–24 weeks | ₹1,50,000 – ₹5,00,000 | Number of core workflows |
| Complex app (marketplace / fintech) | 16–30 weeks | ₹2,50,000 – ₹25,00,000+ | Multiple apps, live data, compliance |
Price bands are what Indian development studios publicly quote in 2026 and match ZoopCoder’s own pricing page. Build times are calendar weeks of active work, not billable hours. For the full money breakdown see our app cost guide and website cost guide.
Want a real date, not a range?
Tell us what you are building and when you need it live. We will come back with a week by week schedule that includes the store review and any GST wait, and we will tell you if the date you want is not achievable. Reply on WhatsApp, within one working day.
A timeline is not one long block of coding. Every project moves through the same five phases, and knowing the shape of them tells you exactly where you can save time and where you cannot. The percentages below are for a typical medium project — a business web app or a mid-complexity mobile app.
| Phase | Share of the calendar | What happens | Who controls the pace |
|---|---|---|---|
| 1. Discovery & scope | 3–7 days (~10%) | Requirements, feature list, written scope, fixed quote | Shared — needs your decisions |
| 2. UI / UX design | 1–3 weeks (~20%) | Wireframes, visual design, your review and sign-off | You — approval speed sets it |
| 3. Development | Bulk of the time (~45%) | Front-end, back-end, integrations, built in two-week sprints | The agency |
| 4. Testing & QA | 1–2 weeks (~15%) | Functional testing, devices, bug fixes, your acceptance testing | Shared |
| 5. Deployment & launch | 3–7 days (~10%) | Hosting or store submission, final checks, go-live | The agency (+ store review for apps) |
Two things jump out of that table. First, only about 45% of the calendar is coding — more than half is discovery, design, testing and launch, which is why “just start building” rarely ends sooner. Second, the two phases you control — approving design and supplying content — are also the two where projects lose the most time. App projects add one thing outside everyone’s control: store review, typically 1–3 days on Google Play and up to a week on the Apple App Store, which you should always leave slack for.
If you have heard that software always ships late, this is the honest reason. Ranked by how often they actually cause the slip:
| Cause of delay | Typical time lost | How to avoid it |
|---|---|---|
| Slow feedback / approvals | 1–3 weeks | Commit to a 24–48 hour turnaround on every review |
| Content and assets arriving late | 1–2 weeks | Have copy, logo and photos ready before development starts |
| Scope added mid-build (scope creep) | 2–8 weeks | Fix scope in writing; park new ideas for phase two |
| Unclear requirements at the start | 1–4 weeks | Spend real time on discovery before quoting |
| Third-party dependencies (payment KYC, APIs) | 3 days – 2 weeks | Start gateway and API approvals on day one, not at launch |
| App store review | 1–7 days | Build in slack; never promise a launch date inside review |
Notice that the biggest single delay — scope creep — is entirely inside the client’s control, and so are the top two. The uncomfortable truth is that the fastest projects are not the ones with the fastest coders; they are the ones with a client who decided what they wanted before the build started and answered emails the same day. This is the same reason we insist on a written scope and a fixed-price quote rather than open-ended hourly billing.
Up to a point, and then no. Throwing a second developer at a small project usually makes it slower, because the two now have to coordinate — a well-known effect that has held true in software for fifty years. What actually compresses a timeline is different, and cheaper:
Realistically, a sensible rush saves days on a website and weeks on a complex app. Pushing harder than that trades quality for speed, and a product that launches a fortnight early but breaks in week one has not actually launched early.
Handover is a milestone, not the finish line. A website needs its first security and plugin updates within the first month. A mobile app has a harder deadline: with Android and iOS each shipping a major OS release every year and both stores enforcing minimum SDK targets, an unmaintained app typically starts breaking or gets pulled within 12–18 months. That is why every ZoopCoder project ships with 30 days of free post-launch support and full source-code ownership — you are never waiting on one vendor to keep your product alive — with optional maintenance from ₹3,000/month after that. The recurring side of the timeline is covered in full in our app cost guide.
We send a fixed timeline and quote within 24–48 hours of understanding your requirement, then build in two-week sprints so you see something real every fortnight rather than waiting in the dark for a launch email. Payment follows a 30-40-30 milestone structure — 30% to start, 40% at the design-approved halfway mark, 30% on completion — which keeps both sides honest about progress. Every project includes discovery, design, development, testing, deployment or store submission, complete source-code ownership, documentation and 30 days of free post-launch support. If your date is fixed — a funding demo, an event, a season — tell us upfront and we scope the first version to hit it, rather than promising the whole thing and slipping.
Tell us what you’re building and we’ll send an honest timeline and a fixed, itemised quote within 24–48 hours — including what we’d need from you to hit a specific date.
Add one week to any quoted timeline for every three days you take to approve something — there are about six approval gates in a normal build. On next-day approvals a 5–10 page business website takes 2–3 weeks. A single landing page can be live in 5–10 days, a WordPress site in 2–4 weeks, an e-commerce store in 3–8 weeks, and a custom web app or portal in 6–16 weeks — assuming you supply content and approvals on time.
A simple 4–8 screen app takes 4–6 weeks, a medium app with logins and payments 8–14 weeks, and a complex marketplace, on-demand or fintech app 16–30 weeks. Building with Flutter keeps Android and iOS on one timeline instead of two.
Week one of the build, not launch week. Rule 9 of the CGST Rules grants registration within 7 working days where Aadhaar authentication succeeds and the file is not flagged; without it, the application goes to physical verification of your premises and the outer limit is 30 days. The costly part is rule 10: apply within 30 days of becoming liable and the registration back-dates to the day you became liable, so the input tax on the build, hosting and tooling is claimable; apply later and it is effective only from the date of grant — with no fallback, because section 18(1)(a) gives transitional credit on inputs held in stock, meaning goods, and a build is a service. On a ₹2,00,000 build that is ₹36,000 of credit lost. General information current as at July 2026, not tax advice.
Almost always because of the client, not the code: slow approvals, content arriving late, and scope added mid-build. A project waiting three days for each of six sign-offs loses over two weeks to waiting alone. A written, fixed scope and 24–48 hour feedback are the two biggest fixes.
Only a little. Adding developers to a small project often slows it down. What genuinely compresses a timeline is cutting scope to a real first version, supplying finished content, and approving each stage within a day or two. A sensible rush saves days on a website and weeks on a complex app, not more.
10–24 weeks, depending on how many core workflows it has to prove. A disciplined MVP that ships in 12 weeks and reaches real users beats a feature-complete build that takes 30 weeks and learns nothing until launch.
A website needs its first updates within a month. An app has a harder deadline: annual OS releases and store SDK minimums mean an unmaintained app usually starts breaking or gets pulled within 12–18 months. ZoopCoder includes 30 days of free support, with optional maintenance from ₹3,000/month after that.
Mobile app development cost in India · Website development cost in India · Freelancer vs agency · ZoopCoder pricing · How we work · Redesign or rebuild your website · What a development quote must include · How much advance to pay a developer · Website maintenance cost in India · SaaS MVP cost in India · All guides