Two website quotes can be very different without either provider being automatically wrong. One may cover a focused page improvement; another may include discovery, page structure, original design, implementation, content support, launch checks, and a more complete handoff. The useful comparison is not just the number at the bottom. It is what that number is meant to include.

Start with the business problem the work is meant to solve.

A useful proposal identifies the primary customer, the service or decision that matters most, and the action the website should support. That does not require a provider to promise a ranking, a lead count, or revenue. It does mean the scope should make clear whether the work is intended to improve service clarity, a project inquiry path, a commercial buyer journey, a redesign foundation, or another specific business need.

Ask which pages and page roles are actually included.

“New website” can mean one landing page, a small brochure site, or a larger system of service, proof, process, resource, and contact pages. A quote should name the proposed pages or explain how they will be decided. It should also distinguish a page that has a real customer purpose from a near-duplicate page created only to repeat a phrase.

For a service business, it is often useful to ask: Which page helps a visitor understand our priority service? Which page answers a commercial buyer’s questions? Where does a customer go when they need to decide whether to call, request an estimate, or start a project conversation?

Clarify what happens with content and proof.

Good website work needs accurate material. A proposal should state whether the business supplies copy, project photos, service details, approvals, testimonials, and other proof—or whether the provider is helping structure and edit that material. It should never quietly turn unavailable proof into invented reviews, unverified results, stock-project claims, or implied credentials.

Separate the visual layer from the working website.

Design matters, but a site also needs to work across common screen sizes, load and navigate sensibly, communicate clearly, and give a visitor a usable next step. Ask whether the quote includes responsive implementation, accessibility-minded structure, actual internal links, and a review of the experience on a phone—not only a desktop design file.

Make the technical and search foundations visible.

Technical basics may include clean page routes, titles and descriptions, canonical URLs, sensible internal linking, crawlable structure, and appropriate schema. These foundations can help search engines and customers understand the site. They are not a substitute for useful content, and they are not a guarantee of rankings or traffic. A responsible quote says what is included without turning technical terms into a performance promise.

For a closer look at this part of the work, see practical SEO foundations.

Ask how launch quality and handoff will be handled.

Before comparing proposals, ask what happens before a site goes live and what you receive afterward. Useful specifics include mobile and desktop checks, link and contact-path testing, ownership/handoff expectations, and what support—if any—is included after the release. The answer should be clear enough that both sides know what “ready” means.

Use a short comparison list.

  • What business decision and customer path is this work designed to support?
  • Which pages, service routes, and content responsibilities are included?
  • What proof, source material, and approvals does the business need to provide?
  • How will mobile use, accessibility, links, and the next step be checked?
  • Which technical/search foundations are included, and which outcomes are not promised?
  • What happens at launch, and what does the business own or receive afterward?

Choose the scope that matches the current reality.

The cheapest quote is not automatically the least useful, and the highest quote is not automatically the best fit. The better choice is the scope that honestly matches the business, the available proof, the customer decision that matters, and the work required to make that path clearer. If the gap is isolated, a targeted improvement may be enough. If the foundation is misaligned, a broader redesign may make more sense.

For help deciding between those paths, read Website redesign or targeted fixes: how to decide.