Affordable web design is easier to judge when competing proposals describe the same work. A low build price can leave content, integrations, renewals, or handoff outside the total. This checklist helps a Toronto small business compare the launch scope and the first year of operation without assuming that every website needs the same package.
Reviewed September 13, 2026. The examples below are unpriced planning scenarios, not Supreme Line quotations, market-rate estimates, or client results. Obtain current written prices from each supplier and third-party provider. No universal website price is claimed here.
Fix the Launch Scope Before Comparing Prices
Our fictional business needs a service website with a home page, three service pages, an about page, and a contact page. The customer task is to request an estimate. The owner supplies approved copy and photographs; the supplier implements the pages and an inquiry form that reaches the office. Online payments, customer accounts, and a live booking calendar are outside this example’s launch scope.
That is a starting brief, not a recommendation that every business needs six pages. Specify reusable page layouts as well as page count: six pages sharing two layouts are different from six independently designed experiences. List existing content that needs migration, including any URLs that must continue working.
Build a Cost Ledger With Renewal Dates
For each line, record the supplier, quoted amount, currency, tax treatment, payment date, renewal date, and whether another line already includes it. Mark an unresolved amount as not quoted, not zero. Some businesses already pay for hosting or email, so compare the change in their actual costs as well as the proposed package total.
| Cost line | What to request in writing |
|---|---|
| Discovery and design | Deliverables, layouts, review rounds, and the charge for an approved scope change. |
| Build and launch | Page setup, form behavior, testing, migration, deployment, and any separate setup fee. |
| Content and media | Who writes, edits, translates, sources images, and obtains usage permission. |
| Domain, hosting, and email | Account owner, billing cycle, renewal price, storage or usage limits, and what is bundled. |
| Plugins and connected tools | License holder, subscription term, usage charges, and consequences of nonrenewal. |
| Maintenance | Included tasks, request limits, response coverage, exclusions, and excess-work pricing. |
| Handoff or exit | Training, files and data supplied, transfer assistance, and any separately quoted work. |
Keep initial discounts and renewal prices in separate fields. A first-year promotional rate is not evidence of the second-year charge. Also ask whether a subscription is paid directly by the business or included in the agency’s ongoing service; that affects both comparison and handoff.
Compare the Same Twelve-Month Window
Choose explicit start and end dates. For a simple first-year cash plan, add the one-time payments due in that window, recurring invoices due in it, estimated usage charges with their assumptions, and applicable taxes not already included. Deduct only confirmed credits or discounts, and remove double-counted bundled items.
Unpriced worked schedule: Suppose hosting starts at launch and is billed monthly, the domain is prepaid for a year, and a paid tool starts in month four. A twelve-month launch window contains twelve hosting payments, one domain payment, and nine monthly tool payments, assuming those billing dates and no other charges. Insert each supplier’s actual amounts. Record any build deposit paid before the window separately so it does not disappear from the overall project cost.
This is a comparison aid, not a supplier estimate or an accounting treatment. Renewal timing, annual prepayment, existing subscriptions, and usage can change the result. If the vendor has not answered a cost question, show a range only when its bounds come from documented terms; otherwise keep the uncertainty visible.
Spot Scope Differences in Two Proposals
| Item | Example A | Example B |
|---|---|---|
| Copy | Client supplies final text. | Supplier edits the supplied draft within an agreed review limit. |
| Inquiry | Form sends an email only. | Form creates a staff-system record and sends a notification. |
| Migration | New pages only; existing URL mapping excluded. | Agreed old URLs mapped and checked after launch. |
| Licenses | Business buys required subscriptions directly. | Selected licenses included while the support agreement is active. |
| Support | Post-launch content changes quoted separately. | A defined amount of editing included; additional work is separate. |
Ask each supplier to price the same selected version of the scope. If your team already has approved copy, editing may add little value. If staff require an inquiry record in their existing system, an email-only form may not meet the requirement. Decide what the business needs before treating an excluded task as a saving.
Reduce Optional Scope, Not Essential Verification
Possible deferrals include a second language the team cannot yet maintain, an unused customer portal, or a custom animation that does not support the customer task. Keep the launch list short, but retain checks for the actions that remain. An estimate form still needs useful error messages and a verified staff destination even when the rest of the website is small.
Use the developer brief and acceptance checklist to define those checks. Phase-two work should have a trigger, such as a documented staff bottleneck, rather than an automatic promise to add every deferred feature later.
Check What You Can Take With You
Ask for a written handoff inventory covering account access, content, media, custom work, licenses, and transfer assistance. Clarify which components depend on the current supplier’s subscriptions and what replacement or migration would involve. Do not assume that receiving one download means the full website can be restored elsewhere.
For example, WordPress documents its Tools Export function as an XML content export. Its separate backup guidance explains that a full WordPress restore needs both files and the database. That distinction is a reason to ask what a supplier’s promised export actually contains, not a claim that every platform has the same portability options.
Leave the Comparison With a Decision and an Owner
Before approving the work, resolve the launch scope, unquoted items, recurring charges, content responsibilities, testing, and handoff. Record who can approve additional work and how the revised cost and timeline will be confirmed. Keep the accepted version of the proposal with the cost ledger so later changes have a clear reference point.
Supreme Line can scope website design and development from that brief. Bring your existing subscriptions, content status, and essential customer task so the proposal can distinguish necessary launch work from optional additions.
