What a good proposal tells you
A website proposal is a document, but it is also a preview of how a studio operates. The way a studio scopes its work, structures its thinking and explains its costs tells you more about the project experience ahead than any reference or case study. Here is what to look for and what the gaps mean.
Clear scope definition
A strong proposal defines what is included and, just as importantly, what is not. The page list should be specific: this many pages, this many CMS templates, these integrations. If the scope is described in general terms, the quote is not the real price. It is a starting point before the scope surprises begin.
Exclusions are equally important. A proposal that defines out-of-scope work, such as content writing, photography or post-launch changes, is being transparent about where extra costs may come from. A proposal with no exclusions either includes everything, which is rare, or has not addressed the question.
A defined process
The proposal should describe what happens and in what order. Discovery, design, build, content, QA, launch and handover should each appear as distinct phases with an indication of timing. A studio that goes straight from signed contract to here is your website in the process description is not describing a process. It is describing a result without explaining how it gets there.
Realistic timelines
A timeline that accounts for client feedback cycles is more trustworthy than one that does not. If a proposal shows a ten-week timeline but allocates no time for review rounds, something is missing. Ask how many rounds of revisions are included at each phase and what happens when feedback takes longer than expected.
What the cheapest quote usually means
The cheapest quote in a competitive process is almost always the one with the narrowest scope. The studio is not more efficient. The project has been scoped more tightly, with less time for revisions or a thinner strategy phase. A comparison between quotes is only meaningful when the scope being quoted is the same. If it is not, the comparison is between different projects at different prices.
Questions worth asking
Who will actually be working on the site? A studio that pitches with senior people and delivers with junior people is not uncommon. Ask directly who you will be talking to week to week and who will be doing the work.
What does handover look like? A site delivered without proper training leaves a business dependent on the studio for changes their team should be able to make themselves. Handover should be a defined part of the project, not a call at the end.
Frequently asked questions
How many quotes should I get?
Two or three is enough to get a useful sense of the market. More than three and the time spent briefing studios starts to outweigh the benefit of the comparison. The goal is to find a studio whose approach and scope make sense, not to find the lowest price across the widest possible sample.
Should I choose the cheapest proposal?
Only if the scope is the same as the others. If it is cheaper because the scope is narrower or the strategy phase is smaller, factor in what the missing elements will cost later. Website projects that start too cheap tend to arrive at roughly the same final cost as well-scoped projects, through change requests.
Is a fixed-price proposal better than time and materials?
Fixed price offers cost certainty. Time and materials offers flexibility. Fixed price is better when the scope is fully defined at the start. Time and materials suits projects where scope is likely to evolve. A good studio can explain which model suits the specific project.
Can I negotiate on a website proposal?
Yes, within limits. Negotiating scope is reasonable. Asking for the same scope at a lower price typically results in less time on the project or a lower rate with quality following. The more productive negotiation is about scope: what can be phased to a second stage, what is essential for launch and what can wait.
.png)