Two proposals for one website: are they quoting for the same work?
To compare website design quotes, start by aligning the scope. Check what each proposal delivers, what you must supply and which costs continue after launch. Only then does the total provide a useful comparison. A more detailed proposal is not automatically better, but an unclear item cannot safely be treated as included work.
Imagine a fictional equipment installation and maintenance business. It wants to explain three services, introduce its team and receive enquiries. It has a logo, an unsorted photo collection and outdated copy. It does not need a shop or a booking system. Two suppliers respond to this brief.
Proposal A offers a business website of up to six pages, mobile-friendly design and SEO included. The client supplies the content. Proposal B names the six pages and includes copy preparation following an interview, selection from the supplied photographs, a form tested through to the receiving inbox and content-editing documentation. Both could be valid proposals, but they are not equivalent.
If the business can prepare its copy and has someone to upload it, A may fit once its open questions are resolved. If nobody will do that work, A's total does not yet represent everything needed to launch. Equally, paying for copywriting in B makes little sense if final content is already available. The decision turns on the work that remains, rather than which proposal sounds more comprehensive.
Put both proposals through these six questions
Copy the questions into a document and mark each answer as included, supplied by the client, additional cost or unclear. Avoid a simple yes or no where the term being compared can mean different things. Design, for example, might cover a configured template or an experience specifically created and reviewed for your identity. Ask for the deliverable to be described.
- Pages: which URLs and content will be delivered? Up to six does not explain whether each service gets a page or all three share one.
- Copy and images: who writes, selects, reviews and uploads each item? Are licences or translations included?
- Design: what is created specifically, and on which screens is it reviewed? How many revision rounds does the agreement include?
- Enquiries: does testing stop at the confirmation message, or cover arrival in the inbox and the ability to reply?
- SEO: which tasks will be done? Separate titles, structure and initial indexing preparation from ongoing content and monitoring.
- Handover: which access, files or documentation do you receive? What can you edit, and what needs further support?
The costs that remain after launch
Ask suppliers to separate the initial project from subsequent payments. A domain, hosting, tools, maintenance and support are different items. A licence may be paid to the original vendor and renewed annually, while a correction or an additional page may be priced separately. The proposal should identify who contracts each service, who controls the account and what happens if you change supplier.
In this example, A excludes maintenance and B offers an optional monthly service. Do not count that service as compulsory or assume that A prevents the website being maintained. Ask what each arrangement covers: updates, backups, restoration, form checks and incident support. An important task needs an owner even if you choose to handle it yourself.
Also distinguish a recurring cost from extra scope. Adding a language or an integration after approval may change the original project. Understanding how a change is estimated and authorised is useful before you need one. This guide does not set market prices or VDNX rates: it provides a method for comparing work and conditions.
Turn fast, secure and SEO-ready into checks
A sales description needs an acceptance criterion. For performance, ask which pages will be checked, under what conditions and how identified problems will be addressed. Testing an empty homepage on a desktop does not, by itself, describe how an image-heavy service page behaves on a phone. The web.dev documentation explains that performance spans several aspects of loading and interaction; it cannot be reduced to an adjective.
For SEO, ask for the tasks and how their completion will be checked. Google recommends understanding a professional's proposed changes and how results will be assessed; it also warns that nobody can guarantee first place. A promise of outcomes does not make a proposal equivalent to one specifying structure, metadata, crawling and monitoring. These are different commitments and need to be assessed separately.
For security, clarify measures within the scope, who receives alerts and how the system will be maintained. Neither proposal should be read as eliminating every risk. A useful acceptance check for this example would be to browse all three service pages on a phone, send a test enquiry with fictional details and confirm arrival in the inbox. This is a suggested criterion, not a test we performed for a real client.
A message to clarify the quotes before choosing
You can adapt this message to your project: We are comparing proposals for a website covering three services, our team and enquiries. We have a logo and photographs, but the copy needs revision. Could you confirm which pages will be delivered, who prepares and uploads the content, what the design covers, how the form is tested and which SEO tasks are included? Please also identify external costs and renewals, handover items, revisions and exclusions. We need to distinguish the launch price from optional maintenance.
Once the answers arrive, compare them against the same priorities. If two proposals deliver the same outcome, you can assess price, communication, schedule and working approach. If they address different needs, decide which scope you require first. Choosing a smaller project can be sensible; the important thing is that deferred tasks are visible before launch.
When requesting a proposal from VDNX, share your existing website if you have one, what needs to change and which content is ready. That context makes a specific discussion possible. Commissioning a website starts with an understandable scope rather than a collection of terms that appear to include everything.
Sources and documentation
- Google Search Central: Do you need an SEO? ↗
- MDN: What will your website look like? ↗
- web.dev: Learn Performance ↗
Content created with AI assistance. Check the sources, date and scope of each guide.