Building a Sales Pipeline Inside WhatsApp
Informal WhatsApp threads became a structured sales pipeline for a Kigali service business. No CRM, no new tools.
Project Details
Operations Consultant
A service business in Kigali ran all customer communication through WhatsApp Business. Multiple numbers, multiple team members, threads living on individual phones. The owner sensed deals were slipping but could not tell where. Someone would ask for a quote, get one, and never be followed up. The person who received the inquiry might not be the one who sent the quote. When a client came back, no one could reconstruct what had been discussed. This is common for businesses of this size in Kigali. WhatsApp is not just a preference, it is the operational layer. Migrating to a CRM was not a serious option. The owner knew this, and I agreed.
Make sure that a customer who expressed interest had a single person responsible for them, a clear next step, and a record somewhere that the owner could check.
The tool had to be WhatsApp. The tracking system had to be something the team could see and update without training on new software. No additional headcount. Any process that added decision-making overhead would get abandoned within two weeks.
Execution
I sat with the owner for about an hour and mapped every kind of inquiry that came in. Not to categorize neatly, but to understand the shape of their customer conversations: what information arrived first, what the business needed to know before quoting, how long quotes took, and what caused deals to go quiet. From that, I drafted six pipeline stages: new inquiry, qualified, quote sent, awaiting decision, closed-won, closed-lost.
The ownership rule was the most important structural decision. Every thread belongs to one person from first response until the deal closes or dies. Handoffs require one message in the team group: "I am handing [client] to [name]. Last status: [one sentence]." Without it, the handoff has not happened.
The tracking log was a single Google Sheets tab. One row per active inquiry: client name, stage, owner, last contact date, next follow-up date. No formulas, no color coding. I wanted the team to update it on a phone in under thirty seconds.
The message templates were starting points, not scripts. I wrote three: initial acknowledgment, quote delivery, and quiet-thread follow-up. Then I ran a half-day session structured around one question: "If you had to hand this to a colleague tomorrow with no conversation, what would they need to know?"
Outcomes
Within a few weeks, inquiries stopped disappearing. The ownership rule made it clear whose responsibility it was to follow up. The log made gaps visible: if a thread sat in "quote sent" for eight days with no follow-up date, the owner could see it.
Handoffs started happening correctly. The team used the format because it was easier than fielding follow-up questions from a colleague with no context. The owner stopped asking for deal status updates. The sheet answered that question.
I can look at how a small team actually works and build process around that reality. The instinct to observe first, then intervene minimally and precisely, tends to produce things people actually use.