Website Design Contract Checklist for Business Owners

A website design contract should explain what will be delivered, who supplies and approves content, how much the work can cost, how changes are authorized, what acceptance means, who owns the domain and completed work, which third parties remain involved, and what happens after launch or termination.

This guide is practical business information, not legal advice. Contract requirements vary. Use qualified counsel for an important agreement, especially when the site handles sensitive information, regulated claims, substantial commerce, accessibility obligations, or material business risk.

1. Identify the parties and decision authority

Confirm the legal names and signing entities. Name the client owner, final approver, provider contact, content reviewers, and people authorized to approve scope, estimates, changes, expenses, launch, and acceptance.

Several stakeholders can contribute, but the contract should define one path for consolidated instructions.

2. State the business outcome

Include the audience and primary action the site should support, such as requesting an estimate, booking, purchasing, visiting, applying, or understanding a service before contact.

The outcome guides decisions but does not replace the deliverable list. "Increase leads" still needs pages, content, functions, measurement, and acceptance.

3. Attach a page and template inventory

List every launch page and reusable type. Distinguish original pages, template-driven entries, migrated pages, merged pages, redirects, archived content, and client-supplied policy pages.

Identify navigation, footer, shared components, error pages, confirmation pages, and other interface states that may not appear in a marketing page count.

4. Define content responsibilities

State who researches, interviews, writes, edits, supplies, licenses, and approves business facts, headlines, service descriptions, biographies, photos, video, illustrations, reviews, testimonials, credentials, claims, privacy language, and other content.

Define revision rounds and review timing. Correcting a provider draft within the agreed direction is different from changing the business offer after content approval.

5. Describe design work and approval

Clarify whether the project uses an existing template, custom visual direction with reusable components, or a bespoke page system. Identify reference screens, mobile behavior, client brand constraints, licensed assets, review stages, and design approval.

A vague promise of "custom design" should not be the only definition.

6. Define functions and integrations

Specify forms, uploads, booking, payments, ecommerce, donations, calculators, directories, maps, search, filters, accounts, portals, languages, CRM, analytics, email marketing, call tracking, inventory, or accounting behavior.

For each external product, identify provider, plan, account owner, data moved, failure handling, recurring fee, and what remains manual.

7. Cover migration and redirects

List pages, posts, products, media, documents, metadata, users, orders, and other records to move. Define client cleanup, provider mapping, trial migration where needed, URL redirects, broken-link checks, and post-launch reconciliation.

A promise to "move the existing site" should state what is included and what source access must be available.

8. Define search, analytics, and measurement

State the included technical foundations: titles, descriptions, headings, crawlable links, sitemap, canonical URLs, structured data where appropriate, redirects, analytics events, Search Console, and launch checks.

No provider can responsibly guarantee ranking or leads. The agreement can require sound implementation and measurement.

9. Address accessibility, privacy, security, and performance

Identify approved requirements, test methods, browsers, devices, keyboard behavior, forms, data collection, consent, retention, authentication, backups, and performance expectations.

Qualified professionals should determine legal and regulated requirements. The contract should separate developer implementation from client policy and professional review.

10. Make price and payment understandable

State the pricing model, hourly rates, estimated hours, fixed or capped amount, deposit, milestone schedule, due dates, expenses, taxes, and third-party fees.

Vertinus charges $49.99 per hour. The client pays for time actually worked up to the approved estimate. Vertinus absorbs overage for the agreed scope; new scope is estimated and approved separately.

11. Define the change process

Explain how a new page, revised direction, added integration, missing content, new stakeholder requirement, or other change is requested, estimated, approved, scheduled, and recorded.

Do not allow material work to proceed from a casual call without written effect on price and schedule.

12. Set schedule and client responsibilities

Identify discovery, content, design, development, integration, migration, review, testing, launch, and target dates. List the access, materials, approvals, professional review, and decision timing the client must provide.

State how late content, access, or feedback changes the schedule.

13. Define review, acceptance, and defects

Use a written acceptance period and observable criteria. Separate a defect—failure to meet agreed behavior—from a new preference or requirement.

Allow reasonable correction and retesting. Define what happens if the client does not respond and which items may be deferred without blocking launch.

14. Confirm domain, code, and account ownership

Identify ownership and control of the domain, repository, source code, designs, hosting, analytics, forms, payment account, email platform, business listings, fonts, images, plugins, and other services.

At Vertinus, the client owns the completed code, interface, project-specific deliverables, and domain after final payment. Third-party assets and services retain their licenses.

15. List recurring providers and costs

Separate hosting, domain, email, forms, plugins, fonts, stock media, booking, ecommerce, payments, CRM, analytics, call tracking, monitoring, support, and marketing. Confirm account ownership and cancellation or export behavior.

Optional Vertinus Managed Website Care is $50 per month and covers hosting, one standard-priced domain, DNS, SSL, monitoring, backups, routine technical maintenance, and deployments. New content and features remain hourly.

16. Define launch and post-launch responsibility

Include domain changes, certificates, redirects, analytics, forms, sitemap, backups, monitoring, rollback, launch checks, documentation, and administrator training.

State whether a defect-correction period, managed care, or no ongoing service follows launch and who handles future updates and provider changes.

17. Plan termination and handoff

Explain notice, payment for completed work, treatment of deposits, access to unfinished work, source and content delivery, account transfer, data return, deletion, and transition help.

Termination is practical only when the business can retrieve current code, content, domain control, data, credentials, and documentation in usable form.

Website contract red flags

Be cautious when there is no attached page scope, content is "included" without definition, all critical accounts remain under the provider, ownership is unclear, recurring services are hidden, or billing can expand without written approval.

Other warning signs include no redirect or migration plan, no acceptance method, guaranteed rankings, no termination handoff, automatic long renewals, and a launch promise dependent on unnamed client or third-party work.

Prepare inputs with the website estimate packet, compare responses using the proposal scorecard, and review payment structure through the website payment schedule guide.