How to compare small-business website proposals before you hire

A website proposal is useful only when you can tell what will be delivered, what you must supply, and what happens after launch. Two quotes can both say “five-page website” while assigning very different amounts of work to you. Compare the deliverables before comparing the total.

For a small service business, SMS recommends starting with one business decision: what should a qualified visitor be able to do on the finished site? Request an estimate, book a conversation, or understand a particular service are clearer goals than “look more modern.” Then compare every proposal against that goal.

1. Ask for a page list with a purpose

“Five pages” is a quantity, not a complete scope. Ask which pages are included and what each one needs to accomplish. A homepage, two distinct service pages, an about page, and a contact page may fit one business. Another may need a focused landing page and improvements to the existing site.

Ask whether the proposal includes new page layouts, reuse of a shared layout, or changes to an existing template. None is automatically the right choice. The important question is whether the approach fits your offer and the content you can maintain.

2. Make the content responsibilities explicit

Before comparing quotes, identify who writes service copy, supplies photographs, checks business details, and obtains permission to use customer feedback. Also ask who uploads the approved material.

If you must provide everything, include that work in your decision. A project can appear inexpensive because writing and organizing the content remain on your to-do list. At SMS, service copy and page organization can be included when agreed in the scope; the exact pages and revision rounds are confirmed before work starts.

Neither proposal wins by default. A business with finished content and internal support may prefer A. A business that needs help explaining its services may find B a better fit. Ask the providers to price the same required scope before treating the totals as comparable.

3. Separate a booking link from a booking system

A button leading to an existing scheduling tool is different from configuring availability, appointment types, notifications, payments, and account access. Ask exactly where the website work ends and the third-party service begins.

For a contact form, ask which inbox receives inquiries, what confirmation visitors see, and who checks delivery before launch. W3C's forms guidance emphasizes clear labels, instructions, and feedback about errors or successful completion. Ask the provider to include these usability checks, rather than judging a form only by its appearance.

4. Clarify control and recurring costs

Ask which accounts you will control and what access the provider retains. Cover the domain, hosting or site platform, content, analytics, and any paid extensions. Request a written explanation of export or transfer options and platform limitations.

Compare one-time project work separately from recurring hosting, software, maintenance, and support charges. Ask which renewals you pay directly and which services stop if a subscription ends. A small launch scope can still be a sensible purchase; uncertainty about its ongoing obligations is what you want to remove.

5. Define SEO and launch checks as deliverables

“SEO included” needs a specific explanation. Ask whether the scope covers page titles and descriptions, internal navigation, indexability checks, a sitemap, and preservation of existing useful URLs. These are tasks you can verify; they are not a promise of rankings.

If existing URLs must change, ask who maps old pages to relevant new destinations and sets up redirects. Google's site-move guidance recommends planning that mapping and monitoring the move. A visual redesign alone is not a reason to rename every page.

Include mobile navigation, readable layouts, working links, and an agreed contact-path test in the launch checklist. Record who gives final approval and what happens if a launch check fails.

6. Agree on revisions and the handoff

Confirm what counts as a revision, when feedback is due, and how additional pages or features are priced. Ask what guidance you receive for routine edits and how future support is requested. Distinguish correcting a delivered defect from buying a new feature.

Before accepting a proposal, you should be able to complete this sentence: “We are buying these pages and functions, supplying these materials, paying these ongoing charges, and receiving this handoff.”