Web Design Proposal Template: Draft Scope, Fees and Timeline With AI

An agency can draft a clear web design proposal with AI by feeding it structured discovery-call notes, your own fees and phase split, and a fixed template, then asking for scope, phases, payment schedule, assumptions and revision limits in plain English. The agency sets the price and reads every line before it goes out.

The safe pattern has one rule: AI organises what you decided, it does not decide. Scope gets disputed, not prose. If the model rounds a vague sentence into a promise ("full SEO optimisation included"), you own that promise. The sections below give a template, a filled example with numbers, the prompt, and the checks that stop the model's tendency to add things.

Follow me on Instagram@sagnikteaches

From discovery call to proposal: what to capture before you prompt

Quality in, quality out. The prompt needs facts from the call, not a transcript. Capture these in a short note straight after the conversation, using the questions from the web design client questionnaire if the client has completed one:

Connect on LinkedInSagnik Bhattacharya

• The business in one sentence and the main action visitors should take.
• The pages and features wanted, and anything explicitly not wanted.
• Who supplies text, photos and logo, and by when.
• The approver, the launch date and what it is tied to.
• Tools to connect (forms, booking, payments, email list).
• The budget range, if the client shared one.
• Your decisions: the fee per phase, the revision limit and the day rate for extras.

The last bullet is the one people skip. If the model has to guess a fee, it will invent one. Give it numbers, even if they will change after review.

Subscribe on YouTube@sagnikteaches

The template, section by section

Nine sections cover most small-business projects. They can be read in five minutes, which is about what a client will give them.

1. Summary: the goal in the client's words and the outcome you will deliver.
2. Scope: the pages, features and deliverables, each as a short line.
3. Out of scope: what is not included, stated plainly.
4. Phases and timeline: what happens when, with client dependencies marked.
5. Fees and payment schedule: one total, split by milestone.
6. Assumptions: what the price relies on, and what happens if it proves wrong.
7. Revisions: how many rounds, what counts as one, what extra rounds cost.
8. Ownership and handover: what the client receives and when they own it.
9. Acceptance: how to approve, and by what date the offer stands.

Sections 3, 6 and 7 do the work in a dispute. A generic template from a download site usually has them as a single line. Expand them for this client.

Filled example: a six-person plumbing firm

Illustrative case. A plumbing firm wants a seven-page site (home, boiler repair, bathroom installation, emergency call-outs, areas covered, reviews, contact) with a quote request form and a click-to-call button. They will supply the logo and 30 photos of their own work, and the owner approves everything. The agency's decisions: a total of $6,400, a six-week timeline from receipt of content, two revision rounds per phase, and $90 an hour for extras. All figures are illustrative.

Check the sum: 40% of $6,400 is $2,560; 30% is $1,920; $2,560 plus two lots of $1,920 is $6,400. A model can slip on arithmetic like this, so recompute every figure yourself. The 40/30/30 split is an example, not a rule. Choose a split that keeps your cash flow safe: a deposit large enough that the client has a stake, and a final payment tied to launch so it does not hang on a late sign-off.

The drafting prompt

Give the model the template headings, your decisions and the call notes, and forbid additions. Illustrative prompt:

You draft web design proposals for a small agency. Use ONLY the notes and decisions below.
Write in plain English, no marketing language, under 900 words, using these headings: Summary, Scope, Out of scope, Phases and timeline, Fees and payment schedule, Assumptions, Revisions, Ownership and handover, Acceptance.
Do not add services, deliverables, guarantees or numbers that are not in the notes. If something needed is missing, write [CONFIRM: what is missing] instead of guessing.
Fees and phases (fixed by the agency): [paste]
Call notes: [paste]

The line about "[CONFIRM: ...]" is the control that stops the model filling gaps with guesses. A good run leaves two or three such flags, which become your follow-up questions. If it leaves none, be suspicious.

What a typical first draft gets wrong

Illustrative first output for the plumbing firm included these sentences, and the edit each needed:

• "We will optimise your site for search engines." Unscoped and unbounded. Replace with a specific deliverable: "page titles, descriptions and headings set for each page; no ongoing search work".
• "Unlimited revisions until you are happy." The model added it to sound friendly. Delete and restate the two-round limit.
• "The site will be mobile-friendly and accessible." The first is a reasonable commitment; the second is not, unless you test against a standard. Say "tested on current phone, tablet and desktop browsers" and, if you promise accessibility, name the level you will test to. Accessibility checks before handover covers what is realistic.
• "Hosting and maintenance included." Not in the brief. Delete, or offer it as a separate line, which is where a maintenance plan comes in.

Assumptions that protect the price

An assumption is a statement that, if false, changes the price or timeline. Each should carry its consequence. Filled examples for the plumbing project:

• "The client supplies all text and photos by the end of week 2. If they arrive later, the launch date moves by the same number of days."
• "One person approves each stage. If feedback arrives from more than one person, the client consolidates it before sending."
• "Up to 30 photos are used. More are charged at the extras rate or the client chooses which to keep."
• "The quote form sends to a single email address. CRM integration is not included."
• "The client owns or controls the domain name and gives us access by the end of week 1."

Ask the model to produce a first list from the call notes and then ask yourself what is missing. The commonest gaps are who owns the hosting, what happens if the client's photographer holds the rights, and whether copy written by AI is acceptable to the client at all. State the last openly if you plan to use AI in drafting copy.

Revision limits that survive contact with a client

A revision limit only works if "round" has a definition. Write it down:

• A round is one consolidated set of changes sent in one message by the named approver.
• Changes within the agreed pages and layout count as revisions; a new page, a new feature or a change of direction is a change request.
• Feedback sent in pieces over several days counts as one round when we receive the last piece, and the clock for turnaround starts then.
• Further rounds cost an agreed hourly rate, quoted before the work starts.

Illustrative failure: a client sends six emails of changes over a week, each marked "small tweak". Without a definition, you have done six rounds. With one, you have done a round and a half, and you have the words to say so politely. When the client then asks for a new service page, a change order handles it without an argument.

Timeline sums with client dependencies built in

Timelines slip at the client's end, so put the dependencies in the schedule. A useful discipline: write the timeline as "X working days after Y" rather than calendar dates. "Design starts 3 working days after we receive the signed brief and deposit" holds up. "Design starts 12 March" does not. Illustrative sum for the plumbing project: 6 weeks is 30 working days; if text and photos arrive 5 working days late, the launch moves 5 working days, not 1 or 10. Say so in the proposal.

Build a 10 per cent buffer into the internal plan, not the client's promise. On a 30-working-day schedule that means planning to finish three working days before the date you gave the client, so one unlucky feedback round uses the buffer instead of moving the launch.

Where the fee comes from: a quick hours model

The model must be handed a fee, so work one out first. A simple method is to list the hours by phase, multiply by your internal rate, add a contingency, and compare the result with what the client can afford. Illustrative hours for the plumbing project: kick-off and structure 6 hours, design 20, build 28, content entry and forms 10, testing and launch 8, project management 8. That totals 80 hours. At an internal rate of $70 an hour the cost is $5,600; a 14 per cent margin and contingency brings it to $6,384, which rounds to the $6,400 quoted. The rate and margin are examples, not benchmarks. What matters is that the number can be traced to hours, so you can defend it and adjust scope instead of discounting when the client's budget is lower.

If the client's budget is lower than your number, reduce scope in the proposal rather than the hours. Drop the reviews page, cut the photos to 15, or move the emergency page to a second phase. Ask the model for "a reduced-scope version at $4,800 that removes the least important items", then check what it removed against the client's stated priorities. It will often cut something the client named as essential, so read the removals line by line.

Choosing a payment schedule: three common shapes

The schedule is part of the proposal, so choose it deliberately and tell the model exactly what you chose.

Whichever you choose, tie the final payment to launch, or to a set number of days after the build is ready for review, whichever comes first. Otherwise a client who delays sign-off delays your money. State the late-payment consequence in your terms, which a qualified adviser should word, and have the proposal point to them rather than invent wording.

Second filled example: a three-person cleaning company

Illustrative case: a cleaning company wants a five-page site with a booking enquiry form and a price guide. Scope: home, domestic cleaning, commercial cleaning, about, contact; a form that emails the office; a price guide page that the client writes. Fee $3,200, split 50/50. Timeline: four weeks from content. Revisions: two rounds in total. Assumptions: the client writes the price guide; the client supplies photos of the team; the domain is already registered.

The AI draft for this client made two instructive errors. It described the booking form as "an online booking system", which is a different and larger product, so the sentence was rewritten to say "a form that emails each enquiry to one address". And it put "we will manage your social media links" in the scope because the owner had mentioned Facebook on the call. The fix was a line in out-of-scope: "Social media accounts are linked from the footer; we do not manage them." Both errors share a pattern: the model turns a passing remark into a deliverable. Reading each scope line against the call notes catches it.

Sending the proposal and handling the follow-up

A proposal read cold gets fewer yeses than one walked through. Offer a fifteen-minute call to go through it, and send a short covering note: what is attached, the one decision you need, and the date the offer stands. If the client asks for changes, treat the reply as a negotiation about scope, not a chance to quietly add work. For each requested addition, say what it costs in hours or fee, or what comes out to make room.

Illustrative reply: a client asks to add a news section to the plumbing site. Do not say yes by reflex. The reply reads: "A news page and set-up for posts is an extra $450. If you would rather keep to $6,400, we could drop the areas page and add the news section instead. Which would you prefer?" The model can draft that reply in seconds from your numbers, and you can send it after a read. The proposal's structure, with its out-of-scope and extras rate, has done the heavy lifting.

When the proposal is signed, move to the next stage with a kick-off note: the brief, the dates, the client's first tasks and who to contact. Keep the signed proposal beside it, because it is the reference that the change order process compares requests against.

Checking the draft before it goes out

1. Numbers. Recompute every total and percentage. Check that phase payments add to the fee.
2. Promises. Search the draft for "guarantee", "unlimited", "fully", "all", "ongoing" and "including". Each is a possible hidden commitment.
3. Trace to notes. Every deliverable must appear in the call notes or your decisions.
4. [CONFIRM] flags. Resolve every one, or turn it into a question for the client.
5. Client's words. Does the summary use their goal, not a model's phrase?
6. Read it as the client. Could someone with no web knowledge tell what they will receive, what it costs and when?

Then send it with a short covering note and a date by which the offer stands. If you also quote against alternatives such as a DIY builder, AI website builder or web designer: what each really costs gives the comparison clients are already making in their heads.

Using the same prompt across clients without producing clones

Once the prompt works, save it with the template, a fee table you have approved, and a library of assumptions to pick from. Each new proposal then starts from your approved wording, and the model's job shrinks to arranging this client's facts. Resist the urge to let it freewrite the summary: it tends to produce similar phrases for different clients, and clients who compare notes will notice. Write the summary yourself in two sentences from the call, and use the model for the sections that are structured.

Keep each sent proposal, with the prompt notes and your edits, so you can see which sections you keep correcting. If you always delete the same sentence, fix the prompt. What ChatGPT gets right and wrong when designing a site is useful background on where model output needs the same sort of correction later in the project.

A short example of the same proposal for a smaller job

Not every project needs nine sections. For a one-page site for a pest-control technician with a single service and a phone number, a half-page proposal is enough: one paragraph of scope, three assumptions, a fixed fee of $900 with half upfront and half on launch, and one revision round. The shape of the template stays the same, so scope, assumptions and revision limits are never missing. Cut sections down rather than leaving them out, because the headings are what protect you.

The same holds for a larger job. A roofing company wanting a twelve-page site with a quote calculator would add a phase for the calculator and an assumption about who supplies the pricing rules. Notice that this is a new line in the scope and the fee, not a larger promise buried in an existing line. If you would rather build the proposal workflow with someone, that is what my AI implementation consultation covers, at the contact page.

Questions agencies ask about AI-drafted proposals

Should AI set the price in a web design proposal?

No. Price is your decision, based on your hours, margin and the client's budget. Give the AI your fee and phase split and ask it to present them clearly. If you ask it to suggest a figure, it will produce a plausible number with no link to your costs.

How many revision rounds should a proposal allow?

Two rounds per phase is a common starting point, but the right number is the one you can deliver profitably. State what counts as a round, name who consolidates feedback, and say what extra rounds cost. The limit matters less than the definition.

What should the assumptions section cover?

Anything that would change the price if it turned out differently: who supplies the content and when, how many pages, who supplies images, the approver, the hosting arrangement and third-party tools. Each assumption should say what happens if it proves wrong.

Can the proposal double as the contract?

Some agencies attach terms to the proposal so one signature covers both. Terms are a legal document, so have a qualified adviser review yours. Use AI for the plain-English proposal and let the adviser's wording govern the contract.

Further reads

• AI Wireframe Generator for Web Designers: From Brief to Clickable Draft — Turn the signed brief into a clickable draft.
• Website Development by AI: What Agencies Can Ship and What Needs Review — What AI can build once the proposal is signed.
• AI Accessibility Audit: Can It Replace a Manual WCAG Check? — Whether AI can replace a manual accessibility check.
• AI Content Management Platform: How a Web Agency Picks One for Clients — Score WordPress, Webflow, Squarespace and Wix per client site on editor AI, hosting, cost and handover, then apply a simple decision rule.
• AI Scope of Work Generator for Agencies: SOWs With Change Control — A worked example from client call to signed SOW: counted deliverables, exclusions, change-control wording and a filled change request form.
• Figma Make for Web Designers: Client Prototypes and Where It Breaks — How a web designer can turn a brief into a clickable Figma Make prototype, which plan to check, and the places it tends to fall short on real client work.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: practical agency workflow; fees and figures in the example are illustrative and not market rates.