How to write a website proposal a local business reads to the end

A bakery owner asks you for a proposal on a Tuesday. She wants online orders for birthday cakes, because the phone rings all through the morning rush and she can't answer it with flour on her hands. You send a tidy nine-page document on Thursday. On Monday she replies: "Sorry, haven't had a chance to read it yet. How much was it again?"

She never got to page six, where the price was. When you run a one-person AI agency and your agent can draft nine pages in minutes, that's an easy trap to fall into.

A good website proposal for a small business is short, written in the owner's words, and built around one decision. It says what problem you'll fix, what you'll build, what it costs, when it will be ready, and how to say yes. Everything else is detail that belongs in an attachment or a conversation.

This guide gives you a proposal template you can reuse, section by section, with the wording that keeps a busy owner reading.

What should a web design proposal include?

Seven sections, in this order. Each one answers a question the owner is already asking.

Section	The owner's question	Length
1. What you told me	Did they listen?	Three or four lines
2. What I'll build	What do I get?	A short list
3. What's not included	What will cost extra later?	A short list
4. Price and payment	How much, and when do I pay?	A few lines
5. Dates	When will it be ready?	Three or four dates
6. What I need from you	What do I have to do?	A short list
7. How to say yes	What happens next?	One or two lines

Notice what's missing: a page about you, your process diagram, your tools and your philosophy of design. If the owner wants to know about you, she'll ask, or she's already looked at your work. The proposal's job is to help her decide.

How do I start a proposal so the owner keeps reading?

Start with her problem, in her words. Not "Digital presence strategy for Sunrise Bakery", but something close to what she said on the call:

You told me the phone rings all morning with cake orders, you can't answer it while you're baking, and some customers give up and go elsewhere. You'd like people to order and pay for birthday cakes online, and to see what's available before they call.

That paragraph does two things. It shows you listened, and it sets up everything that follows as the answer to a problem she already agreed she has.

This is where your research pays off. If you took the time to research a business before pitching, you went into the call with questions, and the answers are the raw material for this paragraph. Use her words, not yours. If she said "the phone never stops", write "the phone never stops".

How should I write the price section?

Put it on the first page, or near the top of the second. Owners look for the price first. If they have to hunt for it, some stop reading, and the ones who keep going read everything else wondering what it will cost.

Write the price section in plain lines:

• The price: one number for the work described above.
• How it's paid: for example, half to start and half before the site goes live.
• What's ongoing: anything monthly or yearly, such as hosting, the domain or a care plan, with who pays for it.
• How long the price holds: for example, 30 days from the date on the proposal.

Payment terms are yours to set. The UK government's guidance for businesses, for example, says you can set your own terms, including payment upfront, and that without an agreed date a business customer must pay within 30 days. Rules differ by country, but terms written into the proposal are the ones both sides saw before saying yes.

How you arrive at the number is a separate job. If you're still working that out, how much to charge for a website walks through pricing from your own costs and time. The proposal just states the result clearly.

Two habits help here. First, don't explain the price with your hours. Owners don't buy hours, they buy a site that takes cake orders. Second, if you offer options, keep it to two and name them by what the business gets: "Online cake orders" and "Online cake orders plus a gift card shop". Three or more options turn a yes into a research project.

What do I write in "what's included" and "not included"?

The included list is what she gets, described as things she'll see or use:

• A five-page website: home, cakes, order online, about, contact.
• An online order form for birthday cakes, with payment taken when the order is placed.
• Your opening hours, address and phone number on every page.
• The site set up so it works well on a phone.
• A short handover: how to change prices and photos yourself.

Then the not included list, with a word on what happens if she wants it later:

• New photography (you'll use her photos, or quote separately for a photographer).
• Writing the cake descriptions (you'll edit what she sends).
• Changes after launch (covered by a care plan, or quoted separately).
• Delivery booking or a loyalty scheme (quoted separately).

The "not included" list feels awkward to write. It is the section that prevents most arguments later, because it turns "I thought that was part of it" into something you both read before starting.

How do I write the dates and what I need from the client?

Give three or four dates, not a detailed schedule:

1. Start: the week after the deposit is paid.
2. First version to review: two weeks after you have her photos and wording.
3. Changes: one round of changes, done within a week of her feedback.
4. Live: the week after she approves the final version.

Tie your dates to hers. "Two weeks after you send the photos" is fair to both of you, because a website usually waits on the client at least once. That's also why the next section matters.

List what you need from her, with a date for each: photos, the cake price list, access to her domain account, and an hour for a call to review the first version. If you run through a written checklist before she sees it, say so. It tells her the version she reviews has already been tested.

How do I make it easy for the client to say yes?

End with one clear next step and nothing else to decide:

If this looks right, reply "yes" to this email and I'll send the invoice for the deposit. Once it's paid, I'll book the start date and send you the list of photos I need.

That's the whole close. You don't need a signature box on page nine or a link to three different tools. A reply saying yes to a written proposal, followed by a paid deposit, is a clear record of what was agreed. That record matters. Australia's business.gov.au says it's much safer to have an agreement in writing than to rely on someone's word, because a written one sets out what both sides agreed to. If your work needs a formal contract, attach it and say so in one line.

Two small things raise the chance she replies at all:

• Send it while the call is fresh. The same day or the next is better than a polished version a week later.
• Offer to walk her through it. "I'm happy to go through this on a ten-minute call" gets the questions answered quickly.

If she goes quiet, follow up once or twice on a date you choose, and write the date down.

What does a one-page proposal look like?

Here's the bakery proposal in outline, short enough to read on a phone:

1. What you told me: the phone rings all morning with cake orders; you'd like online orders and payment.
2. What I'll build: a five-page site with an online cake order form, taking payment when the order is placed.
3. Not included: photography, writing cake descriptions, changes after launch, delivery booking.
4. Price and payment: one price; half to start, half before launch; hosting and domain paid by you, in your name; price holds for 30 days.
5. Dates: start the week after the deposit; first version two weeks after photos arrive; live the week after your approval.
6. What I need from you: photos, the cake price list, access to your domain account, one review call.
7. Next step: reply "yes" and I'll send the deposit invoice.

Keep a copy of every proposal you send, with the date. When the work starts, the proposal becomes the brief. When a question about scope comes up in month two, it's what you both go back to. And when the build begins, the same seven lines tell you, and any tool that helps you build, review and deliver client websites, exactly what was promised.

Where should proposals and prices live?

Proposals get written in documents, sent from email, discussed on calls and paid through a payment link. A month later, the version she agreed to can be hard to find.

Volant keeps each business's research, offer and payment together. Your agent drafts the offer from your prices and the facts you approved, and Volant marks a payment as received only when Stripe confirms it. The page on quotes, deposits and payments shows how that fits together.

Whatever you use, the rule for the proposal is the same: her problem first, the price where she'll see it, what's not included in writing, and one way to say yes.