A web design proposal is the document you send to win a website project: the client's situation, the scope and objectives, the process phase by phase, the fees, a billing plan, and the terms. Its most important job is not persuasion but definition — stating what is included, what is not, how many revisions you will do, who supplies the copy, and what happens when the client asks for something new. A proposal that skips those questions does not avoid them; it just answers them in your client's favour later.
Most web design projects that lose money were priced correctly. They failed in the gap between what the designer assumed and what the client assumed, and the proposal was where that gap should have closed. Below is the structure, the specific clauses that carry the weight, and the claims to leave out. If you are still filling the pipeline, the companion piece covers how to get web design clients.
AI-generated audio summary of this article, created with Google NotebookLM.
The components a design proposal contains
The most useful reference here is not a blog consensus but the profession's own template. AIGA's Standard Form of Agreement, drafted with named intellectual-property attorneys, is modular by design: you write the proposal and attach the standard terms, and together they form the agreement.
Its stated components:
- Cover letter — written last, short, an invitation to a conversation. It must not restate the proposal.
- Overview of the client's situation — their market and competitive challenge, in their language.
- Scope of work and objectives.
- The recommended process — broken into phases. The load-bearing section.
- Recap — total timeframe, fees, expenses, taxes.
- Billing plan — amounts and timing.
- Terms and conditions.
- Two signature lines.
- Optional team bios and credentials — specifically for when the document reaches an executive who never met you.
AIGA adds two pieces of practical advice worth copying: present in person where you can, and put an expiration on it ("effective for ___ days after presentation") so a stale price does not bind you six months later.
The scope section is the proposal
Everything else is framing. The scope is the part that determines whether the project is profitable, and the general project-management evidence is unambiguous about why.
In a survey of 5,402 project professionals, 52% of projects experienced scope creep, up from 43% five years earlier — and two of the three leading causes of project failure were change in project objectives and erroneous requirements gathering. Those are not delivery failures. They are definition failures, which is precisely what a scope section exists to prevent.
Two honest caveats. That data covers projects generally, not design projects specifically — I use it as a labelled proxy because no credible survey of scope creep among designers exists. And PMI's later reports show lower figures on a changed instrument, so treat these as one snapshot rather than a trend.
The corresponding failure is that scoping documents often are not written at all: in a survey of 214 organizations, only 52% mostly or always create a scoping document, and only 34% mostly or always finish on budget. That sample is self-selected, so read it directionally — but the two numbers sitting next to each other tell a coherent story.
For each phase, AIGA instructs you to spell out what is included and what is not, and to specify the sequence of steps, the deliverables and milestones, the number of creative directions shown, the number of revisions included, the delivery format, the timeframe, and a fee subtotal — plus the client's own responsibilities and how they will be integrated into the process.
The two-tier change clause that stops scope creep
This is the single most useful mechanism in the whole document, and most proposals collapse it into one vague sentence.
AIGA splits changes in two:
- General changes bill on a time-and-materials basis at your stated hourly rate. The clause is explicit that these charges apply "despite any maximum budget, contract price or final price" named in the proposal.
- Substantive changes — those exceeding a stated share of the time, value, or scope — entitle you to submit a new and separate proposal, and "work shall not begin on the revised services until a fully signed revised Proposal" is received.
AIGA's commentary suggests defining substantive as anything above roughly 10% of the original schedule or budget, or a fixed dollar amount, whichever is greater. It describes the change order as "essentially a mini-proposal" — referencing the original, confirming the same terms, describing the added time and money, and coming back signed. Each one is invoiced separately as it completes.
The reason the split matters: small changes should bill without interrupting the work, and large ones should stop it. A single "additional work will be charged extra" line does neither. In practice it means you absorb the small requests to stay pleasant and then have an argument about the large one, which is exactly the sequence that damages both the margin and the relationship.
Name who writes the copy
Content is the most reliable cause of overrun in website projects, and one clause decides it.
AIGA makes the client responsible for supplying content "in a form suitable for reproduction or incorporation into the Deliverables without further preparation" unless the proposal says otherwise. That phrase — without further preparation — is what determines whether you write the copy for free. If your proposal is silent, the default is a dispute in week six.
Pair it with the schedule clause: your ability to meet dates depends on the client's prompt performance, and client-caused delay is not your breach. Most studios turn this into a day-for-day extension of the final deadline, which is worth stating plainly, because "we are waiting on content" is otherwise a problem that appears on your side of the ledger.
Define done: acceptance, revisions, and browsers
Three definitions convert a subjective argument into a contractual fact.
Acceptance. AIGA gives the client five business days to object in writing, after which the deliverable is deemed accepted. Commentary suggests five to ten days, and adds the idea of cure — you get the chance to fix non-conforming work before the client can treat it as a failure.
Revisions. The widely repeated "two to three rounds is the industry standard" has no survey behind it. The point is not the number but that a number exists. The best-known professional precedent scopes one main design plus up to two rounds of revisions, after which the client pays for work completed and either stops or continues at the day rate.
Browser and device support. Name the browsers you tested, name those available on request, and name the exclusions outright. "Works in all browsers" is unbounded scope with no upper limit and no way to prove completion.
Note also that professional templates make no promises about business outcomes: AIGA explicitly disclaims any warranty of fitness for a particular purpose. You are not warranting the site will hit a revenue target, and you should not imply otherwise in the proposal's enthusiasm.
Pricing, deposits, and the payment clause that protects you
On price levels, the honest position is that no primary source publishes a trustworthy benchmark range. The best available is a 2025 survey of 208 web designers, which found 57% charging $2,500–$9,999 per project, only 2% above $10,000, 82% pricing per project, and only 15% charging for discovery. That sample was recruited from the publisher's own audience, so treat it as a signal about that community rather than the industry.
The 15% figure is the interesting one. Discovery is the phase that produces the scope, and most designers give away the work that makes the rest of the project definable.
AIGA's method for arriving at a fixed fee is worth more than any benchmark: map the process step by step, size the team, estimate hours against your standard rate, add outside purchases with a markup, then adjust for the value of the work to the client. Third-party costs — photography licences, fonts, hosting — bill to the client unless stated otherwise, and AIGA advises against brokering expensive vendor purchases yourself, since a vendor failure is far safer if the client bought directly.
Two structural protections to carry across:
- Deposits. Ask for one whenever possible, and decide explicitly whether it applies to the first progress billing or is held against the final invoice. The familiar "25–50% is standard" claim is craft convention that no survey has measured.
- Payment as leverage over intellectual property. AIGA conditions every licence and transfer of ownership on receipt of payment in full, and reserves the right to withhold delivery. This is the clause that matters most when a project goes wrong, and it is the one most freelance proposals omit. Non-payment is not a rare event: in a survey of over 5,000 US freelancers, 71% had struggled to collect at least once.
What to leave out of your proposal
Three claims appear constantly in design proposals and none of them survives a prospect checking.
"94% of first impressions are design-related," credited to Stanford. The attribution is wrong. The trail leads to a 2004 study of 15 participants browsing health advice websites — and the 94% split does not appear in accessible versions of that paper at all. The genuine Stanford web-credibility research measured something different and far larger: across 2,684 participants, design was mentioned in roughly 46% of credibility comments. That is a better statistic and it happens to be real.
"Users form an opinion in 0.05 seconds." The underlying study is real, but it measured visual appeal ratings at 50 versus 500 milliseconds. It did not measure trust, purchase intent, or conversion. The common escalation to "users decide whether to buy from you in 50 milliseconds" is not supported by it.
Freelance scope-creep statistics. The figures circulating — that a Freelancers Union study found 67% of freelancers do unpaid work from scope creep, that 72% of freelance projects suffer scope creep, that it costs $15,000–$25,000 a year — are attributed to studies that do not exist. The honest version is more persuasive anyway: the profession's standard contract devotes two full clauses to change control, which tells you what designers collectively learned to defend against.
From scope to signature
A precise proposal takes longer to write than a vague one, and that time pressure is why designers reach for a generic template and then negotiate the scope after signing. The way out is to make the tailored version cheap. Pitchko turns a prospect's own URL into a personalized proposal in minutes, leaving your effort for the parts that carry legal and commercial weight: the phase breakdown, the change-order threshold, and who supplies the copy. For the multi-service version of this structure, the digital marketing proposal guide covers scoping several channels in one document.
Write the scope as though you will have to defend it in month three, because that is when it gets read.
