Writing a Client Contract for Interior Design Work

A designer in Gurugram completed a full villa interior over five months, working off a friendly relationship, a shared WhatsApp thread, and a verbal understanding that the final 20% would be paid "once everything's done and they've moved in." Everything was done. They moved in. And then the final payment simply didn't come — not because the client was dishonest, but because the family had a genuine, if inconvenient, disagreement about whether a few last-minute changes were meant to be included in the original quote, and with nothing in writing, there was no shared reference point to resolve it. The designer spent four months chasing roughly ₹3.8 lakh, eventually settling for less than she was owed, purely because she had no contract to point to.

This is one of the most common and most preventable failure modes for independent interior designers in India — not bad work, not unhappy clients, but the absence of a written agreement that would have made the eventual disagreement resolvable in minutes instead of months. Handshake deals feel efficient and relationship-friendly when a project starts, and most of the time they work out fine. But the projects that go wrong are exactly the ones where a contract would have mattered most, and by definition, you don't know in advance which project that will be.

With India's interior design market growing from roughly US$31.43 billion in 2025 toward a projected US$65.01 billion by 2031 at a compound annual growth rate near 12.87%, according to Mordor Intelligence's India Interior Design Market report (2026), and the industry remaining largely fragmented and dominated by small, informal practices, contract discipline isn't a bureaucratic nicety — it's one of the clearest lines between designers who build a durable, professional practice and those who stay perpetually exposed to disputes they have no way to resolve cleanly.

What a Design Contract Actually Does — and Why Solos Skip It

A client contract for interior design work does three things: it defines what's being delivered (scope), it defines how and when the designer gets paid (payment terms), and it defines what happens when things change or go wrong (change orders, timelines, termination). None of this needs to be adversarial — a good contract is protective for both sides, not just the designer. A client who has a written scope and payment schedule is also protected from a designer who might otherwise be vague about deliverables or timelines.

Independent designers skip contracts for understandable reasons: many projects come through personal referrals where a contract can feel like an unnecessary formality between people who already trust each other; drafting one feels like a legal hurdle when the designer just wants to start designing; and there's a genuine fear that asking for a signed contract might read as distrustful and cost a warm lead. But none of these reasons hold up against the actual cost of a dispute with no paper trail — which, as the opening story shows, can mean months of lost time and a meaningfully reduced final payment, on top of the emotional toll of an ugly ending to what should have been a good project.

Step-by-Step: The Clauses a Contract Should Cover

Scope of work. List every space covered, the deliverables for each (concept, 3D visuals, execution drawings, site supervision visit count), and explicit exclusions — anything outside the listed spaces or outside interior design entirely (structural, plumbing, electrical rewiring).

Fee and payment schedule. State the total fee (or fee model — see the per-sqft vs percentage comparison for how to structure this), and break it into milestone-linked installments — for example, an advance on signing, a payment at concept approval, one or more payments during execution, and a final payment at handover. Milestone-linked payments are dramatically easier to enforce than a single lump sum due "at the end," because each stage is a discrete, provable trigger.

Change-order process. Define exactly how additions to scope will be identified, priced, and approved before work on them begins — this is the clause that would have protected the Gurugram designer's final payment dispute above.

Timelines. State an estimated project duration and, critically, name the dependencies that could extend it — material availability, site readiness, client approval turnaround — so a delay caused by the client's own slow decision-making isn't later blamed on the designer.

Materials and procurement responsibility. Clarify who is sourcing and paying for materials directly — the designer, the client, or a contractor — and how markups (if any) are disclosed.

Intellectual property. State who owns the design concept and drawings, and whether the client can reuse them with a different executor without the designer's involvement.

Termination clause. Define what happens if either party wants to exit early — what's owed for work completed to that point, and any notice period.

GST and applicable taxes. State clearly whether quoted fees are inclusive or exclusive of GST, and the designer's GST registration status if applicable.

Contract Clauses: What They Protect and What Goes Wrong Without Them

The India-Specific Picture: GST, Advances, and Who Signs

A handful of clauses matter specifically in the Indian residential context and deserve deliberate attention rather than being copied from a generic template. GST handling needs to be explicit — whether the quoted design fee is inclusive or exclusive of GST, and if the designer is registered, since this affects the client's total outlay and is a common source of late-stage confusion if left ambiguous. Advance and milestone payment structure should reflect how Indian residential projects actually run, typically with a signing advance (commonly in the 10–20% range as an illustrative norm, not a sourced figure) followed by milestone payments tied to concept approval, execution phases, and handover — rather than open-ended "pay when convenient" terms.

Material-procurement responsibility deserves particular clarity in India, where it's common for designers, contractors, and clients to split sourcing across different categories (client buys the modular kitchen directly, designer sources soft furnishings, contractor handles civil materials) — the contract should name who's responsible for which category to avoid confusion about markups and delivery delays.

Perhaps most distinctively, joint-family and multi-stakeholder decision-making means a project frequently has more than one person weighing in — parents, adult children, sometimes an extended family member with strong opinions — but often only one person's name is on the payment. The contract should explicitly name the actual decision-maker(s) whose sign-off is binding, so a designer isn't caught between conflicting instructions from different family members with no documented authority to resolve the conflict. Site-readiness dependencies (a common cause of Indian project delays — civil work not finished, electrical points not ready) should also be named explicitly as a timeline dependency outside the designer's control.

Mini Scenario: Avoiding a Payment Dispute Through Written Milestones

A Bengaluru-based designer structured her fee for a 4BHK apartment into four milestone payments: 20% on signing, 30% at concept approval, 30% at the start of execution, and the final 20% at handover — each tied to a specific, dateable event rather than a vague project phase. Midway through execution, the client's adult son — who hadn't been part of the original conversations — pushed back on the final payment amount, claiming he remembered a lower total figure being discussed. Because the contract stated the total fee and the milestone breakdown in writing, signed by the client (his mother, the named decision-maker), the designer was able to resolve the disagreement in a single conversation by simply referring to the signed document. There was no ambiguity to argue about, no months-long chase, and the relationship stayed intact because the resolution was a shared fact rather than a matter of competing memories.

From Proposal to Contract

A contract works best when it isn't the first document a client sees — ideally, it formalizes something the client has already reviewed and responded to. DrawMagic's proposals feature lets designers present scope, fee structure, and terms to a client in a structured format before any contract is signed, giving both sides a chance to align on the substance first. By the time a formal contract is drafted, the client has already seen and effectively agreed to the scope and payment structure in the proposal — which makes the contract itself a much smoother, less contentious conversation, since it's documenting an agreement already reached rather than introducing new terms for the first time.

Pro Tips

• Name the decision-maker explicitly in the contract. In multi-stakeholder households, this single line prevents a huge share of later disputes about whose instructions are binding.
• Tie every payment to a specific, dateable milestone. Avoid vague triggers like "on completion" — use concrete events (concept sign-off, execution start, handover) that are easy to point to.
• Define exclusions as clearly as inclusions. What's not covered is just as important as what is.
• Keep the language plain, not legalistic. A contract clients can actually read and understand is more likely to be honored without dispute than one full of jargon they skim past.
• Have a lawyer review the final draft, every time. This guidance is a starting checklist, not a substitute for professional legal review specific to your situation.

Common Mistakes to Avoid

• No written scope at all — relying on verbal understanding or a WhatsApp thread as the only record of what was agreed.
• No change-order clause, leaving mid-project additions undocumented and unpaid.
• Unclear payment triggers, especially a single large payment due "at the end" with no defined milestone.
• No termination terms, leaving an early exit to become an unstructured, potentially bitter negotiation.
• Treating the contract as a one-time template copy-paste rather than something reviewed and adapted per project and, ideally, per client relationship.

How DrawMagic Supports Cleaner Contracting

Getting scope and terms aligned before a contract is signed starts with a clear proposal — DrawMagic's proposals feature gives designers a structured way to present scope, fee, and terms to a client, creating a documented starting point the eventual contract can build on. Your professional profile on DrawMagic — a provider surface that continues to evolve — is where that structured, professional approach to contracting becomes visible to buyers before they even reach out, reinforcing that you run a business with clear terms, not just a freelance practice on handshakes. Buyers discover and shortlist designers through the professionals directory in the buyer app, where a reputation for clean, dispute-free projects compounds into more referral-quality leads over time. Sign up to start building a profile and a proposal-to-contract workflow that protects you from day one.

Contracts as Protection, and the Aggregator Context

A written contract is, in the most literal sense, the independent designer's insurance policy — it's the thing that turns a disagreement into a documented fact rather than a he-said-she-said standoff. This matters more for solos than for firms, because a firm typically has institutional processes (standard contract templates, a legal or admin function) that make contracting close to automatic, while an independent designer has to build that discipline deliberately, project by project. It's worth noting this in the same breath as aggregator economics: providers on platforms like Urban Company have historically absorbed a take-rate in the roughly 20–30% range, according to UnlistedZone's 2026 analysis of the company's FY25 financials, in part because the platform also handles contracting, payment collection, and dispute resolution on the provider's behalf. Independent designers who contract for themselves keep the full fee — but that only pays off if their own contracting discipline is strong enough to actually protect the payment when a dispute arises.

Key Takeaways

• A written contract protects both designer and client by clearly defining scope, payment terms, and what happens when things change or go wrong.
• Milestone-linked payments (advance, concept approval, execution, handover) are far easier to enforce than a single lump sum due at project completion.
• Include a change-order clause so mid-project additions become documented, priced events rather than unpaid scope creep.
• Name the actual decision-maker explicitly in multi-stakeholder, joint-family projects to prevent disputes over whose instructions are binding.
• Clarify GST treatment, material-procurement responsibility, and site-readiness dependencies — all common India-specific friction points.
• Use DrawMagic's proposals feature to align scope and terms with the client before drafting the formal contract.
• A well-presented professionals profile signals contracting discipline to buyers before they even reach out.
• This is general business guidance, not legal advice — always have a qualified lawyer review or finalize your contract.
• Independent designers keep their full fee where aggregator-model providers absorb a 20–30% take-rate (UnlistedZone, 2026) — but only with strong contracting discipline of their own.
• The cost of skipping a contract isn't hypothetical — it shows up as months of unpaid chasing exactly when a project goes sideways.

FAQ

Do I need a lawyer to write my first contract? You don't need one to draft a working first version using a checklist like this one, but you should have a qualified lawyer review or finalize any contract before using it on real client engagements — this content is general guidance, not legal advice.

What if a long-time referral client is offended by a contract request? Frame it as standard professional practice that protects them too, not just you — a contract clarifies expectations on both sides and is common practice among established designers.

How should milestone payments be structured for a typical residential project? There's no fixed rule, but a common illustrative structure is an advance on signing, a payment at concept approval, one or more payments during execution phases, and a final payment at handover — adjust the split to match your own cash-flow needs and project length.

Is a WhatsApp confirmation ever enough instead of a formal contract? It's better than nothing and can help establish a paper trail, but it's not a substitute for a signed contract with clearly stated scope, payment terms, and a change-order process — especially on higher-value projects.