A visual sales pipeline where every stage change is one drag and every column fits the actual shape of the deal.
Strkr's kanban board renders every open deal as a card on a column, grouped by stage, sorted by last activity, color-coded by whatever field matters this week, and filterable by owner, segment, source, risk tier, or any custom field in the schema. Drag a card to change its stage. Drag it twice to change its owner. Drag it a third time to tag it for a bulk review. Everything a sales manager does at the pipeline level collapses from six clicks and three page loads into one gesture, with WIP limits catching stage overload before it becomes a forecast miss and keyboard shortcuts turning the whole board into a thirty-second morning triage.
The gap between a static pipeline report and the way reps actually move deals.
The pipeline page in a CRM is where reps spend their first fifteen minutes every morning and where managers spend their first hour every Monday. The old shape was a report: a list of deals in a table, sorted by stage, exported to a spreadsheet when something had to change. The modern shape is a kanban board where every stage is a column, every deal is a card, and every change is a drag. The useful question is which of those interactions survive contact with a real pipeline that has 400 open deals across 8 stages owned by 15 reps across 3 segments. If the board renders in two seconds, lets a rep drag a card to the next stage without opening a modal, color-codes risk tiers without a configuration project, filters by owner in one click, enforces a WIP limit when a stage swells past its capacity, and offers a keyboard shortcut for the three most frequent gestures, it earns the seat. If the board is slow, modal-heavy, or configurable only through an admin console, it is a report with a card-shaped CSS. The checklist below is the one buyers should walk every vendor through before signing. Strkr ships all nine on every paid tier.
Drag-and-drop stage change
One gesture, one write, one audit log entry.
Grab a card. Drop it in the next column. The deal's stage field updates, the activity log records the stage change with the before and after values, the forecast rolls up to the new stage weight, any flow bound to the stage transition fires, and the card settles into its new column in under a hundred milliseconds. No modal, no "are you sure" dialog, no second-page form to confirm the move. The gesture is the write. Reps who were updating ten deals a day on the old report shape now update twenty-five on the kanban, because the cost per update dropped from twelve seconds to one.
Custom columns per pipeline
Not every team sells on the same eight stages.
The default board ships with the canonical seven-stage pipeline, but every tenant configures their own. SMB teams use five stages. Enterprise teams use eleven, including procurement review and legal redlines. Renewal teams use three. Strkr's admin surface defines columns per pipeline, lets each pipeline have its own board, and lets a single tenant run multiple pipelines side by side so the New Business board does not pollute the Expansion board. Column order is drag-reorderable, column labels are editable inline, and stage weights for forecast math are set in the same screen.
Color-by-field
Any field, any color, no theme configuration required.
Pick a field: risk tier, days in stage, deal size bracket, source, owner, segment, close date proximity, custom priority. Pick a color scale. The cards recolor instantly. A manager who wants to see which deals have been in stage for over 30 days flips the color-by picker and the stale deals bloom red across every column. Switch to color-by-source and the inbound-versus-outbound mix becomes visually obvious without a separate report. Color is a visualization layer, not a data edit, so it never writes back to the record and never conflicts with per-rep preferences.
Grouping
Columns can group by stage, owner, segment, or any picklist.
The default grouping is by stage, which is what makes it a pipeline board. Flip the grouping picker and the columns regroup by owner, by segment, by source, by close month, or by any custom picklist in the schema. A manager running a weekly rep review flips grouping to owner and the board becomes a one-screen view of every rep's book. A rep running a segment-focused outreach flips grouping to segment and the board becomes a prioritized list of accounts by tier. One board, many layouts, no second navigation to learn.
Filters
Owner, segment, source, risk, close month, any custom field.
The filter bar sits above the board. Click a filter chip to narrow by owner, segment, source, risk tier, close month, deal size, product, or any field in the schema. Filters stack, filters are savable as views, saved views are shareable with the team, and the URL updates with the filter state so a link to "my enterprise deals closing this quarter at risk tier high" is a single pasteable URL. The filter engine runs on the same indexed Postgres query path the reports use, so a 400-deal pipeline filtered by three fields returns in under 300 milliseconds.
WIP limits
A column that swells past its cap flags the overload.
Each column can carry a WIP (work in progress) limit. When a stage holds more deals than its cap, the column header turns amber and the limit indicator shows the overage. The warning is advisory, not blocking, so a rep can still drag a card in, but the manager has a persistent visual that a stage is stuck. Teams running a disciplined pipeline motion use WIP limits to catch "every deal lives in Negotiation forever" patterns before they land on the forecast. The limits are configurable per column per pipeline, and the overage threshold triggers an optional notification to the pipeline owner.
Bulk actions
Select ten cards, change one field, write once.
Shift-click or lasso-select cards across any column. The bulk action bar slides up with the available operations: change owner, change stage, change close date, add tag, remove tag, delete, export. Pick an operation, confirm once, and ten records update in a single transaction with a single audit log entry per record. The bulk flow handles 500-record selections without a progress spinner because the server does the work on a background worker and streams completion back to the UI. End-of-quarter cleanup that used to take an afternoon takes four minutes.
Keyboard shortcuts
The whole board without touching the mouse.
Press J and K to move the focus cursor between cards. Press Enter to open the focused card. Press 1 through 9 to move it to the Nth column. Press O to reassign owner. Press F to open the filter bar. Press / to focus the search box. Press ? to see the full shortcut list. The gestures are learnable in a morning and permanent after a week. Reps who have internalized the shortcuts run their morning triage in forty-five seconds; the same work on a mouse-driven competitor board takes four to six minutes.
Density modes
Compact for triage, roomy for review, giant for QBR.
The density picker toggles the card height between compact (just the title, owner avatar, amount, and risk dot), standard (adds last activity and close date), and expanded (adds the top-three next steps, stakeholder count, and the latest note excerpt). A rep triaging their book flips to compact and fits 80 cards on screen. A manager running a 1:1 flips to expanded and the context is on the card without a drill-in. The density choice is per-user and persists across sessions, so each team member keeps the view they prefer without stepping on anyone else.
A kanban board is only as good as the write path underneath. Most CRM kanban implementations are a view layer over a slow report query, which is why they fall apart past 200 deals or when more than one rep is editing simultaneously. The Strkr kanban is a native surface on the deal object, served by the same indexed query path that powers the deals API, under the same permission model as every other surface in the product. Dragging a card is a stage-field write that goes through the standard validation, triggers the standard flows, and lands in the standard audit log. Nothing about the board is a parallel system. There is no shadow data store. There is no "kanban-only" permission tier. There is no divergence between what the board shows and what the forecast computes, because they read the same rows at the same instant.
Real-time collaboration
Two reps on the same board see each other's moves live.
When a teammate drags a card to a new column, every open board in the tenant reflects the move within a second via a WebSocket update. No full-page refresh, no stale-pipeline race condition where two managers argue over whose version of the pipeline is correct. The live update also carries the actor, so the card briefly shows "moved by Alex" so the viewer knows who made the change. End-of-month pipeline cleanup becomes a collaborative session instead of a Slack coordination problem.
Permission-aware
The board shows only what the user is allowed to see.
A rep sees their own deals plus anything their role permits (team deals, segment deals, or the full pipeline for a sales leader). The board respects ownership scopes, field-level visibility, and record-type access without a separate configuration. A rep without owner-change permission sees the Change Owner bulk action greyed out. A manager viewing a peer's board sees everything the peer can see and nothing more. One permission model, one surface, no shadow bypass.
Flows on stage change
Dragging a card is a trigger, not just a UI event.
Stage changes are first-class events in Strkr Flows. Dragging a deal from Discovery to Proposal fires the standard stage-transition trigger, which can create tasks, send notifications, update forecast weights, assign a sales engineer, draft a follow-up email, or kick off any automation the admin has configured. The flow runs on the server, so it fires whether the stage change came from the board, the detail page, the API, or a bulk action. One trigger, every entry point, no "the board skipped the flow" surprises.
Audit trail
Every card move is in the activity log.
When a card is dragged, the stage transition logs with the before value, the after value, the actor, the timestamp, the source surface (kanban board, detail page, bulk action, API), and the flow fired by the change. A manager auditing a deal's history sees exactly who moved it, when, and from where. The audit shape is identical across every entry point, so one review query covers all of them, and the compliance review for the board is one paragraph instead of a six-page questionnaire.
Field-aware cards
The card body is the admin's canvas, not a hardcoded layout.
An admin configures which fields appear on the card for each pipeline. New Business boards might show amount, close date, owner, and risk. Expansion boards might show MRR delta, current contract end, and renewal risk. Services boards might show project type, start date, and PM. The configuration is a drag-and-drop layout editor, saved per pipeline, previewable before publish, and reversible with a one-click revert. No forking the codebase, no custom development, no services engagement.
Mobile parity
The same board, scaled to a phone, drag included.
On a phone the columns scroll horizontally, the cards are tappable, and the drag gesture is a long-press-then-drag. The density defaults to compact so a rep running an airport triage can clear ten updates in a minute. The filter bar collapses into a modal picker, the search is a sticky header, and the keyboard shortcuts become a swipe gesture per cardinal direction. One codebase, two form factors, zero feature parity gap.
Virtualized rendering
A thousand-card board stays at sixty frames per second.
The board uses column-level virtualization so only the visible cards are mounted in the DOM. A 2,000-deal pipeline across 10 columns renders in under a second and scrolls at native frame rate because the browser never carries more than 60 cards in memory at any instant. Competing products that render every card up front hit the browser frame budget at around 400 deals and lock up at a thousand. Scale is a rendering problem, and we solved it on the client, not by capping the dataset.
Saved views
Filter + group + color + density + sort, in one named link.
The state of the board (which filters are on, which grouping is picked, which field colors the cards, which density is active, which column is sorted which way) saves as a named view. Views are personal or shared. Shared views appear in a team sidebar so the sales leader's "stale deals at risk" view is one click away for every rep on the floor. The URL carries the view state too, so pasting a view link in Slack opens the exact same board for the recipient, including the filters.
Undo
A single Ctrl-Z reverses the last drag.
Every stage change, owner change, and bulk action is undoable from the keyboard for sixty seconds after the action. The undo reverses the field write, reverses the audit log entry (as a compensating entry, not a deletion), and reverses any flow-fired side effects where safe. A rep who drops a card in the wrong column recovers in half a second. The undo window is configurable per tenant for teams that want a longer safety net.
Kanban feature maturity, an honest look
Features that photograph well versus features that survive a 400-deal pipeline.
Every CRM demo includes a card dragging smoothly between two columns on a 15-deal pipeline. Fewer demos show what happens when the pipeline has 400 deals, 11 columns, 3 saved filters, color-by-risk, grouping-by-owner, and two other reps editing simultaneously. The honest grading of CRM kanban features is a maturity curve. Here is how the common claims hold up on the way from the keynote to a production team.
Drag performance
Mature when the drag never dropped a frame.
A smooth drag on a 20-deal board is table stakes. A smooth drag on a 2,000-deal board is actually mature. Strkr's board virtualizes columns and GPU-accelerates the drag preview, so the gesture stays at 60 fps regardless of pipeline size. Competing products that render every card eagerly stutter past 400 deals and freeze past a thousand, which is why their sales demos use pre-cleaned pipelines of 50 cards.
Column customization
Mature when every team runs its own pipeline shape.
Teams do not sell on the same seven stages. A mature board lets each pipeline configure its own columns, its own column labels, its own column order, and its own stage weights. Strkr's admin surface does all four in one screen. Products that ship a global seven-stage board force every team to collapse their motion into someone else's template, which is where pipeline accuracy goes to die.
Color-by-field
Mature when any field, including custom, can drive color.
Color-by-stage is trivial because the column already represents the stage. Color-by-risk-tier, color-by-source, color-by-custom-priority is the useful shape. Strkr allows any single-select, picklist, or computed field to drive the color scale, including custom fields the admin added yesterday. Products that ship a fixed set of color-by options force the team to run a workaround or a tag field.
Grouping
Mature when the columns regroup without a page reload.
Grouping by owner or segment or source is the feature that turns a pipeline board into a weekly review surface. Strkr regroups in the client, in under 400ms, with the filters and color still applied. Products that force a navigation to a different page to see "by owner" are shipping a report, not a board.
WIP limits
Mature when the limit is advisory and the overage is visible.
A hard-block WIP limit frustrates reps who legitimately need to move the deal. A silent WIP limit nobody can see is marketing. Strkr's limit is advisory (the drag still succeeds) and the overage is visible (the column header turns amber and shows the delta). Managers see which stages are stuck without hunting through a report.
Bulk actions
Mature when 500 records change in one transaction.
Selecting 10 cards and running a bulk owner change on a slow server is a progress-spinner experience. Strkr runs the bulk on a background worker that writes in batches and streams completion back to the client, so a 500-record owner change finishes in under eight seconds and never blocks the UI. Competing products that run bulk changes through the UI thread lock the browser for the duration.
Keyboard shortcuts
Mature when the whole board is mouse-free.
Shortcuts for a single action (open card) are table stakes. Shortcuts for the full morning triage (move focus, open, change stage, change owner, filter, search, undo) are what let a rep clear their pipeline in forty-five seconds. Strkr ships the full set. Products that stop at "press Enter to open the card" are missing the point of a keyboard-first UI.
Saved views
Mature when a view is sharable by URL and name.
A saved view that only lives in one user's preferences is a convenience. A saved view that is nameable, shareable, URL-encoded, and inheritable by a team is a workflow. Strkr's views carry the full state (filter, grouping, color, density, sort) and share through a sidebar and a URL. Products that save view state in local storage are shipping a bookmark, not a view.
The kanban-pricing trap
How vendors turn a view into a tier.
The pricing problem is not whether the kanban board exists. It is where the vendor hid it in the SKU matrix. Several competitors ship a basic kanban on their lowest tier and lock the useful features (color-by-field, saved views, bulk actions, WIP limits) behind a Pro or Enterprise upsell. The Strkr pattern is the opposite shape. The kanban board ships on every paid tier with every feature on this page available from day one. The seat price is the pipeline price, with no "advanced kanban" line item.
Feature-gated views
The "Pro kanban" that is just the real kanban.
Several vendors ship a toy kanban on the entry tier (one color-by option, no bulk actions, no custom columns) and the actual useful board on a tier that costs three times as much. The pattern makes the pricing page look favorable and the second-quarter invoice ugly. Strkr's kanban is one surface, every feature from Starter upward, no "upgrade to unlock drag and drop" nonsense.
Pipeline cap
The "multiple pipelines" paywall.
Running one New Business pipeline and one Renewal pipeline on the same tenant is a basic sales motion. Several vendors cap pipelines at one on the entry tier and charge for the second. Strkr allows unlimited pipelines on every paid tier because the data model treats each pipeline as a configuration, not a license line.
Saved view cap
The "three views per user" ceiling.
Several products meter saved views per user as a tier-upgrade carrot. A rep running a serious book has eight or ten views (by segment, by close month, by stage, by risk, by source, by product). Strkr has no view cap. Create as many as the team needs.
Automation on stage change
Flows fire from any surface, including the board.
Some vendors route board-driven stage changes through a different code path that skips the automation layer, forcing the team to use a slower surface if they want the flow to fire. Strkr's board and detail page share the same write path, so every automation runs for every stage change regardless of entry point.
HubSpot deal board
Usable, bounded by HubSpot's stage model.
HubSpot ships a credible deal kanban on the Sales Hub tier, with drag-and-drop and basic card customization. The gaps show up on multi-pipeline tenants, custom objects, and deep filtering. For teams running the HubSpot stage model as shipped, it works. For teams needing per-pipeline column configuration or custom-object kanbans, the limits appear fast.
Salesforce Path/Kanban
Powerful, administrator-gated.
Salesforce ships a kanban view with per-record-type customization and reasonable filtering, but every configuration change requires a certified admin and a sandbox deploy. Teams that want to add a column, change a color scheme, or tune a WIP threshold wait on the admin backlog. Strkr's board is end-user configurable within the permission model, so most changes happen without an admin ticket.
Pipedrive
A kanban-first product with mid-market ceiling.
Pipedrive built around the kanban board from day one, which shows in the polish of the drag experience and the simplicity of the configuration. The ceiling shows up on reporting depth, custom objects, and complex permission models. For a 10-rep SMB team, Pipedrive's board is as good as any. For a 100-rep team with product-led signals and multi-year contracts, the Strkr board plus the full Strkr platform is the better call.
Three Strkr kanban patterns in production
What the board looks like on a real sales floor.
The demo video shows a card dragging between two columns. The product in production looks like three specific patterns reps and managers run every day. These are not aspirational screenshots. These are the three Strkr kanban uses that save teams the most time per week by a wide margin.
Morning rep triage
Compact density, color-by-risk, keyboard only.
A rep opens the board at 8:50 AM, flips density to compact, color-by to risk tier, filter to "my open deals closing this quarter." Eighty cards fit on screen. J and K move the focus between cards. Enter opens the one that needs attention. Press 1 through 9 to drag it to the right column, or O to reassign if the deal moved teams. Press Esc to return to the board. The whole morning triage takes forty-five seconds. On a mouse-driven competitor board, the same work took six minutes, which is five full minutes per rep per day of reclaimed selling time.
Monday manager review
Group-by-owner, color-by-days-in-stage, WIP limits on.
At 9:00 AM Monday, the sales manager opens the board, groups by owner, colors by days-in-stage, and switches on WIP limits for the three choke-point stages. Every rep's book becomes a column. Stale deals bloom red. Any rep stuck past WIP limit shows amber in their column header. The 1:1 agenda for the week writes itself: the three red cards per rep plus the amber column header. The Monday review that used to take two hours of pre-reading takes fifteen minutes and runs on the live board instead of a Monday-morning CSV export.
End-of-quarter cleanup
Bulk-select stale deals, bulk-update close date, done.
On the last day of the quarter, the sales operations lead opens the board, filters to "deals with close date in prior quarter still open," and lasso-selects everything. Fifty-seven cards. Bulk action bar slides up. Pick "Change close date to end of next quarter" plus "Add tag: carryover." Confirm once. Four seconds later, every deal has a new close date, every deal has a carryover tag, and the forecast page reflects the shift. The same cleanup on a competitor product took an afternoon of row-by-row edits in a report grid.
The Strkr kanban board ships on every paid tier. Every feature, no upsell, every pipeline, no cap.
Starter includes drag-and-drop stage change, custom columns, color-by-field, grouping, filters, bulk actions, keyboard shortcuts, and saved views. Pro adds WIP limits, flow triggers on stage change, and multi-pipeline configurations. Scale and Enterprise unlock the activity-log compliance pack and the shared-view governance surface. The seat price is the pipeline price, every tier, every month. Open a trial and move your first deal across the board before lunch.
Does the kanban board cost extra, or is it included in the seat price?
It is included. The Strkr kanban board ships on every paid tier at no additional charge. Drag-and-drop stage change, custom columns per pipeline, color-by-field on any field, grouping by any picklist, unlimited saved views, bulk actions, keyboard shortcuts, and virtualized rendering for large pipelines are all available from Starter upward. Pro adds WIP limits, flow triggers on stage change, and multi-pipeline configurations. Scale and Enterprise unlock the activity-log compliance pack and shared-view governance. There is no "advanced kanban" line item.
How does the Strkr kanban board compare to HubSpot's deal board?
HubSpot ships a credible deal kanban on the Sales Hub tier with drag-and-drop stage change and basic card customization. For teams running the HubSpot stage model as shipped, it works well. The gaps appear on multi-pipeline tenants, custom-object kanbans, deep filtering across custom fields, and the WIP-limit feature. Strkr allows unlimited pipelines on every paid tier, supports kanban rendering for any custom object, filters across the full schema including custom fields, and ships WIP limits as a column-header feature with an advisory overage indicator.
How does the Strkr kanban board compare to Salesforce's kanban view?
Salesforce ships a kanban view with per-record-type customization, reasonable filtering, and strong permission inheritance. The friction appears in the admin flow: every configuration change (new column, color scheme, WIP threshold) typically requires a certified admin and a sandbox deploy. Strkr's board is end-user configurable within the permission model, so a sales operations lead can add a column or change a color scheme without an admin ticket. The underlying rendering is also virtualized, so a 2,000-deal pipeline stays at 60 fps where Salesforce's standard kanban stutters above a few hundred records.
How does the Strkr kanban board compare to Pipedrive?
Pipedrive was built around the kanban board from day one, and the drag experience shows that focus. The ceiling appears on reporting depth, custom objects, custom-field filtering, and complex permission models. For a 10-rep SMB team selling simple SaaS, Pipedrive's board is as polished as any. For a 100-rep team with product-led signals, multi-year contracts, custom objects, or a layered permission matrix, the Strkr board plus the full Strkr platform is the better long-term call. The feature-level kanban parity is close; the difference is what sits around it.
Can the kanban board render pipelines with thousands of open deals?
Yes. The board uses column-level virtualization so only the visible cards are mounted in the DOM, which means a 2,000-deal pipeline across 10 columns renders in under a second and scrolls at native frame rate. The underlying query path is the same indexed Postgres path that powers the deals API, with the filter engine pushing selectivity to the database rather than filtering in the client. Pipelines up to roughly 10,000 open deals render without performance degradation; teams with pipelines larger than that typically segment by region or product line through saved views, which is a workflow improvement regardless of performance headroom.
Can stage changes made through the kanban board trigger automations?
Yes. Stage changes are first-class events in Strkr Flows, and the kanban board shares the same write path as the deal detail page, the bulk action surface, and the API. Dragging a card from Discovery to Proposal fires the standard stage-transition trigger, which can create tasks, send notifications, update forecast weights, assign a sales engineer, draft a follow-up email, or run any custom automation the admin has configured. One trigger definition fires for every entry point, so there is no "the board skipped the flow" surprise and no need to maintain parallel automation configurations per surface.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
