webshunya icon logo

Chosen

How to Compare Website Proposals, Agencies and Freelancers Before You Hire

Make website proposals comparable by checking content, migration, testing, ownership and support before the price.

Milan Gohil

·

9 min read

Three ivory proposal sheets on a tabletop, each with a different arrangement of blank blocks and small pictograms.
Three ivory proposal sheets on a tabletop, each with a different arrangement of blank blocks and small pictograms.

OVERVIEW

Here is a short version of what I write.

Compare website proposals by making each provider price and explain the same requirements. Evaluate delivery approach, responsibilities, risks and ongoing costs alongside the total fee.

  • Normalise the scope across strategy, content, design and development.

  • Check migration, integrations, testing and launch responsibilities.

  • Review relevant work and who will deliver the project.

  • Clarify ownership, access, exclusions and post-launch support.

Three website proposals can all say:

Website redesign — $8,000

and still describe three completely different projects. One may include strategy, content migration, SEO redirects, analytics and post-launch support. Another may include only design and development. A third may expect you to provide final copy, upload old content and handle SEO yourself. So before comparing the price, make the proposals describe the same project. GOV.UK’s digital-procurement guidance similarly starts with requirements and evaluation criteria, then assesses suppliers against the work needed. For a business website, use that principle to compare competence, approach, responsibilities and value. GOV.UK: buying digital outcomes and specialist services.


Compare scope before comparing price. 1. Define the same job: Strategy, content and design: Build, CMS and integrations. 2. Check the full delivery: Migration, SEO and analytics: Testing, launch and support. 3. Clarify responsibility: Who provides what?: What is excluded?: Who controls the site?. 4. Compare value: Assess the complete offer: Then compare the totals. A lower price can describe a smaller project.

A cheaper proposal is not cheaper if important work is simply missing.

Want AI to compare the proposals first?

Paste the proposals into an AI tool with this prompt.

I am comparing website proposals from agencies and/or freelancers.

CURRENT WEBSITE:
[PASTE WEBSITE URL]

MY MAIN GOALS:
[PASTE WHAT YOU WANT TO CHANGE]

PROPOSAL A:
[PASTE]

PROPOSAL B:
[PASTE]

PROPOSAL C:
[PASTE IF APPLICABLE]

Act as a buyer-side website project reviewer.

Do not choose a winner based on price, agency size or writing quality.

First normalize all proposals so I can see whether they are actually quoting the same project.

Create a comparison covering:

- discovery / current-site audit
- sitemap / information architecture
- UX / wireframes
- visual design
- responsive design
- content strategy
- copywriting
- content migration
- CMS setup
- development
- forms
- integrations
- SEO migration
- URL redirects
- metadata
- analytics / tracking
- performance testing
- accessibility testing if mentioned
- browser/device QA
- launch
- training / handoff
- post-launch support
- hosting
- ongoing maintenance
- third-party costs
- revisions
- ownership / access

For every item classify each proposal as:

INCLUDED
EXCLUDED
UNCLEAR
CLIENT RESPONSIBILITY
OPTIONAL EXTRA

Then identify:

1. Scope differences that make the prices difficult to compare
2. Important work that appears missing
3. Assumptions hidden inside each proposal
4. Responsibilities being pushed to me
5. Possible change-order risks
6. Recurring costs
7. Migration/SEO risks
8. Ownership or access questions I should clarify
9. What happens after launch
10. The most important questions I should ask each provider

Then review each provider's evidence:

- relevant work
- experience with similar complexity
- who will actually work on the project
- whether the proposal explains the problem clearly
- whether risks and dependencies are acknowledged
- whether the approach fits my stated goals

Do not assume an agency is better than a freelancer or vice versa.

Finish with a neutral comparison showing:
- what each proposal is actually offering
- its important strengths
- its important gaps
- what still needs clarification

Do not invent information that is not in the proposals.

The output gives you questions. You still decide which provider fits the project.

First, make every proposal comparable

Create one table.


Make website proposals comparable. Plan and content: Audit and strategy: Sitemap and copy: Provider A / B / C: ____. Design and build: Design, development and CMS: Integrations and accessibility: Provider A / B / C: ____. Move and launch: Content and SEO migration: Testing and deployment: Provider A / B / C: ____. After launch: Ownership and access: Support and recurring costs: Provider A / B / C: ____. Mark included, excluded or unclear—and name the responsible party.

Work

Provider A

Provider B

Provider C

Current-site audit

—

—

—

Sitemap

—

—

—

Wireframes

—

—

—

Copywriting

—

—

—

Visual design

—

—

—

Development

—

—

—

Content migration

—

—

—

SEO migration

—

—

—

Forms/integrations

—

—

—

Analytics

—

—

—

QA

—

—

—

Launch

—

—

—

Training

—

—

—

Post-launch support

—

—

—

Use only: Included / Excluded / Unclear / Our responsibility / Extra cost This quickly exposes why two prices differ.

Example: the lower quote may not be for the same website

Imagine a manufacturing company is replacing a 70-page website.

Proposal A — $9,000

Includes new design and development of 15 page templates. The client supplies all content. Existing pages are not audited. Content migration is not mentioned. SEO migration is not mentioned.

Proposal B — $14,000

Includes current-site audit, sitemap work, design, development, migration of existing content, URL mapping, redirects, analytics setup and post-launch monitoring. These are not:

$9,000 vs $14,000 for the same website.

They are different scopes. The first question should be:

Who handles everything between the old website and the 15 new templates?

Compare the problem they are solving

A strong proposal should make it possible to understand:

What is wrong today?

and

What are we changing because of it?

If your problem is:

Visitors cannot understand the services and the website has become difficult to expand.

but the proposal mainly discusses:

  • new colours

  • animation

  • modern typography

  • visual references

there may be a mismatch between the problem and the proposed work. Similarly, if your problem is primarily technical:

The existing CMS cannot support the catalogue or integrations we need.

a beautiful visual concept does not answer the important question. Look for the connection:

CURRENT PROBLEM → PROPOSED WORK → EXPECTED IMPROVEMENT

If you cannot see that connection, ask for it.

Compare what happens to your existing website

This matters especially in a redesign. Ask each provider what happens to:

Existing asset

Question

Pages

Keep, rewrite, merge or remove?

URLs

Stay or change?

Blog

Migrated completely?

Images/files

Who moves them?

Forms

Rebuilt and tested?

Analytics

Preserved/reconfigured?

SEO metadata

Migrated/reviewed?

Redirects

Who creates them?

Integrations

Reconnected and tested?

If URLs change, this is not a minor launch detail. Google recommends preparing an old-to-new URL mapping, implementing appropriate redirects, updating internal links and sitemaps, and monitoring the move afterward. So if one proposal says: Google: site moves with URL changes.

SEO migration included

ask what that actually contains.

“SEO included” is too vague

For an existing site, useful questions are:

Ask

Why

Are existing URLs reviewed?

Know what should be preserved

Is an old → new URL map created?

Prevent missing destinations

Are redirects implemented?

Preserve useful old routes

Are internal links updated?

Avoid relying on redirects internally

Are canonicals checked?

Avoid conflicting URL signals

Is the XML sitemap updated?

Reflect new URLs

Is indexing checked before launch?

Catch accidental noindex/robots problems

Is Search Console monitored after launch?

Detect migration problems

Google's migration documentation explicitly covers these steps and lists incorrect redirects, forgotten noindex/robots restrictions and outdated sitemaps among common migration errors.

Compare who is writing and moving the content

This is one of the easiest responsibilities to assume incorrectly. A proposal says:

20-page website

Does that mean the provider: writes 20 pages? designs 20 pages? builds 20 pages using your copy? creates templates while you upload all 20 pages? Those are different jobs. Ask separately:

Content task

Who does it?

Decide what stays

—

Decide what gets removed

—

Write new pages

—

Rewrite existing pages

—

Proofread

—

Supply images

—

Optimize images

—

Upload content

—

Move blog posts

—

Move PDFs/files

—

Final content approval

—

Do not wait until development is finished to discover:

“Content wasn't included.”

Compare the CMS by what your team needs to do afterward

Do not choose a CMS because the proposal says:

modern stack

or:

industry-leading platform.

Ask what you will be able to do. Imagine your company regularly needs to:

  • add a service

  • publish articles

  • add team members

  • create locations

  • publish case studies

  • update forms

Ask each provider to show how those actions work. A technically impressive system can still be a bad fit if every routine update requires the original developer.

Compare the actual people doing the work

This becomes important when comparing an agency with a freelancer. Do not compare:

Agency = professional

Freelancer = cheap

That tells you almost nothing. Instead compare the delivery model.


Agency or freelancer: what changes?. People and skills: Who actually does the work?: Which disciplines are needed?. Capacity and continuity: Can work happen in parallel?: What if someone is unavailable?. Working relationship: Who communicates with you?: Who supports the site later?. Evaluate the delivery arrangement, not the provider label alone.

Question

Why it matters

Who will actually do the work?

Sales presentation may not equal delivery team

How many disciplines are needed?

Strategy, content, design, development, SEO may require different skills

Can one person reasonably cover them?

Sometimes yes, sometimes no

What happens if someone becomes unavailable?

Continuity

Can work happen in parallel?

Timeline

Who communicates with you?

Project experience

Who supports the site after launch?

Ongoing responsibility

Government digital-buying guidance similarly distinguishes between buying a specific specialist for a defined piece of work and buying an outcome that may need a team with different skills.

When a freelancer can make complete sense

Imagine a local consulting company needs:

  • a focused 10-page website

  • an existing brand

  • straightforward CMS

  • no unusual integrations

  • direct collaboration with one experienced designer/developer

One capable freelancer may be a very good delivery model. You may get:

  • direct communication

  • fewer handoffs

  • clear personal ownership of the work

You do not need a multi-person agency just because the word “agency” sounds safer.

When a team becomes more useful

Now imagine an established distributor is rebuilding:

  • 250 pages

  • product categories

  • resources

  • CRM forms

  • several templates

  • organic-search landing pages

  • multilingual content

  • complex migration

The project may need work happening simultaneously across:

  • CONTENT

  • DESIGN

  • DEVELOPMENT

  • SEO / MIGRATION

  • QA

One person may still lead it, but you should understand who is covering each discipline and what happens when several things need attention at once. The right question is therefore:

Does this delivery model fit the complexity and risk of this project?

Not:

Agency or freelancer—which one is better?

Look at relevant work, not only beautiful work

A proposal might contain five impressive websites. Look deeper. If your project includes:

  • large content migration

  • ecommerce

  • multi-location architecture

  • complex filtering

  • SEO-sensitive redevelopment

ask for examples involving those challenges. A beautiful five-page portfolio website proves design capability. It does not automatically prove experience migrating 20,000 ecommerce URLs. Government supplier-evaluation guidance likewise emphasizes evidence of relevant skills and experience, the proposed approach, risk handling and how well the solution fits the buyer's requirements.

Ask who owns and controls everything after launch

Before signing, make this explicit.


Who controls the website after launch?. Core accounts: Domain and DNS: Hosting and CMS admin. Tools and measurement: Analytics and Search Console: Tag Manager and CRM/forms. Files and licences: Agreed source and design files: Images and third-party licences. Recovery and transfer: Backup access: How another provider takes over. Record account control and access. Legal ownership depends on the agreement.

Item

After launch, who controls it?

Domain

—

DNS

—

Hosting

—

CMS admin

—

Source/code repository if applicable

—

Analytics

—

Search Console

—

Tag Manager

—

CRM/form accounts

—

Third-party plugins/licenses

—

Design/source files if included

—

Images/assets

—

Backup access

—

The exact legal ownership can depend on your contract and jurisdiction. The practical goal is simpler: Do not discover after launch that a critical account exists only inside somebody else's personal login. If an agency manages something for you, make sure the arrangement is clear.

Compare recurring cost, not only project cost

Proposal A:

$8,000 build

Proposal B:

$11,000 build

does not tell you total cost. Check:

Recurring item

Cost

Hosting

—

CMS/platform subscription

—

Plugins/apps

—

Search/filter service

—

Forms

—

CDN

—

Maintenance

—

Support

—

License renewals

—

A cheaper build with several mandatory recurring services may cost more over time. That may still be worth it. You simply need to see the complete number.

Ask what is not included

This question is often more useful than:

What is included?

Ask directly:

What do clients commonly assume is included in projects like this that is not included in this proposal?

You may discover:

  • copywriting

  • image sourcing

  • content migration

  • SEO

  • tracking

  • accessibility review

  • CRM configuration

  • hosting

  • post-launch changes

Now you know before the project starts.

Understand how changes are handled

Every project changes. The issue is what happens when it does. Ask:

What happens if we add five pages?

What happens if an integration is more complex than expected?

What counts as a revision?

What counts as new scope?

How is additional work priced?

You are not trying to eliminate change. You are trying to understand it.

Use one comparison sheet

Do not score providers on 47 criteria unless your project genuinely needs that level of procurement. For most business websites, start here:

Area

Provider A

Provider B

Provider C

Understands our problem

—

—

—

Relevant experience

—

—

—

Scope is clear

—

—

—

Content responsibility

—

—

—

Migration/SEO plan

—

—

—

Technical approach fits

—

—

—

Integrations covered

—

—

—

Timeline makes sense

—

—

—

Responsibilities clear

—

—

—

Ownership/access clear

—

—

—

Support after launch

—

—

—

Recurring cost clear

—

—

—

Total project price

—

—

—

The point is not to create a mathematically perfect score. It is to stop a polished presentation or low number from hiding missing work. GOV.UK's buyer guidance recommends setting evaluation criteria in advance and applying the same criteria consistently across suppliers; that principle works just as well for a business comparing a small shortlist.

Before signing, make sure you can answer this

  • WHAT ARE WE BUILDING?

  • WHAT ARE WE KEEPING?

  • WHAT IS BEING MIGRATED?

  • WHAT DO WE HAVE TO PROVIDE?

  • WHAT IS NOT INCLUDED?

  • WHO IS ACTUALLY DOING THE WORK?

  • WHAT WILL WE BE ABLE TO EDIT OURSELVES?

  • WHAT CHANGES AFTER LAUNCH?

  • WHAT DO WE OWN / CONTROL?

  • WHAT WILL THIS COST AFTER YEAR ONE?

If the proposal cannot answer those questions, the problem is not necessarily the provider. The project may simply not be defined clearly enough yet. And that is worth fixing before you compare prices.

Sources and further reading

ARTICLE WRITTEN BY

Milan Gohil

I like looking beyond the obvious problem to understand what is really holding a business back. I write about the patterns, questions and practical lessons I discover while working through real challenges

ARTICLE WRITTEN BY

Milan Gohil

I like looking beyond the obvious problem to understand what is really holding a business back. I write about the patterns, questions and practical lessons I discover while working through real challenges

Book your strategy call

Book your call now

On this page
AI Summary

Book your strategy call

Book your call now

All Blogs

All Blogs & Articles

Two small paper browser windows connected by a sturdy orange bridge; a continuous thin black route crosses intact from old to new, with a small magnifying glass beside the destination..

Found

How to Redesign or Migrate a Website Without Losing SEO

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

Chosen

Website Handover Checklist: What Your Developer Should Give You

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

Found

How Many Service Pages Does Your Website Actually Need?

A small paper analytics panel with an unlabeled black line that dips; a large orange-rimmed magnifying glass examines a disconnected paper link below the chart.

Found

Why Your Website Traffic Dropped After a Redesign and What to Check First

A tactile paper branching pathway with a tiny dark human figure at its entrance.

Seen

How to Test Your Sitemap and Navigation Before a Website Redesign

A miniature paper shopping trolley carrying three simple product boxes crosses a broad orange bridge between two spare storefront cards.

Found

Ecommerce Migration Without Losing Product URLs, Feeds or Customer Journeys

Two small paper browser windows connected by a sturdy orange bridge; a continuous thin black route crosses intact from old to new, with a small magnifying glass beside the destination..

Found

How to Redesign or Migrate a Website Without Losing SEO

A single central paper website card branches into three distinct service cards carrying only simple object icons: a gear, a pencil and a wrench.

Found

How Many Service Pages Does Your Website Actually Need?

A tactile paper branching pathway with a tiny dark human figure at its entrance.

Seen

How to Test Your Sitemap and Navigation Before a Website Redesign

Two understated cut-paper hands pass a single orange key above an open ivory folder holding a miniature website card and neatly arranged small tools.

Chosen

Website Handover Checklist: What Your Developer Should Give You

A small paper analytics panel with an unlabeled black line that dips; a large orange-rimmed magnifying glass examines a disconnected paper link below the chart.

Found

Why Your Website Traffic Dropped After a Redesign and What to Check First

A miniature paper shopping trolley carrying three simple product boxes crosses a broad orange bridge between two spare storefront cards.

Found

Ecommerce Migration Without Losing Product URLs, Feeds or Customer Journeys

Before you invest in another fix, make sure it is the right one.

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

Before you invest in another fix, make sure it is the right one.

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

Something isn’t working as well as it should?

Your website may not need more pages, more content or another redesign. It may need clarity on what is actually holding it back.

© 2026 Webshunya Studio®. All rights reserved.