You do not need to choose the technology first
You do not need a long technical document before contacting a website developer. Start with your business, the people visiting the site and what you want them to do. The details below help both sides understand the same request and reduce avoidable revisions.
1. What is the website for?
Choose the main purpose: introduce the business, receive service enquiries, present products or sell online. A service business may need visitors to understand an offer and email a question. A shop may need a catalog, checkout and an order handling process.
Avoid requesting every feature you have seen elsewhere. Separate launch requirements from additions that can wait.
2. Who will visit and who will update it?
Describe your main audience: what do they look for, which devices do they use and do they need English content? Also decide who approves copy, posts articles and responds to enquiries.
If marketing staff need to update content, ask what they can edit, what guidance is included and whether a developer is needed to add a new page.
3. Which pages do you need?
A business website often includes home, about, services and contact. Articles, careers, products or project pages depend on the business. Write one sentence for each page explaining what readers need to find.
Share reference websites with reasons: readable layouts, clear menus or useful service descriptions. “Make it like this site” can leave the actual work unclear.
4. Is the content ready?
Check your brand name, logo, business introduction, service details, images and contact channels. Mark what is usable, what needs editing and what needs writing. Use only assets you have permission to publish.
For two languages, agree who writes, translates and approves. Do not wait until design is complete before preparing content.
5. Which features need explanation?
Describe use rather than just a name. “Staff save drafts and a manager approves them” is clearer than “admin included”. For enquiries, explain the information needed and who should see it.
For software connections, name the existing tool and the data you want transferred. Do not send passwords or access keys in a quotation request; permissions can be arranged later.
6. Which costs should the quotation cover?
Ask about design, development, writing, images, domains, hosting, paid tools and support after handover. A low initial price may exclude work you need. Compare quotations against the same task list.
Share preferred timing and a budget range if known. If the budget does not cover everything, agree on the first priorities.
7. What should you check at handover?
- Do pages, content and features match the agreed list?
- Can visitors read and use the site on a phone?
- Do phone, email and other links work?
- Can you use the agreed updating features after guidance?
- Are accounts, code, assets and ongoing costs clear?
Start with a short email
Include your business, services, reason for the site, required pages and preferred timing. Add an old site or references if available. You can still send an enquiry with some details missing.
Request a website quotation or see the service and indicative pricing.