Feature · Sales Pipeline

The sales pipeline is where revenue is actually built.

A visual, drag-and-drop sales pipeline that lives inside the CRM. Kanban or list, multiple pipelines per team, custom stages with weighted probability, deal-rotting detection, velocity analytics, and full mobile parity. Every stage change can fire a flow. No admin certification required, no per-feature paywall, no bolt-on.

Start free trial See pricing
What a sales pipeline is for a revenue team

The visible map of every open opportunity.

A sales pipeline is the ordered sequence of stages a buyer walks through on the way to a signed deal. For a revenue team it is three things at once: a forecasting instrument, a coaching instrument, and a workflow instrument. If you can see every open deal, its stage, its age in-stage, its value, and the next step, you can run a team. If any one of those is missing, you are guessing. The pipeline is the CRM feature that pays for every other CRM feature.

Visual kanban

Every open deal on one board.

A column per stage. A card per deal. Amount, close date, owner, next step, and the age-in-stage chip visible without a click. Scan the board on Monday morning and you know what the week looks like. The visual format is not a nicety, it is how human brains process pipeline fastest.

Drag-and-drop advancement

Move a deal, trigger the motion.

Grab a card, drop it in the next column. Strkr writes the stage change, logs the audit entry, fires any attached flows (notify owner, create handoff task, update forecast), and recalculates weighted value. One drag replaces four form fields and a save button.

List view

When the board does not fit the question.

Toggle to list view for the questions kanban cannot answer: sort by amount descending, filter by stage age over 30 days, group by owner, export to CSV. Same data, different lens. Reps often live in kanban, managers often live in list.

Multiple pipelines

New business, renewal, expansion, each their own.

A new-business pipeline looks nothing like a renewal pipeline, which looks nothing like an expansion motion. Strkr lets you build and run as many parallel pipelines as your team needs, each with its own stages, probabilities, and ownership rules. Switch between them from a dropdown in the pipeline header.

Custom stages

Match your real sales motion, not a template.

Add, rename, reorder, and recolor stages per pipeline. Set per-stage default probability. Mark the final stage as closed-won or closed-lost. Strkr does not ship with a hardcoded "Discovery, Proposal, Negotiation" assumption because your motion probably does not match that assumption anyway.

Weighted forecast

Amount times probability, done automatically.

Each stage carries a default probability. Each deal carries a value. Strkr multiplies them to produce weighted pipeline value in real time at the pipeline, owner, team, and account level. Overrides on a specific deal (manually marked as commit, best case, or omitted) flow directly into the forecast module.

Deal-rotting detection

Nothing stays silent on your board.

Set a per-stage threshold. Qualified at 14 days. Proposal at 21 days. When a deal exceeds its threshold with no activity, Strkr paints the card with a warning stripe, surfaces it on the manager pipeline health view, and can fire a flow to nudge the owner. Rot is the number-one quiet killer of forecasts, and visibility is the only cure.

Mobile parity

Edit the pipeline from the airport.

The full board renders on a phone. Drag between stages works with touch. Deal detail opens in a mobile-native drawer. Fields update inline. Reps on the road are the exact users most likely to update pipeline from a parking lot, and the pipeline cannot afford a lag.

What makes Strkr sales pipeline different

The product philosophy, not just the feature list.

HubSpot Pro ships a solid pipeline but gates multiple pipelines and custom probability behind higher tiers. Salesforce has deep pipeline capability but typically requires a certified admin to configure. Pipedrive built the strongest pipeline-first product on the market but ships only a pipeline, so you need a second tool for marketing, projects, docs, and surveys. Strkr positions pipeline as the heart of the CRM and funds it like one.

Visual first, always

Kanban is the default, not the add-on.

Strkr opens on the kanban board every time. List, forecast, and velocity views are one click away but kanban is the home surface. The decision reflects how real revenue teams run pipeline review: everyone around a shared visual, not everyone staring at a spreadsheet dump.

Unlimited pipelines on paid tier

No per-pipeline paywall.

Starter ships three pipelines. Pro and above ship unlimited. New business, renewal, expansion, partner-sourced, outbound, inbound, each as its own board with its own stages. The alternative on competitor tiers is cramming everything into one pipeline and losing visibility into the real motion.

Flow hooks on every stage change

The pipeline is a trigger surface.

deal.stage_changed is a first-class flow trigger. Build "when a deal hits Proposal, generate the proposal doc from a template, email it to the primary contact, and task the AE to follow up in 48 hours" as a four-block flow. The pipeline stops being a reporting surface and becomes a motion surface.

Stage probability vs commit

Two numbers, not one.

Stage probability drives the automatic weighted forecast. Rep-level commit (commit, best case, pipeline, omitted) drives the forecast call conversation. Strkr tracks both independently so a rep can say "the system math says 60 percent but I am calling this one commit" and the manager sees both numbers side by side.

Pipeline velocity analytics

Not just where deals are, how fast they move.

Average days in each stage. Conversion rate from stage N to N+1. Win rate by stage of entry. All computed per pipeline, per owner, per segment, over a selectable window. The velocity view answers the question "where are deals getting stuck" with a chart instead of a hunch.

Group-by and color-by

Reshape the board without a dashboard.

Group the kanban by owner, by segment, by close month. Color cards by amount tier, by probability band, by age. All from a popover on the board, no admin. Managers get the view they want without filing a request against a BI tool.

Linked CRM context

Every card is a doorway, not a dead end.

Open a card. See the account, the primary contact, the last five activities, open tasks, related projects, and the stage history inline in a drawer. No tab-flip, no stale cache. The pipeline is the top of the data funnel, so the CRM surfaces beneath it are one click away.

Stage history audit

Every move logged, nothing silent.

Who moved the deal, when, from where, to where. Timestamp, user, and the activity that preceded the move. The stage history panel on every deal shows the full trail. Essential for coaching ("you jumped from Discovery to Proposal in 48 hours, what did we skip?") and essential for audit.

Bulk edit from the board

Move ten deals at once, not one at a time.

Multi-select cards with shift-click or lasso. Bulk-advance, bulk-reassign, bulk-close-lost. End-of-quarter cleanup that takes 90 minutes on competitor CRMs takes 5 minutes on Strkr because the board itself is a bulk action surface.

The buyer's math

Why native pipeline beats a bolt-on.

The default decision for most sales teams is to live inside whatever pipeline their CRM ships. The alternative, running pipeline in a spreadsheet or a standalone kanban tool and syncing to the CRM, consistently loses on five dimensions that compound into real revenue leak.

Single source of truth

The CRM wins when the pipeline lives in it.

A pipeline in a separate tool means two systems with their own definition of a deal, their own probability math, their own stage names. The sync is always a lagging reconciliation. Reps update one system, managers report from the other, numbers never line up. Native pipeline closes the gap.

Permission alignment

Pipeline respects the CRM permission model.

Native pipeline inherits the CRM permission model: territory, team, role, record ownership. A bolt-on tool runs its own permission system that drifts from the CRM every quarter. Native keeps a rep from seeing the territory next door without a sync job to re-propagate.

Automation surface

Native pipeline is a trigger surface.

A native pipeline fires deal.stage_changed into the same flow engine that handles lead routing, renewal flagging, and handoff creation. A bolt-on pipeline fires a webhook that another tool receives, parses, and acts on, assuming the webhook does not fail silently.

Mobile continuity

One mobile app for everything.

A rep on the road opens one app and sees pipeline, account, contact, email thread, and task list. A bolt-on pipeline forces them to switch between the CRM app and the pipeline app and the activity log app. Each switch is a reason not to update, and un-updated pipeline is the enemy.

Reporting cohesion

Reports and forecasts speak the same language.

When the pipeline is native, the forecast module and the reports module read directly from the same deal records. There is no reconciliation. "What is our weighted pipe" and "what is our forecast" and "what is our quarter-to-date win rate" all pull from one place.

Cost

No separate per-user bill.

Pipeline-focused tools bill between 15 and 65 dollars per user per month on top of your CRM license. For a 20-rep team that is a four- to five-figure annual check for duplication of a feature the CRM already provides. Native pipeline bills under the seat you are already paying for.

Beyond the simple board

Where pipeline tooling earns its keep.

A functional kanban is table stakes. The real differentiation shows up on the dozen scenarios that break toy pipelines: large volume, multi-currency, forecast overrides, team pipelines versus individual pipelines, cross-pipeline deals, and the forty things a growing team eventually needs.

Volume rendering

Thousands of deals on one board, still fast.

Pipelines over 2,000 open deals render with virtualized columns and lazy card hydration. Scroll, drag, filter without a stutter. The board stays interactive at a scale where competitor tools start showing spinners between every column scroll.

Multi-currency

Pipeline value in the currency of your choice.

Each deal carries its own currency and amount. The pipeline header totals in the tenant default (or a selected display currency) using the FX rate on the deal's close date. Reports retain original-currency and converted-currency columns. No manual spreadsheets.

Team pipeline views

A manager sees the territory, not just their own.

A rep sees their deals by default. A manager sees their direct reports' deals. A VP sees the full team. The scope follows the CRM reporting hierarchy automatically. "My team" and "my team's team" are first-class pipeline views without a saved filter per level.

Forecast overrides

Commit, best case, pipeline, omit.

Rep tags each deal with a commit category per quarter. The forecast module aggregates by category per rep, per team, per segment. The pipeline board visibly bands cards by commit category so a manager can scan the quarter in 30 seconds instead of opening a report.

Deal splits

Multiple owners, correct credit.

Not every deal is single-owner. Enable splits on a per-pipeline basis to credit multiple reps on one deal (AE plus overlay, inside sales plus field, partner plus direct). Splits flow into forecast and reports without double-counting the pipeline value.

Pipeline health score

One number per pipeline, computed nightly.

Combine coverage ratio, average age-in-stage, win rate trend, and conversion rate per stage into one score. Red, yellow, green. Published on the pipeline header. A quick signal for the executive asking "how is Q3 pipe looking" without a slide deck.

How teams actually run it

Five pipelines in production today.

Sales ops

New-business inbound, five stages, 300 deals.

A B2B SaaS team runs their inbound pipeline on five stages: New, Qualified, Discovery, Proposal, Negotiation. 300 open deals average. Deal-rotting kicks in at 7 days on New and 21 days on Negotiation. Flow fires a Slack ping into #sales-wins when any deal crosses into Qualified.

Customer success

Renewal pipeline, 90-day forward view.

A CS team runs a renewal pipeline parallel to the AE pipeline. Three stages: At Risk, On Track, Committed. A flow fires 90 days before any renewal_date to create a card in this pipeline. The CSM moves the card based on health signals and QBR notes. The forecast module reads this pipeline for renewal commit.

Expansion motion

Account expansion as its own board.

A separate pipeline for upsell and cross-sell opportunities. Four stages: Signal, Discovery, Proposal, Closed. Cards fire a Slack ping to the AE and the CSM together when they land. Separates net-new acquisition reporting from expansion reporting and keeps the forecast conversation honest.

Partner-sourced

Partner-attributed deals on a dedicated pipeline.

Partner-sourced opportunities route into their own pipeline with partner_id required on the card. Stage transitions fire flows that update the partner portal and credit the partner against the quarterly MDF commitment. The partner team sees exactly what their program sourced without a filter.

RevOps

Quarterly cleanup via bulk actions.

End of quarter, revops multi-selects every deal older than 60 days with no activity, marks them closed-lost with a reason code of "stalled, no response." Thirty minutes of board work that used to be a half-day of spreadsheet reconciliation. The clean board goes into the QBR with no apology.

Sales leadership

Monday pipeline review on the board, not a deck.

The leadership team runs weekly pipeline review directly on the kanban board, filtered to deals over 50k closing in the current quarter. Group by owner, color by probability. Reps walk their column live. The meeting is 25 minutes instead of 60 because nobody needs a slide to show what everyone can see on screen.

Sales pipeline on every paid tier, no per-pipeline paywall.

Starter ships three pipelines, Pro and above ship unlimited. Visual kanban, list view, weighted forecast, deal-rotting detection, mobile parity, and flow hooks included on every tier. Build your first pipeline in under 15 minutes.

Start free trial See pricing
Common questions

What buyers ask about this feature.

What is the difference between a sales pipeline and a sales funnel?

A pipeline is the ordered sequence of stages a specific deal moves through on the way to a close, viewed from the seller's perspective. A funnel is the aggregate conversion math across all deals, viewed from the business's perspective. Pipeline lives on the kanban board. Funnel lives in a report. Strkr builds both, but the pipeline is where reps work day-to-day and the funnel is where leaders review conversion math across cohorts.

How many pipelines can my team run on Strkr?

Starter ships three pipelines. Pro, Scale, and Enterprise ship unlimited. Most mid-market teams land between four and seven pipelines in production: new business, renewal, expansion, partner-sourced, and sometimes one per product line. Running separate pipelines is almost always better than cramming everything into one, because the stage definitions and probability math diverge sharply across motions.

How does Strkr sales pipeline compare to Pipedrive?

Pipedrive built the strongest pipeline-first product on the market and remains a solid choice if a visual pipeline is literally the only CRM feature you need. The limitation is that Pipedrive is a pipeline product, so marketing, project delivery, docs, surveys, and messaging all require separate tools and integrations. Strkr builds pipeline with the same visual-first discipline but ships it inside a full CRM, so one platform covers lead-to-cash with one license.

Can non-admins build and edit sales pipelines in Strkr?

Yes, by permission. The CRM admin can grant pipeline.customize to specific roles (typically sales ops and sales leadership). Those users can add, rename, reorder, and recolor stages, set per-stage probability, and configure deal-rotting thresholds from the pipeline settings page. No certification required, no professional services engagement. For context, Salesforce typically requires a certified admin or a consulting partner for the same level of pipeline customization.

How does Strkr handle deal probability and weighted pipeline value?

Each stage carries a default probability (configurable per pipeline). Each deal carries an amount and a close date. The weighted value is amount multiplied by probability, computed in real time at the deal, owner, team, and pipeline level. On top of the automatic math, reps tag deals with a commit category (commit, best case, pipeline, omitted) that drives the forecast call conversation. The two numbers are tracked independently and surfaced side by side.

Does Strkr sales pipeline work on mobile?

Yes, with full parity. The kanban board renders on a phone, drag-between-stages works with touch, the deal detail opens in a mobile-native drawer, and every field is editable inline. Reps on the road are the users most likely to update pipeline from a parking lot or an airport gate, so mobile is not a stripped-down version of the desktop view, it is the same board rendered for a smaller screen.

Can stage changes trigger automated workflows?

Yes. deal.stage_changed is a first-class trigger in the Strkr flow engine. Build "when a deal hits Proposal, generate the proposal doc from a template, email it to the primary contact, task the AE to follow up in 48 hours, and notify the manager in Slack" as a visual flow with no code. The flow runs atomically, logs every step, and the pipeline board shows a chip on the card for the flow that fired.

What is deal-rotting detection and why does it matter?

Deal-rotting detection flags deals that have sat in a stage past a per-stage threshold with no activity. On a kanban board, those cards paint with a warning stripe. On the pipeline health view, they aggregate as a number per owner. The quiet killer of every forecast is a deal that stops moving but never gets marked as lost. Making rot visible on the board, instead of hidden in a report, is how teams keep their pipeline honest without a weekly manager scrub.

Related features

Pair this with...

Flows (automation) Forecasting Lead Routing Reports Workflow Automation

Try it free. Bring your team next week.

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.

Start free trial See pricing