From business brief to working website
The project does not start with code. Customer needs, pages, content, responsibilities and cost are agreed first - so everyone knows what "done" means at review time.
Tell me about the projectDISCOVERY · 2–5 days
What you offer, who the customer is, what they ask, where enquiries come from today, and which job the website needs to perform. Starts with a 30–60 minute call - no technical brief required.
SCOPE · 2–3 days
The page list is more than names. Each page's purpose, features, content owner, review rounds, exclusions, running costs and handover items go into the written scope. The final project total is stated clearly in the written quote.
CONTENT + DESIGN · 1–2 weeks
What customers see first, what the headings say and where the contact action sits are reviewed early. Mobile view is reviewed together with desktop - not as a later round.
BUILD + REVIEW · 1–2 weeks
Responsive layouts, navigation, forms, WhatsApp/call actions and agreed functionality are built. Feedback arrives at agreed review points so corrections and new scope are not confused.
LAUNCH + HANDOVER · 2–3 days
Indexing controls, metadata, sitemap, Search Console verification, the agreed contact destination and important journeys are checked. Accounts, files and practical notes listed in the quote are handed over. Final 40% invoice after launch.
Before the schedule starts
Perfect copy does not need to exist on day one, but the facts and the person responsible for approvals must be available. The scope states the level of content support included.
Existing copy, photographs, product data and policies can be reviewed for structure and accuracy, then prepared for the build.
Calls, notes, brochures and customer FAQs become a writing brief. The quotation says whether copywriting or editing is included.
Use a pre-project phase to collect decision-makers, product or service details, proof and policies instead of approving a design full of empty placeholders.
Keeping the project moving
Most delays come from missing content and late approvals rather than from code.
What can change the schedule
The stage ranges above are planning examples, not a universal promise. Final dates appear in the written quotation with project-specific dependencies.
A missing price list, policy or consolidated feedback can hold the next stage.
Variants, inconsistent spreadsheets, image preparation and migration affect an ecommerce schedule.
Gateway KYC, domain access, app review or an external API may sit outside Overbuilt’s direct control.
If a new page or feature is added after approval, its cost and schedule effect are documented first.
What launch includes
No technical brief?
India-specific process notes
These are the details where a generic global process template quietly fails - validation, WhatsApp-first communication, festival-season windows and multi-owner decision making. Raising them early in discovery and scope is the most honest thing for the timeline.
The business name and billing address are collected before kickoff so the first milestone invoice does not create a bottleneck.
When Diwali, wedding season or a sale window is the target, the launch buffer is planned 2–3 weeks earlier. Reviewing the calendar at kickoff reduces last-minute risk.
Family businesses often have 2–3 people involved in approvals. Identifying the primary approver in discovery keeps versioning and rework under control.
Feedback often arrives on WhatsApp. Long feedback threads are consolidated into a single document so nothing is missed and the build stays steady.
What sits inside each stage
This table shows what usually sits inside each stage, what moves to the next stage and what becomes a separate scope. The same table is useful during quote review - it keeps the expectation gap small.
| Stage | Included | Not included |
|---|---|---|
| Discovery | Business and customer questions, brief notes, competitor snapshot | Full market-research reports, brand strategy retainer |
| Scope + quote | Written pages, features, exclusions, tax, milestone schedule | Legal review of your contract, third-party vendor quotes |
| Content + design | Important-page direction, mobile-first layout, first-fold message | Full brand-identity system, print design, video production |
| Build + review | Responsive build, agreed features, form/contact wiring, milestone reviews | New pages or features added mid-way (separate change order) |
| Launch + handover | Final QA, indexing/sitemap, Search Console, agreed access transfer, handover checklist | Ongoing SEO campaigns, ad-account setup, long-term maintenance |
Realistic project timelines
Marketing pages sell a "7-day website", but honest planning depends on content readiness, review speed and functionality. Below are typical planning ranges for common Indian business types.
2–4 weeks end to end when content and photos are ready. 6+ weeks if content drifts.
4–8 weeks, driven by gateway KYC and how clean the catalogue is.
4–6 weeks. Capability sections, certifications and multi-office locations need extra research.
3–8 weeks, driven by URL count, migration mapping and access recovery.
Content-ready checklist
Many Indian businesses say "everything is ready" and then in week 2 realise the final service list is not confirmed or the director's photograph is missing. This checklist is for honest input planning - what is missing today becomes a discovery task rather than a launch-day scramble.
Legal name, /tax status, Udyam number (if held), service area, working hours, contact numbers, WhatsApp, email, address (if customers visit).
Confirmed list, prices or price range (if public), scope of work, inclusions and exclusions, delivery or turnaround times.
Owner photo, team photos (with permission), 5–15 work photos, brands worked with, certifications, honest reviews.
The 10–15 most common WhatsApp and phone questions with their honest answers. This is the single most valuable input for Google, Bing and AI answers.
Product spreadsheet (name, price, HSN, tax, variants, stock), 2–3 photos per product, shipping rules, return policy, payment-gateway KYC ready.
Domain login, hosting login, existing analytics access, social page admin and business email. Missing accounts become the first recovery task.
Common questions
The scope can include editing or copywriting support. WhatsApp voice notes, existing brochures and the discovery call become the writing brief.
Only after a feasibility check. If a compressed schedule is possible, additional cost or reduced scope is documented before approval.
Small fixes during the agreed defect window are included. After that, maintenance moves to a retainer or a per-task quote - both transparent.
Yes. The quote and invoice state the project fee, applicable taxes and payment stages. Your accountant should confirm the tax treatment and any ITC eligibility for your business.
Get in touch
You do not need a technical brief. What the business does, who it serves, and the problem you have right now - that is enough to start.