Nested ranks the leads most likely to slip, explains every AI pick, and starts a 30-minute clock on every new enquiry.
About the project
Nested is a mobile CRM for real-estate Relationship Managers, who take every property enquiry from first call to booking. The
As the sole designer, I owned the product end to end. The brief: redesign the RM experience and build in intelligence, so the app guides the day instead of just recording it. This case study follows the four features that moved RMs off Excel and onto the app.
Nested is a stand-in name. The work is real; the client is under NDA, so every screen here was rebuilt from scratch.
The before-state
Eight disconnected tools orbiting one RM. Nothing talks to anything.
Every lead lived in pieces across all eight. So the RM became the integration.
The challenge
RMs didn't need more features. They needed answers to the same four questions, every morning, on a phone, between calls.
Before designing anything, I sat with RMs and watched them work. Their day ran across eight tools that didn't talk to each other, so every answer meant digging: incentive math in Excel, priorities on gut feel, lead history buried in WhatsApp. The app had to answer each question fast, on mobile, without making the RM dig.
“I spend my morning in five apps just to work out who to call. By the time I know, the lead has already spoken to someone else.”
“How am I doing today?”
No single view of the day. Targets, visits and follow-ups sat in different tools, so every morning started with digging.
“How much will I earn?”
Nobody knew until month-end. Incentive math lived in Excel, and RMs didn't trust the numbers until the paycheck arrived.
“Who do I call first?”
Based on gut feeling. No scoring, no prioritisation, nothing telling them where to focus.
“What happened with this lead?”
RMs scrolled back through WhatsApp, and there was no shared context when more than one RM spoke to the same lead.
Each question became a chapter of the redesign. Thumb-first and one question per screen became the ground rules for all four.
The UX work
The structure went through two real shapes before it answered the RM's four questions.
I shadowed five RMs, timed every switch between apps, and turned their day into an information architecture. The first version failed in testing, in a useful way. The second one became Nested.
-
Shadowed RMs through full shifts
Five RMs, two offices. Every switch between apps got a timestamp.
The tools weren't the problem. The missing structure between them was.
-
Grouped the app by data source
Leads from Sheets, chats from WhatsApp, incentives from Excel, visits from Calendar. One app, same four silos.
One lead ended up in three branches.
-
Tested it with RMs, mid-shift
A clickable prototype, real leads on the line. I watched where thumbs went and what got asked out loud.
Tabs broke live calls. Incentives were the first thing anyone looked for.
-
Regrouped by the question being asked
Each section answers one of the four questions from the challenge. A lead lives in one place, and everything else links to it.
Retest: every RM found their incentive in under ten seconds.
Two maps. One that matched how an RM actually thinks.
Artifacts recreated for this case study. Names and numbers changed.
The challenge
How might we create an intelligent product that would actively guide the RM's day and not just record it.
Nested guides the RM through the whole day.

04 · The solution: four features, one working day

The day, ranked for you.
The Daily Brief pins up to three actions to the top, and every card shows where the lead sits in the pipeline. Team Leads and RM Heads see the same data, with their own priorities on top.
Every lead, scored and in order.
Filters open on Today, New and Overdue across six pipeline stages, and every card can call, WhatsApp or navigate in one tap. Voice notes transcribe in the background.
Know what you'll earn, before payday.
One gauge for the month: red until 60% of the goal, amber once you're eligible, green at the goal. Co-tagged bookings count as half, and every booking shows Pending or Confirmed.
One place for every conversation.
WhatsApp, calls, email and notes from every RM on the lead, in one timeline. Read every thread; reply only on your own enquiry.
Design system
One system behind every screen.
Two type families, six colours, a temperature scale that reads without colour, and one rule for AI: always show why.
Hi Ananya, yes, the 20:80 plan applies on the 1 BHK at Greenfield Park.
Call Priya before 4:30 PM. She replies fastest in the late afternoon.
Why this?The AI layer
From signal to suggestion, in five layers.
Every AI moment in Nested follows the same rules, so RMs learn when to trust it and when to check.
The AI reads calls, WhatsApp, email and visits logged in the app. Anything said in person or on a personal phone isn't counted, and the app says so.
Leads get Hot, Warm or Cold from engagement signals, but only after two of them. Until then the lead shows Pending, not a guess.
The Daily Brief pins the three things most likely to slip. Each card is labelled as an AI suggestion, with its confidence.
“Why this?” opens the signals behind every pick, each marked Strong, Medium or Weak, and how many it used.
Summaries and drafts are labelled as AI, drafts are never sent on their own, and the RM can change any score in one tap.
Results
tools in an RM’s day
App. Now the day guides the RM.
Next steps
Where I'd take it next.
Nested v1 covers the RM's day. These are the two things I'd build after it.