How Long Does a Business Website Take? An Honest Timeline
Realistic planning timelines for one-page, business, dynamic and e-commerce websites — plus what actually slows projects down and how to keep yours fast.

Short answer: A simple one-page website is usually ready in about a week. A small business website typically takes two to four weeks. A site with a blog, portfolio or frequently changing content runs closer to four to six, and an online shop or custom integration can take six weeks or more. These are planning estimates, not guarantees — the single biggest variable is how quickly your content and decisions arrive.
Why timelines differ so much between projects
Two projects with the same page count can take very different amounts of time. What actually moves the schedule:
- Content readiness — text, photos, logo and product data. This is the number one factor, ahead of anything technical.
- Scope clarity — a written scope with a fixed page list moves fast; a vague “I need a website” needs discovery time first.
- Feedback speed — designs wait in your inbox, not in ours. Slow approvals stretch the calendar more than slow development does.
- Number of decision-makers — one approver is quick; a committee adds days between every step.
- Integrations — payment gateways, booking systems, stock feeds or anything that talks to another system adds testing time.
What actually happens, step by step
Every professional website project follows roughly the same arc — the difference is how long each stage takes:
- Scope and discovery (a few days) — a conversation about goals, pages, features and content. This ends with a written proposal: scope, price and a planning timeline.
- Content preparation (often the longest stage) — gathering or writing text, choosing photos, collecting product details. It overlaps with design but gates development.
- Structure and design (about a week for small sites) — page structure first, then visual direction. You see and approve the direction before build starts.
- Development (one to three weeks depending on size) — the approved design becomes real pages, responsive on all devices, forms and integrations wired in.
- Review and revisions (a few days) — structured feedback rounds within the agreed scope. Two rounds is typical and honest.
- Testing and launch (a few days) — real devices, forms tested end to end, domain and analytics connected, search basics verified.
Realistic ranges by project type
Based on the way these projects actually unfold — again, planning estimates rather than promises:
| Project type | Typical range | What drives it |
|---|---|---|
| One-page website | ~1 week | Single focused page; fast when copy and images are ready |
| Small business website | 2–4 weeks | A handful of pages, contact form, basic SEO — content speed sets the pace |
| Dynamic site (blog / portfolio / frequently updated) | 4–6 weeks | Templates for content types plus editor training and content migration if any |
| E-commerce / custom integrations | 6+ weeks, scoped individually | Product data, payment and shipping setup, and real transaction testing |
At NIGHTGLYPH these map roughly onto our packages: a one-page site starts at ฿4,900, a business website at ฿9,900, a dynamic build at ฿14,900 — with scope confirmed in writing before anything starts. For cost context beyond the build itself, our guide to website costs in Chiang Mai separates the one-off build from the running costs.
What actually makes projects slow
Rarely the coding. The delays we see most:
- Content and images not ready — the design is done but there is nothing to put in it. Weeks evaporate here.
- Scope changes mid-build — “can we also add a shop?” after development has started reopens structure, design and testing.
- Too many approvers — when three partners must agree on every headline, every round doubles.
- Integrations and product data — supplier feeds, payment paperwork and messy spreadsheets take as long as the build itself.
None of this is dishonest on either side — it is just how projects behave. A good proposal names these risks instead of pretending they do not exist, which is also what our business website checklist is for.
How to make it fast without cutting quality
You cannot compress a build by asking for it to be faster, but you can remove every avoidable wait:
- Decide the one person who approves work — before the project starts.
- Prepare text and photos while the proposal is being written, not after.
- Answer within a day or two at each review point; silence is the schedule-killer.
- Fix the scope in writing, then hold it — put new ideas into a phase-two list.
- Be honest about content: if you will not write it, say so early so copywriting can be scoped instead of discovered.
Checklist before the clock starts
- Do I know what pages the site needs, at least roughly?
- Is my text ready — or do I need help writing it?
- Do I have usable photos and a logo, or does that need arranging?
- Who has final approval on design and copy?
- Do I need integrations (payments, booking, LINE) — and do I have the accounts and paperwork for them?
- Have I allowed time each week to review and respond?
If the honest answer to several of these is “not yet”, that is normal — it just means the timeline starts with preparation, and a straight proposal should say so.
Summary
Figure on about a week for a one-page site, two to four weeks for a small business website, and longer for shops or custom integrations — with content readiness moving the calendar more than any technical work. The fastest projects are not the rushed ones; they are the ones where decisions and content arrive on time.
Next step: Tell us what you are planning through the contact form or by email — we reply with a scoped proposal and a realistic timeline, not a promise. Or browse our services and business website pages first. Still weighing the platform? Is WordPress right for your business? covers that decision honestly.
Want a website that fits the business
Tell us the goal and constraints — get a clear proposal before deciding.
Talk to NIGHTGLYPH

