What do you pay a web designer for? Mostly for the work you never see on the homepage: deciding what the site contains, designing it in rounds, building it so your team can run it, and supporting it after launch. If your quote shows one price for "design", some of that work is either folded in without being named or left out until it shows up as an extra.
Start with the phase before any visuals. Agency proposals usually open with discovery: research, a sitemap, wireframes. It's paid work because it decides which pages exist and what each one has to do. Skip it and the cost doesn't vanish. It moves into redesigns, after the layouts are built. A quote with no line for it is either skipping the step or hiding it inside another price.
Design comes next, and the useful question is how many rounds it includes. Good quotes say how many rounds of changes are covered, ask for requests in writing, and state what happens when you add pages or deliverables mid-project. Wix Studio's guidance on proposals puts it plainly: extra deliverables or extra working days carry additional fees, and the terms should say so up front. If your quote is silent on this, assume the answer is "extra".
Then the build. Development, CMS setup, integrations and testing all live in this line. What owners miss is what they can edit alone afterwards. Phenomenon Studio suggests the quote should spell out what your team can change without a developer, such as blog posts, page copy, images and team profiles, and what still needs one. A site you can't touch without calling the studio is a different purchase from one you can.
Content is where quotes disagree most. Copywriting and photography are among the items proposals most often list as excluded, along with third-party integrations and ongoing SEO. In one itemised example from FreshBooks, content creation sits at $500 in a $6,760 first-year total, but the same page gives a range of $500 to $5,000 for that line. That is the widest swing of any item in the example, so ask who writes the words and who pays for the photos before you compare prices.
Launch and the weeks after are the other place quotes thin out. Migration, QA and training belong in the price. Support should have a stated length, the kinds of issues it covers and how fast they get answered. Phenomenon Studio contrasts a defined ninety-day support period with a thirty-day bug warranty that never says what counts as a bug. The second sounds like cover but promises nothing you could hold anyone to.
Last, look for recurring costs. Domain registration, image licences and plugins are hard costs, and Wix Studio recommends itemising them and noting which renew monthly or yearly. In the FreshBooks example, maintenance alone runs about $500 to $1,000 a year, and the page notes that the $6,760 total covers only the first year. A site costs the quote plus what comes after it.
Payment terms tell you how the studio thinks about the work. Phenomenon Studio argues for tying each payment to your approval of a named deliverable, rather than to a date or a vague percentage complete. It also notes that a flat 50% upfront and 50% on completion shifts the risk towards the studio's side of the table, not yours.
Before you sign, lay the quote next to this list and mark every line it doesn't mention: discovery, design rounds, CMS editing, content, launch, support, recurring costs. Send the gaps back as questions. A studio that prices the whole job will answer them without fuss, and the answers are worth more than the price on the first page.