← All insights

FORMVANT / INSIGHTS

How to Read a Fixed-Scope Website Quote Line by Line

Two quotes for the same five-page site can differ by thousands. Learn what a fixed-scope website quote should itemise and what is fair to bill separately.

Professional header image for step-by-step guide: How to Read a Fixed-Scope Website Quote Line by Line
AI-generated header image for: How to Read a Fixed-Scope Website Quote Line by Line

You have briefed three studios for the same five-page website. One quote comes back at $6,000, another at $9,500, and a third at $14,000. Before you assume the cheapest option is a bargain or the highest is padding its invoice, consider this: two quotes for identical page counts can differ by thousands without either studio being dishonest. The gap usually comes down to what each quote actually includes, and what it quietly leaves out.

This post gives you a line-by-line method for reading a fixed-scope website quote so you can compare proposals on equal terms. You will work through pages and templates, who writes and approves copy, integrations, domain and branded email ownership, analytics and tracking setup, revision limits, and launch support. You will also learn which items legitimately sit outside a fixed price, and why regulators take an interest in prices that only look complete until later.

By the end, you will know how to mark each line of a quote as included, excluded, or billed hourly, and you will have a comparability test to run before you sign anything.

Why Two Quotes for the Same Five-Page Site Can Differ by Thousands

Pages and Templates: What "Five Pages" Actually Includes

The first place scope hides is the page count. Request a page-by-page list with each page labelled unique design, adapted from another page, or standard utility page. Ask whether system pages count toward the five: 404, thank-you, privacy policy, terms, blog index and password reset pages. Then confirm the design sequence: is the home page approved as the master template before inner pages are built, and does that approval gate later revisions? Ask whether tablet and mobile responsive passes are included per template or priced once for the whole site. Finally, verify whether a content management system or editing tool is part of the build, and whether any paid plugin or builder licence is billed on top. For a practical benchmark, see how Formvant structures website builds.

Who Writes the Words and Who Approves Them

With pages and templates settled, the next line decides your timeline: copy. Establish whether the studio, you, or a third party writes it. Copy responsibility carries real cost, because late words push every date after them. If you supply copy, ask what happens when it arrives late or incomplete, and whether editing, formatting, or replacing placeholders with final text is billed hourly. Ask whether the studio writes page titles, meta descriptions, and heading structure for search, or only lays out supplied text. Name one approver, require consolidated feedback, and set a defined number of approval cycles per page. Finally, specify image sourcing: licensed stock, your files, or custom photography, plus who pays licence fees and holds receipts. Use a brief-to-launch process to pin these responsibilities down before signing.

Integrations: Naming Them and Testing Them

Copy and approvals settled, integrations are the next line to pin down. Require each one named individually on the quote, not swallowed by "third-party integrations included." Read our website services as an example of how that itemisation looks in practice.

Then separate an embed from a working integration. Pasting a booking widget is small work. Connecting bookings to a calendar, CRM, payment gateway and confirmation emails is not, and should be priced as the larger job it is.

Confirm whose accounts are used, who holds credentials and API keys, and whether you keep administrator access at handover. Ask which subscription fees the studio pays and which you pay directly, since platform fees often sit outside a fixed build price.

Finally, ask what happens when an integration breaks after launch: a free fix window, an hourly charge, or coverage under a monthly care plan.

Domain, DNS and Branded Email: Ownership and Access

Integrations settle who holds platform keys; apply the same discipline to your domain and email. Check the registrar record: a quote listing "domain setup" does not prove your business is the registrant. Confirm who holds registrar access and whether the account is in your name.

Treat DNS changes as separate work. Ask whether the studio makes them, which credentials they need, and how they manage propagation and brief email interruptions.

Ask if branded email is included at all, and if so, what is configured: mailbox provisioning, MX records, and SPF, DKIM and DMARC alignment. Ask whether migrating existing mailboxes and historical messages is included or quoted separately; migration is often its own job. Where possible, buy and control accounts in your own name so you keep control of access if the working relationship ends. See domain and email setup guidance for what that handover should include.

Analytics and Tracking Setup

Analytics and Tracking Setup
Analytics and Tracking Setup

Once DNS and email access are settled, turn to tracking. Analytics installation and conversion tracking can be treated as separate items; ask which the quote covers and which it omits.

  1. Are Google Analytics 4, Search Console verification and sitemap submission explicitly listed? See what GA4 setup covers for the distinction.

  2. If advertising or remarketing is involved, who configures the consent banner and maintains its categories?

  3. Which events are built and tested before launch: form submissions, bookings, purchases, phone clicks? Where are those definitions documented?

  4. Who owns the analytics property? Do you receive administrator access?

  5. Is post-launch reporting included, billed hourly, or part of a monthly plan?

Revision Rounds: How Many, What Counts and What Triggers More Work

After tracking is settled, pin down revisions in five steps.

  1. Get the number of rounds in writing, and define a round as one consolidated set of feedback, not unlimited separate comments.

  2. Ask the studio where a revision ends and a new request begins: text edits, image swaps, layout changes, new sections, new pages.

  3. Ask what happens to a round when feedback arrives late, and whether unused rounds expire at launch.

  4. Clarify whether post-launch tweaks draw from the same revision budget or switch to hourly billing.

Fewer surprises later, and a cleaner comparison when you review whether to repair or rebuild.

Launch Support and What Happens After Go-Live

Your revision terms settled, the quote must also show launch and aftercare. Request the launch checklist: redirects from old URLs, form and payment testing, SSL, cross-browser and mobile checks, backups, and a named sign-off for each. Confirm the post-launch window: how long fixes are free, what separates a fix from a change, and how requests are submitted. Ask who performs the DNS cutover, when, and how email continuity is protected during the switch. Check whether training or documentation is included, so simple content edits do not become paid work. If a care plan is offered, ask what it covers monthly and what still falls outside it; for studio process questions, see Formvant's process questions. As one example, Formvant's fixed-scope packages start at $995 CAD, with optional monthly care plans that include SEO and analytics reporting.

What Is Fair to Bill Separately

Once the site is live, separate the fixed build from the extras. These are fair to bill separately, provided the agreement names them:

  • New scope after sign-off: extra pages, new templates, added integrations or features. These need a written change order before work starts.

  • Third-party costs: domain renewal, hosting, premium plugins, stock licences, payment processing and email platform subscriptions stay on your side of the ledger.

  • Rework from late approvals, changed direction after sign-off or content delivered mid-build, if the contract says so plainly.

  • Hourly work beyond included revisions, urgent turnaround, and support after the free fix window closes.

  • Recurring work: security updates, backups, content edits, search visibility, analytics reporting and care plans. These are monthly items, not build costs.

The Question That Makes Quotes Comparable: Which Lines Are Billed Hourly?

Separately billable items only become a problem when nobody priced them in advance. That is why the first conversation should include one direct question: which items on this quote are billed by the hour, and at what rate?

Then get specifics in writing: the rate, the billing increment (15 minutes or a full hour), any minimum billing block, and whether a written estimate precedes hourly work.

Next, ask what triggers the switch from fixed price to hourly. Late copy, changed direction, extra integrations? Have that trigger documented rather than discovering it mid-project.

Ask for the change-order process: written request, estimate, approval, work, invoice. No written approval, no work, no invoice.

Finally, ask the studio to mark hourly items directly on the quote, and confirm whether the rate holds for the project's duration.

Price Transparency Context: What the Competition Bureau Guidance Says

Canadian price-transparency material is written mainly for consumer advertising, so treat it as context for a business-to-business website quote, not as a checklist.

The practical habit that carries over is simple: ask for the complete price up front, including items added later. Proposals to tighten drip-pricing rules were floated in 2024, but their status is unconfirmed; check the Bureau's published guidance rather than commentary.

The Comparability Test: Mark Both Quotes Before You Choose

The Bureau framing points one way: compare complete prices, not headlines. Turn that habit into a method. Build a three-column table: line item, included or excluded, and the hourly rate where one applies. Work both quotes against the same rows, marking every line you can and leaving the rest blank on purpose. Blanks are questions to send each studio, not evidence of bad intent. Recalculate a like-for-like total: fixed price, plus hourly work you realistically expect, plus known third-party costs. Ask each studio to confirm your marked version in writing. Attach it to the agreement so later scope changes are measurable rather than arguable.

Put the Checklist to Work Before You Sign

Before you sign, turn your completed table into a signed scope document. Get the page and template list in writing, with every line marked included, excluded or billed hourly. Ask each studio which lines are hourly, the rate, the billing increment and the trigger that switches fixed work to hourly. Compare like-for-like totals, not headline prices: add expected extras and third-party fees such as domain, hosting and platform subscriptions. Finally, attach your marked quote as an annex to the agreement, so the scope you compared is the scope you can enforce.

Conclusion

Comparing website quotes isn't about finding the lowest headline price; it's about understanding exactly what you're buying. This post has shown you how to break down a fixed-scope quote line by line.

The key takeaways are clear. First, scrutinize the details: what "five pages" includes, who is responsible for content, and which integrations are covered.

Your next step is to build that three-column table for each quote you receive. Mark every line included, excluded, or billed hourly, then send it to the studios with your questions. This simple act transforms a confusing comparison into a structured negotiation. You'll move forward with clarity, confidence, and a signed document that protects your investment.