A clear scope. A shared understanding.
The practical details we discuss before starting a website project. Your agreed proposal defines the work, costs and responsibilities.
Discuss your project ↗
Before work begins
We discuss the brief and prepare a scope that identifies the deliverables, responsibilities and review points. An enquiry alone is not a booking or acceptance of a quotation.
- Pages, functionality and exclusions recorded
- Content, assets and approvals assigned
- Costs, payment milestones and timing agreed in writing
Reviews and changes
Give feedback against the agreed scope, with one consolidated list and a nominated approver. A request that changes the agreed work needs a discussion about cost and timing.
- Review the design and functional requirements
- Record approved decisions in your project portal
- Agree additional work before it begins
Ownership and handover
Domain, hosting, licences and third-party services have their own owners, costs and conditions. We clarify access and handover arrangements for the specific project.
- Approved accounts and access arrangements
- Licence and recurring service costs identified
- Maintenance and future changes discussed separately
Keep the conversation useful
Your project reference helps connect a request to its brief. The portal keeps shared progress and messages together, while private owner notes remain separate.
- Use your reference when asking about a project
- Keep passwords and access codes out of ordinary email
- Ask when a scope or responsibility is unclear
Tell us what you need.
Start with your business, your priorities and the details you know. We can discuss the rest together.
Start a project brief ↗