Revisions are part of the job. Doing three extra rounds for free because nobody wrote down what was actually agreed is not part of the job, and that gap is exactly where a healthy project margin quietly disappears. This one is for the studio owner who keeps hearing "can we just change one small thing" and then watches a week of unpaid rework eat the profit that was supposed to be sitting in the project.
Let me be honest about something up front. Most studios I talk to don't lose money on revisions because their design is weak, they lose it because the revision has no paper trail, no price attached, and no clear line between "included" and "extra". So the client keeps asking, the team keeps redrawing, and at the end of the project you've done the work of two projects and billed for one.
Where the money actually leaks on revisions
The leak is not the first revision, or even the second. Good work needs iteration and clients deserve to see options. The leak is the fourth, fifth and sixth round that happens after the design was effectively approved, because there was never a moment where everyone agreed "this is locked, anything past this is a change order".
Think about a mid-size living room and two bedroom project. You present the mood board, the client loves it, you move to procurement in your head. Then a week later the client's cousin visits and suddenly the sofa fabric is wrong, the accent wall needs a rethink, and the wardrobe shutter finish should be matte after all. Each of those feels small in isolation. Together they are a full redraw of your specs, your quote, and sometimes your interior design intent for the whole room, and none of it is billed.
Why this happens so often in Indian studios
There is a cultural piece here that global software never accounts for. In a lot of Indian projects the relationship is warm and personal, the client is a family friend or a referral, and saying "that will cost extra" feels awkward in the middle of a friendly WhatsApp thread. So we absorb it. The problem is that absorbing one change sets the expectation that every change is free, and by the third project with that client you've trained them to treat your studio as unlimited revisions included.
The second reason is structural. When your design lives in one tool, your quote in Excel, your approvals in WhatsApp and your invoice somewhere else, there is no single place that says "version 3 was approved on this date". So when a dispute comes up about whether the marble was signed off, you have nothing to point to, and the client's memory always favours the client. This is the same disconnection problem I unpack in the true cost of running a studio on five tools, and revisions are one of its most expensive symptoms.
| Revision round | What it should be | What it usually becomes |
|---|---|---|
| Round 1 to 2 | Included iteration, priced in | Fine, this is normal |
| Round 3 | Gentle "we're close, let's lock it" | Another free redraw |
| Round 4+ | A billed change order | Silent unpaid rework |
| Post-approval tweaks | Change order with new quote | "Just one small thing", repeated |
Fix one: make scope and the approved version impossible to argue about
The single most effective thing you can do is create a clear, visible moment of approval that both sides can see later. Not a verbal yes, not a thumbs-up emoji, an actual recorded sign-off on a specific version of the design. When the client taps approve on a mood board and it's timestamped, the conversation three weeks later changes completely, because now you're both looking at the same record instead of arguing from memory.
This is where a branded client portal earns its keep. The client sees the room, sees the finish options, approves online, and that approval is on the record. Anything after that approved version is, by definition, a change, and you can say so kindly and clearly because the system is showing both of you where the line is. Scope creep and revision creep are cousins, and I go deeper on the prevention side in how to stop scope creep before it starts.
Fix two: attach a price to every change, automatically
Here's the mindset shift. A revision after approval is not a favour, it's a change order, and a change order has a number. The reason studios don't bill it is that re-pricing feels like a whole exercise, you'd have to redo the quote, recalculate, and then have the awkward money talk.
But if your specs, your costs and your quote are the same connected object, then changing the spec changes the price on its own. You don't sit down to "make a revised quote", the quote is simply the current state of the approved specs, and when the client asks for the imported handle instead of the local one, the delta is right there in rupees. That makes the money conversation easy, because you're not negotiating, you're just showing what the change costs.
Fix three: keep the revision history in one place
Part of losing money on revisions is losing the revisions themselves. You made version 2, the client approved something close to version 3, and now there are four PDFs called "final", "final-v2", "FINAL-final" and "latest" sitting in three different WhatsApp chats and an email. When you can't find the approved version quickly, you redo work you'd already done, which is rework you're paying for twice.
Keeping every version and every approval in one workspace means the history is the source of truth. You can always see what was shown, what was approved, and what changed after, which is also the backbone of raising a clean bill later, something I walk through in how to turn a quote into a GST invoice in minutes.
Key takeaways
- The leak is post-approval rework with no price and no record, not honest iteration
- A timestamped approval on a specific version ends most revision disputes
- When specs and quote are one connected object, every change re-prices itself
- One version history means you stop redoing work you already did
What this looks like inside one connected workspace
In Designa the flow is deliberately boring, which is the point. You build the project room by room, spec the furniture and finishes with photos and live costs, the client approves the mood board in the branded portal with unlimited free client logins, and that approval is on the record. When a change comes in after that, you update the spec, the quote reflects the new number, and if it's a billable change you carry it straight to a compliant GST invoice with Razorpay collection attached. Nothing gets absorbed silently because the system keeps showing everyone where "approved" ended and "change" began.
If you want the wider case for running everything in one place instead of stitching tools together, I made it in why one connected system beats five disconnected tools, and if you're comparing options seriously, the best software for interior designers in India guide lays out what to actually look for.
This matters for architecture practices too, not just interior studios. Firms registered with the Council of Architecture run the same approval-and-change cycle on drawings, and members of the Institute of Indian Interior Designers deal with the exact revision-billing problem I've described here.
Frequently asked questions
How many revisions should I include in an interior design contract?
Most studios include two or three rounds and bill anything past that as a change order. The key is stating it clearly up front and having a recorded approval so everyone knows when included rounds end.
Can I charge a client for revisions after they approved the design?
Yes, a change requested after a recorded approval is a change order and can be billed. It's far easier to do when your specs and quote are connected, so the price of the change is visible instead of negotiated.
How do I prove a client approved a specific version?
Use a client portal that timestamps the approval on a specific mood board or spec version, so the record exists independently of anyone's memory or WhatsApp history.
Does Designa handle revision pricing automatically?
Yes. Because specs, costs and the quote are one connected object, changing a spec updates the quote, and a billable change flows into a GST invoice without redoing anything.
You will never stop clients from wanting changes, and you shouldn't want to, because iteration is where good design happens. What you can stop is doing that work invisibly and for free. If you want to see how a recorded approval and an auto-repricing quote actually feel, poke around a real setup at demo.designa.work, and when you're ready to close this leak for good, the founding offer is one flat price for your whole studio, billed in rupees, with unlimited free client logins at go.designa.work.