From Delayed Enquiries to Real-Time Lead Management
One system where every lead is captured, routed, owned, contacted, followed up and closed.
The Outcome
Inquiry2Leads replaced a fragmented workflow of separate databases, email, WhatsApp and manual handoffs with a single system where every lead could be captured, routed, owned, contacted, followed up and closed. The agency was running paid campaigns for 10+ clients and managing more than ₹1 lakh in monthly client ad spend, so a delay in getting an enquiry to the right person directly affected how quickly the team could act.
| Metric | Before | After |
|---|---|---|
| Enquiry delivery | 2 days | Real time |
| First contact | Around 2 days | 1–2 hours |
| Conversion rate | 40% | 60% |
| Admin coordination | 2 hours/day | 20 min/day |
| Commercial outcome | — | 2 new clients |
The Problem
Before the product, an enquiry moved through separate campaign databases, manual checking, messages and forwarding before reaching the person expected to call it.
The failure was not simply "poor lead management." It was lead latency + invisible ownership + missing follow-up.
Who owns this lead? When did it arrive? Has anyone contacted it? What happens next?
The design opportunity was therefore not "build a CRM." It was to create a dependable operational path from enquiry → ownership → first contact → follow-up → close.
What I Found
I interviewed 3 people during discovery: 2 agency staff and 1 client. The strongest signal was about speed and visibility:
By the time I get the lead, they've already talked to someone else.
The Client Employee was a key role in the product brief, but was not directly interviewed during discovery. Their jobs were therefore derived from the brief and client/team context rather than direct employee interviews.
That distinction stayed explicit throughout the design.
From Research to Product Direction
| Step | Lead speed | Admin overhead |
|---|---|---|
| Observed | Enquiries arrived late and could disappear between handoffs. | Admin work was spread across databases, messages and manual coordination. |
| Insight | A lead loses value when the team cannot act while the prospect is still interested. | The overhead was repeatedly finding, checking and passing information between people. |
| Job | Know immediately when an enquiry arrives, who owns it and what happens next. | Manage clients, assignments and activity from one place. |
| Design | Real-time routing, notifications, waiting-time signals, first-contact logging and follow-up tracking. | Centralized client/lead management, role-specific dashboards and activity history. |
UX Thinking
Jobs to Be Done
I mapped each role from When → I want to → So I can → Where, connecting the job directly to the product surface.
Information architecture. One system of record, but three role-specific experiences:
Lead lifecycle
The lifecycle made ownership, next action and closure explicit rather than leaving progress in notes or messages.
Key Product Decisions
Decision → Design → Impact
Selected UI
Admin
The Admin surface answers: Is the business healthy? Which clients need attention? Where are leads coming from?
Client
The Client surface answers: Which enquiries are waiting? Who owns them? Which follow-ups need intervention?
Employee
The Employee surface is action-first: Call Next → follow-up → conversation → close.
Lead detail
One screen connects status, owner, first contact, next follow-up, conversation history and activity.
V2 Roadmap
The next planned iteration was not a rewrite of the core product. It focused on two extensions:
The Result
Inquiry2Leads was more than a dashboard redesign. It turned a fragile handoff process into a shared operational system.
Interested in the long version?
This is the short read. The full case study goes deeper into the discovery interviews, the jobs to be done for each role, the information architecture, the lead lifecycle and the trade-offs behind each decision. Email me and I'll send it over.