A polished proposal is not evidence of a good agency. It’s evidence of a good sales process. The two are often unrelated.
Most web design proposals are written to win the deal, not to give you an accurate picture of what you’re buying. Learning to read them critically is one of the most valuable things you can do before committing $5,000–$20,000+ to a website build.
What a Proposal Is — and What It Isn’t
A proposal is an offer, not a contract. Until you sign a statement of work (SOW) or service agreement, nothing in a proposal is legally binding. The timeline, deliverables, team structure, and price can all change once the engagement starts — unless the contract explicitly prevents that.
When you read a proposal, read it as a marketing document first. Ask: what is this agency trying to communicate about itself? Then look for what’s missing — the specifics that would make the offer enforceable and comparable.
How to Read the Scope Section
The scope section is the most important part of any proposal, and the section most likely to be vague. Look for these elements specifically:
Deliverables listed by page or feature, not by category. “Full website design and development” tells you nothing. “10-page WordPress site with custom theme, contact form, Google Maps integration, and SEO metadata on all pages” tells you what you’re buying.
Revision rounds. How many rounds of design revisions are included? One? Three? Unlimited? “We work until you’re happy” is not a revision policy — it’s a liability. And conversely, “one round of revisions” on a fixed-price project is tight. Know what you’re getting before you start.
What’s explicitly excluded. A good scope section tells you what’s not included — copywriting, photography, hosting setup, email configuration, plugin licenses. Agencies that omit the exclusions tend to price low and charge separately for every addition.
Tom hired an agency based on a $7,200 proposal for a custom site. By the time the site launched, he’d paid an additional $2,400 in “out-of-scope” charges for stock photo sourcing, a contact form plugin license, and “additional revision cycles.” The original proposal hadn’t mentioned any of those items as exclusions.
The Timeline Problem
Agency timelines in proposals are almost always optimistic. The question isn’t whether the timeline is realistic — it’s whether the contract holds anyone to it.
Look for milestone-based timelines, not calendar-based ones. “Design complete in week 3, development complete in week 6, QA and launch in week 8” is a timeline you can track. “Project completed within 8 weeks of kickoff” is an intention.
Also look for what extends the timeline. Most contracts include a clause that pauses the clock when the client is slow to provide feedback or assets. That’s fair. But some agencies pad their scopes with enough review periods that any delay — including their own — can be attributed to the client.
A realistic timeline for a custom 10–15 page WordPress site is 4–8 weeks if both sides are responsive. If the proposal quotes 12+ weeks for a straightforward business site with no unusual features, ask why.
Team Structure: Who Actually Does the Work
Many proposals include language about “our team of designers and developers” without specifying who, at what experience level, is doing your project.
Some agencies quote senior rates and assign junior staff. Some use overseas contractors at different skill levels than their principals. Neither of these is necessarily disqualifying — but if the proposal implies senior-level work and the build gets handed to a junior developer, you’re not getting what you paid for.
Ask directly: who will be the primary developer on this project? Can I see their work specifically — not the agency portfolio, their work?
At Designodin, the person who scopes the project builds the project. No junior handoff, no subcontracting without disclosure.
Evaluating the Pricing Structure
Pricing structures reveal priorities. There are three common models:
Fixed-price proposals quote a single number for defined scope. Good for the client when the scope is specific enough to hold. Risky when scope is vague — because “out of scope” charges become unpredictable.
Hourly proposals quote a rate and an estimated number of hours. The client pays for actual time spent. Good for genuinely open-ended projects. Risky for straightforward builds where an experienced agency should be able to commit to a price.
Phased proposals break the project into separately-priced stages — discovery, design, development, QA. Good for complex projects. Problematic when each phase requires re-approval and re-commitment, extending the sales cycle indefinitely.
For most business website builds, a fixed-price contract with clearly defined scope is the cleanest arrangement for both sides. The Start packages at Designodin publish prices, scope, and timeline before any conversation starts — because the way an agency handles their own pricing tells you how they’ll handle yours.
What Proposals Often Don’t Tell You
Some omissions are accidental. Some are strategic. Watch for:
No mention of performance standards. If a proposal doesn’t mention PageSpeed scores, mobile optimization benchmarks, or Core Web Vitals, ask whether they’re included. “Mobile-friendly” is a minimum, not a differentiator.
No post-launch support terms. What happens after the site launches? If there’s a bug discovered a week later, who fixes it and at what cost? Most proposals are silent on this, which usually means it costs extra.
Technology stack not specified. If a proposal doesn’t tell you what tools the site is built with — WordPress, custom theme vs. page builder, which plugins — ask. The answer affects performance, ownership, and maintainability.
Portfolio links that don’t include performance data. Run the sites in an agency’s portfolio through Google PageSpeed Insights. If they’re consistently scoring under 60 on mobile, the proposal’s performance claims don’t match reality.
You can audit any site’s technical setup yourself before signing anything. Honest runs a fast, independent check on SEO health, speed, and technical quality — useful for evaluating an agency’s existing work before you hand them yours.
The Comparison Problem
Comparing proposals from different agencies is genuinely difficult because scopes are rarely equivalent. One agency quotes $6,000 for a “custom site.” Another quotes $12,000 for “custom development.” The difference might be quality, or it might be page count, or it might be that one is using a template and one is writing code from scratch.
Build a comparison matrix. For each proposal, fill in: number of pages, design rounds included, page builder or custom code, performance benchmarks promised, ownership terms, timeline, and what’s excluded. When you lay them side by side on those dimensions, pricing differences become much easier to evaluate.
A higher price for clearly better terms is usually the right call. A higher price for vague terms compared to a lower price for vague terms is a coin flip.
For custom WordPress development where performance, ownership, and timeline accountability matter, ask the agencies you’re evaluating to fill out that matrix for their own proposal. Agencies with good processes can answer those questions clearly. Agencies running on vague language tend to deflect.
FAQ
Is it normal to pay for a proposal? For complex projects — large e-commerce builds, multi-site networks, applications — paid discovery or scoping work is reasonable. For a standard business website, you should not have to pay for a proposal. If an agency charges for a proposal on a 10-page site, that’s a preference, not a necessity.
How many agencies should I get proposals from? Two or three is enough to establish a reasonable comparison. More than four tends to be noise — at that point the difference between proposals is harder to evaluate clearly, and you’re investing a lot of time in conversations that are mostly sales processes.
What if a proposal has a non-disclosure clause? Some agencies include NDAs around their pricing. This limits your ability to share the proposal with other agencies for comparison. It’s a legal right they have but a signal worth noting — agencies that don’t feel the need to hide their pricing are usually more confident in it.
Can I negotiate the price on a proposal? Yes. But negotiate scope, not just price. Asking an agency to cut 20% of the price without cutting scope puts pressure on quality or margin — and the quality is what usually suffers. A better negotiation is: what scope would $X get us? What’s essential and what isn’t?
What’s a reasonable payment structure for a website build? The standard is roughly: 30–50% upfront, 30–50% at design approval, and the remainder at launch. Any proposal asking for 80–100% upfront before work starts is a risk concentration problem. Any proposal asking for nothing until launch is asking you to carry all the risk.
How do I know if the portfolio work is actually theirs? Ask for the client’s name or company so you can verify. Agencies occasionally show work that isn’t theirs or inflate their team’s role in a project. A straightforward agency will give you references for the projects in their portfolio.