Back to all articles

Website Development Agreement Checklist for Indian Businesses: Scope, Payments, Ownership & Handover (2026 Guide)

Website Development Agreement Checklist for Indian Businesses: Scope, Payments, Ownership & Handover (2026 Guide)

Hiring a web development company or freelancer is an important business decision. Before development begins, both sides should understand exactly what is being built, how much it will cost, when payments are due, who owns the finished website, and what happens after launch.

Many website projects run into disagreements because these details are discussed verbally but never properly documented.

A client may expect unlimited design revisions, while the developer has included only two rounds. An agency may assume that the client will provide website content, while the client expects copywriting to be included. Both sides may assume they own the website files, source code, domain, and hosting accounts without having clarified those rights.

A written agreement helps prevent these misunderstandings.

This website development agreement checklist explains the important clauses Indian businesses should review before hiring a web development agency or freelancer. It also covers what developers should document to establish clear expectations with clients.

Whether you are commissioning a business website, WordPress website, e-commerce store, web application, or custom software project, use this guide to understand what should be agreed upon before work begins.

Disclaimer: This article provides general business information, not legal advice or a ready-to-sign contract. Contract terms, intellectual-property rights, taxation, data protection, stamp duty, and dispute-resolution requirements depend on the particular project and applicable law. Have a qualified Indian lawyer review agreements involving material commercial or legal risk.

1. What Is a Website Development Agreement?

A website development agreement is a written arrangement between a client and a web developer, freelancer, or agency that defines the terms of a website development project.

It explains what the developer will deliver, what the client must provide, how the project will be managed, and what responsibilities each party has.

A website development agreement may cover:

  • Project objectives and scope of work.
  • Website pages, features, and functionality.
  • Design and development responsibilities.
  • Project timeline and milestones.
  • Pricing and payment terms.
  • Revisions and change requests.
  • Testing and approval procedures.
  • Intellectual-property and source-code rights.
  • Domain and hosting responsibilities.
  • Third-party software and licences.
  • Security and data handling.
  • Maintenance and post-launch support.
  • Project termination and final handover.

The agreement does not need to be unnecessarily complicated. It needs to be specific enough that both parties can understand what they have agreed to.

2. Why Is a Website Development Agreement Important?

A website project involves more than a developer writing code or designing pages. It requires decisions about content, technology, approvals, payments, ownership, and ongoing responsibilities.

Without written terms, even a relatively small project can create avoidable disagreements.

For business owners

A clear agreement helps you:

  • Understand exactly what you are paying for.
  • Avoid unexpected additional charges.
  • Know when payments are due.
  • Understand who owns the website and its deliverables.
  • Maintain access to important accounts and files.
  • Know what support is included after launch.
  • Understand what happens if the project is delayed or cancelled.

For developers and agencies

A clear agreement helps you:

  • Define project boundaries.
  • Prevent unlimited revision requests.
  • Establish payment expectations.
  • Document client responsibilities.
  • Manage additional feature requests.
  • Set realistic delivery timelines.
  • Separate development work from ongoing maintenance.

The objective is not to create an agreement that favours only one party. It should establish reasonable responsibilities and protect both sides.

3. Website Development Agreement Checklist: Essential Clauses

Before signing an agreement, review the following sections carefully.

1. Identify the parties involved

The agreement should clearly identify the client and the service provider.

Include:

  • Full legal name of the client or business.
  • Full legal name of the developer or agency.
  • Business name, where applicable.
  • Registered or correspondence address, where appropriate.
  • Contact email and phone number.
  • Name and designation of the authorised representative.
  • Agreement date.

If an agency operates as a sole proprietorship, the agreement should identify the proprietor and the business name appropriately rather than incorrectly treating the business as a separate incorporated company.

Both parties should verify that the person signing has the authority to enter into the agreement.

2. Define the project scope of work

The scope of work is one of the most important parts of a website development agreement.

Avoid vague descriptions such as:

  • Complete website development.
  • Professional business website.
  • Modern e-commerce website.
  • All required features included.

These descriptions do not establish what will actually be delivered.

Instead, specify the work in detail.

For example, a business website project might include:

Pages

  • Homepage.
  • About Us.
  • Services.
  • Portfolio.
  • Blog.
  • Contact Us.

Design

  • Custom homepage design.
  • Responsive layouts.
  • Consistent typography and colours.
  • Standard navigation and footer.

Functionality

  • Contact enquiry form.
  • WhatsApp contact button.
  • Blog publishing functionality.
  • Basic website search, if included.

Technical requirements

  • Agreed CMS or development technology.
  • Mobile responsiveness.
  • SSL configuration.
  • Basic on-page SEO setup.
  • Website deployment.

Also document what is excluded, such as:

  • Professional photography.
  • Logo design.
  • Paid stock images.
  • Advanced SEO campaigns.
  • Paid advertising.
  • Third-party subscription charges.
  • Additional pages not listed in the scope.
  • Ongoing content updates.

The clearer the scope, the easier it is to determine whether a later request is included work or an additional requirement.

3. Specify the technology and platform

The agreement should identify the platform or technology being used.

Depending on the project, this could include:

  • WordPress.
  • Shopify.
  • WooCommerce.
  • Custom HTML, CSS and JavaScript.
  • React or Next.js.
  • Node.js or other backend technologies.
  • PostgreSQL, MySQL, or another database.
  • Third-party APIs and integrations.

For a custom project, document important technical requirements such as the expected hosting environment, database, integrations, and deployment arrangements.

Do not force unnecessary technical details into a simple website agreement. Include enough information to avoid confusion about what is being delivered.

4. Define project deliverables

The agreement should list the items the client will receive.

Possible deliverables include:

  • Completed website.
  • Approved page designs.
  • Website source files.
  • Custom code developed for the project.
  • CMS administrator access.
  • Agreed design assets.
  • Database export, where applicable.
  • Documentation.
  • Deployment details.
  • Agreed credentials and account access.
  • Basic training or handover session, if included.

For projects involving custom applications, also specify whether API documentation, repository access, build instructions, and deployment configuration are part of the delivery.

Do not assume that every item is included simply because the client has paid for website development.

5. Set project timelines and milestones

A website project should have a realistic schedule.

A useful project structure might include:

Milestone 1: Discovery and planning

  • Requirement discussion.
  • Sitemap preparation.
  • Scope approval.
  • Content and asset collection.

Milestone 2: Design

  • Wireframes, where applicable.
  • Visual design.
  • Client feedback.
  • Design approval.

Milestone 3: Development

  • Frontend development.
  • Backend development, if required.
  • CMS configuration.
  • Integration work.

Milestone 4: Testing and review

  • Functional testing.
  • Mobile testing.
  • Content review.
  • Bug fixing.
  • Client acceptance.

Milestone 5: Launch and handover

  • Production deployment.
  • Domain and DNS configuration.
  • Final testing.
  • Credentials and documentation handover.

The agreement should identify expected dates or durations and explain what happens if either party delays an activity.

For example, the project may be delayed if the client does not provide approved content, images, access credentials, or feedback within the agreed time.

Avoid guaranteeing a launch date without considering these dependencies.

6. Clearly define pricing and payment terms

The agreement should state the total project price and the payment schedule.

It should clarify:

  • Total development fee.
  • Advance payment.
  • Milestone-based payments.
  • Payment due dates.
  • Applicable taxes, including GST where relevant.
  • Third-party costs.
  • Late-payment terms, if applicable.
  • Conditions for releasing final deliverables.

For example, a project could use this illustrative structure:

  • 30% advance before work begins.
  • 30% after design approval.
  • 30% after development and staging review.
  • 10% after final acceptance and agreed handover.

This is only an example, not a universal or legally prescribed payment structure. The appropriate arrangement depends on project size, risk, deliverables, and the commercial agreement.

The important point is that payment milestones should correspond to identifiable work or deliverables.

7. Define revisions and change requests

Revision policies should be written clearly.

For example, the agreement might specify:

  • Two rounds of design revisions.
  • A defined review period for each milestone.
  • Consolidated feedback from the client.
  • Additional revisions billed separately.
  • Written approval before additional work begins.

A revision and a new feature request are not necessarily the same thing.

Example of a revision:

Changing the colour of an approved button or adjusting the spacing of a section.

Example of a change request:

Adding a customer login system after the original scope included only a contact form.

Additional requirements can affect project cost and delivery time.

A written change-request process should identify the requested work, additional charges, timeline impact, and approval before development continues.

8. Establish website ownership and intellectual-property rights

This is one of the most important clauses in the agreement.

Many clients assume that paying for website development automatically transfers every intellectual-property right to them. That assumption can create problems.

India's Copyright Act, 1957 addresses first ownership of copyright and assignment of copyright. Section 19 sets out requirements for a valid assignment, including a written and signed assignment identifying the work and specifying the rights, duration, and territorial extent.

The agreement should therefore clearly explain:

  • Who owns custom code created specifically for the project.
  • Who owns original design work.
  • Who owns website content created for the project.
  • When any agreed ownership transfer takes effect.
  • Which pre-existing tools or reusable components remain with the developer.
  • Which third-party assets are governed by separate licences.

A practical agreement may distinguish between:

Custom project work

Code, designs, or other materials created specifically for the client, with ownership or licensing arrangements clearly documented.

Pre-existing developer assets

Reusable frameworks, internal tools, libraries, templates, and components that the developer already owned or developed independently.

Third-party assets

Themes, plugins, fonts, stock photographs, software libraries, and other components subject to their respective licence terms.

Do not use a blanket statement such as "the client owns everything" without checking whether third-party licences and pre-existing components permit that arrangement.

For higher-value custom development, have a lawyer draft or review the intellectual-property assignment and licensing provisions.

Official reference: The Copyright Act, 1957 – India Code.

9. Clarify domain name and hosting ownership

The domain name and hosting account should be addressed separately from the website's code ownership.

The agreement should clarify:

  • Who registers the domain.
  • Whose name and contact details are used for registration.
  • Who pays domain renewal fees.
  • Who owns or controls the hosting account.
  • Who can access the hosting control panel.
  • Who manages DNS records.
  • What happens when hosting services are discontinued.
  • How the website will be transferred to another provider.

For most businesses, maintaining direct control over their domain registration is a sensible arrangement.

If the agency manages hosting or DNS on the client's behalf, document the access and transfer process.

Do not rely solely on a verbal promise that the domain or hosting account will be transferred later.

10. Define source-code and account access

A website is more than its public-facing pages.

Depending on the project, the client may need access to:

  • Source-code repository.
  • Website administrator account.
  • CMS dashboard.
  • Hosting control panel.
  • Database.
  • Domain registrar.
  • DNS management.
  • Analytics accounts.
  • Search Console.
  • Relevant third-party integrations.

The agreement should specify which accounts are created, who controls them, what access is provided, and when credentials or ownership are transferred.

For custom development, define whether the repository and project documentation are included in the handover.

Avoid sharing passwords through unsecured messages. Use appropriate access controls and secure credential-transfer methods.

11. Document third-party tools and recurring costs

A website may depend on external services.

Examples include:

  • Premium WordPress themes.
  • Paid plugins.
  • Payment gateways.
  • Email services.
  • Booking platforms.
  • CRM software.
  • Stock image libraries.
  • External APIs.
  • Marketing and analytics platforms.

The agreement should explain:

  • Which tools are included.
  • Which tools require separate payment.
  • Who purchases the subscriptions.
  • Who owns the relevant accounts.
  • What happens when a subscription expires.
  • Whether licence renewals are included in maintenance.

A low initial development quotation may not include ongoing third-party subscription costs.

Make these expenses visible before signing.

12. Define testing and acceptance criteria

The agreement should explain how the client will review and approve the website.

Testing may cover:

  • Page loading and navigation.
  • Forms and email notifications.
  • Mobile responsiveness.
  • Browser compatibility.
  • Payment functionality, if applicable.
  • Login and registration.
  • API integrations.
  • Content accuracy.
  • Broken links.
  • Basic accessibility checks.
  • Security configuration.

Define a reasonable review period for each milestone.

Also distinguish between a defect and a new requirement.

Defect: A feature specified in the approved scope does not work as agreed.

New requirement: The client requests functionality that was not part of the approved scope.

The agreement should describe how defects are reported, corrected, and retested, and how new requirements are priced.

13. Include a post-launch bug-fix and support period

A website may need corrections after it becomes publicly available.

The agreement should define a post-launch warranty or bug-fix period, if offered.

Clarify:

  • How long the support period lasts.
  • Which defects are covered.
  • How support requests are submitted.
  • Expected response times.
  • Whether emergency support is available.
  • What work is chargeable.

For example, a developer may include a 30-day period for correcting defects in agreed functionality.

That does not automatically mean all new features, design changes, content updates, or third-party failures are included.

Define the boundaries rather than using vague promises such as "lifetime support."

14. Separate website maintenance from development

Website development and ongoing maintenance are different services.

A development agreement may include launch support without including indefinite maintenance.

If maintenance is offered, document its scope separately.

It may include:

  • CMS and plugin updates.
  • Backup checks.
  • Security monitoring.
  • Minor technical corrections.
  • Uptime checks.
  • Content changes, if included.
  • Restoration assistance.
  • Support response times.

Also specify the maintenance fee, billing frequency, exclusions, and cancellation procedure.

Read our Website Maintenance Checklist for Small Businesses in India to understand the ongoing responsibilities involved in maintaining a business website.

15. Include confidentiality and data-handling responsibilities

Website projects may involve access to customer information, business records, login credentials, enquiry forms, or other sensitive information.

The agreement should explain:

  • What information is confidential.
  • Who can access project data.
  • How credentials are protected.
  • Whether information can be shared with subcontractors.
  • How test data is handled.
  • How information is returned or deleted after the project.
  • How security incidents are communicated.

Where personal data is processed, consider the applicable provisions of India's Digital Personal Data Protection Act, 2023 and relevant rules and commencement notifications.

The parties should clarify their respective roles and responsibilities rather than assuming that a general confidentiality clause covers every data-protection obligation.

Official reference: Digital Personal Data Protection Act, 2023 – India Code.

16. Define termination and project handover

Not every project reaches completion as originally planned.

The agreement should explain what happens if either party wants to end the engagement.

Clarify:

  • Conditions for termination.
  • Required written notice.
  • Outstanding payment obligations.
  • Payment for work completed.
  • Treatment of advance payments.
  • Ownership and delivery of paid work.
  • Return of confidential information.
  • Transfer of relevant accounts and files.
  • Access required for project continuity.

Avoid vague termination language that leaves both parties uncertain about what happens to work already completed.

The handover process should also be documented before development begins, not negotiated during a disagreement.

17. Specify dispute resolution and governing terms

For commercial agreements, the parties should consider documenting:

  • Governing law.
  • Appropriate jurisdiction.
  • Dispute-resolution procedure.
  • Negotiation or mediation arrangements, if agreed.
  • Arbitration provisions, where appropriate.
  • Notice and communication methods.

The suitability and enforceability of particular clauses depend on the agreement and applicable law.

Have a qualified lawyer review these provisions, especially for higher-value projects.

4. Website Development Agreement Checklist Before Signing

Use this practical checklist to review the important commercial and technical details.

Project scope

  • Client and developer details are correct.
  • Project objectives are documented.
  • Website pages are listed.
  • Features and integrations are specified.
  • Technology or platform is identified.
  • Included and excluded work is clear.
  • Client responsibilities are documented.

Payments and timelines

  • Total project fee is mentioned.
  • Payment milestones are defined.
  • Taxes and third-party costs are clarified.
  • Project timeline is realistic.
  • Client approval dependencies are documented.
  • Late-payment and delay terms are clear.

Revisions and acceptance

  • Revision limits are defined.
  • Change-request process is documented.
  • Testing responsibilities are clear.
  • Acceptance criteria are specified.
  • Bug-fix period is documented.

Ownership and access

  • Intellectual-property terms are written.
  • Source-code delivery is addressed.
  • Pre-existing and third-party components are identified.
  • Domain ownership is clarified.
  • Hosting account responsibilities are clear.
  • Administrator and repository access are addressed.

Security and support

  • Confidentiality obligations are documented.
  • Data-handling responsibilities are clear.
  • Backup and security responsibilities are assigned.
  • Maintenance scope and charges are clarified.
  • Support response expectations are documented.

Handover and termination

  • Handover deliverables are listed.
  • Project documentation is addressed.
  • Termination conditions are defined.
  • Outstanding payments are addressed.
  • Account and file transfer is documented.
  • Dispute-resolution terms are reviewed.

5. Common Red Flags in Website Development Agreements

Before signing, look for terms that could create problems later.

1. Vague project descriptions

A contract that only promises a "complete professional website" does not establish the actual deliverables.

2. Unclear pricing

If additional pages, revisions, plugins, or integrations have no defined pricing or approval process, the final cost may become unpredictable.

3. No written ownership terms

Do not assume that payment alone settles every intellectual-property question.

4. No domain or hosting access arrangements

A business should understand how it can access and transfer its domain and hosting services.

5. Unlimited or undefined revisions

Both sides need to understand what counts as a revision and what counts as additional work.

6. No testing or acceptance procedure

Without an agreed review process, disagreements about whether the website is complete become harder to resolve.

7. Unrealistic delivery promises

A fixed launch date without clear client responsibilities, content deadlines, and approval dependencies may be unrealistic.

8. Vague maintenance promises

Statements such as "free support forever" should be replaced with specific support terms and exclusions.

9. No handover process

The agreement should explain what happens to source files, credentials, accounts, and documentation when the project ends.

6. Website Development Agreement vs Website Maintenance Agreement

These agreements serve different purposes.

Website development agreement

Covers the creation or major development of a website.

Typical subjects include project scope, design, features, deliverables, payment milestones, ownership, testing, and launch.

Website maintenance agreement

Covers ongoing services after the website is live.

Typical subjects include updates, backups, security checks, technical support, bug fixes, and maintenance fees.

Some businesses use one master agreement with separate project and maintenance schedules. Others use separate documents.

The important point is to distinguish one-time development responsibilities from recurring service obligations.

7. What Should Be Included in the Final Website Handover?

A project is not fully handed over simply because the website is publicly accessible.

The final handover should follow the agreed deliverables and ownership arrangements.

Depending on the project, it may include:

  • Live website URL.
  • CMS administrator credentials.
  • Hosting control panel access.
  • Domain registrar and DNS access.
  • Agreed source-code files or repository access.
  • Database export, where applicable.
  • Design files, if included.
  • Integration documentation.
  • Relevant third-party account information.
  • Backup information.
  • Deployment instructions.
  • Maintenance and support details.
  • Basic training or knowledge transfer, if agreed.

Both parties should confirm the handover in writing.

For a custom application, include enough technical documentation for another qualified developer to understand the deployment and operation of the delivered system.

8. How to Prepare Before Hiring a Website Development Company

An agreement works best when the business owner understands the project before requesting quotations.

Before contacting an agency, prepare:

1. Business objectives

Explain what the website should achieve: enquiries, product sales, bookings, brand awareness, or another measurable outcome.

2. Required pages

List the pages and explain what information each page should contain.

3. Required features

Identify contact forms, payment gateways, booking tools, customer accounts, API integrations, or other requirements.

4. Design references

Share examples of websites you like and explain which elements are relevant.

5. Content and branding

Clarify whether you will provide text, images, logos, and other brand assets or expect the agency to create them.

6. Budget and timeline

Share a realistic budget range and any important launch deadlines.

7. Ongoing requirements

Decide whether you need hosting, maintenance, security updates, SEO, or technical support after launch.

For a more detailed provider-selection process, read How to Choose a Website Development Company in India in 2026.

9. Frequently Asked Questions

1. Is a website development agreement necessary for a small business website?

A written agreement is useful even for a small project. It clarifies the deliverables, price, timeline, revisions, ownership, and support responsibilities. The level of detail should be proportionate to the project's complexity and commercial risk.

2. Who owns a website after development in India?

Ownership depends on the applicable law, the nature of the work, the parties' relationship, and the agreement. The Copyright Act, 1957 addresses first ownership and assignment. Clients should not assume that paying a development invoice automatically transfers every copyright or licence. Get the intended rights documented in writing.

3. Should the client own the domain name?

For most business websites, it is sensible for the client to retain direct control over domain registration. If an agency manages the domain or DNS, the access, renewal, and transfer arrangements should be documented.

4. Should website development payments be made in advance?

The payment schedule should be agreed before work begins. Many projects use an advance followed by milestone payments. The appropriate structure depends on the project, risk, and deliverables. Avoid paying without a written scope and clear payment conditions.

5. What happens if a client requests additional features during development?

Additional features should go through a documented change-request process. The developer should explain the cost and timeline impact and obtain approval before starting the extra work.

6. Does website development include maintenance?

Not automatically. Development and maintenance are separate services unless the agreement explicitly includes maintenance. Check the duration, scope, pricing, and exclusions of any post-launch support.

7. Should source code be included in the handover?

The agreement should specify whether source code and repository access are included, which components are covered, and what rights the client receives. This is especially important for custom websites and web applications.

8. Can a website development agreement be signed electronically in India?

Electronic contracting and electronic signatures are recognised under applicable Indian law, subject to the relevant legal requirements and exclusions. The appropriate execution method depends on the agreement and transaction. Obtain legal advice if the contract has significant commercial value or specific execution requirements.

Final Thoughts

A website development project should begin with clear expectations, not assumptions.

A well-prepared agreement explains what will be built, what each party must provide, how payments will work, who receives which rights, and what happens after launch.

For business owners, the website development agreement checklist is a practical starting point for asking the right questions before committing to a development project.

For agencies and developers, it is a way to define responsibilities, reduce misunderstandings, and manage projects more professionally.

Before signing, make sure the commercial and technical terms reflect the actual project. For significant legal or intellectual-property matters, have the agreement reviewed by a qualified lawyer.

Planning a new business website or custom web solution?

Arctis Digital provides website design and development, backend and API development, UI/UX design, e-commerce development, SEO, and website maintenance services.

Visit Arctis Digital or contact our team to discuss your project requirements.

Official References and Useful Resources

Related Guides from Arctis Digital