What should you prepare before requesting a website quote?
You do not need to arrive with a technical specification. Explain what the company does, whom it should reach and what currently prevents enquiries or sales. A short brief with concrete examples helps discuss priorities and compare proposals addressing the same problem.
Start with an outcome and a real person
Instead of asking only for a modern website, describe a situation. For example, a maintenance manager needs support, wants to confirm the service area and must send photographs of the problem. This scenario informs the pages, form and response. Choose one main action and explain how the team recognises a useful enquiry.
Separate existing content from missing content
List services, projects, photographs, approved testimonials and available materials. Identify who writes, reviews and approves them. Missing content can affect the schedule more than the page count. For multiple languages, decide who validates each version and how it will be updated after launch.
- The website's objective and priority audience.
- Three questions customers ask before buying.
- Services and projects that deserve prominence.
- Available and missing content, with its owner.
- A preferred date and any event that makes it relevant.
Explain what happens after the click
Describe where enquiries arrive and who handles them. Include CRM, bookings, payments or required documents. Explain who edits the website and how often. If a platform already exists, share the public URL and its limitations; technical access can be arranged later. An integration should be estimated by expected behaviour, not simply the supplier's name.
Compare scope, handover and support
Ask proposals to distinguish implementation, content, recurring costs and out-of-scope work. Confirm what is delivered, how it is approved and who owns maintenance. A lower price may include less editorial work or fewer integrations. Comparison becomes useful when each cost maps to a responsibility and a verifiable result.
Frequently asked questions
Do I need to choose technology first?
No. Describe goals, functions and constraints. The technical choice should be explained in terms of those requirements and who will maintain the website.
Should I include a visual reference?
Yes, with an explanation of what you like: clarity, structure, photography or tone. A reference does not need to dictate your entire website.
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements