Web Design Pricing: Compare Scope, Total Cost, Rights, and Risk
A practical method for comparing briefs, teams, deliverables, accessibility, security, ownership, recurring costs, acceptance tests, launch support, and measurement without invented market price bands.
You cannot compare website quotes until each bidder prices the same work. Page count alone does not show research, writing, access needs, or links to other tools. It also hides data moves, safety, site data, tests, and launch work.
A high price does not prove good work, and a low price does not prove poor work. Broad market price bands age fast, and they often compare unlike scopes. This guide shows how to build one clear brief and a total-cost view. TTGC gives a quote only after the real scope of work is known.
Start With a Comparable Website Brief
State the business task, the users, the markets, the languages, the launch limit, and the current site. Name the content owner and the choice owner, then list the success checks.
List each page type, shared part, form, linked tool, user role, work step, and data source. Then list each redirect, consent path, and reporting need.
Keep required work apart from optional ideas. Record guesses and unknowns. That way no bidder can hide them in a vague allowance.
Count the Work Hidden by Page Totals
Research: old records, staff interviews, and user research. Also site data, a content list, a site check, and decision sessions.
Content: message plan, copy, and edits. Then legal or health review, other languages, photos, clips, and art. Also data, rights, and move work.
Design: page map, rough layouts, and visual routes. Then shared parts, screen sizes, actions, and access needs. Also test models and review rounds.
Build: CMS fields, sign-in, search, payments, linked tools, and data import. Then test sites, logs, backups, a safety review, and performance work.
Launch: redirects, page data, site data, and consent. Then tests, training, guides, release, and rollback. Also warranty, upkeep, and event help.
Give each item a count and a pass test. Five page layouts are not fifty written pages, and a design idea is not a live site. “SEO included” does not name redirects, page markup, page data, crawl rules, site data, or copy work. “Accessible” does not name the rule, the goal, or the test method. It also does not name support tools or the duty to fix errors.
Compare the Team, Work Plan, and Proof
Name who leads the plan, the copy, the design, the build, access, safety, testing, launch, and support. Confirm which work goes to another firm.
Ask for useful examples and references. Check the role, scope, date, rights, and starting point. Then check what the result means, the outside causes, and the fit with this brief.
Set review rounds, reply times, choice rights, change rules, linked tasks, and client duties. State what happens when a project guess turns out to be wrong.
Require a live check against the pass rules before final sign-off. A clean mockup does not prove that forms, data, or access work. It does not prove that safety or redirects work.
Build the Full Cost Record
Include the quote, staff time, copy and media, and licenses. Add fonts, stock, domains, host, platform fees, and payment fees. Add linked tools, data work, rule review, tests, training, and moves. Then add upkeep, logs, safety updates, help, and likely changes. Mark each cost as fixed, an estimate, based on use, repeat, optional, or left out.
A platform changes who owns each duty, not just the price. Check ownership, export, move rights, access, and roles. Check backups, logs, vendor terms, and where the data sits. Check safety notices, access limits, use limits, and help. Then check end terms and exit cost. Do not say one platform is always faster, safer, cheaper, or easier to run.
Set Rights, Access, and Handoff First
State who owns or may use the plan, the copy, the code, the designs, and the source files. Do the same for fonts, photos, clips, data, add-ons, models, prompts, and outside assets.
Keep domains, site data, ads, CMS, and host accounts under approved company access. Do the same for code, email, payment, and vendor accounts. Give the least rights and set up safe recovery.
List handoff files, guides, training, and logins. Add linked tools, renewal dates, known limits, and open risks. Then add warranty, upkeep, and exit support.
Use One Scorecard and a Clear Test Plan
Score each bidder against the same brief. Show sales interests and referral ties. Record why each key gap matters. Before launch, save the old baseline and note data quality. After launch, track agreed user tasks, errors, access issues, and valid contacts. Also track consent, safety events, speed, copy upkeep, and total cost. Do not give the site credit for sales or conversion change without a sound test and clear limits.
What TTGC Can Quote
TTGC can price an agreed site scope once the duties are known. That covers research, copy, design, build, access, tests, launch, and help. TTGC does not promise a price tier, launch date, platform result, speed score, rank, conversion rate, payback, sales, or growth.
Ready to compare a real website scope?
TTGC can turn requirements, responsibilities, acceptance tests, rights, total cost, launch, and support into a reviewable project brief and quote. Outcomes are not guaranteed.
Sources
- Federal Trade Commission — Advertising and Marketing: claims must be truthful, not deceptive or unfair, and evidence-based. https://www.ftc.gov/business-guidance/advertising-marketing
- U.S. Department of Justice — Guidance on Web Accessibility and the ADA: practical accessibility barriers and testing considerations. https://www.ada.gov/resources/web-guidance/
- W3C — Web Content Accessibility Guidelines 2.2: the current W3C Recommendation for testable accessibility criteria. https://www.w3.org/TR/WCAG22/
- CISA — Secure by Design: security should be treated as a core product requirement rather than shifted to customers. https://www.cisa.gov/securebydesign
