How to Read a Website Proposal Line by Line

Start with the scope: what are they actually building?

The first thing to look for is the list of pages and the kind of site being built. A good proposal should say how many pages are included and name them in plain words, such as Home, About, Services, Service Area, Contact, or an FAQ page. If your business needs special pages for each service or each neighborhood, those should be named too.

Do not accept a line that says the site will have “a few pages” or “a custom layout” without more detail. That can leave you guessing later when the designer says a page is outside the original scope. Ask for a page list, even if it is short.

If the proposal mentions “template” or “custom design,” ask what that means in practice. A template may still look good, but you should know how much will be built from scratch and how much will be adapted from a starting point. That matters for the work involved and the final look.

Look for one sentence that says what the site is for. A locksmith site, a salon site, and a clinic site may all need calls, forms, maps, and service pages, but the content and tone should be different. The proposal should show that the builder understands your type of business.

• Ask for a page list by name, not just a page count.
• If you need service area pages, make sure they are listed one by one.
• If a line feels vague, ask, “What would be missing if I signed this as-is?”

Read the content section like a checklist

Many owners assume the website builder will write the copy, gather the photos, and clean up the details. Sometimes that is included. Sometimes it is not. A good proposal should spell out who writes the text, who provides photos, and who gives the business details like hours, services, phone numbers, and service area.

Watch for lines like “content support,” “basic copy,” or “client-provided materials.” Those phrases can mean very different things. If they are writing the copy, ask how many pages are included. If you are providing the copy, ask how much editing they will do and who makes the final call on wording.

Photos deserve special attention. If the proposal says it includes stock images, ask whether those are licensed for your site and whether any real photos of your business are expected. For local businesses, your own photos often help more than generic images, but the proposal should say who is responsible for taking them, selecting them, and placing them on the site.

Also check for line items about logo cleanup, image resizing, and basic formatting. Those small tasks take time. If they are not mentioned, you may be asked for extra work later or told they were never part of the agreement.

If your business serves people in person, the proposal should mention details like service hours, contact methods, map placement, and review or testimonial sections if needed. These are small pieces, but they shape how easy the site is to use.

• Ask, “Who writes the first draft of the page text?”
• Ask, “How many rounds of edits are included on the copy?”
• Ask, “What happens if I only have a few phone photos right now?”

Make hosting, WordPress, and support plain before you sign

Hosting is one of the easiest places for a proposal to stay fuzzy. The line should say who is paying for hosting, where the site will live, and who has the login details. If the builder handles hosting for you, ask what happens if you leave later and how you get access to the files and settings.

If the proposal mentions WordPress, ask whether the site will be built on your own WordPress setup or on a platform you do not control as much. You do not need a long technical explanation. You only need to know how updates, plugins, backups, and access will be handled. If those words are not in the proposal, ask for them.

Support after launch should be written down with the same care as the build itself. Look for lines about bug fixes, small edits, training, and what counts as a new request. “Support included” sounds nice, but it is not enough. You want to know what is covered, how to request help, and how long that help lasts.

Also check whether email setup, backups, security checks, and domain help are part of the work or separate. A proposal can look complete and still leave out these practical pieces. For a local service business, those details matter because lost access or a broken form can interrupt calls and leads.

• Make sure you can get into every account tied to the site.
• Ask what support looks like after launch: email, phone, or form?
• If backups are mentioned, ask who can restore them and when.

Watch the change language and the words that hide extra work

This is where many proposals get slippery. Look for phrases like “minor changes,” “basic revisions,” “small updates,” and “as needed.” Those words may sound fair, but they can mean different things to different people. Ask what counts as a change and what counts as a new task.

A good proposal should say how many revision rounds are included for design and for copy. It should also say what happens if you change direction halfway through. If you decide to add a page, switch the layout, or rewrite the services section after work starts, the proposal should explain how that is handled.

Pay close attention to lines about forms, booking tools, maps, galleries, and special features. A proposal may call them “simple additions” even though they can take real setup time. If your business needs online booking, quote requests, or service filters, ask that they be named directly.

The same goes for mobile design and basic search setup. Those may be part of the build, but they should still be stated clearly. Do not rely on the idea that “of course that is included.” If it matters to you, it belongs in writing.

• Circle every vague word: basic, minor, simple, standard, support, custom.
• Ask, “What is included in the first draft, and what is extra?”
• If a feature matters to your leads, ask for it in plain language.

Check ownership, access, and what happens when the work ends

Ownership lines are easy to skip when you are focused on the design. Do not skip them. The proposal should say who owns the website content, the design files, the images that were created for you, and the login access. If the wording is unclear, ask for a plain answer before you sign.

You should also look for any line that limits your access after the project ends. If the builder keeps control of the site, hosting, or key files, you may have trouble making changes later. That may be fine in some setups, but it should be your choice, not a surprise.

Ask what happens if you want to move the site later or work with another person in the future. The proposal does not need to be long, but it should say how handoff works. This saves headaches if you ever need to switch help or make a change in-house.

The close of the project should be clear too. Look for launch steps, final approval, and any training or handoff notes. If the proposal says “launch support,” ask what that includes and how long it lasts. That way you know when the project is done and when ongoing work begins.

• Make sure you know who holds the logins.
• Ask for a plain handoff process at the end.
• Keep a copy of the final proposal and all approval notes.

Read the timeline like a plan, not a wish

Timeline language can be the most misleading part of a proposal. Look for dates, phases, and what needs to happen before each phase can move forward. A useful proposal should say when the work starts, what the review points are, and what the builder needs from you to keep moving.

If you see words like “fast,” “quick,” or “soon,” ask for more detail. That kind of language is not enough on its own. You want to know the order of work: first planning, then content, then design, then edits, then launch. Even a short timeline is better than a vague promise.

Also look for delays caused by waiting on your side. If the proposal says the timeline changes when content or photos are late, that is fair. But it should be written clearly so there is no blame game later. A good builder will explain what they need from you and when.

If your business has a busy season, mention that before you sign. The proposal should reflect your real schedule, not just the builder’s normal pace. A project that fits your calendar is easier to manage and less stressful for everyone.

• Ask for the sequence of work, not just a final date.
• Write down what you must provide and by when.
• If the timeline feels too loose, ask them to split it into steps.