Describe the goal and audience
State the main outcome you want: relevant enquiries, appointment requests, sales or a clearer explanation of your work. Describe the people visiting the website and the questions they usually ask. If different audiences need different information, identify that early so the page structure can accommodate them without becoming confusing.
List the real pages and services
Write down the pages you need and the services each page must explain. Include contact methods, languages and any content that should remain from an existing site. If a page is only an idea, mark it as optional. This helps separate a useful first release from features that can be added later.
Gather approved assets
Share your logo files, brand colours, approved photographs and existing text. Say which images belong to which service. Identify anything that is only a reference and should not be copied or presented as your work. A short asset list prevents visual mismatches and reduces time spent guessing what is current.
Define functions in plain language
Instead of asking only for a “smart form”, explain where the enquiry should go and what the visitor should see. Describe whether you need editing access, payment, booking, multilingual pages or a WhatsApp draft. Note any existing tools or accounts involved so that access and integration requirements are understood before development.
Agree review and launch responsibilities
Name the person who approves content and collect feedback in one place. Discuss the expected review stages, domain and hosting access, ownership of files and post-launch support. Avoid treating an unapproved estimate as a final commitment. A written scope and a simple launch checklist keep the project easier to manage.
A quick checklist
- Explain the visitor and the desired action.
- Separate required and optional features.
- Confirm content, access and approvals.