Audit before scope
Access, architecture, content, data, team capacity, and blockers define the implementation plan.
DELIVERY PLAYBOOK
From an inherited website to an owned operating system.
The playbook connects discovery, brand, templates, Astro, GCP, measurement, verification, and handoff. This website follows the same process as a client migration.
- 1 week
- standard readiness audit
- 30 days
- founding installation window
- 6 templates
- shared public page families
- 1 owner
- required per client decision surface
The work is designed to survive handoff.
A migration is incomplete when only the pages moved. Brand rules, components, cloud ownership, publishing operations, and verification have to move with them.
Structured specification
Routes, components, APIs, data, models, analytics, ownership, and test evidence are explicit.
Shared templates
Layouts and components remove duplication while preserving page-specific intent.
Isolated delivery
Each engagement uses its own repo or worktree, branch, credentials, and cloud boundary.
Release gates
Types, build, routes, security, responsive behavior, and production readback are checked.
Operating handoff
The client receives source, cloud access, brand rules, runbooks, ownership, and a measurable baseline.
A named path from input to verified output.
The workflow is reusable because each stage has a purpose, owner, and observable result.
Discover
Inventory the current website, business, team, integrations, evidence, and risks.
Design
Define brand, information architecture, templates, data contracts, and migration scope.
Install
Build, migrate, connect, verify, document, and prepare the production cutover.
Improve
Monitor health, fix supported regressions, and add proven tools through an approved backlog.
The system must remain understandable after the engagement.
Client-owned by default
Production source, GCP resources, data, and runbooks stay under the client's control.
Evidence over completion claims
Build output, browser checks, data readback, and platform state show whether work is done.
Commercial boundaries stay visible
Every phase names included work, outputs, dependencies, exclusions, and additional rates.