The sales process that enforces itself.
A growing interior design company. A defined way of selling. A master spreadsheet, WhatsApp messages and employee memory holding it together. We replaced the spreadsheet with a system that makes the process unavoidable.
Outcome
The client
The process existed. The system did not enforce it.
A growing interior design and home-renovation company serving residential customers across India. The business ran a high-consideration sales process involving multiple consultations, qualification meetings, floor plans, quotations, proposal presentations, negotiations and project handovers.
The company already had a defined way of selling. But the process was not embedded in a system. It lived partly in a master spreadsheet, partly in individual employees' devices and partly in people's understanding of what should happen next. As the company grew, that became difficult to control.
Industry
Interior design & home renovation
Market
India
Sales roles
Designer, CRE, Business Lead, Branch Head
Lead sources
Meta, Google, forms, referrals
Pipeline stages
7 named stages
Existing tools
Google Sheets, WhatsApp, email
Client name
Withheld
Engagement
Custom CRM build
The problem
Six ways the same lead could go wrong.
Every lead in the business lived in one Google Sheets master tracker. The sheet could show that a lead existed. It could not reliably show whether the lead had been contacted, what happened during the last conversation, how long it had remained at its current stage, whether a discount had been authorised, or who was responsible for the next action.
Operational symptoms
Leads could move forward without being ready
A lead could be marked qualified without a confirmed budget. A proposal could begin without the floor plan. A customer could enter onboarding without a final quotation. The process existed as operating knowledge, not as enforcement.
Handoffs were soft
When a lead changed owner, the new employee had to search the spreadsheet, read WhatsApp messages, ask a colleague, call the customer again and reconstruct what had already been discussed. Some leads fell between roles entirely.
Follow-ups happened when someone remembered
No systematic service-level tracking existed for first contact, qualification, proposal preparation or presentation. Managers discovered problems only after reviewing the spreadsheet. There was no consistent way to distinguish an active opportunity from a forgotten one.
Discounts had no controlled approval path
Designers could discuss discounts with customers without a structured hierarchy. The business could not determine who had requested a discount, why, what value it was calculated against, or whether the employee had authority to approve it.
Customer communication stayed on personal devices
WhatsApp conversations were held through individual accounts. When a lead changed owner, the conversation history did not move with it. The lead record and the actual relationship were two different things.
Marketing produced enquiries without revenue attribution
Campaign parameters were not consistently captured and connected to later sales activity. The business could see spend and enquiry volume. It could not connect a campaign to qualified leads, onboarded customers or average project value.
The diagnosis
Replacing the spreadsheet was not the answer
The initial requirement appeared to be straightforward: replace the spreadsheet with a CRM. But replacing the sheet with a standard CRM would only have created a cleaner database. It would not have corrected the behaviour causing lead leakage.
Pressense mapped the company's sales journey from the initial enquiry through project handover. The diagnosis examined what information entered at every stage, which employee owned each step, what the next employee needed, what had to be completed before a lead could progress, and what the company needed to measure.
The root cause: soft handoffs
Employees were allowed to progress leads without completing the work or recording the information required by the next stage. The business did not need another system that suggested good practice. It needed hard operational gates.
The pipeline required enforcement, not guidance
Seven named stages existed as operating knowledge. The CRM had to enforce the company's actual process rather than expect every employee to remember it.
SLA compliance was invisible
Management could not reliably determine whether a first-contact or follow-up deadline had been missed. There was no consistent way to distinguish an active opportunity from a forgotten one.
Discounting had no commercial control
The financial effect of discounting was visible only after the commercial decision had already been made. Every discount request needed a structured authority hierarchy enforced by the system.
Attribution ended at the enquiry
Campaign parameters were not connected to later sales activity. The company needed to measure which campaigns produced onboarded customers, not just enquiries.
What Pressense built
A custom sales operating system
The new platform unified pipeline management, qualification, tasks, meetings, communications, quotations, discount approvals, campaign attribution and reporting. It was also integrated with the company's existing quotation builder. Both applications used the company's visual identity, creating the experience of one connected internal product.
Gated sales pipeline
Seven named stages. Six mandatory gates. A lead cannot progress until the system confirms the required information has been entered. Forward jumps accumulate all intervening requirements.
Automated SLA engine
Four service-level rules embedded into the workflow. Every lead checked hourly. Breaches surface to the Business Lead and all Branch Heads immediately. Management can see every outstanding breach in real time.
Controlled discount approvals
Four authority tiers. Server-side percentage validation. Every request records the requester, amount, reason, forwarding history, reviewer, decision and comments. No request is invisible.
Nightly performance scoring
Conversion rates, average project values and SLA compliance recalculated for every active Designer and CRE at 2:00 a.m. Performance discussions can be grounded in consistent data.
Fourteen management reports
Lead summary, pipeline, conversion funnel, lead ageing, monthly trend, timeline performance, sales cycle, meeting performance, designer performance, business lead performance, source performance, campaign performance, offer performance and inactive leads.
Communication connected to the lead
Eight pre-built email templates. SMS reminders and feedback links. WhatsApp conversations connected to the appropriate lead record. One continuous account of every call, meeting, message and decision.
Enforced meetings and tasks
Every recorded call requires an outcome, a follow-up task and a due date. A completed meeting cannot close without meeting notes. A task cannot be marked complete unless activity has occurred on the lead after it was created.
Campaign attribution
Source, medium, campaign, term and content captured at intake and attached to the lead as it progresses. The company can compare campaign performance using onboarding rates and project values, not enquiry volume.
Intelligent lead assignment
Round-robin distribution for even allocation. Performance-tier assignment for directing leads to higher-converting employees under approved business rules.
Intent scoring
Every lead receives a score from one to five based on budget, possession timeline, call activity and meeting status. Teams can prioritise without replacing human qualification judgement.
SLA enforcement
Every lead checked every hour
When a lead crossed a threshold, it was marked as breached, the assigned Business Lead was notified, every Branch Head received an in-app alert, the breach appeared on the management dashboard, and the lead remained visible until action was taken.
| Sales event | Required time |
|---|---|
| First contact after lead creation | 24 hours |
| Effective Lead to MQL | 5 days |
| MQL to DQL | 5 days |
| Proposal Ready to Proposal Presented | 2 days |
| Verified outcome | 100% detectable within 1 hr |
What changed
The first gains were structural and verifiable
- 1Leads could move forward with missing information
- 2Managers could not reliably identify missed SLAs
- 3Discounts discussed without an approval history
- 4Performance compared manually by managers
- 5Communications lived on personal devices
- 6Meeting notes were inconsistent or missing
- 7Marketing measured mainly by enquiry volume
- 8Inactive leads disappeared without explanation
- 9Assignment depended on manual decisions
- 10Managers reconciled spreadsheet data manually
- 1Six enforced gates prevent incomplete progression
- 2Every breach is detected within one hourly check
- 3Every system-based request has a complete audit trail
- 4Metrics recalculate automatically every night
- 5Lead-level email, SMS and WhatsApp history
- 6Meetings cannot close without Minutes of Meeting
- 7Campaign parameters remain attached through the funnel
- 8Feedback and inactivation reasons are captured
- 9Round-robin and performance-tier allocation
- 1014 live, exportable management reports
Because the system had only recently entered production, conversion or revenue uplift data had not yet accumulated. The first gains were structural and verified.
The outcome
A sales process that employees follow and management can measure.
15–20%
Benchmark-supported sales productivity improvement opportunity, to be measured over 90 days
₹24k+
Annual per-user SaaS licence cost avoided by replacing the evaluated industry CRM
90 days
Measurement plan for converting structural gains into a fully quantified outcome
Independent CRM and marketing-automation research supports a 14.5 to 20% improvement in sales-team productivity where systems are properly adopted. For this business, that means administrative time per lead, leads managed per employee, follow-up time, report preparation and time spent seeking internal approvals.
The company did not merely receive a new CRM. Its sales method became a system that employees could consistently follow and management could finally measure. The clearest difference after launch was not a dashboard. It was the absence of ambiguity: every lead had an owner, a required next action and a visible status.
The bigger picture
Is your CRM recording the process, or enforcing it?
A generic CRM could have been configured to record much of this information. But the company needed deeper enforcement: mandatory transition gates, cumulative validation across stage jumps, discount ceilings by organisational role, server-side percentage validation, mandatory follow-up tasks after calls, activity requirements before task completion, required meeting notes and automated SLA escalation.
Pressense first diagnoses where information, accountability and revenue are being lost. We preserve the systems that already work and build the missing operational layer around the way the business actually runs. Your process should not depend on people remembering every step.
Is your sales process enforced or optional?
We diagnose where leads, accountability and revenue are being lost. Then we build the missing internal system around the way your business actually runs.
Start your diagnostic