When a company commissions its first site, the real unease is often not the fee but having no idea what happens next. Without a clear view of how a build progresses, you cannot track status or know which materials to hand over and when. The result is endless back-and-forth, slipping dates, and a project that overruns both budget and months.
This article walks through each part of a typical website build as projects are usually run. Whether you are commissioning a site for the first time or comparing partners as a marketing lead, you will see the full path: eight stages from the first conversation to go-live.
Many first-time clients worry less about quality than about when they are supposed to act. Once those responsibilities are clear, half the project risk is already gone.
Eight-Stage Build Overview
Before the details, use this table to form a picture of the full production sequence:
| Order | Stage | Core work | Client input | Typical time |
|---|---|---|---|---|
| 1 | Discovery | Clarify business goals, features, and brand position | Share a profile, reference sites, and a budget range | 1–2 weeks |
| 2 | Quote and contract | Confirm scope, estimate cost, and sign | Approve the budget, sign, and pay the deposit | 3–5 days |
| 3 | Information architecture | Sitemap, content plan, and feature specs | Approve the structure and supply copy and assets | 1–2 weeks |
| 4 | Visual design | Homepage concepts, inner pages, and revisions | Review designs and send feedback | 2–4 weeks |
| 5 | Front-end build | Markup and styles, responsive layout, interaction | Mid-project review | 2–3 weeks |
| 6 | Back-end build | Admin tools, database, and third-party connections | Provide accounts and data needed for integrations | 2–4 weeks |
| 7 | Test and sign-off | Feature checks, device tests, and content proofing | Review page by page and submit one change list | 1–2 weeks |
| 8 | Launch and upkeep | DNS, go-live, and search setup | Confirm the launch date and provide domain details | 3–5 days |
As a guide to overall timing: a simple brand site often takes 6–8 weeks, a mid-size company site 8–12 weeks, and a large store or heavily custom system 12–20 weeks. In practice, the biggest delay is usually how fast the client supplies assets and approves designs, not the engineering itself.
Stage 1: Discovery Sets the Tone
This is the most important start of the build process. A capable partner uses it to understand the business: what you do, who you serve, whether the site is for brand presence, product display, or online sales, which reference sites you like, which features you need, and what budget and timing you expect.
Preparing these items speeds the conversation: a company profile, logo and brand colors, three to five sites you consider well done, a rough budget, and a hoped-for launch date. The more specific this stage is, the less likely later rework becomes.
Practical note: Unless you only want a page that “opens and that is enough,” state admin needs and features you may add within two years at the first meeting. The structure can then leave room to grow, so adding features later does not mean rebuilding at roughly double the cost.
If you are comparing partners, see how to judge a web design partner.
Stage 2: Quote and Contract
The partner turns the discovery notes into a scope and fee proposal. A clear quote should list: line items (pages and features), cost split (design, development, and annual fees apart), payment points (often 30% at signing, 30% at design approval, 40% at acceptance), a schedule, and contract points (intellectual property, warranty, and maintenance scope).
When reading a quote, do not look only at the total. Look at what is included and what is extra. Common add-ons include hosting, SSL, a cap on revisions, and charges for extra pages. Some clients signed a low initial quote, then faced a sizable extra fee for an English version after launch, so the real cost was higher. For more on fees, see how to assess a website design budget.
Stage 3: Structure and Content
This stage is drawing the plan before construction. Four outputs usually matter:
- Sitemap: every page and how they relate, the base of the build
- Wireframes: layout sketches for each page, focused on information, not visual style
- Asset list: copy, images, and video needed on each page
- Feature spec: admin needs, form fields, and similar details
The client’s main job here is to review the sitemap carefully so no page is missing, and to start preparing copy and images—often the slowest part. Partners usually provide a full asset list so you know what each page needs. For a corporate presence site, planning points for a company site can guide the content.
Stage 4: Visual Design
Designers turn the wireframes into visuals. A common design sequence is to set the overall style with the homepage, then extend inner pages after approval. Two or three homepage directions are often offered; after a choice, revisions begin. Contracts commonly include two or three rounds.
When reviewing, ask: Does the style fit the brand? Are color and layout comfortable? Is the information hierarchy clear? Are calls to action easy to see?
Decision-makers often get stuck on vague comments such as “it does not feel grand enough.” Concrete descriptions work better. If several people have opinions, one contact should collect them before replying. It is also common to approve a concept in the afternoon and reverse it after showing family at night. Bring every decision-maker to the first presentation and decide in the room.
Send all design comments at once. A cycle of “change a little, look, change a little more” is the most common way to stretch the schedule.
Stages 5–6: Front and Back End
After visuals are approved, engineering starts. Front-end work covers what people see: turning designs into markup and styles, building a responsive layout for phone, tablet, and desktop, plus motion and interaction.
Back-end work covers what people do not see: the content admin system, database, third-party connections (payments, logistics, APIs), forms, and member features. During development, front and back end often run in parallel to shorten the total time.
The client has less to do here, but still should: supply integration accounts and data on time; review any mid-stage demo carefully and comment early; and have copy and images ready instead of filling gaps at acceptance. The gap between custom builds and templates directly affects workload and timing in this stage.
Stage 7: Testing and Sign-off
Full testing is a production step you should not skip. It should at least cover:
- Feature checks: buttons, forms, and links all work
- Browser checks: Chrome, Safari, Firefox, and Edge look consistent
- Device checks: phone, tablet, and desktop layouts are correct
- Content proofing: no typos, and images are the right ones
- Speed checks: load performance via Google PageSpeed Insights
- Search basics: meta data, alt text, and sitemap are in place
Accept the site page by page and feature by feature, on both computer and phone. Collect every comment into one list and send it once, not as scattered messages.
Separate bug fixes from new requests. Anything outside the contract is extra work and needs a separate quote. A clear line keeps both sides comfortable.
Stage 8: Launch and Upkeep
Before launch, prepare DNS, an SSL certificate (HTTPS), Google Analytics and Search Console, 301 redirects (required for a redesign), and a final backup.
After launch: submit the sitemap to Google, watch the site closely (especially the first 72 hours), and start publishing content.
Many clients leave a new site idle, then notice six months later that competitors have redesigned twice. Upkeep usually covers hosting and domain renewal, security updates and backups, small content edits, and traffic tracking. To keep search value after launch, see design principles that support search. For an existing-site rebuild, a redesign guide is more specific.
Five Ways to Speed the Build
These habits make the build smoother and more efficient:
- Prepare assets early: start organizing copy, images, and logo files after signing, not when someone chases you
- Name one decision contact: avoid several people speaking at once; one person speaks outward
- Send design feedback in one batch: do not change color today, type tomorrow, and reverse it the day after
- Trust professional advice: design and engineering suggestions usually have a reason; respect makes the work easier
- Keep expectations realistic: a strong site takes time; do not expect a large-company result in two weeks
Common Questions
How long from start to launch? The full cycle depends on complexity: a brand site about 6–8 weeks, a mid-size company site 8–12 weeks, a large store or custom system 12–20 weeks. The biggest variable is how fast the client prepares assets and approves designs.
Do I have to write the copy? You should draft it, because you know the business best. A partner can polish wording and suggest layout, but the core should come from you so the message stays accurate. Unless you have no capacity at all, do not outsource all writing; the result often will not sound like the company.
How many design revisions are included? Contracts usually include 2–3 rounds. Extra rounds may cost more. Collect a full set of comments before each round so you do not burn the allowance.
Can we switch partners halfway? Technically yes, but handoff cost in the production process is high and often means starting over. Choosing carefully matters more than changing midstream. Unless there is a serious dispute, do not switch halfway.
Can we update content ourselves after launch? Yes. A proper project usually includes an admin system and a short guide, so publishing posts, swapping images, and updating campaigns can be done in-house.
What if we want new features later? You can add them, but that is extra scope and needs a separate quote. Thinking requirements through at the start of planning saves later cost.
Know the Process, Reduce Stress
Understanding the full build sequence helps you track progress, prepare early, cut rework, and avoid needless cost. A partner with a transparent process lets you see where you are and what comes next. To start from how sites are set up, read a primer on setting up a website.
Clarify needs, assets, and timing before formal work begins, and the project will run more smoothly.
