Our process
Good work starts with a clear agreement.
A defined scope, visible decisions and a useful handoff. Each stage has a purpose, a responsibility and a point at which both sides agree to move forward.
Project fit → Plan → Build → Review → Delivery → Operations
Project Fit
Is this the right work?
A short project note is reviewed before either side invests time in a full plan.
Your role
Shares the existing website, business context, service need, timeline pressure, and any access constraints.
Our role
Reviews the note against the services and responds with fit confirmed, a clarifying question, or a clear decline.
Ready to move on when: Both sides agree the project is worth planning in detail.
Project Plan
What exactly will be built?
The work is documented before billable production begins.
Your role
Provides business context, available assets, practical constraints, and approval of the written plan.
Our role
Prepares the project plan, exclusions, client responsibilities, estimate basis, and timeline assumptions.
Ready to move on when: The plan is approved in writing and work may begin.
Build
How does the work move without drifting?
The work follows the approved plan, with important decisions captured as the build progresses.
Your role
Provides approved content and answers decisions that cannot be resolved from the agreed project context.
Our role
Builds the site structure, page content, visual system, integrations, and support materials within the approved plan.
Ready to move on when: The planned build is complete and a preview is ready for review.
Structured Review
Does the build match the agreement?
Review checks the built work against the plan instead of opening an unlimited revision loop.
Your role
Reviews the preview for accuracy, completeness, functionality, representation, and plan match.
Our role
Addresses agreed corrections and identifies any new requests that need a separate decision.
Ready to move on when: Approved review items are resolved and final approval is given.
Delivery
What does ownership look like?
Launch includes verification, access transfer, and guidance the client can use after delivery.
Your role
Provides required domain or account access and confirms the delivery materials are received.
Our role
Launches the site, verifies the live version, delivers the guide, and explains the access and update steps.
Ready to move on when: The site is live, the guide is delivered, and the client has what is needed to manage it.
Operations
What happens after launch?
The client chooses Monthly Management or operates independently with what was included at delivery.
Your role
Chooses the support path that matches their internal capacity and expected update rhythm.
Our role
Defines monthly support where useful, or closes the engagement cleanly so any new work starts from a fresh review.
Ready to move on when: The ongoing path is active, or the project has a clean close.
Working together
Clear communication is part of delivery.
One written record
Email is the default communication channel so decisions, approvals, project changes, and access notes stay easy to find.
Milestone-based updates
Updates happen when the work reaches a meaningful point or when a decision is needed.
Decision prompts with context
When a client decision is needed, the request includes the question, the options, and the implication of each choice.
Start a conversation
Start with the situation, not a specification.
You do not need a complete technical brief. Describe what is happening today and what you want to improve.