Tithi MondalBlog

Guide7 min readUpdated

Design Contract Basics: Terms, Ownership and NDA Explained

Learn what a design contract should cover: scope, payment terms, revisions, file ownership and an NDA for your app idea. Not legal advice.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Design Contract Basics: Terms, Ownership and NDA Explained: cover illustration

Suppose a founder in Indore agrees on WhatsApp that a designer will make "a complete app design". Three weeks later, the founder expects 40 screens and 2 user roles. The designer planned 25 screens and 1 role. Both people are polite, both feel cheated, and no document shows who is right.

A design contract is a written agreement between a client and a designer that states the work, the price, the dates and the rights over the finished files. It protects both sides. This guide explains the common parts in plain words.

Important: this is general information, not legal advice. Contract law depends on your situation. Ask a lawyer to review any agreement that involves large amounts of money, a business idea you must protect, or ownership of a brand.

Do I need a design contract for a small project?

Yes, you need some written agreement even for a small project, but the agreement can be short. A one-page document that both sides accept by email or message is far better than a spoken promise.

A small logo job may need only a simple summary of scope, price, deadline and revisions. An app design with many screens and user roles needs a fuller document. The cost of a project, your risk if the work goes wrong, and the number of people involved should decide the length.

Before you sign anything, read the questions to ask a UI/UX designer before hiring. Many of the answers become clauses in the contract. If you are still choosing between people, the guide on how to hire a freelance UI/UX designer in India helps.

What should a freelance designer agreement include?

A freelance designer agreement should include 8 things: scope, deliverables, timeline, price, payment schedule, revisions, ownership and confidentiality. If any of the 8 is missing, ask for the missing part to be added.

  1. Scope: what is included and, just as important, what is not. For example: "Mobile app, 25 screens, customer and seller roles. Admin panel not included."
  2. Deliverables: the exact files you receive, such as Figma file access, exported images, a logo in vector format, or a style guide.
  3. Timeline: start date, dates for each stage and final delivery. Include what happens if the client is late with feedback or content.
  4. Price: the total in rupees, and what is included in the price.
  5. Payment schedule: when each payment is due, and by which method.
  6. Revisions: how many rounds of changes are included, and the cost of extra rounds.
  7. Ownership: who owns the files, and when ownership passes.
  8. Confidentiality: what each side must keep private.

The design brief guide helps you write the scope part clearly. A good brief can be attached to the contract.

What are fair payment terms for a design project?

A common arrangement is to split payment in two: part before work begins and the rest when work is complete. The split should be written in the contract with a date or a condition for each payment.

My own terms are 50% to begin and 50% on completion. I accept UPI and bank transfer, and PayPal for international clients. Two to three revision rounds are included in the price. Other designers may use different splits, for example 3 payments for a long project. Both options can be fair.

Points to agree in writing:

  • Total price and what the price covers. Prices vary because of the number of screens, user roles and the depth of research. The UI/UX design cost guide explains the main factors.
  • Advance payment. An advance shows commitment and lets the designer reserve time for your project.
  • Final payment. State clearly that the final payment is due on completion, and when the final files are released.
  • Late payment. Say what happens if a payment is delayed by many days.
  • Cancellation. If either side stops the project, state what is paid for the work already done.
  • Fixed price or hourly. Read fixed price vs hourly design projects before you choose.

Keep payment records, such as UPI references or bank receipts, for your accounts. Ask your accountant about tax and GST questions, because I cannot advise on them.

Who owns the design files?

Ownership of design files is whatever the contract says, so write the rule down. A common arrangement is that the designer keeps ownership until the final payment, and the client receives full rights to the final approved design after payment. Your agreement may differ.

Many people mix up 3 different things, so separate them.

  • Final deliverables: the logo, screens or files you paid for. You normally expect to use the files freely in your business.
  • Working files and drafts: early sketches and unused concepts. The contract should say whether you receive these.
  • Tools and materials the designer brought: fonts, stock images, icon sets and templates carry their own licences. Ask the designer which licences apply, and who pays for them.

Also ask whether the designer may show the project in a portfolio. Many designers like to, so say yes or no clearly. If the project is confidential, the client can ask to delay or skip the portfolio mention.

For a logo or brand identity, ask a lawyer how to protect the name and the mark. Read more in the logo design guide for small businesses.

Should I ask a designer to sign an NDA for my app idea?

An NDA, or non-disclosure agreement, is a document in which a person promises to keep your information private. You can ask a designer to sign one when you share sensitive material, such as unreleased plans, customer data or technical details. Many designers sign an NDA when the request is reasonable.

An NDA protects secrets, such as private documents, not general ideas that anyone could think of. Most app ideas succeed or fail on execution, not on secrecy. Ask yourself what exactly is secret.

Before you request an NDA:

  • Share the minimum information needed at the first call.
  • Name what counts as confidential, and what does not.
  • State how long the promise lasts.
  • Make the NDA fair for both sides. A one-sided NDA with heavy penalties may make good designers decline.

An NDA does not replace a design contract. You can also put a confidentiality clause inside the contract itself. Ask a lawyer to check the NDA wording, because the exact terms matter.

Design contract checklist you can copy

Copy this list and check your agreement against it. A lawyer can then review the final document.

  • Names and contact details of both sides
  • Project description and goals
  • Scope: what is included and what is not
  • Number of screens, pages or concepts
  • User roles, if an app
  • Deliverables and file formats
  • Start date, stage dates and final date
  • Client duties: content, feedback within an agreed number of days
  • Total price in rupees
  • Payment schedule and methods
  • Number of revision rounds, and cost of extra rounds
  • What counts as a change in scope, and how a change is priced
  • Ownership and when ownership passes
  • Licences for fonts, images and tools
  • Portfolio permission
  • Confidentiality terms
  • Cancellation and refund rules
  • How disagreements will be discussed first
  • Signature or written acceptance from both sides, with the date

What if the project scope changes after we sign?

When the scope changes, write down the change, the extra cost and the new date before any extra work begins. Small written change notes prevent most arguments.

For example, a founder in Nagpur adds a seller dashboard after the contract is signed. The designer replies by message: "A seller dashboard adds about 8 screens and 5 days. Here is the additional price. Please confirm." The founder confirms, and the message becomes part of the record.

Free changes are fine when both sides want them. Say so, so that the exception does not become the rule.

If you want to talk through scope, payment terms and timeline before you commit, you can write to me through the contact section.

Frequently asked questions

Is a WhatsApp message a valid agreement with a designer?

+

A written message can record what both sides agreed, and it is better than a spoken promise. For important projects, ask a lawyer whether a fuller signed contract is needed.

How much should I pay a designer in advance?

+

Many designers ask for part of the fee before starting. My own terms are 50% to begin and 50% on completion, but other arrangements can also be fair.

Can a designer reuse my design for another client?

+

That depends on the contract. Ask for a clause that says whether the final design is exclusive to you.

Does an NDA stop a designer from copying my app idea?

+

An NDA only protects information you define as confidential, and only as far as the law enforces the NDA. A lawyer can explain what protection you really get.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.