Who is the website for?
Describe your most important customer group: where they are, which language they read, why they look for your service and what they need to know. Avoid asking the homepage to speak to everyone at once. New visitors often need the offer explained; existing customers may need information or support.
What should a visitor do next?
Choose a primary action for each type of page, such as learning about a service or making an enquiry. Connect that action to the content. Repeated purchase buttons cannot answer the questions of someone who has not understood the offer yet.
Who supplies the content?
Gather company details, service scope, contact information, brand assets and approved examples. Check image rights and client permissions. Do not pass off a design concept as real project work. If materials are missing, create a clear list rather than filling the space with unsupported figures.
Which languages can you maintain?
A multilingual website needs more than translated buttons. Service information, navigation, contact prompts and search descriptions all need consistent maintenance. Choose languages that reflect your audience and give each version a clear, shareable URL.
Which features belong in the first version?
Separate essential features from later options. A service website may need clear content and contact details. Booking, payments or member accounts introduce workflows, permissions and data. Understand actual use before adding complexity.
Who handles launch and updates?
Confirm domain ownership, hosting accounts, update methods, backups and maintenance responsibilities. For a redesign, map existing URLs and redirects. Launch is not the end of content work: changes to services and contact details need attention over time.
Prepare a one-page summary of your audience, primary actions, offer, languages, essential features and launch conditions. It is more useful than a requirement expressed only as a number of pages.