WhatsApp Kanban Board: 2026 Sales Pipeline Guide

Why I built a WhatsApp Kanban board after watching 200 resellers fail

You open WhatsApp Web Monday morning. 47 unread chats. Three are hot leads from last week's ad. Eleven are people who said "let me think about it" and went silent. Six are existing customers asking renewal questions. The rest are noise. Sound familiar?

I'm Rakshit Soni, co-founder of Lion CRM at LotsOfCode Private Limited. I've spent four years watching small businesses, agencies, and whitelabel resellers try to run sales pipelines inside WhatsApp — most of them with nothing but stars, archive, and a notebook. Some made it work. Most didn't. The ones who made it work all did the same thing eventually: they built a WhatsApp Kanban board. The ones who failed kept trying to scale the chat list itself.

This is the post I wish someone had handed me on day one. What a WhatsApp Kanban board actually is. The four stages that cover 90% of real businesses. The Lion CRM architecture choice — Chrome extension on top of WhatsApp Web, 100% local data, no Meta API, no BSP middleman — and why that matters when your pipeline lives in WhatsApp. The pitfalls I see on almost every new board. And a 10-minute setup so you can stop reading and start dragging.

Honestly? If you only take one thing from this guide, take this: the chat list is for talking. The Kanban board is for selling. They're not the same tool. Let's get into it.

What a WhatsApp Kanban board actually is

A WhatsApp Kanban board is a vertical-column view of every contact in your WhatsApp pipeline, where each column is a stage of your sales process and each card is one contact. You drag a card from "Lead" to "Prospect" when a chat heats up. You drag from "Prospect" to "Customer" when they pay. You drag back to "Lead" if they ghost you. The board sits next to your WhatsApp Web chat list, so you never leave the place where the conversation is actually happening.

The Kanban method itself isn't new — it came out of Toyota's manufacturing line in the 1940s and got adopted by software teams in the 2000s. Pipeline CRM has a clean explainer on why Kanban maps so well to sales pipelines — visual progress, stage caps, bottleneck detection. What's new in 2026 is putting that board inside WhatsApp itself, instead of in a separate dashboard you have to open in another tab and copy-paste between.

This matters because of how WhatsApp sellers actually work. You're in a chat. The reply lands. You answer. You decide whether the lead just moved forward, stayed flat, or fell off. With a separate CRM tab, that decision is a context switch — Cmd-Tab, find the contact, update the field, Cmd-Tab back. Most people skip it. With a Kanban board pinned next to the chat list, the decision is one drag. The board stays in sync because there's no second tool.

Don't confuse a Kanban board with WhatsApp's built-in labels (in the Business app) or with a tag list. Labels and tags are passive — they describe a contact ("VIP", "Hyderabad", "interested-in-API"). A Kanban stage is active — it tells you what comes next. "Prospect" doesn't describe the contact; it describes the next action: "follow up with quote in 48 hours." That's the entire mindset shift. Tags answer "who is this?". Stages answer "what do I do next?"

Why Kanban beats lists, broadcast, and group chats

Most people running sales on WhatsApp use one of four mental models. Each one breaks at scale, and Kanban is what fixes the breakage. Let me walk through them.

The chat list as a to-do list. You scroll until you find the chat that needs a reply. Works fine at 5 chats. Falls apart at 50. By the time you have 200 active conversations, you can't tell which contact is one nudge away from buying versus one that hasn't replied in three weeks. The chat list sorts by recency, not by stage. Recency is useless for sales because the cold lead from last month who finally replies looks identical to the customer asking a renewal question.

Broadcast lists. Broadcasts are great for one-to-many announcements — sale, restock, event. They're useless for pipeline because every recipient gets the same message regardless of where they are in the funnel. You don't send a "buy now" pitch to someone who's already a customer, and you don't send a "thanks for your purchase" message to a cold lead. Broadcast assumes one stage. Real pipelines have at least four.

Group chats. Group chats turn into noise the moment more than ten people are in them. They're a community tool, not a sales tool. If your "leads" are sitting in a group chat with 45 other leads, none of them feel addressed and none of them convert.

Spreadsheets. A Google Sheet of "Name | Phone | Status | Last contact | Notes" is a real CRM, but it's not where the conversation lives. Every sale generates two updates: one in WhatsApp, one in the sheet. Half the time the second update doesn't happen, the sheet drifts out of date, and you stop trusting it. Three weeks later, you stop opening it.

The Kanban board fixes all four because it sits inside the chat tool. There's no second tab. There's no "and-also-update-the-sheet" step. You read the message, decide if the stage moved, and drag if it did. The board stays accurate because updating it is one motion, not a workflow.

Beyond that — and this is the founder POV from watching real teams — Kanban surfaces the right questions. "Why do I have 80 cards in Lead and only 4 in Prospect?" (Answer: your top-of-funnel works, your qualifier doesn't.) "Why has this card been in Prospect for 17 days?" (Answer: stale follow-up, send a nudge.) "Where do most cards die?" (Answer: the stage right before that, fix that stage.) The chat list cannot ask any of these questions. The board does, automatically, by being visual.

The four-stage default that works for most WhatsApp sellers

Lion CRM's Kanban Board ships with a four-stage default: Lead → Prospect → Customer → VIP. The product page describes it like this — "Visualize your customer journey. Drag-and-drop contacts through stages: Lead → Prospect → Customer → VIP." Four stages isn't accidental. After running this for hundreds of partner businesses, four is what fits almost every real WhatsApp seller. Here's what each stage means in chat-behaviour terms.

Lead — they replied at least once. They opened the conversation, asked a question, clicked an ad, or signed up for a list. They have not yet shown buying intent. The action you owe them: a qualifying question or a value-first reply within 24 hours. If a Lead doesn't move in 7 days, it's getting cold. If it doesn't move in 21 days, it's archived.

Prospect — they've shown intent. They asked about price, they asked about features, they asked when you can deliver, they asked for a demo. The action you owe them: a clear next step (quote, call slot, free trial link). Prospect is the stage where most pipelines leak, because the seller waits for the buyer to push and the buyer waits for the seller to push and nobody pushes. The Kanban board makes the leak visible — when 14 cards are in Prospect and none have moved in 5 days, you have a leak.

Customer — they paid. They're using the product. The action you owe them: onboarding nudges, success check-ins, and a path to the next stage. The biggest mistake here is treating Customer as a terminal stage. It isn't.

VIP — they paid more than once, they referred someone, they responded to your last upsell. The action you owe them: keep them happy, ask for a testimonial, and route them to a slower-cadence cycle. VIPs are who you go back to when you need case studies, when you launch a new feature, and when you need a referral.

Every stage in this default has an entry condition (what gets a card into the stage) and an exit condition (what moves it out). Stages without exit conditions are where pipelines die. If "Prospect" doesn't define what makes a Prospect a Customer, every Prospect just sits there forever and your board fills up like a bathtub with the drain plugged.

WhatsApp Kanban board inside the Chrome extension (Lion CRM)

Here's where the architecture matters. There are two ways to put a Kanban board on WhatsApp data, and they look almost identical from the outside but behave very differently from the inside.

Path A: Hosted SaaS dashboard with WhatsApp Business API. This is what Interakt, AiSensy, WATI, MyOperator, and other BSP (Business Solution Provider) tools do. You sign up for the platform, the platform plugs into the WhatsApp Cloud API on your behalf, your messages route through Meta's servers, and the Kanban view lives in their dashboard at app.theirbrand.com. Strengths: scales to thousands of agents, supports approved templates outside the 24-hour window, is the official Meta-blessed path. Trade-offs: per-message cost (₹0.08–₹1.40 each in India depending on conversation type), 1–3 weeks to set up Meta verification + template approval, your contact data lives on the BSP's servers, and you're pulled out of WhatsApp Web into a separate dashboard.

Path B: Chrome extension on top of WhatsApp Web. This is what Lion CRM does. You install the extension, open WhatsApp Web in your browser the way you always have, and the Kanban board appears inside that same tab. Your messages flow through your own WhatsApp Web session — the same one you'd use without any extension. Nothing routes through Meta's BSP servers because there is no Meta integration. Lion CRM is not a BSP, not on the WhatsApp Business API, not on the Cloud API, and has no Meta partnership. The architecture is intentionally different.

What that means for your Kanban board:

• 100% local data. Every card on your board, every stage definition, every contact tag, every note is stored on your device. There's no cloud database with your customer list in it. If you turn off the extension, your data stays on your laptop.
• Zero per-message cost. You're sending from your own number, so there's nothing to meter. A Kanban with 1,000 cards costs the same as a Kanban with 10 cards.
• No API approval needed. No Meta verification, no template review, no BSP onboarding. Install, open WhatsApp Web, drag.
• One-tab workflow. The Kanban panel sits next to the chat list inside WhatsApp Web. You never context-switch out of WhatsApp.
• Drag-and-drop directly on the contact. Pull a card from Lead to Prospect — that's it. The card carries the contact's chat history, tags, custom fields, and Smart Calendar follow-ups with it.

The trade-off is honest: this path is built for SMBs, agencies, coaching businesses, and whitelabel resellers running their pipeline through their own WhatsApp number. If you're a multi-agent helpdesk routing 50,000 inbound messages a day across a contact center, you want the API path. The good news is the architecture choice is yours, and most people running real WhatsApp sales pipelines fall into the first bucket. We covered the deeper trade-offs in WhatsApp CRM vs WhatsApp Business API: which to pick (2026).

Custom stages — when and how to deviate from the default

The four-stage default works for most. Some businesses genuinely need different stages because their sales motion is different. Here are three real customisations I've seen partners run successfully.

Real estate / property — Inquiry → Site Visit → Offer → Token Paid → Closed Won. Real estate sales motion has a hard milestone (the site visit) that the four-stage default obscures. Splitting it lets the agent see "I have 8 site visits booked this week" at a glance, which is the metric that matters for that vertical.

Coaching / online courses — Lead → Demo → Trial → Paying → Renewed. Coaching businesses live and die on the demo conversion. Making "Demo" its own stage forces the agent to track demo-show-up-rate, which is the leakiest part of the funnel. Adding "Renewed" as the terminal stage replaces VIP because for coaching, renewal is the loyalty metric.

D2C and e-commerce on WhatsApp — Cart Abandoned → Question Answered → Pay Link Sent → Paid → Repeat Buyer. E-com WhatsApp sellers don't have leads in the traditional sense; they have shoppers at varying levels of intent. Each stage is a recovery action.

The rule of thumb I give partners: 5 stages is the comfort ceiling, 6 is the absolute max, anything beyond is over-engineering. Hot take: more than 6 stages and you're managing the board, not the customers. The board exists to make decisions faster. When the board has so many stages that deciding what stage a card belongs in becomes its own decision, the tool is now slowing you down.

Stage names should be verbs or actions, not vibes. "Hot Lead" is a vibe — what does that mean to your team-mate when you're on holiday? "Quote Sent" is an action — anyone can read the card and know what comes next. The Kanban board's biggest superpower is that someone else can pick up your pipeline cold and make sensible moves. Vibe-named stages destroy that.

One more rule: every stage must have an exit condition that the board can see. If "Prospect" exits to "Customer" when payment lands, great — the agent drags when they confirm payment. If exit is "when it feels right" — the card never moves. Pipelines die in stages without exit conditions.

Integrations and automations — making the board do the work

A static Kanban board is already a 5x improvement over a chat list. An automated Kanban board is a 50x improvement, and it's what makes the difference between "I have a board" and "the board runs my pipeline." Lion CRM connects to four classes of automation, all running locally inside the extension, all without an API contract with Meta.

Stage-change → external system, via WebHooks. When a card moves from Prospect to Customer, push that event to a Google Sheet, a Zapier flow, or your accounting software. The most common pattern partners run: Customer-stage entry triggers an invoice generation in their billing tool. Powerful WebHooks support Zapier, HubSpot, Google Sheets, and any custom HTTPS endpoint. This is the integration that turns the Kanban board into a hub instead of a dead-end.

AI Integration — auto-tag incoming chats by intent. Lion CRM lets you connect your own OpenAI, Gemini, or DeepSeek API key. New incoming messages can be auto-classified as "buying intent / question / support / complaint" before you even read them, and you can wire stage-suggestions on top of that ("this Lead just said 'how much' — suggest moving to Prospect"). It's not magic — the model is doing what you'd do manually, faster. The win is reducing the decide-and-drag loop on hundreds of new chats per week. Our WhatsApp AI chatbot guide covers the full setup if you want to wire ChatGPT or DeepSeek into the extension end-to-end.

Smart Calendar — automatic follow-up cadence per stage. When a card moves into Prospect, set a 48-hour follow-up reminder automatically. When it moves into Customer, set a 14-day check-in. The Smart Calendar feature handles this without you remembering. The Kanban board provides the trigger; the calendar provides the nudge. Together they close the "I forgot to follow up" leak that kills more pipelines than anything else.

Backup & Restore. Local data is a feature, but it's also a single point of failure if you lose your laptop. Backup & Restore exports your entire Kanban (stages, cards, tags, history) so you can move to a new device, share with a team-mate, or restore after a re-install. It's the safety net that makes the local-data architecture viable for businesses that take this stuff seriously.

If you want to see the integrations stitched together in motion, the LotsOfCode YouTube channel has walkthroughs that go feature-by-feature. I'd rather show than tell on this one.

Five pitfalls I see on almost every new WhatsApp Kanban

After watching hundreds of partners and direct customers set up their first WhatsApp Kanban boards, the same five mistakes show up over and over. None of them are fatal — they're just the difference between a board that runs your business and a board you stop checking after two weeks.

Over-stage-ing. Someone reads about Kanban best practices, gets excited, and creates 9 stages on day one. Lead → Cold Lead → Warm Lead → Engaged → Qualified → Proposal Sent → Negotiation → Closed Won → Onboarded. Within a week they realise that "Engaged" and "Qualified" are basically the same thing and they're spending more time deciding which stage to move to than actually moving. Start with 4. Add a 5th only when the existing stages stop carrying enough information.

Stale cards without movement. A card in Prospect for 21 days is one of two things: a lead you forgot, or a lead that's gone cold and should be archived. Either way, it should not still be in Prospect. Set a rule — if a card hasn't moved in 14 days, it gets a force-decision: move forward, move backward, or archive. The board exists to surface this decision; you have to actually make it.

Ghost contacts. Numbers that you added to the board but never replied to your message. They sit in Lead forever, never moving, taking up visual space and inflating your top-of-funnel count. The fix is upstream of the Kanban: use the Bulk Number Validator before importing contacts in bulk so dead numbers never reach the board. We wrote up the safe-send pattern in How to send bulk WhatsApp messages without getting banned — number validation is step one of that playbook for a reason.

Stages without exit conditions. Already mentioned, worth repeating because it's the #1 killer. If "Prospect" doesn't have a clear "what makes this card a Customer" definition, the card lives there until the heat death of the universe. Every stage needs a sentence-long exit condition written somewhere your team can read it. The condition can be subjective ("they confirmed they want to proceed") as long as it's something.

One-person bias. You set up the board for how you think. Your stages are named in your shorthand. The exit conditions live in your head. Then you go on holiday, or hire a teammate, or hand the pipeline to a co-founder, and they can't make a single move without asking you what each stage means. The fix: write a one-line "what this stage means and what moves a card out" note next to every stage name. Stage names should be verbs, not vibes.

Chrome-extension Kanban vs WhatsApp Business API

The honest comparison, side by side. I'm not going to pretend one path is universally right.

Time to first board. Chrome extension: 10 minutes (install, open WhatsApp Web, define stages, drag chats in). API + hosted CRM: 1–3 weeks (Meta business verification, BSP onboarding, template review, dashboard configuration, agent training). If you need to start tracking a pipeline this week, only one of these gets you there.

Cost. Chrome extension: flat license fee (Lion CRM is $100/year direct, $150–$250 one-time + $1–$2.50/user/month whitelabel). API path: per-message + BSP markup. For a typical small business sending 2,000 conversations a month in India, API works out to ₹2,000–₹6,000/month just for the messages, before the hosted CRM subscription on top. Chrome extension scales linearly with users; API scales linearly with messages.

Where your data lives. Chrome extension: on your device. API + hosted CRM: on the BSP's cloud. Neither is universally "better" — local data is a privacy win and a backup risk; cloud data is a backup win and a privacy trade. Match the choice to your business.

Scale ceiling. Chrome extension: comfortable up to several thousand active conversations on a single number with disciplined Kanban hygiene. API path: needed once you're running multi-agent helpdesks at hundreds of thousands of inbound conversations a month or sending templated marketing outside the 24-hour window. There's a real ceiling on the extension path; the question is whether your business will hit it.

Ban risk and account safety. This is the question I get asked most. The honest answer: any tool can get a number banned if it's used badly, and any tool reduces ban risk if it's used responsibly. WhatsApp's own anti-spam policy is clear that mass messaging unknown contacts is what triggers bans, not the existence of any particular tool. Lion CRM ships with built-in safety features — pause settings, human-like delays, the Bulk Number Validator — specifically to keep extension users on the right side of WhatsApp's quality detection. Use them. Send to opted-in contacts at human cadence and your number is materially safer than it would be without them. Send 5,000 cold messages in 90 seconds and any tool — extension or API — will get you in trouble.

For most SMBs, agencies, coaching businesses, real estate teams, and whitelabel resellers, the Chrome-extension Kanban is the right starting point. It's how I started, it's how every Lion CRM partner starts, and it's how almost every business that doesn't need the API ends up running their pipeline.

Step-by-step: build your first WhatsApp Kanban board in 10 minutes

This is the actual setup I'd walk a new partner through over a screen-share. No magic. Ten minutes start to finish.

1. Install the Lion CRM Chrome extension. Get it from lioncrm.site (or from the whitelabel partner who sold it to you, with their branding). Pin the icon to your Chrome toolbar.
2. Open WhatsApp Web at web.whatsapp.com and scan the QR code with your phone the way you normally would. The extension hooks into the same session — your number, your messages, no separate login.
3. Open the Kanban panel from the extension toolbar inside WhatsApp Web. The default four stages — Lead, Prospect, Customer, VIP — are pre-configured.
4. Decide if the default works for your business. Read the Custom Stages section above. If you're a real estate agent, coaching business, or D2C seller, customise. Otherwise, keep the default and ship.
5. Drag your first 20 chats into stages. Don't try to sort everyone on day one. Pick the 20 most active conversations from the last week. Move them into Lead, Prospect, Customer, VIP based on where each one actually is. This takes 5 minutes and gives you an immediate visual snapshot.
6. Set Smart Calendar follow-up cadence per stage. Lead = check in 7 days. Prospect = follow up 48 hours. Customer = check in 14 days. VIP = check in 30 days. The Smart Calendar feature will nudge you so you don't have to remember.
7. Use the board for one full week before changing it. This is the rule almost everyone breaks. Resist the urge to add stages or rename things on day three. Run the default for a week and then decide what's missing. Most of the time, what felt missing on day three turns out to be unnecessary.

By the end of week one you'll know two things: which stage is leaking the most cards (the leakiest stage is where you focus your sales energy next), and which integrations you actually want (you'll feel the absence — "I wish stage changes pushed to my Google Sheet" — before you wire it up). That's the order: Kanban first, automations second.

Lion CRM at a glance — 16 features, 9 languages

The Kanban Board is one of 16 features inside Lion CRM. The other 15 exist because pipeline management isn't useful in isolation — you also need to talk to those contacts efficiently. Here's the canonical list, in case you're sizing up the whole package: Bulk Messaging, Custom Tabs, Message Templates, Quick Reply, Kanban Board, Smart Calendar, Profile Chat, Chat Toolbar, Bulk Number Validator, WhatsApp Status Automation, AI Integration (OpenAI / Gemini / DeepSeek with your own key), 9 Languages, Backup & Restore, Powerful WebHooks, Configure API, and Custom Signature.

The extension UI ships in 9 languages — English, Portuguese, Spanish, Hindi, German, French, Italian, Dutch, with more being added — so a partner reselling into Brazil or LATAM gets a localised interface out of the box. That matters because the end-customer using the Kanban board is often not the technical buyer.

Pricing is deliberately simple. Direct end-user: $100/year for one WhatsApp number on up to 4 devices. Whitelabel partner: Starter $150 one-time + $2.50/user/month, Growth $200 one-time + $2.00/user/month (most popular), Enterprise $250 one-time + $1.00/user/month, with a 30-active-user-after-3-months minimum after the grace period. The Webstore Setup add-on ($250 one-time) configures a public marketing site under your brand if you want one. The whitelabel admin lives at admin.lioncrm.site/public/login.php. The full whitelabel breakdown is in Whitelabel WhatsApp CRM Software: founder's 2026 guide — start there if you want to resell rather than just use.

For comparison shopping, Best WhatsApp CRM Extensions for Chrome walks through how Lion CRM stacks up against the rest of the Chrome-extension category, and Lion CRM vs Watidy covers the head-to-head against the closest direct competitor.

Frequently asked questions

Can I use a Kanban board inside WhatsApp Web?

Yes. Lion CRM is a Chrome extension that adds a Kanban panel to WhatsApp Web — you scan the same QR code on your phone, the same way you'd use WhatsApp Web on its own. The Kanban board sits next to the chat list, so you drag cards between stages without leaving WhatsApp. The extension does not require the WhatsApp Business API or any Meta partnership.

How is a Kanban different from WhatsApp labels?

Labels (in the WhatsApp Business app) are passive — they describe a contact. A Kanban stage is active — it tells you what action comes next. A "VIP" label says "this is an important contact." A "Prospect" Kanban stage says "follow up with a quote in the next 48 hours." Labels answer "who is this person?". Stages answer "what do I do next?". You can use both together — Lion CRM has Custom Tabs (label-style filtering) alongside the Kanban Board.

Do I need the WhatsApp Business API to use a Kanban board?

No. Two paths exist: (a) hosted CRM dashboards built on the WhatsApp Business API, which need Meta verification, template approval, and per-message fees, and (b) Chrome-extension CRMs like Lion CRM that sit on top of WhatsApp Web. Both can show a Kanban view. The extension path is faster to set up (10 minutes), avoids per-message cost, and keeps your data on your device. The API path is needed when you're running multi-agent helpdesks at very high message volumes or doing template marketing outside the 24-hour window.

How many pipeline stages should I use?

Start with four — Lead, Prospect, Customer, VIP. Add a fifth stage only when one of the existing stages stops carrying enough information. Five is comfortable, six is the upper limit, and anything beyond is usually over-engineering. The Kanban board exists to make decisions faster. Once you have so many stages that deciding which stage a card belongs in becomes its own decision, the tool is slowing you down rather than speeding you up.

Can my team see the same WhatsApp Kanban board?

In Lion CRM, the Kanban data is stored locally on your device by default — that's the privacy and zero-cost trade-off of the Chrome-extension architecture. To share a board across a team, you have two options: (1) use the Backup & Restore feature to export and import the same Kanban configuration across team-mate devices, or (2) push stage-change events to a shared Google Sheet via Powerful WebHooks so everyone sees the same pipeline summary. For team-wide concurrent editing of the same board across devices, the API + hosted CRM path is a better fit.

Will using a Kanban-board Chrome extension get my number banned?

The honest answer: any tool can get a number banned if you use it to mass-message strangers, and any tool keeps a number safer if you use it to nurture opted-in contacts at human pace. WhatsApp's policy is about behaviour, not about which tool is on the other end. Lion CRM ships with pause settings, human-like delays, and the Bulk Number Validator specifically to make safe behaviour the default. The detailed playbook is in our bulk WhatsApp without getting banned guide — read that before you do anything beyond 50 messages a day.

Related guides

• Lion CRM — The Ultimate WhatsApp CRM Chrome Extension (Complete Guide) — the canonical pillar guide for the product, with screenshots of every feature including the Kanban Board.
• WhatsApp CRM vs WhatsApp Business API: Which to Pick (2026) — full architecture comparison if you’re still deciding between the two paths.
• Whitelabel WhatsApp CRM Software: Founder’s 2026 Guide — how the Kanban-board extension powers a whitelabel reseller business.
• Best WhatsApp CRM Extensions for Chrome — Which One Can You Rebrand & Sell? — comparison of the top Chrome-extension CRMs.
• Lion CRM vs Watidy — head-to-head against the closest direct competitor.
• Follow Up WhatsApp Message — From Manual to Fully Automated — pairs with the Smart Calendar / Kanban automation section above.
• How to Schedule WhatsApp Messages — No Per-Message Cost — how the Chrome-extension path handles scheduling without API templates.
• How to Send Bulk WhatsApp Messages Without Getting Banned — required reading for anyone running outbound at any scale.

The honest verdict on WhatsApp Kanban boards

If you're running sales on WhatsApp and you don't have a Kanban view of your pipeline, you're navigating with a chat list and a memory of what each chat is. That works at 5 conversations and falls apart at 50. Every WhatsApp seller I know who scaled past that ceiling did it by getting a Kanban board in place and trusting it to surface what the chat list cannot — what stage everyone is in, where cards are sticking, and what the next action is.

The choice between Chrome-extension Kanban and API + hosted CRM Kanban is real, and I won't pretend the extension path is universally right. It's the right starting point for almost every SMB, agency, coaching business, real-estate team, D2C seller, and whitelabel reseller running their pipeline through a small number of WhatsApp accounts. It's not the right path for high-volume multi-agent contact centers. Both are legitimate. Pick the one that matches your business.

If you're going to try the extension path, Lion CRM's free 7-day trial is the lowest-risk way in. Install the Chrome extension, open WhatsApp Web the way you already do, set up the four-stage default, drag 20 chats into stages, and run it for a week. If after a week you don't think it's better than your old chat-list workflow, walk away — no contract, no per-message cost, no API approval to undo. That's the entire pitch. You can also subscribe to the LotsOfCode YouTube channel for the walkthrough videos that show each feature in action — the Kanban setup video runs about 8 minutes.

Whatever path you pick, get a Kanban board in place this week. Lion CRM, a product by LotsOfCode Private Limited, exists because too many businesses lose too much pipeline to a chat list that wasn't built for selling. Don't let yours be one of them.

Try Lion CRM free for 7 days

Want to test before you commit? Install Lion CRM directly from the Chrome Web Store — every first-time install gets an automatic 7-day free trial.

Steps:

1. Click the install link → Get Lion CRM on Chrome Web Store.
2. Click “Add to Chrome” — the extension installs in seconds.
3. Open WhatsApp Web in your browser — Lion CRM activates automatically.
4. Your 7-day trial starts the moment you log in. No credit card needed.
5. After 7 days, choose a paid plan or upgrade to whitelabel reseller.

Written by Rakshit Soni, co-founder of LotsOfCode Private Limited and creator of Lion CRM. Kuldeep Dadhich, co-founder, leads engineering on the extension. Both are reachable through the WhatsApp number on the lioncrm.site contact page if you want to discuss your specific pipeline before signing up.