What a Website Quote Should Include (And How to Audit One You Already Have)

A website quote is a document, not a number. A real one specifies scope in countable units, names who writes the content and by when, sets a revision limit, states what happens to the code and the accounts at handoff, and lists what is explicitly excluded. Anything a quote does not mention is not included for free — it is an assumption, and assumptions turn into change orders once you have already signed and have no leverage left.

This article is about the document itself. If you want to know what a build should cost in this market, that lives in our breakdown of Canadian website pricing. What follows is an audit you can run this afternoon on a quote sitting in your inbox.

Why quotes are vague on purpose (and sometimes not)

Vagueness is not always malice. A firm quoting a project it does not fully understand has two options: pad the number, or leave the boundary undefined and bill the difference later. The second feels cheaper at signing, which is why it wins deals.

There is also market pressure. In French Canada, soumission site web carries a cost-per-click between $6.15 and $16.21 CAD (Google Keyword Planner, Canada, August 2026). Firms are paying real money for each person requesting a quote, which is why so many "quotes" are actually meeting invitations. A number that arrives only after a 45-minute call was calculated with your budget as an input.

The counter-test is simple: a firm that can produce a written fixed-price scope from a written brief has a repeatable process. A firm that cannot does not know its own costs.

The eleven line items

Run your quote against this list. Score each one specified, vague, or absent.

1. Page count — and a definition of "page"

"Up to 8 pages" means nothing until "page" is defined. Is a blog post a page? A location page? A service page with three tabs? A page that is really a filterable listing of forty items?

The failure mode has a name and I see it constantly: the container page. The quote says eight pages; one of them is "Services," which turns out to need six sub-pages nobody counted. Your quote should list the actual page names.

2. Who writes the content, and the date it is due

The single most common cause of a stalled project is not development. It is copy. "Content to be provided by client" with no deadline is the most expensive sentence in the web industry — it stops the clock without stopping your obligations, and when you deliver copy four months late, the team that reserved capacity for you is gone.

A good quote states either we write it (with a per-page or per-word figure) or you write it, due on this date, or the timeline resets.

3. Language scope

In Québec this is the assumption that bites hardest. Bilingual is not "the same site twice" — it is double the content, double the QA, and a whole layer of hreflang, URL structure, and language routing that monolingual sites never touch. TravelDesign By Lisa, a client platform, runs 834 URLs across three languages; the translation surface was the largest single line in that scope, and it had to be named before anyone wrote code.

If your quote says "bilingual" without saying who translates and whether translation is included, that is not a scope. That is a hope.

4. Revision limits — which protect you too

"Unlimited revisions" is a red flag, not a perk. Unlimited revisions means either the price already includes a buffer for the worst client the firm has ever had, or the firm will simply stop responding once it is losing money. Neither serves you.

A limit — two rounds at design, two at build, with a stated hourly rate beyond — is a working agreement. It also forces consolidated feedback, which produces better sites than drip-fed opinions.

5. What "SEO included" actually means

This is where quotes are least honest. "SEO included" can mean anything from we set title tags to a full technical and content programme. Ask for the specific deliverables. Reasonable inclusions on a build: unique titles and meta descriptions, clean URL structure, XML sitemap, structured data, redirects from any old URLs, Core Web Vitals targets. Not included on a build, and shouldn't pretend to be: ongoing content, link acquisition, rank tracking.

If the quote guarantees rankings, the rest of the document is not worth auditing. Nobody controls Google — the diagnosis order for a site that isn't ranking will show you how many variables sit outside a builder's control.

6. Performance targets, in numbers

"Fast and responsive" is a description of intent. A target is a number: Largest Contentful Paint under 2.5 seconds on mobile, Cumulative Layout Shift under 0.1, a stated Lighthouse floor. These are measurable on delivery day, which is the entire point — see the Core Web Vitals guide for what each threshold means.

A quote with no performance number cannot be failed.

7. Integrations, named individually

Booking system, CRM, payment processor, email platform, inventory feed, accounting export. Each one is a separate piece of work, and each one has a failure mode nobody anticipates. "Integrates with your existing tools" is not a line item; it is a category.

8. Third-party costs that are not in the price

Domain, hosting, email, premium fonts, stock photography, plugin or app subscriptions, transactional email service. These are usually the client's, and usually unstated. Ask for the annual total. On a small site it is rarely large, but it is never zero, and finding out after launch feels like a bait-and-switch even when it wasn't one.

9. Handoff: code, accounts, and ownership

Ask the question directly: on the day this ends, what do I have, and in whose name is it?

You want, in writing: the repository, in an account you own; the hosting account, in your name; the domain registrar, in your name; the analytics and Search Console properties, owned by you. Transfer conditional on final payment is normal and fair. Transfer that never happens — because the platform is proprietary, or because "we host it for you" — means you are renting.

10. Post-launch support window and what comes after

How long after launch are bugs fixed for free, and what counts as a bug versus a change? Thirty days is common and reasonable. Then state what ongoing support costs. Ours is published: maintenance plans and emergency work at $150–$600 CAD one-time, depending on scope, alongside the rest of our pricing.

A quote that goes silent after launch day is describing the moment its interest in your site ends.

11. Exclusions — written down

The strongest signal of a serious quote is a section that says what is not included. It means someone thought about the boundary. A quote with no exclusions has not been scoped; it has been priced.

Where scope creep actually enters

Not through big requests. Big requests are visible and get quoted. Creep enters through four doors:

• The undefined noun. "A gallery." "A blog." "A booking form." Each of these is a family of things spanning an hour to a fortnight.
• The stakeholder who appears in week five. Feedback from someone who never saw the brief restarts decisions that were already closed. Name the approver in the quote.
• Content that arrives in a different shape than assumed. The quote assumed 300 words per service page; you deliver 1,400 and a video. That is a layout change, not a paste.
• "While you're in there." Individually tiny, collectively a week.

None of these are dishonest. They are the reason a written scope exists.

The honest trade-off nobody mentions

A fixed-price scope moves risk from you to the builder. Builders are not charitable — they price that risk in. On a well-specified project, you will likely pay a modest premium over time-and-materials for the certainty.

That premium is worth it in exactly one situation, which happens to be most situations: when you cannot absorb an overrun. If you genuinely have a stable specification, in-house technical oversight, and tolerance for variance, hourly billing is cheaper. If you are a small business with a fixed budget and a launch date, buy the certainty. Just know you are buying something, and that the thing you are buying is the document.

That is also the honest limitation of everything above: a perfect quote does not make a project succeed. It makes failure visible early, which is the most a document can do.

---

If you want to see what a specified scope looks like, write down what the project has to do and who it is for and send it. You get a written fixed-price scope back — line items, exclusions, and handoff terms included — with no mandatory sales call: stillawake.studio/start. Use it to audit somebody else's quote if that is more useful to you.