Purpose and outcomes
The business problem, intended audience and useful project outcomes are stated clearly.
How it works
A clear website process, with visible decisions and purposeful communication.
Projects are organised around thoughtful written communication, defined responsibilities, visible decisions and scheduled conversations when talking will genuinely move the work forward.
Conversation remains part of the process and is used where it adds the most value.
01 · Before the project starts
Agree the essentials before work starts.
A clear agreement gives both sides a dependable basis for managing decisions, responsibilities and change.
Included scope
Pages, deliverables, integrations, content responsibilities and technical work are listed.
Boundaries
Exclusions, revision limits and assumptions are stated clearly so both sides are working from the same understanding.
Price and payment
The agreed price, payment stages and treatment of additional work are recorded.
Timetable and dependencies
The start date, working sequence, client inputs and realistic response windows are identified.
Ownership and handover
Account control, licensing, source materials and final handover are defined for the particular project.
02 · Communication
Written first. Calls when useful.
The asynchronous-first process keeps questions, decisions and feedback easy to find and review, while scheduled calls remain available for work that benefits from live discussion.
Written by default
Keep decisions easy to find and revisit.
- Questions and answers can be thought through properly.
- Decisions remain visible to everyone involved.
- Links, examples and documents stay attached to their context.
- Both sides can respond within agreed working windows.
- Diary time is reserved for conversations that genuinely benefit the project.
Calls when useful
Use calls where conversation genuinely helps.
- Initial discovery where the business is difficult to summarise.
- Complex decisions with several connected consequences.
- Visual or structural reviews that benefit from live discussion.
- Resolving genuine misunderstanding quickly.
- Agreed milestone conversations with a clear purpose and outcome.
The project route
A clear route from enquiry to handover.
The precise work changes with the project, while the route from first enquiry to verified handover remains clear.
Enquire
Share the current site, business context and reason for acting now.
Qualify
Check the likely service route, working fit, budget and timing.
Agree
Confirm the scope, responsibilities, price, timetable and boundaries.
Understand
Gather the business knowledge, evidence, content and technical context.
Make and review
Shape, implement and review the work at defined decision points.
Verify and hand over
Test the result, document the arrangements and complete the agreed scope.
03 · Feedback and change
Keep feedback clear, consolidated and purposeful.
A defined review process gives the project one consolidated response at each stage, makes unresolved questions visible and keeps changes deliberate.
How reviews work
- Review points are agreed in advance.
- The client gathers one consolidated response.
- Comments identify the problem as well as the preferred change.
- Decisions and unresolved questions are recorded.
- Agreed revision rounds remain within the project scope.
When the scope changes
New pages, changed objectives, additional integrations or major reversals are assessed before work continues. The effect on cost, timing and dependencies is explained so the client can make a deliberate decision.
Any change to scope is explained and agreed before additional work begins.
04 · Ownership and access
You keep control of your website accounts.
The written project agreement records the precise legal and licensing position, while the operational aim is clear client ownership and understandable access.
Client control
The business owns or controls the accounts on which the website depends.
- Domain registration
- Hosting account
- Business email and relevant service accounts
- Analytics and search accounts used for the project
- Final materials and documentation covered by the agreement
Working access
Access is granted for a defined purpose, kept proportionate and reviewed at handover.
- Credentials are shared through an appropriate secure route.
- Permissions are limited to the access the work requires.
- Temporary and supplier access is reviewed at handover.
- Important deployment and recovery arrangements are documented.
- The client receives a clear record of where the website lives and how it’s controlled.
05 · Shared responsibilities
Clear responsibilities on both sides.
Business truth and timely decisions.
Access to the right people, accurate facts, useful evidence, existing materials and consolidated feedback.
Judgement and a coherent route through the work.
Interpretation, structure, writing, visual direction, technical implementation, quality control and clear communication.
The agreed objective and working relationship.
Questions are raised early, dependencies remain visible and significant changes are agreed explicitly.
Start with the business context
You don’t need a finished brief to get started.
Share the current website, what’s changed and what the business now needs from it. I’ll respond with an initial view of fit, likely scope and the most useful next step.