Kanban CRM: Run Your Pipeline and Client Projects on One Board
A kanban CRM turns deals and client work into cards on a board. Learn how to design stages, avoid card drift, and connect sales to delivery.
A kanban CRM shows your customer records as cards on a board. Columns are stages, cards are deals, accounts or projects, and dragging a card is the status update. The format works because you see every open deal at once. It only keeps working if the board stays accurate and every move triggers something real downstream. This guide covers how to design the board, which rules keep it honest, and how to extend it from sales into client project tracking and intake.
TL;DR
- A kanban CRM is a board view over live CRM records, grouped by a stage field. It is not a separate to-do app.
- Boards answer questions lists hide: where deals pile up, what has gone stale, and who is overloaded.
- The main failure is card drift, where reps forget to drag cards. Required fields and automated stage triggers prevent it.
- The best boards drive action: a move to “Won” should create the project, update the forecast and notify the team.
- Agencies and consultancies get the most value when the sales board and the delivery board share the same data.
Table of Contents
- What a kanban CRM actually is
- Why a board beats a list for pipeline work
- How to design a pipeline board that holds up
- Card drift: the failure mode to design against
- From sales board to client project tracking
- Building a project intake workflow on the board
- Perspective: what we think most kanban CRM setups get wrong
- Choosing a kanban CRM: criteria that matter
- How Strkr handles it
- A one-week rollout plan
- FAQ
- Sources
What a kanban CRM actually is
Kanban started on the factory floor. Taiichi Ohno developed it at Toyota to improve manufacturing efficiency, and software and project teams later adopted it. The idea is simple: work items sit on cards, columns represent steps, and everyone sees the whole flow.
In a CRM, the cards are not tasks you invented for the board. They are the records you already manage: leads, opportunities, accounts, onboarding projects, renewals. The board is one view over that data. Switch to a table and the same records appear in rows. Edit a field and the card updates. That distinction matters, because a board that lives apart from your customer data becomes a second system to maintain.
It is also worth separating kanban from other methods. Kanban is a continuous-flow model that uses cycle time as its main metric, while Scrum works in fixed-length sprints, commonly two weeks, and plans capacity with velocity. Sales rarely fits a sprint. Deals arrive and close on their own schedule, so a continuous-flow board suits a pipeline well. Some teams blend the two into a hybrid often called Scrumban, which can suit delivery work that needs a weekly cadence on top of visual flow.
Why a board beats a list for pipeline work
A list view tells you what exists. A board tells you what is happening. In a weekly pipeline review, three questions matter most, and practitioners tend to describe the same three:
- Where is the pile-up? A column with twice the cards of its neighbors is a bottleneck. Maybe proposals wait on a pricing approval, or discovery calls are not converting to demos.
- What has gone stale? Cards that have sat in a stage far longer than your typical cycle stand out immediately on a board and hide inside a sorted table.
- Who is overloaded? Group or filter by owner and you see the rep carrying 40 open deals while a colleague has 12.
The underlying principle is work-in-progress limits. Kanban is rooted in Lean manufacturing and designed to limit work in progress, and the sales version is a cap on how many deals one rep actively works in a given stage. The cap forces a decision: advance a deal, or disqualify it. Neither is the same as leaving it parked.
If you are still defining your stages, start with our guide to what a sales pipeline is and how to build one, then come back to design the board. For the review rhythm that goes around it, see what pipeline management involves.
How to design a pipeline board that holds up
Name stages by buyer evidence, not rep activity
“Followed up” describes what a rep did. “Budget confirmed” describes what the buyer did. Stages built on buyer evidence are harder to inflate and much easier to forecast from. A workable B2B board often looks like this:
| Stage | Exit evidence required |
|---|---|
| New lead | Contact and company fields complete |
| Qualified | Need, timeline and decision-maker identified |
| Discovery done | Notes logged, next meeting booked |
| Proposal sent | Scope, price and document attached |
| Negotiation | Named champion and approver confirmed |
| Won / Lost | Close date plus a reason for the outcome |
Your stages will differ. Keep the count to six or seven. More than that and cards stop moving in a way anyone can read.
Gate the moves
Research on customized CRM implementations in project-based service companies points to the same practice: requiring specific data points before a card can advance, so the board reflects pipeline health instead of serving as a cosmetic layer. In practice that means a card cannot enter “Proposal sent” without an amount, a close date and an attached proposal. Reps experience this as a small speed bump. Your forecast experiences it as the difference between data and guesses.
Pick card fields that earn their space
A card should show what a manager needs in two seconds: deal name, amount, owner, days in stage and next step date. Anything beyond that clutters the board. Put the rest on the record behind the card.
Card drift: the failure mode to design against
The most common way a kanban CRM fails is quiet. Reps have a conversation, the situation changes, and nobody drags the card. Within a month the board shows a pipeline that no longer exists, and it is as unreliable as the spreadsheet it replaced. Practitioners call this card drift.
Three defenses work together:
- Mandatory fields on movement. If moving a card requires a fresh next-step date, the rep has to touch the record, and the data improves as a side effect.
- Automated triggers. When a rep sends a proposal from the CRM, the card moves itself. When an email reply arrives from a prospect, the “last activity” stamp updates without anyone typing.
- A staleness rule. Any card with no activity for a set number of days gets flagged, and the owner gets a task. This is a simple automation, and our overview of CRM automation, flows and triggers explains the building blocks.
This is the daily-habit side of what we call CRM hygiene. A board is only as honest as the maintenance behind it, so build the maintenance into the tool rather than relying on discipline.
From sales board to client project tracking
For agencies, consultancies and implementation partners, the sale is not the end of the story. A signed deal becomes a project, and the project has its own stages: kickoff, production, review, delivery, invoicing. Teams searching for client project tracking often end up with a sales board in one tool and a delivery board in another, with a manual handoff between them. That handoff is where scope details, contract terms and promised dates go missing.
The stronger pattern is a single data model with two boards:
- The sales board groups opportunities by stage.
- The delivery board groups projects by phase, and each project links back to the account and the original deal.
Moving an opportunity to “Won” should create the project automatically, copy the scope and amount, assign an owner and notify the delivery lead. Case study research on project-based service companies supports this approach: the most effective implementations treat the board as a real-time mirror of business data, where a change automatically triggers downstream actions such as forecast updates or project creation, rather than as a standalone project tool for sales.
There is evidence that connected processes pay off. A 2024 simulation study of one company’s sales process found that integrating CRM with ERP, supported by visual process mapping, cut average time in the sales process from 177.36 to 74.30 hours. That is one company’s model, not a universal benchmark, but it shows why removing manual handoffs is worth the design effort. For a deeper look at choosing a system with this capability, read how to pick a CRM with project management. Video production teams in particular can look at CRM and automation tools for video production agencies.
Building a project intake workflow on the board
Intake is the step between “the client said yes” and “the team starts work,” and it is where many agencies lose a week. A board makes intake visible. A practical flow:
- Request received. A form submission or a won deal creates an intake card with the client, scope and requested date.
- Needs review. The delivery lead checks that scope, assets and approvals are complete. Missing items become tasks assigned to the account owner.
- Scheduled. The project gets an owner, a start date and a capacity check against current work.
- In progress. The intake card becomes a project with its own phases.
- Delivered and invoiced. Closing the project triggers a feedback survey and flags the account for renewal or cross-sell.
The capacity check in step three is where WIP limits earn their keep. If your team can run five active projects well, a sixth card should wait in “Scheduled” rather than quietly overloading everyone. Our explainer on sales capacity planning covers the same arithmetic on the selling side.
Perspective: what we think most kanban CRM setups get wrong
We see the same two mistakes again and again. The first is treating the board as the product. Teams spend a week on colors and card layouts, then discover the board does nothing when a card moves. The board is the visible edge of the data model underneath, and the data model is where the effort belongs.
The second is forcing a rigid CRM into a flexible process. Teams coming off heavyweight systems often tell us the board was easy and the admin was not: every new stage, field or object needed a specialist. That is why we built Strkr around custom objects and no-code Flows. If your business tracks retainers, implementations or statements of work, you should be able to model them as first-class records with their own boards, without hiring an admin.
Our view, in short:
- Gate stage moves with required data, so forecasts rest on evidence.
- Let automation move cards wherever it can, so reps do not have to remember.
- Connect sales and delivery on one record chain, so a won deal becomes a project without retyping.
- Judge a board by what happens after a card moves, not by how it looks.
, Josh
Choosing a kanban CRM: criteria that matter
When you compare tools, ignore the demo’s drag-and-drop animation. Every product has it. Ask these questions instead.
| Criterion | What to check |
|---|---|
| Board on any object | Can you build a board for projects or renewals, or only for deals? |
| Stage gating | Can you require fields or attachments before a move? |
| Automation on move | Does a move trigger tasks, emails, project creation, forecast updates? |
| Forecasting link | Do stage changes feed the forecast automatically? See what revenue forecasting is |
| Pricing clarity | Are features gated behind higher tiers or sales calls? |
| Integrations | Does it connect to your email, calendar and chat with each user’s own account? |
A lightweight add-on that bolts a board onto a record grid can be enough for a three-person team. Planning tools built into office suites offer simple kanban for task tracking, but they lack the specialized reporting that dedicated tools provide, and they do not hold your customer records. If your team runs pipeline, delivery and marketing together, you want one platform. Our roundup of all-in-one CRM and revenue platforms lays out the options by team type.
How Strkr handles it
Strkr gives you kanban boards over any object, including custom ones, so the same workspace can show your deal pipeline, your client projects and your renewals. No-code Flows move cards, create projects and send notifications when records change, and Strkr AI forecasting reads the pipeline so the board and the forecast stay in step. Native integrations with Gmail, Google Calendar, Slack, Microsoft 365, HubSpot and Stripe, among 40+ more, use per-user OAuth, so each rep connects their own accounts.
Pricing is published and seat-based: Starter is $29 per month per seat, Pro is $59 per month per seat and Scale is $119 per month per seat. Projects is $79 per month and Marketing is $99 per month as native modules on the same platform. You can see every plan and fee on the Strkr pricing page, or start from the Strkr homepage and try it with a real pipeline.
If marketing hands leads into your board, shared marketing and CRM workflows explain how to keep the two aligned, and contracts attached to cards are covered in CRM with document management.
A one-week rollout plan
You do not need a quarter to get this running. A realistic week looks like this:
- Day 1: Write down your current stages and the evidence that proves each one. Cut to six or seven.
- Day 2: Import contacts and open deals. Map each deal to a stage.
- Day 3: Add required fields for the moves that matter most: into Proposal sent and into Won.
- Day 4: Build two automations: one that creates a project on Won, and one that flags stale cards.
- Day 5: Connect email and calendar for each rep, so activity logs itself.
- Week 2 onward: Run your pipeline review from the board. Whatever you keep asking reps to explain verbally is a field or a rule you have not built yet.
FAQ
Is a kanban CRM better than a table view?
Neither is better in every case. Boards are best for spotting bottlenecks, stale deals and uneven workloads. Tables are better for sorting, bulk edits and exporting. A good CRM offers both over the same records, so you switch by task.
Can I use a kanban board for client project tracking inside my CRM?
Yes, if the CRM lets you create projects or custom objects with their own stage field. Link each project to its account and original deal, and the delivery board inherits scope and contract details without retyping. That removes the handoff gap between sales and delivery.
How many columns should a pipeline board have?
Six or seven is a sound range for most B2B teams. Each column should have a clear exit condition based on buyer evidence. If two stages feel interchangeable to your reps, merge them.
How do I stop reps from forgetting to move cards?
Make the board update itself where possible: sending a proposal, booking a meeting or receiving a reply should move or refresh the card. Then require key fields when a card advances, and flag cards with no recent activity. Reminders alone rarely hold.
What is the difference between kanban and Scrum for a sales team?
Kanban is continuous flow and tracks how long items take to move through stages. Scrum uses fixed sprints, often two weeks, and plans around velocity. Sales pipelines are usually continuous, so kanban fits; delivery teams sometimes blend both.
Sources
- What is Kanban? Azure DevOps, Microsoft Learn
- Customizing Odoo CRM for Pipeline, Opportunity, Project Delivery, and After-Sales Management: A Case Study
- Analysis and improvement of sales management through CRM and simulation utilisation