The web design process is one of the least transparent things in the professional services world. Agencies quote a number, a timeline appears, and then weeks of back-and-forth happen without a clear sense of what stage you are at or what is expected of you. After seven years of building sites for small businesses in the US, UK, and Switzerland, we have learned that most project delays and client frustrations trace back not to design taste or technical difficulty, but to a process that was never explained at the start.
This is what a well-run web design project for a small business actually looks like — and, more usefully, what it should not look like.
Why the “discovery call, then quote” order is backwards
Most agencies lead with a sales call and follow with a proposal. The proposal is based on a 30-minute conversation and a look at your existing site. What this produces, reliably, is a quote for a site the agency thinks you want rather than the site your business needs. The difference shows up at the brief stage, when you discover that the scope you agreed to does not include the features you assumed were standard, or includes features you will never use.
A better sequence starts with a structured discovery document before any pricing conversation. The document covers what the site needs to do for your business, who the primary audience is, what actions you want those visitors to take, and what the competitive landscape looks like online. Once that document exists, a quote is a meaningful number rather than a best guess.
Stage 1: discovery and strategy (weeks 1–2)
Discovery is the most undervalued stage of the web design process for small businesses. It is also the one most often billed at zero, which is part of the problem. When discovery is free, it is short. When it is short, the brief is thin. When the brief is thin, the design goes in the wrong direction and revisions pile up later.
At minimum, discovery should produce: a clear statement of the site’s primary business goal (not “look professional” — something measurable, like “generate 20 quote requests per month”), a defined primary audience and what they need from the site, a competitive analysis of three to five sites in your category, and a site map that both parties have agreed to before design starts. If you are entering a design process and none of these have been discussed, ask for them before anything else moves forward.
Stage 2: content and structure (weeks 2–3)
Content before design. Not design first, content later. This is the single most important sequencing decision in the entire process, and it is the one most often skipped.
When a designer builds pages before the copy exists, one of two things happens. They use placeholder text (Lorem Ipsum), which means every spacing, font, and layout decision is made for words that will be replaced. Or they use the client’s old copy, which means the new site inherits every structural problem of the old one. Neither produces a site that is designed around what the business actually needs to say.
Content work at this stage means: drafting or reviewing all headline copy, writing the key service and about page text, gathering testimonials and case study material, and identifying what photography or imagery is needed. A client who says “I will sort the copy after we can see the design” is a client whose project will run four to six weeks over schedule. In our experience, content delays account for about 70% of timeline overruns on small business web projects.
Stage 3: design and build (weeks 3–6)
With discovery complete and content drafted, the design and build stage has a fighting chance of going smoothly. Without those prerequisites, this stage is where the project starts to slide.
What should happen: the designer presents a homepage or key template design for approval before building every page. This is a one-round decision point, not an open-ended iteration session. Feedback at this stage should be structural (“the services section should appear before the about section”) rather than cosmetic (“I think I prefer a different shade of blue”). Cosmetic preferences at the template stage are fine; cosmetic preferences on page 12 of a 15-page build are expensive.
What to watch for: agencies that build everything then present the whole site for review at the end. This feels efficient but it front-loads all the risk. If the design direction is wrong, you find out late and pay for revisions to a complete build rather than a single template.
Stage 4: review, testing, and pre-launch (weeks 6–7)
Review is not an open revision window. It is a defined round of structured feedback with clear scope. A well-run project will define this upfront: one or two rounds of revisions included, additional rounds at a day rate. This is not stinginess — it is the mechanism that keeps a project from expanding indefinitely while protecting both sides from unrealistic expectations.
Testing at this stage covers every form submission across three devices (desktop, iOS, Android), all links (internal and external), page speed on PageSpeed Insights, the checklist items in our small business website checklist, and a cross-browser check on Chrome, Safari, Firefox, and Edge. Mobile rendering on real devices, not emulators, for the most critical pages.
Stage 5: launch and handover (week 7–8)
Launch day is quieter than most clients expect. DNS propagation takes 24–48 hours. The new site is not instantly live for every visitor the moment you point the domain. What matters more than the launch moment is what happens in the two weeks after: monitoring for 404 errors (especially if you have changed URL structures from a previous site), setting up 301 redirects for any old URLs that still have backlinks, verifying GSC is indexing the new site, and submitting the sitemap.
Handover should include: admin access credentials, a short recorded walkthrough of how to update the core content types, documentation of any third-party services connected to the site, and a clear statement of what support is included and for how long.
What a realistic timeline looks like
A five-to-eight-page small business site, done properly, takes four to eight weeks from signed brief to launch. Anything less than four weeks is either a template build with minimal customisation or a project skipping the discovery and content stages. Anything more than ten weeks, for a standard small business site, suggests a process problem rather than a complexity problem.
If you want a partner who follows this process rather than a faster version of it, our affordable web design for small businesses covers every stage above as standard. Discovery, content review, template approval, and full launch support are included — not extras. And if the next question is how to get traffic to the site once it is live, our small business SEO services are built to pick up exactly at that point.
Use our small business website checklist alongside this process guide — it covers every technical and SEO check that should be completed before handover. For ongoing visibility after launch, our small business SEO checklist is the logical next step.
Red flags in web design proposals and agency pitches
The web design process for small businesses goes wrong most often before a line of code is written — at the proposal stage. After seven years of working with clients who have been burned before, the patterns are consistent. Here are the ones worth knowing.
How much does web design cost for a small business?
The range people find online is unhelpfully wide. “Anywhere from $500 to $50,000” is accurate and useless. Here is the range that applies to a professionally designed, properly built five-to-eight page small business website — the kind that will perform rather than just exist.
Freelancers from platforms like Upwork or Fiverr: $300-1,500. The quality variance is enormous. The most common outcome is a site that looks fine and performs poorly — no SEO setup, no documentation, no support after handover. Specialist small business agencies: $1,500-6,000. This is where the economics make sense for most small businesses — professional process, proper technical setup, and a team you can return to. Mid-market agencies: $6,000-20,000. Often the right choice for complex sites, e-commerce, or businesses that need ongoing retainer work. Enterprise: $20,000+. Almost never appropriate for a small business first site.
The number almost every quote leaves out: the cost of the process going wrong. A project that runs three months over schedule because content was not ready costs you in opportunity. A site that needs rebuilding after 18 months because the brief was wrong costs you the entire first investment. The process stages in this guide exist to prevent both.
How to give feedback your designer can actually use
Design feedback from clients tends to arrive in two broken forms: too vague (“I want it to feel more premium”) or too specific and wrong (“can you make the logo 40% bigger”). Neither moves the project forward. The useful kind is structural: it identifies what is not working for the business goal, not what the client personally prefers.
Structural feedback — the useful kind — sounds like this: “The services section is below the fold on mobile, which means most visitors never see it. Can we move it up?” or “The contact button is not visible until the user scrolls to the bottom. Given that our primary goal is enquiries, it should be persistent in the header.” This tells the designer what problem to solve. Cosmetic feedback — the kind that derails projects — sounds like this: “I am not sure about the blue” or “my spouse thinks we should use a different font.” These are opinions, not problems. Address structural problems first; save cosmetic preferences for the final review round.
One practical rule for review meetings: for every piece of feedback, state the business reason. If you cannot state a business reason, the feedback is probably cosmetic and should wait.
