One quotation says “business website”, another “bespoke web design”. Both list five pages. Yet the first may include finished copy while the second covers design only. The lower total does not tell you which is better value for your actual project.
Describe the project before requesting a web design quote
A website quotation benefits from a short description of what visitors should achieve. Suppose a trades business wants to explain three services and receive suitable enquiries. A homepage and three service pages may share a template, while an enquiry form needs its own inputs, error states and confirmed delivery. “Five pages” hides that difference. Describe the distinct page types and specific functions separately before comparing total prices.
Also record what already exists. Approved wording, usable photographs and an established brand are different starting points from rough notes and unedited images. If an agency must first structure or create the material, that work belongs in the scope. A cheaper quotation may simply assume that you will do exactly that preparation yourself.
Anyone preparing a web design offer or looking for a quotation template therefore needs a traceable structure: starting point and goal, deliverables and functions, required contributions, review and handover, and one-off versus recurring costs. That template is a working basis for the service description. The actual agreements must fit the project and cannot be created merely by replacing the company name.
Establish a common basis
You can make the quotations comparable by defining the outcomes you need first, then mapping each supplier’s information to those outcomes. A reference to the quoted item makes that mapping traceable. If an item remains unclear, leave the field open: “not mentioned” means neither included nor excluded.
| Deliverable | Ask both suppliers |
|---|---|
| Service pages | Which templates and how many completed entries will be created? |
| Text and images | Who creates, edits and enters the material? |
| Enquiry flow | Where is the message stored or delivered, and what feedback does the sender receive? |
| Content editing | What can your team change later, and with which roles? |
| Handover | Which files, accounts and instructions will you receive? |
Use the same example for functionality. For instance, an enquiry covering two requested services must reach the responsible team. This helps establish whether both quotations cover the same flow.
Included, optional or your responsibility?
Labelling each row as included, optional or your responsibility reveals whether one agency is quoting for a complete project while the other expects you to handle content or setup.
An optional item becomes necessary for the comparison if the website cannot perform its agreed task without it. Add that item to the comparable scope. Keep later wishes separate. Also consider your team’s time, without presenting it as an external invoice cost.
For evaluation work, ask which pages and flows are examined and how findings are addressed. The W3C planning guidance places accessibility within responsibilities and regular assessment. You can compare that scope; “accessible” on its own leaves these questions open.
Agree feedback and evaluation as actual work
For revisions, it should be clear what is being revised and how feedback is consolidated. One coordinated response to an agreed design differs from several new design directions after development begins. Ask when your team makes decisions and what happens if wording or product information later changes substantially. Changes can then be discussed without automatically treating every question as new work or unlimited included work.
The specific enquiry journey described in the brief also provides a basis for evaluation. It includes normal input, a missing required field and feedback after submission. A desktop design alone does not establish whether the journey works with a keyboard and on a phone. The states checked and treatment of findings should therefore be explicit parts of the comparison.
A proposed date also depends on the decisions and materials needed. Ask for those prerequisites and the handling of late content rather than treating a calendar week as a promise independent of every dependency. What matters for your decision is a traceable process to a reviewable result, alongside the date in the first quotation.
What you pay after handover
Recurring costs become comparable over the same period. Billing intervals, included work and external licences explain what the total covers; separating fees passed on by the supplier from contracts you hold directly also shows whom you will owe each payment.
For a later change of provider, clarify export options, domain administration and the ability to continue working on the code. This includes the agreed rights to the actual text, images and technical materials. Have open points specified in the quotation so another developer can take over the work. An export feature answers the technical question but does not automatically settle usage rights.
Giving both suppliers the same unresolved questions creates a common basis for your next decision. A dated revision records which answers have become part of the quotation, so you can compare scope, working arrangements and costs on that basis. An explicitly excluded task is a defined boundary, not automatically a quality problem.
The website services show examples of defined scopes. For your comparison, use each supplier’s clarified, dated quotation. Finish by recording which differences determine your choice and what still needs answering before you agree.
Treat a quotation configurator as preparation
A web-based quotation configurator can help record page types, functions and available content in a structured way. Its result does not by itself establish a fully agreed project scope. For an existing website, technical constraints, missing access or an unclear data handover may only become apparent during review. Record the assumptions behind the calculated or proposed selection and which investigation remains before a specific quotation.
For comparing providers, a completed brief is particularly useful when everyone receives the same version. Later answers and added items then belong to the dated quotation. Comparing only the original totals could otherwise overlook a newly added function in one offer and a task that remains excluded in another.
Describe comparable results through actual projects
For NISTA-IT, we developed the brand and website together, including information architecture, responsive interfaces and technical implementation. At Hundeschule Hopen, our described contribution includes the website, content, photography and communication material, and access to the booking portal. These different tasks explain why projects with similar page counts need not involve the same effort. The project descriptions help identify the content, design and functions your own website needs.
If you are planning a limited new site, website or shop rebuild describes the specific starting scope with supplied content and an agreed system. If design and content are already approved, website and landing page development serves a different starting point. This distinction lets you enquire about the scope that fits your current state and compare the answer with other offers against the same outcomes.
