Define the outcome
We begin with the user need and the deliverable: pages, interactions, content, integrations, ownership, and acceptance conditions. A shared scope prevents misunderstandings about what a finished delivery includes.
We distinguish agreed requirements from optional ideas, identify the person responsible for supplying content and approvals, and confirm the target devices and primary visitor journeys.
What a website delivery does and does not include
A public information website can include pages, navigation, enquiry links, installable access, and selected offline support. It does not automatically include user accounts, private records, a ticket-management service, payment processing, or ongoing monitoring. We name any external service that is part of the agreed result.
We do not describe a visual form or button as a working service unless the required processing and support arrangements have actually been connected and tested.
Review changes responsibly
When a request changes the agreed outcome, we review its impact on timing, cost, privacy, accessibility, and maintenance before implementing it. A useful change record explains the request and decision rather than silently expanding the work.
Acceptance and handoff
We compare the delivered result against the acceptance criteria, test the important journeys, identify remaining limitations, and confirm who owns future updates. Ongoing support, service-level commitments, and content maintenance are included only when agreed.