Define what customers need to do
Choose the main tasks: read a menu, request a quote, make a booking or buy a product. Provide the business facts, photographs and languages needed for those tasks before agreeing the build scope.
Agree features and responsibilities
Confirm pages, content ownership, accessibility, hosting and integrations. A booking form and a payment checkout require different testing and maintenance. Identify who approves text and who can change it after launch.
Set a project-specific schedule
Missing text, photography or translations can affect the timetable, as can integrations needing testing. Agree review points and a launch plan for this project rather than relying on a universal delivery promise.
Plan launch and ongoing care
Test contact paths, mobile use and recovery before release. Agree backups, software updates, renewals and content changes. A website can help customers find information, but neither a new design nor technical SEO guarantees enquiries or rankings.
Questions about this guide
What should I prepare before the first conversation?
Bring a short description of your business, the people you want to reach and the action you want visitors to take. Existing branding, photos and examples of websites you like are helpful, but you can still start a conversation if some material is missing.
Do I need bookings or a shop on my website?
Start with what your customers actually need to do. A clear inquiry route may be enough for some businesses; others need bookings or purchases. Discuss those needs early because they affect the content, testing and ongoing work.
Who will update the site after launch?
Agree this before the site goes live. Decide who changes prices, opening hours, photos and translated text, and who handles maintenance. Ask what is included in the proposed arrangement and how additional work will be agreed.