web-build-deliverylisted

# Web Build Delivery ## Overview Website projects fail on two things, and neither is code: **scope that was never defined precisely** and **content the client never delivered**. Both are predictable and both are preventable at the contract stage. The delivery discipline is: fix the page count, collect content before design starts, cap revisions, and treat launch as a checklist rather than an event. ## When to Use - Scoping or quoting a website project - Building a marketing site for a client - A project has stalled on content or scope - Preparing a site for launch or handoff Don't use for: single conversion pages for campaigns (use `landing-page-and-funnel-build`) or brand identity (use `brand-and-design-system`). ## Scope Control **Quote by page count and template count, never by "a website."** The contract must name: - Exact page list, with the count stated numerically - Number of unique templates (a 20-page site on 4 templates is far less work than 20 unique pages) - Number of revision rounds included — **two is standard** - Who writes the copy, explicitly - Who supplies photography, explicitly - What "done" means for each page - Hourly or per-page rate for anything beyond scope - What happens if content is not delivered by the stated date **The content clause is the most important line in the contract.** Add: if content is not delivered within N days of request, the project pauses and resumes at the next available slot, with the deposit non-refundable. Without t