What a web-build quote and scope should spell out

You've just realised your business needs a website, or it needs rebuilding, and you've asked a designer or developer for a quote. They've sent back a document — maybe a PDF, maybe a Google Doc — but you're staring at it unsure whether it actually tells you what you're paying for. A vague line item like "design and build" or "website package" leaves you guessing about what's included, what happens if you want changes, and what you'll hand over at the end.

A solid quote and scope of work document should make the entire project transparent. It answers the fundamental question: what exactly are you building, and what's in or out of that price?

The core deliverables need naming

Your quote should spell out the actual outputs. This means listing the number of pages, the types of pages (homepage, about, services, contact, blog, etc.), and what functionality each one will have. If your site needs a contact form, appointment booking, product listings, a payment gateway, or integration with your email marketing platform, each should be named explicitly. If it's WordPress, Shopify, a custom build, or a page builder — the platform matters, and it should be stated.

Don't accept vagueness like "unlimited revisions" or "as many pages as you need." Instead, look for specific numbers: "five main pages plus a blog template"; "up to two rounds of revisions on each page design"; "custom code for X feature." If the designer offers "revisions," ask how many rounds, and whether revisions mean tweaks to existing designs or full redesigns. The boundary matters; moving a button once is different from rebuilding an entire section.

Included should also be clarity on imagery. Will they source stock photos? Do you provide your own? Is video hosting included, or is that hosted by you? Are there limits to how many images or videos the site can contain? Web hosting, domain management, SSL certificates — these often confuse buyers because they sound like they should be free but aren't. The quote should state whether the final price covers a year of hosting, or whether that's separate and payable to someone else.

What maintenance and future changes look like

Most quotes cover the build phase but stay silent on what happens after launch. Ask whether the price includes handing over a site you own and control, or whether you're renting access. Can you update content yourself, or do you need to pay the designer every time you want to change a sentence? Does the quote include training or documentation so you (or someone cheaper later) can manage the site independently?

Small sites don't always need ongoing maintenance, but larger or more complex ones do. If security updates, backups, performance monitoring, or plugin updates are part of the plan, these should be listed separately as optional add-ons with their own cost. If the designer assumes they'll manage the site forever and you assume you'll do it yourself, that's a collision waiting to happen. Your scope should clarify this boundary.

Hidden or often-missed elements

Many quotes miss things that become obvious only after the build starts. Is mobile responsiveness automatic, or does designing for phones and tablets cost extra? Is SEO setup (clean URLs, meta tags, sitemaps) included, or is that a separate package? What about performance testing or accessibility checks? If you're selling products, does the price cover basic payment processing setup, or does that vendor's integration fee land on you later?

Also ask: what happens if you change your mind halfway through? Is there a kill fee? Can you pause the project? If the designer goes out of business before launch, do you own the partially finished work? These scenarios feel unlikely until they happen.

A strong quote also notes the timeline clearly — start date, expected completion, and what counts as completion (launch to a live domain, or handing over files you then deploy). It should name who does what: if you're responsible for writing page copy or gathering images, that's your job, not the designer's scope.

When you receive a quote, don't assume gaps will be filled in later. Pick it apart with the designer, ask for clarifications in writing, and only once it reads like a complete picture — one you'd be comfortable explaining to someone else — should you commit. A clear scope protects both you and the designer. On Strove, you can compare quotes from verified web designers side by side, which makes it easier to spot which ones leave you guessing and which ones spell it all out.