A consultancy selling Rapid Web Build services cannot ship its own marketing platform as a technically indebted asset. If the methodology works, the firm’s own site must prove it: TDD-first, zero JavaScript by default, edge-deployed, and with a test suite that passes.
The Architectural Pivot
The decisive choice was applying TDD-first governance to what is normally treated as a marketing project. Every component was written RED→GREEN via Playwright E2E, producing a platform with a passing test suite that proves it works rather than one that appears to. Architecture compounds the governance: Astro’s zero-JS-by-default makes the Lighthouse baseline structurally inevitable, GEO semantic structure was baked in from sprint 1, and Cloudflare Pages edge deployment required no runtime configuration. Sub-24-hour deployment is a byproduct of architectural clarity, not a sprint constraint.
The Friction
The primary friction is cultural: enterprise governance disciplines (TDD, zero-JS defaults, semantic structure) are consistently treated as overhead on marketing projects. The industry default of retrofitting accessibility, adding tests post-launch, and treating performance as a post-build audit is itself an architectural decision. It produces platforms that cannot be confidently modified, cannot be handed over cleanly, and cannot serve as evidence of methodology.
The Rulebook
- A marketing asset without engineering governance accrues the same categories of technical debt as production software. Build marketing platforms to the same governance standard as the software they are designed to sell.
- Rapid delivery is a byproduct of architectural discipline, not a substitute for it. Speed at the cost of governance produces a deliverable that cannot survive its first maintenance cycle.
- Prove your methodology on yourself before asking clients to trust it on their systems. The platform is the credential.
