Define the business objective
Begin with what should become easier because the website exists. Perhaps potential customers need a clearer explanation of the service, the business needs better-qualified enquiries, or important information is currently scattered across social profiles and messages.
Describe the change rather than prescribing the layout. “Help local customers understand our three services and request a quote” gives the project a job. “Build a five-page website with a large slider” describes a solution before the problem has been explored.
Describe the audience and offer
Explain who the business is trying to reach and what those people need to understand. Include the confirmed service area, delivery model and important boundaries of the offer.
Avoid broad descriptions such as “everyone” unless the offer genuinely has no useful distinction. A clearer picture of the visitor helps the project decide what language, evidence and routes the website needs.
Identify the important visitor journeys
Think about the actions a visitor may need to complete. That might be understanding a service, comparing options, checking an area covered, viewing relevant work or making an enquiry.
Rank the journeys. A website can support several actions, but the quote needs to know which are essential at launch and which are supporting routes. This also helps determine whether one focused page is enough or whether genuinely different subjects need their own pages.
Gather the content you already have
List the available copy, photographs, logos, brand guidelines, reviews and project examples. Confirm that the business has permission to publish them and identify anything that still needs to be written or created.
Be candid about gaps. Final copy and usable brand assets affect the work required. A designer can propose structure around realistic content, but the quote should not silently assume that missing material will appear without time or responsibility attached to it.
List specialist functions and constraints
Mention booking systems, online shops, member areas, content management, analytics, existing domains, third-party services and any integration the website must use.
Also explain deadlines that have a real external reason, such as an event or business launch. A preferred date is still useful, but it should not be presented as fixed if the content and decisions needed to meet it are not yet available.
Separate must-haves from later ideas
Projects become difficult to quote when every possibility is treated as a launch requirement. Divide the list into three groups: essential for the website's first job, useful if time and scope allow, and possible future development.
This does not dismiss good ideas. It protects the work that matters now and gives later phases somewhere sensible to live.
Clarify accounts and paid services
Record who owns the domain, hosting and any existing website accounts. Mention paid fonts, plugins, booking tools, email services or other subscriptions the project may depend on.
The business should buy and control its own domain, hosting and paid services. The quote can then describe any setup or deployment help separately without hiding ongoing provider costs inside an unclear arrangement.
Explain how decisions will be made
Identify who will provide content, consolidate feedback and approve the work. A project with several stakeholders needs one dependable route for decisions.
This is not about limiting useful input. It prevents contradictory comments from arriving as separate instructions and helps the refinement stage stay connected to the agreed goal.
What the written quote should confirm
A useful quote or proposal should make the deliverables, assumptions, exclusions and total clear before work begins. It should explain the review process, responsibilities for content and assets, treatment of additional work and the intended handover.
If an important part of the project remains unknown, the document should say so rather than disguising uncertainty as certainty.
A compact preparation checklist
You do not need every answer before the first conversation. You need enough clarity to discuss the right problem and enough honesty to identify what remains undecided.
- The business objective for the website
- The audience, offer and service boundaries
- The most important visitor journeys
- Existing copy, images and brand assets
- Publication permissions for supplied material
- Required functions and third-party services
- Essential launch scope versus later ideas
- Domain, hosting and paid-service ownership
- A realistic timing constraint, if one exists
- The person responsible for consolidated feedback and approval