Frame
Clarify the business outcome, audience, constraints, owner inputs, and disqualifying conditions.
CONNECTED ACCOUNTABILITY
The person defining the architecture stays responsible for the build.
The process is designed to expose risk early, prevent anonymous handoffs, and leave the client with an understandable operating system.
Architect
Define the content model, user paths, data boundary, providers, fallbacks, and migration path.
Construct
Build semantic pages, typed configuration, isolated dynamic routes, and editable visual assets.
Verify
Test accessibility, performance, security, resilience, content, and the JavaScript-disabled path.
Launch
Deploy into client-owned accounts with usage caps, monitoring, rollback, and recovery instructions.
Operate
Maintain through SITEBORNE Care or transfer through the documented operating system.
Decision record
Major architecture, provider, scope, accessibility, security, and exclusion decisions are documented.
Fresh-clone rule
The base site installs, runs, builds, and demonstrates modules without paid credentials.
Acceptance rule
No launch occurs with a broken build, exposed secret, inaccessible primary journey, fabricated claim, or undocumented third-party cost.
Begin with useful context.
The project brief creates a reviewable record before a consultation is offered.
Start the project brief