Procurement is where studios lose real money without ever seeing it happen. Not in dramatic ways, in quiet ones, a purchase order raised at last month's rate, a delivery that slipped by three weeks, a vendor invoice that's higher than the quote and nobody cross-checked. This is for the studio owner who finishes a project, looks at the numbers, and can't quite explain why the margin came in thinner than the estimate promised.
Let me say the uncomfortable part plainly. In most small and mid-size studios, procurement isn't a system, it's a set of habits living in one or two people's heads and a pile of WhatsApp threads. That works right up until the moment it doesn't, and when it breaks, it breaks on the money side where it hurts most.
What a procurement leak actually is
A procurement leak is the difference between the number you costed and the number you actually paid, multiplied across every line item on a project. On a single order it looks trivial, a few hundred rupees here, a rate that crept up there. Across a full home with fifty or sixty purchase lines, it adds up to a chunk of margin that should have been yours.
The leak has a few usual sources, and they're worth naming because you fix what you can see:
- A PO went out at the wrong rate, because the person raising it pulled an old quote or remembered the number wrong.
- The vendor billed more than the agreed quote and nobody compared the invoice line by line before paying.
- A delivery slipped and the site sat idle, so labour costs ran while nothing progressed.
- The same item got ordered twice because two people were procuring from two different lists.
None of these are exotic. They're the everyday texture of running procurement in your head, and they're exactly the same failure mode I describe in the true cost of running a studio on five tools.
Why it happens in Indian studios specifically
Indian procurement has a texture that global software doesn't model well. A lot of buying is from local vendors on informal terms, rates move, and relationships matter more than portals. You call the carpenter, you WhatsApp the tile supplier, you get a rate over a phone call that never becomes a document. That flexibility is genuinely useful, it's how things get done fast, but it means there's often no clean record of what was agreed, which is precisely the condition a leak needs to survive.
The second reason is that procurement usually isn't tied to the approved design. The client signed off a spec, but the person placing orders is working from a separate list, so when a spec changes late, the order doesn't always change with it. Now you've procured something the client no longer wants, or the wrong quantity, and that mismatch is a loss. If procurement, specs and approvals lived in the same place, the order would reflect what was actually signed off, which is the whole argument I make in why one connected system beats five disconnected tools.
Where the margin goes on a typical project
Those numbers are illustrative, not a survey, but the shape is real, rate drift and delivery slippage are usually the two biggest holes, and both are invisible until you tie the order to the quote and track it to delivery.
Fix one: raise every PO from the approved quote, not from memory
The cleanest way to kill rate drift is to make the purchase order inherit its numbers from the quote the client already approved. When the PO is generated from the approved spec, the rate on the order is the rate you costed, not a number someone half-remembered. You stop the leak at the source, because there's no manual re-keying step for an error to sneak into.
This is also where procurement and revisions connect. If a change came in after approval and re-priced the quote, the PO should reflect the new number, which is why keeping the whole chain connected matters so much, something I cover from the billing side in how to stop losing money on revisions.
Fix two: compare, then commit, before the PO goes out
For anything meaningful, get two or three vendor rates and compare them in one view before you commit. This sounds obvious, and yet most studios skip it under time pressure and just go with the vendor they always use. A structured compare step, request, compare, then raise the PO, routinely saves a few percent, and a few percent on procurement is often the difference between a good project and a break-even one. I walk through the full sequence in how to run procurement from PO to delivery without chaos.
Fix three: track delivery against the PO, with someone accountable
A PO isn't done when it's sent, it's done when the goods arrive, are checked, and match what was ordered. The leak that hides here is the slipped delivery nobody was tracking, so the site waited and the labour meter kept running. Give every PO a delivery status and an owner, so an overdue order surfaces on its own instead of being remembered at the site meeting after the damage is done.
| Procurement stage | The leak if it's manual | The fix |
|---|---|---|
| Raise PO | Wrong or old rate keyed in | Generate from the approved quote |
| Select vendor | Default vendor, no compare | Request and compare two or three rates |
| Delivery | Slips unnoticed, site idles | Status and owner on every PO |
| Vendor invoice | Overbill paid without check | Match invoice to PO line by line |
Key takeaways
- Procurement leaks are the gap between costed and paid, multiplied across every line
- Rate drift and delivery slippage are usually the two biggest holes
- Raising the PO from the approved quote kills the biggest source of drift
- Tracking delivery with an owner stops the silent site-idle loss
What closing the leak looks like in one workspace
In Designa, procurement isn't a separate island. You spec the project room by room, the client approves the specs in the branded portal, and the purchase order carries the approved rates through, so the PO reflects what was actually signed off. You request and compare vendor rates, raise the PO, and track it to delivery in the same place, and when the vendor invoice comes in you're checking it against a real document, not a memory. Because it's all one connected workspace, the leaks that thrive in the gaps between tools simply have fewer gaps to hide in.
This applies whether you run an interior design studio buying furniture and finishes, or an architecture practice registered with the Council of Architecture coordinating material procurement across a build. Members of the Institute of Indian Interior Designers deal with exactly this vendor-rate-and-delivery problem on every project, and it's worth getting systematic about it. If you're evaluating tools for this, the best software for interior designers in India guide is a good place to start.
Frequently asked questions
What is a procurement leak in an interior design project?
It's the money lost between what you costed and what you actually paid, from rate drift on purchase orders, uncaught vendor overbilling, duplicate orders, and delivery slips that leave the site idle.
How do I stop vendors from billing more than the quote?
Match every vendor invoice against the purchase order line by line before paying, and generate the PO from the approved quote so the agreed rate is on the document from the start.
Should I compare vendor rates for every purchase?
For anything meaningful, yes. A quick request-and-compare step before raising the PO routinely saves a few percent, which on procurement is often your whole margin difference.
Does Designa track purchase orders to delivery?
Yes. You raise the PO from the approved quote, compare vendor rates, and track each order to delivery with an owner, all in the same workspace as your specs and approvals.
You don't need a procurement department to stop these leaks, you need the order tied to the approved design, a compare step before you commit, and a delivery status someone actually owns. If you want to see how the PO-to-delivery chain feels when it's connected, click through a real setup at demo.designa.work, and when you're ready to run procurement without the quiet bleed, the founding offer is one flat price for your whole studio, billed in rupees, with unlimited free client logins at go.designa.work.