Write down the job of the site.
Choose the main action a useful visitor should take: request a scope, call, book an appointment or purchase. Explain what must happen after that action. Your team needs a working process for handling the enquiry as well as a button on a page.
List the services and the questions people ask before buying. A service page should help someone judge fit, understand the next step and know what information to provide.
Gather the material you own.
Collect approved logos, brand files, photographs, service descriptions and any client work you have permission to show. Name the person who can verify prices, credentials, dates and operating arrangements. Keep sensitive customer records out of the initial brief.
For an existing site, identify important pages and links that should continue working. Provide authorised access through a secure process when it is needed. Avoid sharing passwords through a public enquiry form.
Identify the functions and costs.
Payments, booking, account logins, newsletters and file uploads each bring additional requirements. Describe the actual workflow and the systems currently involved. The proposal should explain what is included, what is integrated and which subscriptions or transaction fees remain your responsibility.
Agree who writes and approves the content. Identify image licensing, hosting, domain renewals and maintenance costs. A page count alone cannot describe the complexity of the project.
Agree the handover and checks.
Ask what source files, access and documentation you receive. Decide who maintains the website and what support is available after launch. Before publication, test the mobile navigation, links and enquiry route with clearly labelled test activity.
Our Studio Desk helps organise the initial requirement. It produces a downloadable brief from your inputs. Submitting an enquiry is a separate action, and a final quotation follows the agreed scope.
