How to compare website development estimates

Compare scope, exclusions, running costs and handover terms. Ten checks and a reusable template for two proposals.

Download the comparison template Go to the ten checks

Start with one shared brief

Estimates become comparable when suppliers share the same brief. Align pages, content, functions, checks and handover. Mark any unstated item as needing clarification. Then compare launch fees, recurring costs and timing.

Describe what the company offers, its audience and the action visitors should take.
Provide one list of sections and materials, including what is ready and what must be prepared.
List required functions: forms, catalogue, search, CRM and languages.
State constraints: current website, existing URLs, access, target date and approvers.

Ten points to compare

For each item, record what is included, excluded and expected from your team. Resolve an unstated item before choosing a supplier.

Task and pages: Which services and audiences does the website cover? Compare the page list, distinct layouts and pages the supplier will populate. Six copies of one template and six different journeys are different scopes.
Structure and content: Who collects materials, writes and approves copy, and selects images? Separate supplier work from inputs your team must provide.
Design and revisions: Is the design custom or adapted from an existing template? Which screens are approved before development, how many review rounds are included, and what counts as a new request?
Mobile layouts: Does the scope cover every agreed page? Include long copy, tables, navigation, documents and forms in mobile checks.
Content management: What can your team change: services, projects or documents? Check CMS access, roles and instructions. A platform name alone does not define those capabilities.
Forms and integrations: Where is an enquiry saved, who receives it and which fields reach the CRM? Compare error and retry handling as well as the number of forms and connected systems.
Search preparation: Which tasks are included: URLs, metadata, Sitemap and redirects? Technical launch preparation and ongoing work to attract search traffic are separate scopes.
Testing and acceptance: Which scenarios establish acceptance? Agree page, form and integration checks, including fixes for defects found before launch.
Licences and recurring costs: What is separate: domain, hosting, CMS, fonts, applications or an integration service? Check billing periods and account ownership.
Handover and support: Which accounts, source files, materials and instructions are handed over? Who publishes the site, how long does agreed support last, and how are new changes estimated?

Download a text template for two estimates

Separate launch and running costs

Comparable launch cost combines the proposal with necessary work excluded from it. Do not add copy, a licence or a connection twice when already included. Also record work your team must do, even when the supplier does not invoice for it.

Before launch: Agreed structure, content, design, development, population, integrations, testing, migration and publication.
Recurring: Hosting, licences, paid services and agreed maintenance. Use the same comparison period.
When scope changes: New sections, languages, functions or integrations after agreement. Establish how the supplier will estimate changes.

Six pages can mean different scopes

An illustrative company needs service pages and an enquiry form. Both proposals list six pages. This example explains how to read estimates; it is not a client quote or BYstudio price list.

Proposal A: The supplier adapts an existing design. The company supplies finished copy and images. The form sends an email. CRM and additional page population are estimated separately.
Proposal B: The scope includes structure, copy from company materials, custom layouts, page population and saved-enquiry checks. CRM connection is included in the agreed scope.
Make them comparable: Decide which work is necessary and request the same scope from both suppliers. Remove CRM if not needed. If copy is unfinished, clarify its preparation cost and ownership.

A portfolio reference: service areas and client letters belong to the corporate website scope for Скилл Строй. Creating a CRM order is a separate function in DOROGA. List those tasks separately, even when both proposals are called a website.

Скилл Строй: structure and content DOROGA: website and CRM

Questions before choosing

Can I choose the cheapest proposal?

Yes, when it meets the actual need, includes the necessary work and has clear acceptance criteria. A higher fee alone does not prove quality. Scope and delivery should explain the difference.

What if the estimate contains only a total?

Ask for a scope appendix: pages, work, exclusions, stages, client inputs and acceptance criteria. An hourly breakdown is not essential, but the deliverable boundaries should be clear.

How do I compare hourly and fixed pricing?

Compare the intended outcome first. For hourly work, ask about the estimate, reporting and approval of overruns. For a fixed fee, clarify scope boundaries and change pricing.

Does the same CMS mean the same result?

No. Templates, configuration, content, integrations and handover can differ. Compare the actions the site supports and the definition of completion.

Is an SEO line item enough?

Ask which tasks and deliverables it covers. Metadata and redirects can be checked at launch. Content, visibility and enquiry outcomes need ongoing work and observation.

What should I do after filling in the template?

Send each supplier the same list of missing items, obtain revised proposals and then compare totals, timing and responsibility.

Define your project scope

The initial BYstudio review is free. Describe the website task, available materials and points where proposals differ. We agree scope and acceptance criteria before estimating the project.

B2B website development: scope and acceptance