A useful website quote tells you what will be delivered, who supplies each input, how acceptance works, and what you will pay after launch. If two proposals leave those questions unanswered, their totals are difficult to compare.
The most useful detail is often a boundary. Does “five pages” mean five completed pages with writing, or five layouts awaiting your copy? Does “contact form” mean a message sent to one inbox, or requests routed to different teams? Clarify those differences before treating a lower number as better value.
Start with the website's job
For our website-design service, the first conversation is about how the business works, who the website needs to reach, and what a visitor should be able to do. That should become a short purpose statement in the proposal.
For example: “Help homeowners understand our three main services and send an estimate request to our office.” This fictional scope statement is more useful than “Create an engaging digital experience.” It gives both parties a way to judge whether the proposed pages and functions belong in the project.
Our owner puts it this way: “A new design cannot fix an unclear offer.” Resolve the audience, service, and next step before approving a larger list of features.
Compare proposals with the same scope sheet
Ask each provider to complete or confirm the same categories:
| Category | Detail to request | What ambiguity can hide |
|---|---|---|
| Pages | Named page list, unique layouts, and repeatable templates | A page count without a usable structure |
| Content | Interviewing, writing, editing, entry and approval responsibilities | Unexpected writing work for the owner |
| Images | Existing assets, new photography, licensing and optimization | Images the business cannot legally or accurately use |
| Forms | Fields, recipients, uploads, confirmations and delivery tests | A form that looks finished but does not reach the team |
| Integrations | Named tools, included setup and testing | Separate subscriptions or unfinished connections |
| Revisions | Included review stages, feedback process and scope changes | Disagreement about whether a request is an edit or new work |
| Ownership and access | Domain, accounts, content, code where applicable, licenses and handoff | A site the business cannot manage or move as expected |
| Search and migration | Metadata, URLs, redirects, internal links and launch checks | Existing customer paths lost during a redesign |
| Support | Launch support, ongoing care, response channels and edit allowance | “Support included” with no defined service |
| Fees and schedule | Build payments, recurring charges, dependencies and approval points | A headline price or date with important omissions |
Use “included,” “excluded,” and “optional” beside each item. If an answer is unclear, record the open question rather than guessing the provider's intention.
A small site still needs a complete handoff
A basic landing page may be a sensible scope when the offer is focused. It still needs accurate services, usable contact details, a mobile layout, and an agreed launch path. Clarify who connects the domain, who checks inquiry delivery, and who handles changes afterwards.
Local Legacy websites start at $500 for a basic landing-page website. The starting options describe that offer. The small size of a project should simplify the agreement, not remove essential responsibilities.
A larger business needs more than a larger page allowance
Consider a company with several services and separate staff handling inquiries. The proposal should describe the content structure and workflow: which pages are repeated from a template, which need individual writing, and how a request reaches the correct recipient.
A useful form specification might read: “Collect service type, town or ZIP code, project summary, and preferred contact method; send the request to the office; display a confirmation.” If conditional routing or file uploads are required, list those separately. This is an illustrative specification, not a promise that every Local Legacy package includes those functions.
Our selected work includes both service-business websites and ecommerce. A store's catalog, product discovery and operational connections should not be buried inside a generic “business website” line item.
Make content responsibility explicit
Local Legacy helps turn the owner's knowledge into clear website copy. You do not need to arrive with every sentence written. You do need to confirm services, coverage, relevant pricing, contact details, photos, and legal or industry requirements that cannot be independently established.
Have the proposal distinguish that collaboration from the volume of custom copywriting included in the package. Identify the person who approves the facts, and schedule feedback before the build depends on it.
For photos and testimonials, record what is approved for public use. A placeholder image in a preview is not automatically the final licensed or authorized image.
Review ongoing fees beside the build price
List hosting, domain renewal, email, paid applications, licenses, maintenance, and content support. Identify which charges go to the designer and which go directly to a platform.
For any monthly website arrangement, also clarify the minimum term, cancellation process, ownership and export access, and what happens when the relationship ends. “No upfront build fee” does not mean there is no total cost. The website cost guide is the place to compare pricing options and ownership costs; this checklist is for making the scope comparable.
Should a quote guarantee leads or rankings?
Ask for clear deliverables and a measurement plan. Lead volume depends on more than building the site, and a ranking promise is not a substitute for specifying the work.
How should revisions be described?
The proposal should identify the review stages, who supplies consolidated feedback, and how added pages or functions affect price and timing. Ask the provider to define an included revision with a concrete example.
What if I do not know the full scope yet?
Start with a discovery conversation and identify open decisions. A preliminary estimate can state its assumptions; a final proposal should resolve the decisions needed to authorize the work.
Request a scoped proposal. Bring your requirements or existing quotes, and we can define the website work in terms you can compare.