Compare website proposals by normalizing the outcome, pages, content work, design system, functions, integrations, migration, redirects, search foundations, accessibility, performance, testing, launch, ownership, estimated effort, schedule, exclusions, change process, and recurring costs. Two totals are not comparable until those responsibilities are visible.

A lower proposal may be the better choice because it removes unnecessary work. It may also omit writing, migration, mobile behavior, form delivery, analytics, redirects, ownership, or launch support that the business assumes is included. Compare the actual release, not the cover-page number.

Quick scorecard: business outcome, page inventory, content responsibility, design depth, functions, providers, migration, redirects, search, accessibility, speed, analytics, testing, launch, ownership, hours, schedule, acceptance, exclusions, changes, care, and total recurring cost.

Give every provider the same starting brief

Ask each provider to respond to the same goal, audience, launch pages, content status, functions, integrations, migration, budget, deadline, and ownership requirements. Different recommendations are useful; different hidden assumptions are not.

If one proposal includes twelve original pages and another uses five existing pages, the price difference does not show which provider is expensive. It shows two different projects.

1. Compare the outcome before the deliverables

Look for a clear statement of what the site should help a specific visitor understand and do. A proposal that begins with colors, animations, or a platform without explaining the customer decision may be pricing production without defining value.

Confirm how success will be measured: qualified calls, estimate requests, appointments, visits, purchases, applications, or another observable action.

2. Normalize the page inventory

Create a table with every proposed page or template. Distinguish:

  • Unique pages with original structure and content.
  • Reusable templates for services, people, locations, products, or articles.
  • Existing pages moved largely unchanged.
  • Pages merged, redirected, archived, or excluded.
  • Policy pages supplied by the client or qualified adviser.

"Up to 20 pages" says little if the proposal does not explain whether those pages receive strategy, writing, design, assembly, or automated import.

3. Identify who creates and approves content

Compare responsibility for interviews, research, messaging, page outlines, writing, editing, business facts, photography, image selection, video, testimonials, claims, credentials, and professional review.

Ask how many revision rounds are included and what counts as a revision. Rewriting an approved service after the business changes its offer is different from refining a draft within the agreed direction.

4. Understand the design depth

A configured template, custom visual direction using reusable components, and bespoke art-directed page system are different services. Ask what is original, what is licensed, which page types receive design work, how mobile behavior is handled, and how feedback is approved.

More design hours are worthwhile when they improve clarity, credibility, usability, and differentiation. They are wasteful when they add effects without helping a customer decide.

5. Define functions and integrations precisely

For forms, booking, payments, ecommerce, donations, calculators, maps, directories, search, portals, CRM, analytics, or accounting, compare:

  • Specific product and plan.
  • Fields, rules, routing, and user states.
  • Failure, retry, duplicate, and reconciliation behavior.
  • Accessibility, privacy, consent, and security responsibilities.
  • Provider setup and recurring fees.
  • What remains manual.

6. Make migration and search protection visible

For an existing site, compare content inventory, current URL export, keep/merge/remove decisions, media migration, metadata, canonical URLs, structured data, redirect mapping, sitemap, analytics, Search Console, and post-launch crawl checks.

No responsible provider can guarantee rankings. A proposal can commit to preserving useful URLs and signals, creating a sound technical foundation, and measuring what happens after launch.

7. Compare quality assurance and acceptance

Ask which devices, browsers, viewport sizes, forms, integrations, failure paths, keyboard interactions, accessibility checks, performance conditions, analytics events, and redirects will be tested.

Acceptance should describe observable completion. "Website delivered" is weaker than an agreed page list, working actions, tested routes, approved content, ownership transfer, and launch checklist.

8. Confirm domain, code, accounts, and licenses

The business should know who owns and controls the domain, source code, repository, hosting account, analytics, forms, email provider, business listings, fonts, photos, plugins, and third-party services.

At Vertinus, the client owns the completed code, interface, project-specific deliverables, and domain after final payment. Third-party assets retain their licenses. Managed infrastructure does not transfer ownership away from the client.

9. Normalize price and recurring cost

Separate one-time build, content, photography, licenses, provider setup, migration, launch, hosting, domain, plugins, maintenance, support, and marketing. Compare at least the first-year total and the cost to leave.

Vertinus charges $49.99 per hour for time actually worked up to the approved estimate. Work within the agreed scope does not exceed that estimate; new scope is estimated and approved separately. Optional Managed Website Care is $50 per month.

10. Compare schedule assumptions

A schedule should identify discovery, content, design, development, review, integration, migration, testing, launch, and client decision dates. Ask what happens when content, access, or approval is late.

A very short timeline may be credible for a focused site with ready content. It is not automatically credible for stakeholder interviews, original writing, photography, large migration, and several integrations.

A simple weighted scorecard

  • Outcome and recommended scope: 20%. Does the proposal solve the right customer problem?
  • Pages and content: 20%. Are deliverables and responsibilities complete?
  • Functions and migration: 15%. Are behavior and transition risks defined?
  • Quality and measurement: 15%. Are testing, search foundations, analytics, and acceptance credible?
  • Ownership and recurring cost: 15%. Can the business control and move its assets?
  • Price and schedule: 15%. Are effort, timing, assumptions, and changes understandable?

Adjust the weights to the business. Use written evidence from the proposal, not sales-call confidence.

Prepare comparable inputs with the website estimate packet, understand price variation through why website quotes differ, and verify asset control with the website ownership checklist.

Send Vertinus your website brief and the scope categories you want compared. We will return a written estimate with pages, responsibilities, hours, exclusions, ownership, recurring providers, and acceptance stated directly.