The deal path, redesigned. Named stages, enforced exit criteria, and funnel geometry that holds up to scrutiny.
A sales pipeline is the deal path a buyer walks from first touch to signed order. Most CRMs let you name stages and stop there. Strkr ships stage definitions, exit criteria enforcement, stage SLAs, probability weighting, and funnel analytics as one coherent surface.
Every B2B sales team has a pipeline, and almost none of them have a deal path that is actually enforced. The stages are named well enough. The exit criteria exist as a Google Doc the sales ops lead circulated 18 months ago that nobody has reread. A rep moves a deal to "Proposal" because they emailed a PDF, not because the buyer agreed on scope and budget. The forecast rolls up those stage labels as if they meant something. By Q2 the funnel geometry is noise, the stage conversion rates look fine on paper, and the manager cannot tell which stages are actually leaking. The six pain points below are the ones that come up on every pipeline-redesign demo call.
Stages that mean different things to different reps
"Qualified" means something different on every account team.
When exit criteria live in a shared Google Doc instead of the CRM, every rep interprets the stage definition slightly differently. One rep treats "Qualified" as BANT-complete; another treats it as "they took the second call." The funnel geometry rolls up with mixed definitions, so the stage conversion rate is noise. Strkr ships exit criteria as structured checklist items on the stage definition, visible on every deal in that stage, and configurable to require completion before the stage advances.
The Proposal stage swallows deals
Deals age in Proposal for 60 days and nobody catches it.
The Proposal stage is where mid-market pipelines go to die, and most CRMs offer no way to enforce a stage SLA. A deal sits in Proposal for 60 days with the next-step field reading "waiting on their legal team" and the manager does not realize until the quarterly review. Strkr runs stage SLAs as a nightly check and flags any deal past the configured threshold (typically 7 to 21 days per stage). The flag lands in the manager's coaching queue before the stall becomes a slipped quarter.
Probability percentages pulled from the air
Discovery = 25%, Proposal = 60%. On what basis?
Default pipeline probabilities (25% at Discovery, 50% at Proposal, 75% at Negotiation) are either copied from a Salesforce template or pulled from a RevOps lead's intuition. The actual historical conversion rate from Discovery to Won on a team's book is almost never 25%. Strkr computes stage probability from the team's own trailing-quarter data and surfaces the drift between the configured probability and the actual conversion, so the manager calibrates against reality.
Lost reasons that are useless
"No budget" and "no decision" cover 70% of lost deals.
Most CRMs ship a lost-reason picklist with ten options. Three of them get used (price, no decision, lost to competitor), the other seven get ignored. The data is useless for pipeline redesign because every lost deal looks the same. Strkr ships a two-layer lost-reason model: a required category plus a required second-level detail that varies by category, so "lost to competitor" asks which competitor and on which dimension. The quarterly lost-deal review opens with actual patterns, not three buckets.
Stage skipping that nobody logs
A deal moves from Discovery to Closed Won. Nobody asks why.
Occasionally a rep marks a deal Closed Won from Discovery without the deal walking through Proposal, Negotiation, or Verbal. Usually there is a legitimate reason (small-dollar expansion, warm referral with existing budget), but the funnel analytics treat the deal as if it skipped stages. Strkr captures stage-skip events as structured data with a reason field, so the pipeline report can separate "proper walkthroughs" from "exceptional closes" and the funnel geometry stays interpretable.
Multiple paths for one pipeline
Inbound and outbound deals need different stages.
An inbound deal from a form fill walks a different path than an outbound deal from a cold email: the first few stages are different, the qualification evidence is different, the time per stage is different. Most CRMs force both deals onto one pipeline, so the stage conversion report mixes paths and produces noise. Strkr supports multiple deal paths in one workspace (inbound, outbound, partner-sourced, expansion), each with its own stage set and exit criteria, so the manager can read the actual geometry.
Designing the deal path
The surfaces that make stage design a one-afternoon job.
Pipeline redesign is usually a two-week project that requires a RevOps lead, three stakeholder interviews, and a change-management plan. Strkr ships the design surface as a focused admin screen so a manager can draft the new path in a morning, pilot it on a test tenant, and roll it to the team the following Monday. The cards below are the pieces that make stage design actually fast.
Stage builder
Named stages with order, color, and category.
The stage builder is a drag-ordered list with name, color, category (Open, Won, Lost), and position. The admin can rename, reorder, and recolor stages without a migration script. Changes propagate to open deals immediately. The feature exists because pipeline redesign iterations should take minutes, not hours.
Exit criteria checklist
Structured requirements per stage, enforced or advisory.
Each stage carries an exit criteria checklist: BANT fields complete, mutual action plan drafted, decision maker identified, demo completed, pricing shared. Each item is either required (blocks stage advancement) or advisory (shows a warning). The admin sets the mode per item. Deals that attempt to advance without required items complete surface a confirmation dialog explaining what is missing.
Stage SLA
Days-in-stage threshold per stage, flag past the limit.
Each stage carries a target duration (Discovery = 14 days, Proposal = 7 days, Negotiation = 10 days, etc.). Strkr runs a nightly job and flags any deal past the threshold on the manager's coaching queue. The threshold is based on the team's own historical median duration by default; the admin can override. SLAs replace the manager's private spreadsheet of "deals I need to check on" that was always three days stale.
Historical probability auto-fit
Stage probability computed from the team's own data.
Strkr computes stage probability as a trailing-4-quarter conversion rate from each stage to Closed Won on the team's own deals. The admin sees the configured probability versus the computed probability side by side and can adopt the computed value with one click. The feature replaces the "Discovery = 25%, Proposal = 60%" guesswork with actual math.
Multiple deal paths
Inbound, outbound, partner, expansion each as their own pipeline.
Strkr supports multiple deal paths in one workspace, each with its own stage set, exit criteria, and SLAs. A deal is created on a path (inbound, outbound, partner-sourced, expansion, renewal) and the path is captured on the record. Reports can scope to a single path or roll up across paths. The feature is required for any team that runs mixed inbound and outbound motions and needs the funnel analytics to stay clean.
Lost reason two-layer picklist
Category plus detail; detail depends on category.
Lost reason has two layers: a required top-level category (Price, No Decision, Competitor, Timing, Fit) and a required second-level detail that varies by category. "Competitor" asks which competitor and on which dimension (price, features, incumbent). "Timing" asks the push reason (budget cycle, project paused, personnel change). The quarterly retro reads actual patterns instead of three undifferentiated buckets.
Stage change audit
Every stage move captured with user, timestamp, reason.
Every stage advance, push, or skip is captured as an event with user, timestamp, from stage, to stage, and optional reason. The audit log is on the deal record and queryable across the workspace. Stage-skip events require a reason field. The audit replaces reconstructing "when did this deal actually enter Proposal" from activity notes six weeks later.
Stage change triggers
A stage move fires an automation flow.
When a deal moves to a named stage, Strkr fires a workflow: send an internal notification, assign a solutions engineer, create a mutual action plan, start a nurture sequence, kick off a legal review ticket. The trigger is wired in the Flows module with full access to the deal record and related objects. The feature replaces the manager's mental checklist of "when a deal hits Proposal remind me to do X" with actual automation.
Pilot mode
Test the new deal path on a subset of reps first.
The admin can pilot a new deal path on a subset of reps or teams before rolling to everyone. Reports can filter to the pilot cohort to see whether stage conversion rates and velocity improve on the new path. The feature exists because pipeline redesigns that ship team-wide on day one usually get rolled back by day fourteen when a corner case breaks.
Funnel geometry you can read
Conversion, velocity, and leak detection without a BI tool.
Funnel analytics is where pipeline redesign pays back: a stage with a 70% drop-off rate is a design problem, not a rep problem. Most CRMs ship a static funnel chart and leave the actual leak detection as a BI exercise in Tableau or Looker. Strkr ships funnel geometry as a native surface on the pipeline report with conversion, velocity, and leak flags per stage.
Conversion heatmap
Stage-to-stage conversion rates with color coding.
The conversion heatmap shows the conversion rate from each stage to the next in a trailing-quarter window with red, amber, green color coding. A stage with a conversion rate below the team's median by more than one standard deviation gets a red flag. The admin reads the heatmap in 30 seconds and knows which stage transition is leaking.
Velocity per stage
Median days in stage over trailing quarters.
Velocity is tracked as median days in stage over the trailing quarters, with the team's baseline and the current quarter side by side. A stage that is slowing down shows up as a trending-up line. Velocity drives the stage-SLA calibration conversation each quarter so the SLAs stay honest.
Leak detection
Where deals disappear versus where they advance.
Leak detection groups lost deals by stage and category to show which stage transitions are producing the losses. A Proposal-to-Negotiation leak at 50% with "price" as the dominant category is a packaging problem. A Discovery-to-Proposal leak with "no decision" is a qualification problem. The report surfaces the pattern in a one-screen view so the manager can run the right redesign conversation.
Deal-path comparison
Inbound vs outbound funnel geometry side by side.
If the workspace runs multiple deal paths, the report can compare funnel geometry across paths. Inbound Discovery to Won is 18% at a 45-day cycle; outbound is 7% at a 72-day cycle. The data drives the resource allocation conversation (how many SDRs versus how much paid media spend) with actual numbers instead of intuition.
Cohort view
How did last quarter's pipeline convert versus this quarter.
A cohort view groups deals by the quarter they entered the pipeline and tracks the full walk. A deal created in Q1 that closes in Q3 counts in the Q1 cohort. The view separates pipeline-generation performance from pipeline-conversion performance, which are two different jobs on different timescales.
Stage-skip report
How often deals skip stages and why.
Stage-skip events are captured with reasons, so the admin can see what fraction of Won deals walked the full path and what fraction skipped. A healthy pipeline has a small single-digit skip rate; a 30% skip rate means the stage definitions are not matching how deals actually flow and the design needs revisiting.
Deal path on a real team
The admin cadence that keeps the path honest.
A deal path is not a one-time admin setup. It is a quarterly recalibration ritual that keeps the funnel geometry useful as the team's selling motion evolves. The cards below are the admin cadence a Strkr customer runs to keep the path from drifting into noise over 18 months of growth.
Quarterly stage review
A 90-minute meeting where sales + RevOps read the funnel.
Each quarter the sales leader and RevOps lead run a 90-minute stage review. They read the conversion heatmap, the velocity trend, the lost-reason patterns, and the stage-skip rate. The output is a short list of adjustments: tighten an exit criterion, split a stage, merge two stages, revise an SLA threshold. The ritual is on the calendar as a recurring block so the recalibration actually happens.
Lost-deal retro
A monthly review of 10 lost deals selected by variance.
Each month the manager pulls 10 lost deals from the trailing month, selected to span lost reasons and deal sizes. The team reads the deal narrative, the stage transitions, and the final lost reason. The retro surfaces pattern issues that the quarterly funnel review would miss. The output is a note on the deal path doc with "watch for X" entries that drive the next quarter's stage review.
Probability recalibration
Auto-fit stage probability each quarter.
Strkr recomputes stage probability from the trailing 4 quarters each month and surfaces the drift from the configured value. The admin accepts or rejects the auto-fit per stage. Over 6 quarters the configured probabilities drift toward the team's actual conversion math, so the forecast weighting stays honest without a RevOps lead manually tuning the numbers.
Exit criteria audit
Which criteria are being skipped and why.
Strkr tracks exit criteria completion rate per stage. A criterion that is completed on 95% of advancing deals is working. A criterion completed on 20% is either a bad criterion, poorly enforced, or widely bypassed with the override dialog. The audit flags the low-completion items for review at the quarterly stage meeting.
Pilot before rollout
New paths tested on a cohort before team-wide.
Any stage redesign that touches the exit criteria, the SLA, or the probability runs as a pilot on a subset of reps for one full sales cycle before rolling to the full team. The pilot cohort reports side by side with the control, so the redesign ships on data, not intuition. The feature exists because pipeline redesigns that ship team-wide tend to get reverted when a corner case breaks.
Rollback and version history
Every path version stored; one-click rollback.
Each deal-path version is stored as a snapshot with timestamp and author. A rollback to a prior version is a one-click action from the admin screen; open deals continue to use the version they were created on until the admin runs a migration pass. The versioning replaces the "which Google Doc has the right stage definition" question that comes up every three months.
Head-to-head
Strkr deal path vs HubSpot pipelines.
HubSpot pipelines are the common incumbent for mid-market B2B teams running inbound-heavy motions. The surface works, but the design cadence falls on the admin. Here is the head-to-head.
Feature
Strkr
HubSpot Pipelines (Sales Hub Pro + Operations Hub)
Named stages with order and color
Native, drag-ordered, propagates to open deals immediately
Native; similar capability
Exit criteria as structured checklist
Required vs advisory per item; blocks advancement when required
Required properties per stage; limited enforcement
Stage SLA with nightly flag
Native per-stage threshold with coaching-queue surfacing
Workflow-based; must build per stage
Auto-fit stage probability
Computed from trailing 4 quarters; one-click adopt
Static or revenue analytics add-on
Multiple deal paths in one workspace
Native; each with own stages, SLAs, exit criteria
Multiple pipelines; shared property schema
Two-layer lost reason
Category + category-dependent detail; both required
Single picklist; custom properties for second layer
Stage-skip audit
Captured as structured event with required reason
Activity log; no structured skip event
Conversion heatmap with red/amber/green
Native report surface
Funnel report; limited color coding
Pilot mode for new path
Subset rollout with cohort comparison
Not native; requires separate pipeline + manual compare
Version history + rollback
Every path version stored; one-click rollback
Audit log; manual revert
How teams use Strkr
How teams redesign the deal path with Strkr.
Teams that move to Strkr for the deal-path story tend to run the redesign in the same shape: audit the current path, draft the new path, pilot on a cohort, roll to the team, recalibrate at quarter end. The playbooks below are motions live on customer accounts today.
Mid-market SaaS, 28 reps, 2 motions
Split inbound and outbound into separate deal paths.
A 28-rep SaaS team ran inbound and outbound deals on one pipeline for three years. The funnel geometry was useless because inbound deals walked a 45-day path and outbound deals walked an 80-day path, and the stage conversion rates mixed into noise. The team split into two deal paths in Strkr with path-specific stages and SLAs. One quarter later the admin could see inbound Discovery-to-Won at 18% and outbound at 7%, which drove a resource reallocation worth roughly $340k in annual pipeline from reassigning two SDRs onto the stronger motion.
Agency sales, 14 AEs
Exit criteria enforcement cut cycle time by 11 days.
A 14-AE agency sales team shipped exit criteria as advisory checklists for one quarter, then flipped the three highest-leverage items (BANT complete, decision maker identified, mutual action plan drafted) to required. Rep complaints lasted a week; stage velocity improved for two months. The median deal cycle dropped from 68 days to 57 days in the first full quarter, and the Discovery-to-Proposal conversion rate climbed 9 points because reps stopped moving deals forward with incomplete qualification evidence.
Enterprise FinServ, 22 reps
Stage SLA caught the Proposal stall before Q2 close.
An enterprise FinServ team had Proposal-stage deals aging past 45 days quietly. The manager spotted the pattern on a Monday after Strkr's stage SLA job flagged 7 deals past the 21-day threshold. The team ran a coaching intervention on all 7 in the following week; 4 closed within 30 days and 2 disqualified cleanly. The intervention recovered roughly $220k in committable pipeline that would have slipped the quarter under the old visibility.
B2B expansion team, 8 CSMs
Expansion deals got their own path.
An 8-CSM expansion team ran expansion deals on the same pipeline as new logo. Expansion deals walked a 20-day cycle with no cold outreach stages, so the funnel geometry mixed badly with new-logo deals walking 60-day cycles. The team built an Expansion deal path in Strkr with four stages (Opportunity Identified, Scoped, Approved, Closed) and dedicated exit criteria. The expansion motion's win rate and velocity data stayed clean, which drove a quarterly review conversation that spun up a dedicated expansion comp plan.
Series B SaaS, 18 reps
Two-layer lost reason surfaced a packaging problem.
A Series B SaaS team ran a quarterly lost-deal retro and found that 38% of lost deals had "lost to competitor" as the top-layer reason. Before the two-layer picklist in Strkr, that was where the data stopped. With the second-layer detail required ("which competitor" and "on which dimension") the retro surfaced that 65% of competitor losses were to one competitor on the pricing dimension. The finding drove a packaging change in the following quarter that cut competitor losses on that dimension roughly in half.
A deal path that holds up to a quarterly board review.
Start a 14-day trial with the deal-path surfaces live: structured exit criteria, stage SLAs, auto-fit probability, multiple paths per workspace, pilot mode, version history. See how pipeline redesign fits into an afternoon.
How is a deal path different from a sales pipeline?
A sales pipeline is the thing you see on a Kanban board: cards in named columns. A deal path is the full design behind that board: the stages, the exit criteria, the stage SLAs, the probability weights, the automation triggers, the version history. Most CRMs ship the pipeline (the Kanban view) and leave the deal-path design as an admin's weekend project in Google Docs. Strkr treats the deal path as a first-class design surface with structured exit criteria, native SLA enforcement, auto-fit probability, pilot mode, and version history. The result is a pipeline you can actually recalibrate quarterly instead of a Kanban board whose stage definitions drift into noise over 18 months.
How many deal paths should a mid-market B2B team run?
The pragmatic range is 2 to 4. One pipeline is almost always too few because inbound and outbound deals walk fundamentally different cycles and mixing them produces noise. Four plus is usually too many because the admin overhead of keeping exit criteria consistent across paths outstrips the analytical gain. Most mid-market B2B customers run 3 paths: inbound (form fill, website chat, warm referral), outbound (SDR-sourced, cold email), and expansion or renewal (installed base). Teams with heavy partner motions sometimes add a fourth path. The design decision should fall out of whether the funnel geometry on each candidate path is meaningfully different; if two candidate paths have similar stage conversion and velocity, they are one path.
How do you set stage SLAs without just copying what the last CRM had?
Strkr computes a baseline SLA for each stage from the trailing-4-quarter median duration on the team's own deals, with a plus-one-standard-deviation ceiling. The admin accepts or overrides. The baseline is almost always more honest than the SLA copied from a Salesforce template or set by intuition. The admin should ship the baseline for the first quarter, read the coaching queue flag rate (if 40% of deals are flagged, the SLA is too tight; if 2% are flagged, too loose), and recalibrate at the quarterly stage review. Over 2 to 3 quarters the SLAs settle at values that are tight enough to catch stalls and loose enough that reps are not fighting the system.
Can Strkr enforce exit criteria without reps revolting?
Yes, when the enforcement is layered. Start with every exit criterion as advisory for one quarter so reps see the warning dialog but can still advance deals. Review the completion rate at the quarterly stage meeting and pick the two or three highest-leverage criteria to flip to required. Repeat the next quarter. The rolled-out layering gives reps time to adapt the discovery habits before the system blocks them. Teams that ship every criterion as required on day one usually get rep complaints, workaround patterns (bogus checkbox completion), and a rollback within a month. Teams that layer in over 2 to 3 quarters end up with 4 to 6 enforced criteria that genuinely improve pipeline hygiene without creating adversarial behavior.
How does the auto-fit probability compare to Einstein Deal Insights or similar AI probability tools?
Strkr's auto-fit is a straightforward conversion-rate calculation from the trailing 4 quarters: of all deals that entered stage X, what fraction eventually reached Closed Won. The number is deterministic, auditable, and defensible to a CFO reviewing the forecast methodology. Einstein Deal Insights, Clari's AI projection, and similar tools layer a machine-learned score on top of per-deal features (activity volume, email sentiment, engagement signals). Those scores are often more accurate on a per-deal basis but harder to defend in a quarterly board review because the inputs are opaque. Strkr ships both: the auto-fit conversion rate as the baseline probability, plus a per-deal risk score for coaching surfaces. The two layers serve different jobs.
Is Strkr deal-path data queryable through an API or just the UI?
The deal-path configuration, stage history, exit criteria completion, and funnel analytics are all available through the open REST API with webhooks. A RevOps team can pull stage transitions into a BI warehouse (Snowflake, BigQuery, Redshift) in real time via webhooks or on a schedule via the API. The webhook payloads include the full event detail: user, timestamp, from stage, to stage, reason, exit criteria completion state at time of transition. Teams that run deep BI on their funnel geometry tend to combine the Strkr-native analytics for day-to-day pipeline reviews with a warehouse-backed Looker or Tableau dashboard for the quarterly board deck.
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.
