CRM adoption failure from context switching
Rejected a web-portal-first design. Every feature was evaluated against one question: does this require leaving WhatsApp? The CRM lives where attention already is.
← Back to Work
7UNIT / CASE STUDY 002
WhatsApp-native sales CRM forteams that close inside conversations.
UAE sales teams were losing deals in the gap between WhatsApp and their CRM. We owned the product that closed that gap — pipeline and follow-up inside the conversation itself.
THE SITUATION
UAE sales teams were managing their entire client relationship inside WhatsApp — but their CRM was a separate tool that required manual data entry after every conversation. Deals were falling through the gap between where conversations happened and where data lived. Pipeline visibility was zero unless the salesperson manually updated the CRM after every message.
THE STAKES
Every silent deal was revenue walking out. Without a system that lived where the conversation already was, follow-ups depended on memory, pipeline reviews were fiction, and stalled opportunities stayed stalled until a competitor answered first.
WHAT WE OWNED
7Unit owned product architecture and delivery end to end: WhatsApp as the primary interface, pipeline state, AI-triggered follow-up, lead qualification, team assignment, and session memory across conversations — shipped as a production CRM surface, not a notification layer bolted onto a web portal.
Honest boundary
We did not own the client's sales process design, pricing strategy, or day-to-day deal negotiation. The system surfaces next actions and recovers silence — humans still close.
WHAT WE BUILT
A CRM system that operates entirely within WhatsApp. Pipeline tracking, AI-triggered follow-up automation, lead qualification, and team assignment — all without leaving the conversation. The system reads conversation context, maintains deal state, and surfaces the next action without requiring the salesperson to touch a separate tool.
RISK REDUCED
Stalled deals dying in silence
Silence detection with AI-generated, context-aware follow-ups — not template blasts — so inactive deals get a personalised nudge before they go cold.
Lost conversation context across weeks
Session memory preserves deal stage, last touchpoint, and next suggested action so salespeople never re-read entire threads to continue a deal.
ARCHITECTURE DECISIONS
WhatsApp as the primary interface
The temptation was to build a web portal with WhatsApp as a notification channel. We rejected this. The product had to live inside WhatsApp itself — because that is where the salesperson's attention already is.
Rationale: UAE sales teams do not switch tools mid-conversation. If the CRM requires a context switch, it will not be used.
Trade-off accepted: WhatsApp API limitations constrain some UI patterns — accepted in exchange for zero context-switching for the end user.
AI-triggered follow-up
Silence detection with configurable threshold. When a deal has been inactive for N days, the system sends a personalised follow-up based on the last conversation thread.
Rationale: Generic follow-up templates have low response rates. Context-aware messages perform significantly better.
Trade-off accepted: Slightly higher per-message cost from AI generation in exchange for meaningfully higher response rates.
Session memory across conversations
Conversation context preserved across sessions so a deal can resume after weeks without forcing a full history re-read.
Rationale: Deals in UAE often span weeks or months. Lost context forces wasted senior time before the next real conversation.
Trade-off accepted: Higher storage requirements for conversation state in exchange for seamless continuity across sessions.
OUTCOMES
Outcomes
In-chat
Pipeline & follow-up
Deal state and next action live in WhatsApp — not in a portal updated after the fact.
Nudged
Silence recovery path
Inactive threads get context-aware follow-up instead of waiting on human memory.
Native
WhatsApp as the CRM
Designed so salespeople do not leave the conversation to keep the pipeline honest.
STACK
WhatsApp Business APIFastAPIPostgreSQLClaude APIReact
IF THIS SOUNDS LIKE YOUR PROBLEM
If your sales team already lives in WhatsApp — and your CRM is a second system they update after the fact — you are losing deals in the gap. We build the system that closes inside the conversation.
UAE / GCC sales-led SMBs and WhatsApp-native operators who need pipeline truth without forcing a portal.
CONTINUE EXPLORING