Proposal comparison guide
How to compare website proposals and RFP responses
A proposal is useful when it makes the work understandable. Compare what each supplier will do, what the business must provide and how the project will be completed.
The useful numbers, with the conditions attached.
- Normalise scope before comparing price.
- Check assumptions, exclusions and owner responsibilities line by line.
- Assess process, evidence and handover alongside the visible design work.
Put proposals on a common comparison sheet
A low total cannot be interpreted until you know whether it includes discovery, content, design, development, mobile testing, migration, training and support. Create a simple comparison sheet and place each supplier’s stated scope against the same rows. Mark unclear items as questions rather than assuming they are included.
Look for different definitions hiding under the same label. ‘SEO’, ‘copywriting’, ‘custom design’ and ‘support’ can describe very different deliverables. Ask for the page types, activities, review rounds or response expectations that sit behind each term.
- Discovery and planning
- Content and translation
- Page types and features
- Testing and launch
- Training and support
- Third-party costs
Read the assumptions and exclusions as carefully as scope
Every proposal relies on something the client supplies: approved content, product data, access, decisions or feedback by a certain date. A strong response makes these dependencies visible. That lets the business judge whether the timeline and price are realistic for its own capacity.
Exclusions are not automatically a warning sign. They can be healthy when they are specific and paired with options to add work. The risk is an unexplained exclusion that appears only when a necessary task is already delaying launch.
- Client-supplied content
- Approval timing
- Integrations and licences
- Migration work
- Translation
- Out-of-scope change process
Assess how the supplier thinks, not only how pages look
A portfolio can show visual taste, but it does not explain how the supplier will work with your content, handle uncertain requirements or test an enquiry journey. Ask for examples of the process, the role of the proposed team and how decisions are documented.
Be cautious about promises that cannot be controlled, including guaranteed rankings, exact lead volumes or a universal launch date before requirements are confirmed. A credible supplier explains what they can commit to and what depends on timely business decisions or third-party services.
- Relevant work examples
- Named delivery roles
- Decision and feedback process
- Testing approach
- Evidence-based promises
Compare what remains with the business
Ask who owns the domain, hosting, design assets, content, accounts and operating access at the end. The answer may vary by platform and contract, but it should not be a surprise. A project that launches successfully but leaves the business unable to manage renewals is incomplete.
Finally, compare the post-launch route: routine edits, fixes, maintenance, improvements and supplier transition. The best proposal is not necessarily the most detailed document; it is the one whose scope, responsibilities and operating model your business can actually carry out.
- Account ownership
- Handover materials
- Maintenance terms
- Change request process
- Supplier transition route
Common questions
Questions worth settling before you commit.
Should I choose the cheapest proposal?
Only after confirming it covers the same necessary scope and ownership as the others. A lower total may place content, testing or support work back on the business.
What should an RFP ask for?
Ask suppliers to respond to your goals, audience, scope, content, integrations, timeline, ownership, process, price assumptions and support needs.
How many proposals should I compare?
Use a manageable shortlist that you can question properly. The aim is informed comparison, not collecting the greatest number of documents.