Before accepting a website quote with unclear exclusions, turn every assumption into a written responsibility, deliverable, price or decision rule. Confirm content, pages, templates, migration, SEO, accessibility, integrations, hosting, licences, testing, ownership, support and change control. Compare suppliers using the same requirements schedule, not their headline totals.
This is a website design and digital strategy procurement decision. A cheap quote can become expensive when essential work appears later as a surprise variation.
South Africa's Consumer Protection Act contains provisions addressing fair and understandable terms, notice of certain terms, and fair value and quality in applicable consumer transactions Source: South African Government. Applicability depends on the parties and transaction, so obtain legal advice for a specific agreement.
Start with one requirements schedule
Write what the website must enable for users and the business. List audiences, important tasks, public routes, languages, content types, integrations, accessibility expectations, compliance needs, performance targets and launch constraints.
Send the same schedule to every supplier. Ask each to mark included, excluded, optional, assumed and client-supplied. This exposes differences that a total price hides.
Separate pages from reusable templates
Confirm the number and type of unique templates, not only a page count. A service page repeated twenty times is different from twenty individually designed layouts. Specify responsive states, reusable blocks and content-management controls.
Ask whether search, filtering, authentication, ecommerce, bookings, multilingual content or location pages require separate templates or functional work.
Define who loads the content and how many rounds are included. Clarify whether additional pages use an agreed rate, a change request or internal templates.
Clarify content responsibility
State who performs discovery, messaging, copywriting, editing, proofreading, image sourcing, photography, video, illustration and legal review. Identify the number of interviews and revision rounds.
If the client supplies content, define format, deadline and quality requirements. State what happens when content is late or incomplete. Placeholder text can conceal a major launch dependency.
Confirm whether metadata, alternative text, redirects and structured data are included. Do not assume SEO content comes with visual design.
Define migration and SEO preservation
Inventory existing URLs, traffic, backlinks, metadata, structured data, media and downloadable files. Ask whether the quote includes crawling, redirect mapping, implementation, validation and post-launch monitoring.
Confirm who owns analytics, Search Console, consent tools and tag migration. Include a rollback and defect process for material launch problems.
If a supplier excludes SEO, determine whether that means keyword research only or also excludes redirects, crawlability, metadata, sitemaps and performance. Those technical basics affect whether a replacement site can preserve visibility.
Make functional integrations explicit
For every CRM, payment gateway, booking system, email platform, ERP, identity provider, chat tool or third-party feed, specify the exact workflow, direction of data, fields, authentication, failure behaviour and responsible vendor.
Ask whether the quote covers configuration, custom development, testing, vendor liaison and production credentials. Record licence and transaction fees separately.
Avoid the phrase integrates with unless acceptance criteria define what successful integration means. A form email is not the same as a deduplicated CRM record with consent and source data.
Check accessibility and browser coverage
Name the accessibility standard or practical acceptance level expected, the journeys to test and the methods used. Confirm keyboard, focus, form error, contrast, zoom, screen-reader and caption responsibilities.
Define supported browsers, devices and responsive breakpoints based on audience evidence. Ask whether real-device testing is included and how defects are prioritised.
An automated scan alone does not establish that the experience is accessible. Include human review for important journeys.
Confirm hosting, environments and operations
Document development, staging and production environments, domain and DNS responsibility, certificates, backups, restore testing, monitoring, logging, uptime expectations, patching and incident response.
Ask where data is hosted, which subprocessors are involved and who controls the accounts. Confirm usage limits and costs for traffic, storage, email, media and third-party APIs.
Separate once-off implementation from monthly hosting, maintenance and support. Calculate costs over at least the expected contract period.
Protect ownership and portability
Clarify ownership or licence rights for source code, designs, custom assets, copy, data, analytics properties, domains and third-party themes or plugins. Record when rights transfer and whether final payment is a condition.
Require administrative access to business-owned accounts. Define handover materials, repositories, credentials, deployment instructions, design files, content export and dependency list.
Ask how the site can move to another supplier and what exit assistance costs. Portability reduces operational risk even when the relationship is healthy.
Examine privacy and security scope
List personal information processed through forms, accounts, analytics, calls and integrations. Confirm who prepares privacy notices, consent behaviour, retention rules, access controls and deletion workflows.
Require secure development, dependency management, least-privilege access, secret handling, backup protection and incident notification appropriate to the risk.
The Protection of Personal Information Act establishes conditions for lawful processing and responsibilities relevant to personal information Source: South African Department of Justice. A website quote should not imply legal compliance without defining operational responsibilities.
Define revisions and change control
State the number and scope of design, content and development revision rounds. Define one consolidated feedback owner and response periods.
A change request should describe the requested change, effect on scope, cost, timing, dependencies and approval. Emergency verbal instructions should be documented promptly.
Distinguish correction of work that fails agreed requirements from a new requirement. Otherwise ordinary defects can be charged as changes or genuine additions can be treated as unlimited revisions.
Write measurable acceptance criteria
Define what must be true for milestone approval and final acceptance. Include working journeys, approved responsive layouts, content completeness, redirects, analytics, accessibility checks, performance thresholds, integration outcomes and handover.
Set a review window and defect classification. Explain whether minor defects can remain after launch and by when they must be resolved.
Avoid acceptance based only on the site being live. Launch can occur while critical business requirements remain incomplete.
Understand payment and cancellation
Link milestone payments to specific deliverables and acceptance evidence. Confirm deposits, tax, expenses, third-party purchases, late payment, paused work and restart fees.
Read cancellation, suspension and termination terms. Ask what work and materials the client receives if the project stops at each stage. Record refund treatment and outstanding licence commitments.
Do not pay for a large undefined final phase simply because earlier milestones used calendar dates rather than outputs.
Check warranty, maintenance and support
Separate defect warranty from ongoing maintenance and new development. Define support hours, response targets, channels, included time, priority levels and escalation.
Ask who patches the framework, CMS, plugins and dependencies. Confirm backup and restore responsibility. Determine how browser or third-party platform changes are handled.
A site without an operating owner begins accumulating risk at launch.
Build a comparable total-cost view
Calculate discovery, design, content, development, migration, integrations, licences, hosting, support, internal staff time and likely options. Model at least one change scenario and one year of operation.
Compare delivery confidence, relevant experience, team capacity, references, communication and commercial risk alongside cost. A detailed higher quote may include work omitted from a lower one.
My take is that unclear exclusions are rarely a small contract detail. They usually indicate that the buyer and supplier have not yet agreed what the project is.
Hold a clarification meeting before signing
Walk through every excluded, assumed and client-supplied item. Ask what commonly surprises clients on similar projects. Record answers in an amended proposal or schedule incorporated into the agreement.
Do not rely on meeting notes that the contract says have no effect. Ensure the final signed documents contain the agreed scope and order of precedence.
For material legal, tax or data-protection questions, obtain qualified professional advice.
Frequently asked questions
Is a fixed-price website quote always safer?
No. It is safer only when scope, assumptions, acceptance and change rules are clear. Ambiguity can still produce disputes.
Should the client own the source code?
The answer depends on the delivery model and reused components. Clarify ownership, licences, access, portability and handover explicitly.
How many design revisions are reasonable?
There is no universal number. Define review stages, consolidated feedback and what constitutes a correction versus a new direction.
What is the biggest hidden website cost?
Common costs include content, migration, integrations, licences, maintenance, internal review time and changes caused by unresolved requirements.
Turn a quote into a controlled delivery agreement
If your business needs a website scope it can evaluate confidently, get in touch for website design and digital strategy.
Related guides
For further background, read our website design packages vs custom builds and website maintenance costs. The user journey glossary explains the terminology used in those guides.