Most firms track sales in one long list: an enquiry, a quote and a live site all sitting in the same row. A proper CRM for interior designers refuses that shortcut. It keeps the lead, the deal and the project as three distinct records, linked but never merged, so negotiation history, win-rate visibility and clean conversion all survive contact with a busy pipeline.
The one-blob problem
When everything lives in a single record, the record cannot tell you what stage you are actually at. Is this a cold enquiry, a quote you are chasing, or a project already on site? The same row is asked to mean all three at different times, so it ends up meaning nothing precise. Reporting becomes a shrug. Your win rate is unmeasurable because you cannot separate "enquiries" from "opportunities we quoted." Old rates cling to a client who came back a year later for a completely different flat. And the story of how a job was negotiated, the discounts, the site visits, the who-said-yes, gets overwritten the moment the record moves on to execution.
Interior work makes this worse than most trades. One client can be a lead this month, a signed deal next quarter, and a repeat customer with three separate projects two years later. Squash that into one blob and you lose the plot. This is the core reason a real CRM beats moving pipeline around in spreadsheets: a sheet has one shape per row, but your sales reality has three.
What a CRM for interior designers keeps separate
Panzo models the pipeline as three first-class objects, each with a job the others should not do.
| Record | What it is | The question it answers |
|---|---|---|
| Lead | An enquiry you are still qualifying | Is this worth pursuing, and what is the next move? |
| Deal | A quoted opportunity with commercials and approvals | Will this close, at what value, and who owns it? |
| Project | Signed, funded work in execution | Are we delivering it on scope, time and margin? |
The point is not bureaucracy, it is that each transition is a real event worth capturing. A lead becomes a deal when you decide to quote. A deal becomes a project when it is won and funded. Because the objects are distinct, each transition is clean, deliberate and recorded, rather than a silent edit to a field. And because they are linked to a single customer record, nothing is orphaned: the customer detail page tabs through their contacts, deals and projects, so a repeat client on a new job never accidentally inherits old pricing.
A lead, a deal and a project are three different questions. When one record tries to answer all three, it answers none of them well.
How leads work (and one honest caveat)
A lead in Panzo carries the fields an Indian sales team actually uses: secondary phone, city, project location, work-start timeline, language and enquiry count. Open one and the header offers Call, WhatsApp and Email in a single tap, a follow-up date that turns amber when due and red when overdue, and stage-aware next actions that tell you whether to call, book a site visit or convert. WhatsApp is a first-class channel here, which is why we treat it as core rather than a bolt-on; see how WhatsApp fits an interior business for the wider picture.
Note
Leads are entered manually
That honesty matters more than a flashy integration checkbox. What you get instead is a disciplined pipeline board where every enquiry has an owner, a follow-up and a next action, so nothing sits cold. When it is time, one click converts the lead into a deal and hands presales over to sales without retyping a thing.
Deals: where negotiation history is protected
A deal is the record that protects your commercials. It holds the requirement and the money in one place, project location, service, area in sqft, probability and balance, then moves through your own stages. This is the object that a good CRM for interior designers must keep separate, because it is where negotiation actually happens and where the audit trail earns its keep.
Quotations attach to the deal
Every quote and its BOQ hangs off the deal, with one marked as the baseline. Change orders ride alongside as sub-orders, so the commercial story stays in one thread instead of scattering across files.Discounts route for approval
A discount above your set limit stops for approval before a quote can go out. The record then shows who approved the exception and when, so a thin margin never leaves the building unchecked.Winning provisions the money
When a deal is won, the contracted value drops into payment milestones, so collections start from a real number rather than a guess. Ownership stays with sales roles, so revenue always has a name against it.
None of this survives if the deal is not its own record. Merge it into the project the moment work starts and you lose the discount trail, the version history and the reason the price is what it is. Keep it distinct and you can always answer, months later, exactly how the job was priced and who signed off.
Projects: clean conversion, not a reset
A project is signed, funded work, and it should begin from the deal, not from a blank form. Because the deal carried the scope, the baseline quote and the milestones, conversion into a project is a handover, not a re-entry. Execution, procurement, finance and handover then run against that project without ever touching the sales history behind it. The negotiation stays frozen on the deal; the delivery moves on the project. That separation is what lets you compare quoted margin against delivered margin honestly, because the two live in two records that agree on where they came from.
Why this gives you real win-rate visibility
Win rate only means something when the denominator is clean. If leads, deals and projects are one blob, you are dividing wins by a mixed pile of cold enquiries and running sites, and the number is fiction. With deals as their own object, you measure conversion on deals, and meetings and activities attribute back to the deal they moved. A qualification call logged against a lead still counts toward the deal that lead becomes, so the sales dashboard can report meetings-per-win without double-counting or losing the early touches.
The three-object pipeline is one piece of how the whole system fits together. See the full sales stack on the features page, how the modules connect across the Panzo product, and why owners in particular gain from one linked thread on the owners solution page. If you are still weighing tools, the interior design software guide for India puts the CRM in context with the rest.
Key takeaways
- Keep the lead, the deal and the project as three distinct records: each answers a different question and merging them loses all three answers.
- Leads are entered manually in Panzo. There is no Justdial or IndiaMART auto-ingestion, and Meta campaign fields are filled in by hand.
- Deals protect negotiation history: attached quotations, discount approvals and won-deal milestones only survive if the deal is its own object.
- Conversion is a clean handover, not a reset. A project starts from the deal, so nothing is retyped and old pricing cannot leak in.
- Distinct deals give you an honest win-rate denominator, with meetings and activities attributing back to the deal they moved.
Frequently asked questions
Why should a CRM for interior designers keep leads, deals and projects separate?
Does Panzo automatically pull leads from Justdial or IndiaMART?
What happens to the lead's history when it converts to a deal?
How does the three-object model keep my win-rate numbers honest?
Written by the Panzo Team · Published 28 Aug 2026
Back to all postsMore from the blog
Choosing interior design software: a buyer's checklist for India
A vendor-neutral checklist to judge any interior or fit-out platform before you commit your studio to it.
The quote revision trap: what your client actually approved
Why version history and a clear approval trail prevent the most expensive disputes in an interior project.
How to price an interior project so you actually keep the margin
Where interior margin quietly leaks, and how a rate library and a live budget stop it.