SabNode
    ProductsFeaturesEnterpriseCustomersPartnersResourcesPricing
    AllConversationsAutomationCustomer DataGrowthAnalyticsCommerceDeveloperExplore products
    1. Home
    2. Features
    3. Customer Data
    4. Kanban Pipeline
    CRM · Customer Data

    Sales pipelines that breathe with your conversations

    Kanban Pipeline gives every sales motion — leads, deals, support tickets, onboarding — a visual board with custom stages, drag-and-drop, automations on entry and exit, and a forecast that updates as deals move. Built for teams who sell in WhatsApp threads, not in spreadsheets.

    • Unlimited pipelines with custom stages
    • Drag-and-drop with automation on stage change
    • Lead scoring with custom rules
    • Forecast and conversion roll-up per pipeline
    Feature signature
    SabNode . CRM
    Kanban Pipeline

    Lead → qualified → proposal → won. Drag, filter, score, forecast.

    Live
    ∞
    pipelines per tenant — no cap
    40%
    reduction in deals lost to staleness
    <300ms
    p95 drag-to-update latency on the board
    The problem

    The pipeline that updates itself, finally

    Sales pipelines are where CRMs go to die. The board looks great in the demo — colored columns, drag-and-drop, big numbers at the bottom. Three months in, half the deals are stuck in "Qualified" because nobody bothered to move them. The closed-won column is empty because reps forget to update after they close on WhatsApp. The forecast is fiction. Leadership distrusts the board and runs Monday standups off a Google Sheet instead.

    The problem is not the visualisation — kanban boards are fine. The problem is that the board is a separate place from where the actual conversation happens. A rep closes a deal in WhatsApp on Friday afternoon and remembers to update the CRM card on Monday morning, maybe. By then three other deals have moved, and the board reflects last week's reality.

    Kanban Pipeline in SabNode CRM is fused to the conversation surface. The contact card on the board is the same contact you chat with in the inbox. Stage changes can trigger flows automatically — moved to "Proposal Sent" fires the proposal template, moved to "Won" triggers onboarding, moved to "Lost" tags the contact for re-engagement in 90 days. Conversation activity feeds back: an inbound message after 14 days of silence flags the deal for follow-up. The board updates because the work updates it, not because someone remembers to.

    What it is

    Kanban Pipeline, in depth.

    A Pipeline is a sequence of named stages with a defined purpose — sales (Lead, Qualified, Proposal, Won, Lost), onboarding (Signed, Setup, Training, Activated), support (New, In Progress, Resolved). You can run unlimited pipelines in parallel; a contact can sit on multiple boards at once (a Won customer can simultaneously be at "Training" in onboarding and "New" in support). Each pipeline has its own stages, automations, scoring rules and forecast settings.

    Stages are configurable as much or as little as you need. Each stage has a name, color, an optional WIP limit (no more than 20 deals in "Proposal" at once), a target duration (deals over 14 days here are flagged stale), and entry/exit automations. Entry automation is "fire a flow when a deal enters this stage" — auto-send the proposal template when a deal moves to "Proposal Sent". Exit automation handles cleanup or notifications. No manual orchestration; the pipeline is a state machine you operate visually.

    Drag-and-drop is the primary interface, but every stage transition can also happen programmatically — from a flow node, an API call, an AI Studio tool, or an auto-rule. This dual-mode is critical: humans drag deals when they have context, automation moves deals when signals fire. A deal that has been silent for 21 days in "Proposal" can auto-move to "Stalled" via rule. A new inbound from a previously-Lost contact can auto-move back to "Lead — Re-engaged". The board reflects the truth the conversation is creating.

    Lead scoring runs in the background per pipeline. Define rules — +20 for "title contains CTO", +30 for "company size > 500", -10 for "no reply in 7 days" — and every deal carries a live score. The board sorts within each stage by score so reps work the highest-value cards first. Scores feed segments ("hot deals: score ≥ 80") and flows ("if score crosses 90, alert AE in Slack"). The forecast at the bottom of the board rolls up score-weighted deal values per stage to project pipeline coverage.

    Capabilities

    Everything you get with Kanban Pipeline.

    7 capabilities
    01

    Unlimited custom pipelines

    Run separate pipelines for sales, onboarding, support, refund disputes, partner deals. Each pipeline has its own stages, automations, scoring rules and access controls. Contacts can sit on multiple pipelines simultaneously without conflict.

    02

    Stage entry and exit automations

    Wire a flow to fire when a deal enters or exits a stage. Auto-send proposal on Proposal Sent, trigger onboarding on Won, tag and re-engage in 90 days on Lost. Replaces the manual playbook with deterministic execution.

    03

    WIP limits and target durations

    Set per-stage WIP limits to enforce focus. Set target durations to surface stale deals automatically. The board highlights overflows and stalls so leads catch process issues without running reports.

    04

    Lead scoring with custom rules

    Compose scoring rules from any contact signal — firmographic, behavioral, engagement. Scores update in real time. Board sorts within stage by score. Scores feed segments, flow branches and Slack alerts.

    05

    Forecast roll-up

    Each deal has an expected value and a stage-based probability. Forecast at the bottom of the board sums weighted values per stage and totals pipeline coverage. Configurable probability per stage. Updates instantly on drag.

    06

    Drag-and-drop + programmatic moves

    Humans drag deals when they have context. Flows, rules and AI tools move deals when signals fire. Both paths share the same audit log. Stage history per deal queryable for win-loss analysis.

    07

    Pipeline-level RBAC

    Restrict who can see, edit or move deals on a pipeline. Sales reps see only their pipeline; managers see all; finance sees forecast totals only. Granular roles support agencies running multiple client pipelines in one tenant.

    Use cases

    Built for the way teams actually work.

    D2CCase 01

    D2C inbound WhatsApp leads

    Single sales pipeline: Inquired, Qualified, Quoted, Negotiating, Won, Lost. Auto-move from Inquired to Qualified when AI flags purchase intent. Manual drag for everything else. Entry automation on Won creates a Shopify customer and sends the onboarding sequence.

    SaaSCase 02

    B2B SaaS multi-pipeline ops

    Three pipelines: Sales (Lead → Closed), Onboarding (Signed → Activated), Renewals (90-day, 30-day, 7-day). A contact moves through all three over the year. Each pipeline has its own RBAC — sales reps cannot see renewals; CSMs cannot edit sales stages.

    EdTechCase 03

    EdTech admissions counsellor board

    Pipeline: Inquired, Counselled, Application Started, Documents Submitted, Enrolled. Scoring on student demographics and engagement. Stage entry on Enrolled triggers a payment-link flow. Counsellor wakes up to a board sorted by lead score, not random order.

    Real EstateCase 04

    Real-estate site-visit pipeline

    Pipeline: Inquired, Property Sent, Site Visit Scheduled, Visited, Booked. Stage entry on Site Visit Scheduled auto-sends a calendar invite and sets a reminder. Stale deals over 14 days in any pre-Booked stage auto-tag for re-engagement. Brokers focus on hot deals, not the queue.

    LogisticsCase 05

    Logistics dispute pipeline

    Pipeline: New, Investigating, Resolution Proposed, Customer Confirmed, Closed. AI tags inbound disputes by type. Exit automation on Closed updates Shopify with the resolution code. Ops manager sees aggregate volume per dispute type and average time-to-resolution.

    How it works

    From signup to first send in minutes.

    Kanban Pipeline is included on every SabNode workspace. No separate billing, no extra setup, flip it on from your workspace settings.

    1. 01

      Define a pipeline

      Name it, add stages, configure colors, WIP limits, target durations. Set the contact entry rules — manual only, or auto-create on a specific event.

    2. 02

      Wire automations

      Attach flows to stage entry and exit. Configure auto-move rules from contact events (inbound silence, score threshold, custom field change).

    3. 03

      Score and forecast

      Build scoring rules from contact signals. Set expected value and stage probability for forecast. Both update in real time as deals move.

    4. 04

      Operate the board

      Reps drag deals based on context. Flows move deals based on signals. The board reflects current reality. Filter by owner, score, recency, custom field.

    5. 05

      Review and optimise

      Forecast at the bottom of the board. Stage-conversion report shows leaky stages. Win-loss analysis reveals patterns. Iterate on scoring and stages quarterly.

    Plays well with

    Works with the tools you already ship on.

    Connect directly with your existing stack or leverage the Platform Core tools to extend capabilities natively.

    ShopifyHubSpotSalesforcePipedriveSlackGoogle CalendarRazorpayStripe

    Platform Core Tools

    Enhance this feature with deep integrations into our core infrastructure. Connect via API, utilize webhooks, or embed directly using our SDKs.

    • Unified Dashboard Apps

      Manage all settings seamlessly within the core UI.

    • Developer APIs and Webhooks

      Extend functionality with custom automated workflows.

    Frequently asked

    Questions about Kanban Pipeline.

    Can't find what you're looking for? Talk to our team.

    Can a contact be on multiple pipelines at once?
    Yes, and most production tenants run it this way. A customer can simultaneously be at "Activated" in onboarding and "New" in support — these are independent pipelines, independent stages. The contact detail page shows every pipeline they are on with current stage. RBAC controls which team sees which pipeline so cross-team views stay clean.
    How does the forecast probability per stage get set?
    Each stage has a default probability (e.g. Lead 10%, Qualified 25%, Proposal 50%, Negotiating 75%, Won 100%, Lost 0%). You set these per pipeline based on historical conversion. The forecast sums (deal_value × stage_probability) across the pipeline. Advanced mode lets you override probability per deal — a normally 50% Proposal might be 80% because of a strong signal. Audit log captures every override for win-loss accuracy review.
    Can I see the conversion rate between stages?
    Yes. The pipeline analytics page shows funnel conversion per stage pair (Qualified → Proposal: 38%, Proposal → Won: 22%), average duration per stage, and stage-where-deals-die distribution. Filter by owner, source, time window. Critical for spotting that "deals reaching Negotiating convert at 80% — we should send more there" or "Qualified to Proposal drops 60% — interview the reps".
    How are deals created on a pipeline?
    Three ways. (1) Manual: rep clicks "New Deal" on the board, picks a contact, fills required fields. (2) Auto on event: a rule like "when contact replies to broadcast X, create deal in pipeline Y at stage Z". (3) API: external systems POST to `/api/pipelines/{slug}/deals` to create programmatically. All three share the same validation and audit log.
    What happens to a deal when the contact is deleted?
    Deals are soft-deleted alongside the contact. The deal row remains in the audit log for compliance and historical reporting (win-loss totals, forecast accuracy) but is removed from the active board. If the contact is restored within 30 days (undelete window), the deal reactivates at its last stage. After 30 days, hard delete purges both.
    Can two reps own the same deal?
    Yes. Each deal has a primary owner (for SLAs and notifications) and optional collaborators. Collaborators get visibility and can edit but are not the responsible owner. This handles common patterns like an SDR who qualifies and an AE who closes — both are involved, but the responsibility transfers cleanly when the deal moves to the AE's stage. Ownership history is logged.
    How does lead scoring stay accurate over time?
    Scoring rules are versioned. When you adjust a rule, existing scores recompute in the background within minutes — no manual rebuild. The score history per deal is logged so you can see "this deal was 65 last week and is 82 now because of this new event". Quarterly we recommend a model review: which rules predicted outcomes, which were noise. The dashboard surfaces rule-level lift over baseline so you can prune dead weight.
    Related features

    Stronger when stacked.

    Browse every feature
    Contacts
    Every conversation becomes a contact record — auto-deduplicated.
    Read more
    Segments
    Dynamic audiences from any signal. Reuse across flows, broadcasts and AI.
    Read more
    Tags
    Multi-value tags with auto-apply rules and bulk edit.
    Read more
    Custom Fields
    Structured properties on any contact or deal — text, date, number, JSON.
    Read more
    CRM · Customer Data

    Ship kanban pipeline into production this week.

    No credit card. No sales call required. Spin up a workspace, plug in a number, and your team is live in under an hour.

    Start free Book a demoSee pricing
    SabNode

    SabNode is the operating layer for customer conversations. Chat, automation, CRM, broadcasts, commerce and AI in one workspace.

    Talk to sales
    Conversations
    Browse
    Automation
    Browse
    Customer Data
    Browse
    Growth
    Browse
    © 2026 SabNode. All rights reserved.
    PrivacyTermsStatusContact