A business website of up to seven pages takes 7–10 working days to build in India once the content is ready. A 15-page site with a blog and on-page SEO takes 2–3 weeks, an e-commerce store 3–4 weeks, and a web application 6–12 weeks after a discovery sprint. Those are build days, not calendar days, and the difference between the two is where almost every delayed project actually goes wrong.
The code is rarely the bottleneck. The clock stops every time a project is handed back to the client for words, photographs or a decision. Below are both figures for each type of site, the stages they break into, and what to have ready before day one.
Realistic timelines by project type
Build time means days a team is actually working on your site. Realistic calendar time is what you will experience from kick-off to go-live at normal human response speeds. The right-hand column is our published pricing at Codelith Lab, excluding 18% GST, so you can see what each timeline costs.
| Project type | Build time | Realistic calendar time | Our price (excl. 18% GST) |
|---|---|---|---|
| One-page site for a single service | 2–3 days | About a week | Not a separate tier — a trimmed business site |
| Business website, up to 7 pages | 7–10 working days | 2–3 weeks | ₹24,999 |
| Up to 15 pages + blog + on-page SEO | 2–3 weeks | 4–6 weeks | ₹49,999 |
| E-commerce store, up to 100 products | 3–4 weeks | 5–8 weeks | ₹99,999 |
| Web app or SaaS | 6–12 weeks | 3–5 months | From ₹1,49,999, after a ₹49,999 discovery sprint |
The gap between column two and column three is not padding. It is content collection, two review rounds, and waiting on things nobody in the project controls: payment gateway activation, a domain auth code held by an old developer, or a decision that needs three family members in the same room.
What happens in each stage
Here is how a 7–10 day business website is spent. Larger projects use the same stages with more days in each.
Discovery — half a day to one day
One call and a written questionnaire: what you sell, who buys it, which enquiry you want (a phone call, a WhatsApp message or a form), the page list, and the name of the one person who approves work. Skipping this does not save a day. It moves that day to the end of the project, where it costs three.
Structure and copy — one to two days
The page list, the order of sections on each page, and the actual words. When a client has no content we write it from the questionnaire and the call, then send it back for correction. That is deliberate: a draft you can fix is far faster than waiting for a business owner to write 2,500 words between customer calls. If you insist on writing it yourself, add a week to the plan and be honest with yourself about it.
Design — two to three days
The home page is designed first, on a phone screen, because that is where most Indian traffic arrives. Once it is approved, inner pages follow the same type sizes, spacing and components in hours rather than days. Redesigning the home page after inner pages are built is the most expensive change you can ask for.
Build — two to three days
Pages coded, forms wired to WhatsApp and email, SSL installed, images compressed, speed and security checked, Analytics and Search Console connected. On a store this stage runs longer because payments, shipping rates and tax settings each need real test transactions.
Content loading — runs alongside the build
Photos cropped, alt text written, map embedded, hours and address set. For e-commerce this is the stage that quietly eats a week: 100 products with names, prices, weights, dimensions, HSN codes and two images each is a data-entry job. If your product sheet is ready, it is imported while the store is built. If it is not, nothing else on the plan matters.
Review rounds — one day of our time, unknown days of yours
A revision round takes about a day to apply. What varies is how long feedback takes to collect. Send one consolidated list, not eleven WhatsApp messages over five days. A single reviewer with authority closes a round in a day; a group of five takes a fortnight and contradicts itself.
Launch — one day, plus DNS
Final checks — we run a 40-point pre-launch checklist covering forms, mobile layout, broken links, redirects, indexing, backups and analytics — then the domain is pointed at the new hosting. DNS changes can take 24–48 hours to settle across networks, so the old site may still appear on some phones for a day. Do not launch on a Friday evening, and never the night before a festival sale.
What actually causes delays
- Content from the client. The number one cause, by a wide margin. A seven-page site needs roughly 2,000–2,500 words, 15–25 usable photographs and a logo in a vector file. When those arrive on day 20 instead of day 2, the project is 18 days late and no development process on earth fixes it.
- Scope changes mid-build. “Can we add a booking system?” on day six is not a small request; it reopens structure, design and testing. Park additions and add them after launch as extras — an extra page is ₹1,999 with us — rather than reopening a finished design.
- Slow approvals. Feedback arriving in pieces turns a one-day round into a seven-day round; two such rounds add a fortnight to a ten-day build.
- Third parties. Payment gateway activation with Razorpay or PhonePe needs your current account, PAN, GSTIN and business proof, and takes a few working days when the documents match — longer when the name on the bank account does not match the GST certificate. WhatsApp Business API access needs Meta business verification, and courier accounts such as Shiprocket or Delhivery need a pickup address and KYC. None of it is developer time, and none of it moves faster if you pay more.
- The previous developer. If someone else holds your domain, hosting or business email, budget a week to recover access. This is why we register the domain, hosting, admin logins and analytics in the client’s name from day one.
- The calendar itself. Audit season and long festival breaks slow approvals on both sides. If the launch must land before a sale, count backwards from the sale date.
How to compress a timeline honestly
Some things genuinely speed a project up. Others only move the pain later.
What works
- Have the content ready before kick-off. Worth 5–10 days on a business site and more on a store.
- Name one decision-maker with authority, and let the group send feedback through that person.
- Accept a proven layout instead of a design exploration. We keep live demo websites at codelithlabdemo.online that anyone can open on a phone (our own demonstrations, not client sites), and our website design by industry pages show a finished site for a given sector. Choosing from something real removes days of guesswork.
- Launch in phases. Put five finished pages live and add the blog, gallery and case studies over the next month. A live five-page site earns more than a perfect ten-page site still stuck in review.
- Buy parallel work only on large builds. Extra developers help on a web app and do nothing useful on a seven-page site.
What does not work
- Cutting review rounds. The corrections still happen, just after launch, in public.
- Skipping mobile testing to save half a day. Most of your traffic is on a phone, on a mid-range Android, on a patchy connection.
- Starting the gateway paperwork in the last week of an e-commerce build.
- Expecting a fast build to buy rankings. A site built in three days and one built in three weeks both need months of work before Google takes them seriously; see our SEO services page for what that timeline actually looks like.
What a 3-day or 24-hour website really is
These offers are real and they are not automatically bad. A 24-hour or 3-day website is nearly always a purchased theme with your logo, colours and text placed into an existing layout. The time saved is design time and copywriting time — which is exactly the time that would have made the site look like yours and read like you.
That trade is sometimes correct. If you run a single-service local business and you need a phone number, a map, a few photographs and a WhatsApp button, a three-day one-pager is enough, and we would rather say so than sell you seven pages. Equally honest: if your total budget is under ₹20,000, a do-it-yourself builder is a better use of that money than a cheap custom build done in a hurry.
Four things to ask any 24-hour offer:
- Is this a template, and may I see the template’s original demo?
- Whose name are the domain and hosting registered in?
- Is the mobile layout designed, or is the desktop layout squashed?
- What arrives in 24 hours — the whole site, or the home page with inner pages later?
The last question catches most of them. A home page in a day is ordinary; a complete, tested, indexable site in a day is not.
The client-side checklist for day one
Collect these before you sign anything, whatever the size of the project.
- Domain registered in your own name, with the registrar login, and the auth code if you are transferring it
- Logo in a vector file (AI, SVG, EPS or PDF), not a compressed PNG pulled out of a WhatsApp chat
- Legal business name, GSTIN, full address, working hours and service areas, written exactly as they should appear
- The page list, and five to ten lines about each service in your own words
- 15–25 photographs at least 1,600 pixels wide, shot in landscape; if you have none, plan a phone shoot or accept licensed stock
- A decision on prices: published, on request, or a starting-from figure
- Where enquiries should land — a WhatsApp number, an email address or a CRM
- One named approver, and a second person only as backup
- Google Business Profile access, so the site and the profile point at each other from day one
- For a store: current account, PAN, GSTIN and cancelled cheque for the gateway; a product sheet with weights and dimensions; a pickup address; and a written policy on COD and returns, because RTO on cash-on-delivery decides whether the store makes money
Owners who arrive with this list finish in the build-time column of the table above. Owners who do not, finish in the calendar column, or later.
How we run the clock
Codelith Lab is a registered Indian company (CIN U62091PN2025PTC247887). Our office is in Pune and roughly 60% of clients are elsewhere in India, so delivery is built for distance: a WhatsApp group for daily updates, Google Meet for review calls, a shared content checklist and the 40-point pre-launch check. Payment is 50% to start and 50% at launch, with a GST invoice at each milestone. Our timelines start on the day content is received, not the day the advance is paid — that one line in a proposal prevents most timeline arguments. Scope-specific details sit on the web development in India, small business websites and startup websites pages.
The short version
- Seven-page business site: 7–10 working days of build, 2–3 weeks on the calendar. Store: 3–4 weeks of build, 5–8 weeks on the calendar. Web app: 6–12 weeks.
- Content from the client is the number one cause of delay, ahead of scope changes and slow approvals. Nothing on the developer’s side fixes it.
- Honest ways to go faster: content ready before kick-off, one decision-maker, a proven layout, a phased launch. Gateway KYC and DNS cannot be rushed at any price.
- A 24-hour website is a template with your content in it. For a single-service local business that is often enough; for a site you intend to rank or sell from, it is not.
Frequently asked questions
How long does it take to build a small business website in India?
Up to seven pages takes 7–10 working days to build once the content is ready, which usually means two to three weeks on the calendar after review rounds and approvals. The build itself rarely runs late. If your text, photographs and logo are in hand on day one, the working-day figure and the calendar figure end up almost the same.
Can a website really be built in 24 hours?
Yes, and it is almost always a purchased theme with your logo, colours and text placed into an existing layout. That can be the right choice for a single-service local business that needs a phone number, a map and a WhatsApp button. It is not enough for a site you intend to rank on Google or sell from. Ask whether the 24 hours covers the whole site or only the home page.
How long does an e-commerce website take to build?
Three to four weeks of build time for a store of up to 100 products, and five to eight weeks on the calendar. The build is not the slow part. Product data, payment gateway activation with Razorpay or PhonePe, and a courier account with Shiprocket or Delhivery each run on their own clock. A ready product sheet with weights, dimensions and images saves the most time.
Why do website projects get delayed in India?
Content from the client is the number one cause, ahead of scope changes and slow approvals. A seven-page site needs roughly 2,000–2,500 words, 15–25 photographs and a vector logo; when those arrive three weeks late, the project is three weeks late. After that come mid-build additions, feedback from a group instead of one person, and access still held by a previous developer.
How soon after launch will a new website bring enquiries?
Enquiries from WhatsApp, ads and people you send to the site can begin on day one. Google is slower. A new site usually needs three to six months of on-page work, content and profile activity before it ranks for anything competitive, and longer in crowded categories. Anyone promising rankings in weeks is guessing. Plan your launch date around your sales season, not around Google.
