DIRECT ANSWER
A website build pays for nine stages of work: discovery, structure, content, design, build, search and sharing setup, testing, launch and handoff. Visitors see only parts of three of them: the content, the design and the build. The rest decides whether what they see is right. Experience shows most in what a builder leaves out and in the failures they prevent.
Key terms
- Build work
- All the work in a website build: discovery, structure, content, design, build, search and sharing setup, testing, launch and handoff.
- Visible work
- The parts of a build a visitor sees directly: the words, the design and the pages as they appear on screen.
- Underlying work
- The build work a visitor never sees directly, such as discovery, structure, testing, launch and handoff, which decides whether the visible work is right.
- Proposal basis
- The set of written commitments a website proposal makes in discovery, customer experience, content, functionality, testing and handoff. Full entry: Why Page Count Is a Poor Way to Compare Website Proposals
The visible part of the work
A visitor sees a website's design and its words. The owner who commissions it usually judges the work by the same two things, often from a mockup. Most of the work in a website build sits beneath them: deciding who the site is for, what each visitor needs, which facts are true, how each action reaches the business and whether everything works on every device. That underlying work decides whether the visible part is right.
Judging by appearance has a known weakness. The aesthetic-usability effect is the tendency to perceive an attractive design as easier to use, and it can lead reviewers to overlook real problems [1]. A mockup can be approved in minutes. Whether the site behind it serves the business takes the rest of the project to establish.
What the build work includes
| Stage | What it produces | Visible to a visitor? | What goes wrong when it is skipped |
|---|---|---|---|
| Discovery | An understanding of the customers, their pathways and the business's facts | No | A site built for the wrong customers or decisions |
| Structure | A page plan, an action inventory and a link map | Indirectly, as navigation and links | Visitors cannot find their next step |
| Content | Researched, written and approved copy and catalog entries | Yes, as words | Generic or inaccurate claims |
| Design | A visual system, layouts and imagery that belong to the business | Yes | A generic look and an unclear order on the page |
| Build | Code, responsive layouts, forms and connections to outside tools | Partly | Pages that break on phones and forms that fail |
| Search and sharing setup | Page titles, descriptions, structured data and a sitemap | In search results and link previews | Poor previews and data that disagrees with the page |
| Testing | Evidence that each layer of the site works | No | Failures discovered by customers |
| Launch | The domain connected, old addresses redirected and the live site checked | No | Lost pages and broken links |
| Handoff | Accounts in the owner's name and documentation | No | An owner who cannot change or move their own site |
Three of the nine stages are visible to a visitor, and only partly. The rest are the reasons the visible stages are correct. Google's guidance supports several of the invisible ones directly: it recommends a distinct description for each page so search previews are accurate [2], pages served securely and readable on phones [3], and a mapped, redirected move when a site replaces an older one [4].
How expertise shapes what gets built
Experience shows most clearly in decisions about what to leave out. A page nobody needs, a tool the business cannot keep running, a form field that changes nothing and a claim the business cannot prove each add cost to build and cost to maintain. An experienced builder removes them before they are built, and the result often looks simpler than an inexperienced one: fewer pages, fewer buttons, shorter forms.
Experience also knows where projects fail. Inquiries that never arrive, redirects that loop, embedded tools that break on phones and facts that drift between pages are predictable failures with known checks. Standards add a third layer of knowledge: accessibility targets set out in WCAG 2.2, with each success criterion assigned to level A, AA or AAA [5], and the search guidance that applies to every public page.
Costs that sit outside the build
A website build is one cost among several. The domain registration, hosting, outside tools such as booking or ordering software, and ongoing maintenance each carry their own charges, sometimes paid to different companies. Comparing what a build includes, and what remains the owner's to pay or manage, is covered in comparing website proposals and costs.
Applications
An electrical contractor's approved mockup
Illustrative example. An electrical contractor approves a homepage mockup in one meeting. The work that follows is mostly invisible to him: an emergency pathway that puts the phone number first on every page, the license information placed where a homeowner checks it, a service area statement before the quote form, a catalog entry on whether a panel upgrade needs a permit, a quote form routed to the dispatcher and a test of every page on the phones his crews carry. The finished homepage looks almost exactly like the mockup. The difference is in what happens when a homeowner uses it.
A dance studio's simple design
Illustrative example. A dance studio's new site has a simple, bright design. Beneath it, the class schedule is embedded from the studio's management software so it never needs retyping, registration hands off to that software, liability waivers go to the software's secure forms, a catalog answers parents' questions about recital costs and dress codes, and every page offers a trial class. The design took a fraction of the project. Families experience the rest of it every week.
Limits and edge cases
- Smaller projects. A one-page site still passes through every stage, at a smaller depth. Discovery may be a single conversation; testing may take an hour.
- Doing the work yourself. An owner who builds their own site takes on the underlying work as well as the design, as covered in building it yourself or hiring a designer.
- Claims of expertise. Expertise is shown by specified commitments and finished work. A proposal that describes the underlying stages in checkable terms, as described in why page count misleads, is stronger evidence than a statement of experience.
- Prices. This entry describes the work. Prices are set in a written proposal, and they vary with the complexity of the project.
How So It Sticks applies this
Our process runs from brief to direction, concept, build and launch, and the statement of work lists the underlying work at each stage, so the parts a visitor never sees can still be checked. Start a Project Brief, and see our plans for how builds are scoped.
Sources and method
The stage table, the examples and the analysis of expertise are So It Sticks editorial frameworks. The examples are illustrative and describe no real business. Each linked source supports only the statements numbered beside it. Sources verified October 15, 2026.