A website development agreement is the contract between a client and a web developer or agency for the design, development, and delivery of a website. It is one of the most commonly signed technology contracts in India, and one of the most commonly disputed - because scope, payment milestones, revision rights, and IP ownership are frequently left vague in the initial brief and become contentious when the project runs into difficulties. This guide covers what a website development agreement must contain to protect both the client and the developer, with specific attention to the clauses that generate the most disputes.
Why Website Development Disputes Are So Common
Website projects combine creative work (design), technical work (development), and ongoing dependency (hosting, maintenance) - each with different metrics for "done," different skill sets, and different stakeholder expectations. Common sources of dispute: Scope creep: the client adds features mid-project that were not in the original brief; the developer implements them but claims additional payment; the client disputes that additional payment was agreed. Subjective quality standards: "the design doesn't look professional" is not a contractual standard. Without defined acceptance criteria, delivery disputes are almost impossible to resolve. IP ownership gap: the developer retains copyright in the code by default; the client discovers this only when they try to change developers. Payment disputes: the client withholds the final milestone payment claiming the site is not complete; the developer claims all deliverables were met. A well-drafted agreement addresses each of these before the project starts.
The Scope Section Is The Most Important Part Of The Agreement. It Must Describe:
The number and type of pages: list every page and template (homepage, about, services/product listing, individual product page, contact, blog, checkout, order confirmation, 404, etc.) Design specifications: custom design from scratch, or adaptation of a purchased template? Mobile responsive? Browser compatibility (which browsers and versions)? Functional requirements: shopping cart, payment gateway integration (which gateway?), user login/registration, search functionality, contact forms, newsletter signup, third-party integrations (CRM, booking system, inventory) Content: who provides the text copy, images, and videos? Does the developer populate the content management system (CMS) or does the client? Number of products to be listed (for e-commerce) CMS: which platform (WordPress, Shopify, custom)? Who hosts and manages the CMS? SEO: basic on-page SEO (meta titles, descriptions, alt text) included, or is it out of scope? Languages: English only, or multilingual? Excluded items: explicitly state what is NOT included - logo design, copywriting, photography, ongoing SEO, social media integration beyond basic sharing buttons Attach the full scope as a Schedule to the agreement rather than describing it briefly in the body. The Schedule is the deliverable; the body is the legal framework.
The Most Contentious Phase Of Most Web Projects Is The Design Phase. Define:
Wireframes first: low-fidelity wireframes for layout approval before full design work begins. This prevents expensive redesigns. Design comps: the number of design concepts the developer will present (typically 1-2 per template type). The client has [X] rounds of revision per design comp. Design approval: the client has [X] business days to approve or request revisions after each design comp is presented. Deemed approval: if the client does not respond within [X] days, the design is deemed approved and development proceeds. Out-of-scope redesigns: if the client requests a fundamentally different design direction after final approval, this is a scope change and is billed separately at [rate].
Payment Milestones
Milestone-based payments align financial incentives with project progress. A typical structure for a medium-sized website: 25% on contract signature (advance to commence project) 25% on approval of design mockups 25% on completion of development (pre-launch, client testing) 25% on website go-live Each milestone payment must be tied to a specific, objectively verifiable deliverable. "Completion of development" should be defined as delivery of a functional staging site that matches the approved design and passes the agreed functional testing checklist.
Define The Acceptance Process:
Functional testing checklist: a list of specific features that must work correctly (all forms submit successfully, payment gateway processes test transactions, all links work, mobile responsiveness confirmed on specified devices) User acceptance testing (UAT) period: the client has [X] business days after delivery of the staging site to conduct testing and report bugs Bug fix protocol: the developer must fix bugs within [X] business days of the client's written bug report. A "bug" is defined as a failure of functionality that was specified in the Scope of Work - not a change in requirements. Acceptance deemed: if the client does not raise issues within the UAT period, the deliverable is deemed accepted and the milestone payment falls due.
Intellectual Property
Without an IP assignment clause, the developer owns the copyright in the website's code and design. This means: The client cannot legally give the code to a different developer without the original developer's consent The client cannot modify the code without the developer's consent The client has only an implied licence to use the code on their own website
The Ip Clause Must Clearly Address:
Assignment of all foreground IP (code, design, content templates created for this project) to the client, effective on payment of all fees Carve-out for pre-existing IP (the developer's proprietary frameworks, libraries, plugins, themes) - these remain with the developer. The developer grants the client a perpetual licence to use these components as embedded in the delivered website. Third-party components: the developer must disclose all third-party libraries, plugins, and themes used, and confirm that their licences permit use in the client's website. Open source components: the developer must disclose any open source components and confirm that their licences do not impose obligations on the client (e.g., GPL copyleft).
Hosting And Maintenance
Post-launch, the website needs hosting, security updates, and occasional maintenance. These are often separate from the development agreement. If the developer also provides hosting and maintenance: Hosting: specify the server specifications, uptime guarantee, backup frequency, and pricing. Maintenance: define what is included (security updates, CMS updates, bug fixes for the code delivered under this agreement) vs what is out-of-scope (new features, design changes, content updates). Support: response time for support requests, support hours, and whether emergency support is available.
When to obtain a review
A review is especially useful when…
- — You are about to sign, send, rely on or respond to this document.
- — The draft was copied from an old template or another state.
- — There is money, property, business control, statutory deadline or reputation risk involved.
- — You need Surat/Gujarat-specific drafting, review or negotiation support.
Legal information notice
This article is general legal information for India and Gujarat. It is not a substitute for advice on your specific facts, documents, limitation period, stamp duty position or court strategy.