Introduction
Most web projects fail for the same handful of reasons: unclear scope, no owner, and a build nobody can maintain. This playbook sets out how we run projects so those failures don't happen.
Who This Is For
Founders scoping a first product, operations leads replacing a legacy internal tool, and owners of local businesses whose website no longer brings in work. If you are about to commission a web project, this is the briefing document we wish every client had read first.
What Makes Projects Fail
Scope agreed verbally. A designer and a developer who never speak. Plugins stacked to cover missing functionality. No performance budget, no analytics, no documentation. Each of these is avoidable, and each one is avoided by a decision made before the build starts.
How to Use This Playbook
Read the stage that matches where you are. If you have not started, begin with Discovery. If you already have a brief and quotes in hand, skip to Build and Launch to check what your supplier has and has not included.