How to Build a Sales Pipeline in a CRM (Step-by-Step for SMEs)

A sales pipeline is only useful if it reflects how your customers really buy. Too many SMEs copy a template with ten stages from a software tutorial, then abandon it after a month because nobody knows when to move a lead.

This guide is for owners and sales managers setting up a pipeline in a CRM for the first time, or rescuing one that has gone stale. It uses chat.or.ke as the example, but the steps work in any CRM.

What is a sales pipeline in a CRM?

A sales pipeline is the set of stages a lead passes through from first contact to a paid sale, shown in your CRM so you can see where every deal stands. Each lead sits in exactly one stage at a time, has an owner, and moves forward (or out) as the customer takes action.

The point is visibility. At a glance, you should see how many enquiries are waiting for a quote, which deals are close to closing and which have not moved in a fortnight. If you are still deciding whether you need a CRM at all, read CRM vs Excel for tracking leads first.

Before you start

You need a few things in place before you build anything. Gather these first:

• A CRM with pipeline stages. In the chat.or.ke CRM, you define the stages, assign owners and see which leads are stuck.
• A list of recent sales. Ten to twenty deals from the last few months, won and lost, to see how buying actually happens.
• Your existing leads. A spreadsheet or phone export of open enquiries, saved as CSV.
• The people who sell. Names of everyone who will own leads, with access to the CRM.
• One hour with your sales team. Stages agreed together get used; stages imposed from above get ignored.

Step 1: Map how your customers actually buy

Start from real deals, not theory. Take your list of recent sales and, for each one, write down what the customer did between the first message and payment.

A Nairobi furniture maker might find the same pattern every time: the customer sends a photo of a design on WhatsApp, asks for a price, gets a quote, visits the workshop or asks for fabric samples, pays a deposit by M-Pesa, then pays the balance on delivery. That sequence is your pipeline.

Look for the points where deals usually stall or die. Those are the stages you most need to see.

Step 2: Turn milestones into five to seven stages

Each stage should be a customer milestone with a clear exit rule. Name stages after something verifiable that happened, so two people looking at the same lead would put it in the same place.

Here is how pipelines might look for three different Kenyan businesses:

Write the exit rule for each stage in one line. For example: "Move to Quote sent only when the quote, with price and delivery date, has been sent in the chat." Share the rules with the team.

Step 3: Set up the stages in your CRM

Now create the stages in your CRM in the order you agreed. Keep the names short so they fit on screen, and avoid vague ones like "In progress" or "Follow up", which describe your activity rather than the customer's position.

Also decide what extra information each lead needs. In chat.or.ke you can add custom fields, such as budget, location or product of interest, and tags such as "Westlands branch" or "Corporate". Only add fields someone will actually fill in; three useful fields beat twelve empty ones.

Step 4: Assign an owner to every lead

Every open lead should belong to one named person. Shared ownership feels collaborative but in practice means nobody follows up.

Decide how leads get assigned. Common approaches:

• By product or branch: office furniture to one person, home furniture to another.
• By channel or source: leads from a particular Click-to-WhatsApp ad go to the person running that campaign.
• First reply owns it: whoever answers the first message keeps the lead.

Because the shared WhatsApp inbox lets the whole team reply from one number, the owner can hand a lead to a colleague with an internal note, and the full chat history goes with it.

Step 5: Bring in your existing leads

Load the open leads you already have so the pipeline starts complete. Export your spreadsheet as CSV with one column for the stage, import it, and check the preview before saving. Phone numbers are tidied into +254 format during import in chat.or.ke.

New enquiries then build up on their own, because every new WhatsApp, email or SMS conversation creates or updates a contact. For detailed clean-up tips, see how to import and segment contacts.

Step 6: Capture leads automatically at the top

The top of the pipeline should fill itself. When a customer messages you, they should arrive as a contact with as much context as possible, without anyone typing.

Automation flows help here. A short flow can ask a new enquirer two or three qualifying questions, such as budget, location and timeline, save the answers, and then hand over to a person. A property agency in Kilimani, for example, can ask for budget and move-in month before an agent steps in, so the agent starts with a qualified lead.

Step 7: Review the pipeline every week

A weekly review keeps the pipeline honest. Spend 20 minutes with the sales team, stage by stage, and ask three questions of every lead older than a week:

1. What is the next step, and who owns it?
2. When did we last hear from the customer?
3. Is this still real, or should it be marked lost?

Close leads that are clearly dead and record why: price, timing, chose a competitor, never replied. After a few months, those reasons tell you more about your sales than any dashboard.

Use the review to agree follow-ups. Our guide on how to follow up leads on WhatsApp covers timing, the 24-hour window and templates.

What mistakes make sales pipelines fail?

Most failed pipelines die from the same few habits. Watch for these:

• Too many stages. If moving a lead needs a debate, you have too many.
• Stages nobody updates. If leads only move during the weekly meeting, the stages are too fine-grained or the team was not involved in designing them.
• No lost stage. Pipelines without a "lost" outcome fill with ghosts and give false confidence.
• Tracking activity, not outcomes. "Called twice" is a note, not a stage.
• Leaving the pipeline outside the chat. If agents must switch apps to update a lead, they will not. Keep the pipeline where the conversations are.