Pipeline stages work when the stage definition carries weight, exit criteria, and expected activity. Strkr ships seven default stages plus templates for high-velocity, enterprise, PLG, and channel motion, each with weight percentages, exit criteria, and AI drafting that respects the stage definition.
The sales pipeline stage design conversation shows up every 18 to 36 months inside a growing revenue team. The CRO walks into a quarterly business review and realizes the stage definitions are stale, inconsistent across managers, and nobody can defend the weighting. The pain points below are what Strkr hears from revenue leaders redesigning their stages.
Three managers running three teams define Qualify three different ways. One wants BANT, one wants a budget conversation, one wants three discovery calls. The forecast rolls up across inconsistent definitions. Strkr ships stage definitions with exit criteria printed on each card so reps and managers share the same bar for stage change.
The default stage probability (Qualify 20 percent, Propose 40 percent, Negotiate 70 percent) is a convention from mid-2000s Salesforce documentation. The weight does not reflect your actual close rates. Strkr lets admin tune stage weight per team or per segment, and the weighted forecast calibrates to your historical close rate on similar deals.
A stage like Verbal gets added to catch deals waiting on signatures. Over 18 months the stage either empties out (reps skip it) or clogs (reps park deals there). Strkr prints stage-use analytics showing average time in each stage, exit rate, and skip rate. The admin tunes the stage based on real data.
Teams running new business, renewal, and expansion as one pipeline carry stage definitions that fit none of the three motions. Strkr supports multi-pipeline configuration with motion-specific stages. New business runs the seven-stage flow. Renewal runs a four-stage renewal flow. Expansion runs a five-stage expansion flow.
Exit criteria lives in a 60-page sales playbook deck nobody opens. The rep moves a deal from Qualify to Propose based on gut feel. The forecast suffers. Strkr prints exit criteria on the deal card so the rep sees what qualifies the stage change at the moment of the decision.
A rep hitting a quarter miss sometimes rushes deals through stages to inflate pipeline. Strkr prints a stage-change audit showing deals that skipped stages, deals that spent less than 48 hours in a stage, and deals that moved backward. The sales leader catches the pattern before the quarter miss.
The seven-stage default pipeline ships for mid-market B2B motion. Each stage carries a weight percentage, exit criteria, expected activity, and typical duration. The cards below walk through the seven stages.
Prospect weighs 5 percent. Exit criteria: fit criteria confirmed (ICP match on industry, size, geography), initial contact attempted. Expected activity: one outbound email, one connect attempt. Typical duration: 3 to 10 days before advancing or disqualifying.
Discover weighs 10 percent. Exit criteria: discovery call held, pain identified, authority surfaced (buyer or Champion role mapped). Expected activity: discovery call summary logged with SPIN or MEDDPICC pain fields populated. Typical duration: 5 to 21 days.
Qualify weighs 20 percent. Exit criteria: budget conversation held, decision timeline confirmed, next steps mutually agreed. Expected activity: second meeting with wider buyer group, mutual close plan started. Typical duration: 10 to 30 days.
Propose weighs 40 percent. Exit criteria: proposal delivered, pricing shared, decision process mapped, Economic Buyer verified. Expected activity: demo tailored to pain, proposal reviewed with Champion. Typical duration: 7 to 21 days.
Negotiate weighs 70 percent. Exit criteria: contract redlines in play, legal involved, pricing finalized, implementation plan outlined. Expected activity: contract version 2 or later, legal review, procurement engagement. Typical duration: 7 to 30 days.
Verbal weighs 90 percent. Exit criteria: verbal commit from Economic Buyer, contract out for signature, close date within 14 days. Expected activity: signature chase cadence active. Typical duration: 2 to 10 days.
Closed Won weighs 100 percent. Exit criteria: contract signed, onboarding assignment made, customer success handoff logged. Expected activity: closed-won onboarding workflow triggered. The handoff workflow fires the customer success assignment and the initial kickoff email.
Not every revenue motion fits the seven-stage default. Strkr ships four alternative templates for common motions. The cards below describe each template.
High-velocity motion (SMB inside sales, under 30-day cycles) runs four stages: Qualified, Demo, Trial, Won. Weight: 15, 40, 70, 100. The template fits teams running trial-based conversion with sub-$10,000 ACV. Stage durations are measured in days, not weeks.
Enterprise motion runs nine stages: Target, Engage, Discover, Validate, Propose, Legal, Procurement, Verbal, Won. Weight: 2, 5, 10, 20, 40, 60, 80, 90, 100. The extra stages reflect the stakeholder, legal, and procurement gates typical of enterprise motion. Durations measured in weeks and months.
PLG motion runs five stages: Signup, Activated, Qualified, Expansion, Won. Weight: 1, 5, 20, 50, 100. The pipeline tracks product usage signals (users invited, workflows run, integrations connected) as stage criteria. Sales-assisted layer kicks in at Qualified stage.
Channel motion runs six stages: Registered, Engaged, Qualified, Co-sold, Verbal, Won. Weight: 5, 15, 30, 50, 90, 100. The pipeline tracks partner attribution, deal registration status, and partner commit. Partner comp calculation ties to the Won event.
Renewal motion runs four stages: Approaching, Health Review, At Risk, Renewed. Weight: 50, 70, 40, 100. The pipeline tracks customer health signals (NPS, usage, support ticket volume) as stage criteria. Renewal risk flagging ties to the Health Review stage.
Admin can design a custom pipeline from scratch with any number of stages, custom weight percentages, custom exit criteria, custom expected activity, and custom typical duration. The pipeline design surface accepts drag-and-drop ordering, inline weight editing, and criteria configuration.
Pipeline stages drift over time. Strkr ships stage-use analytics so the sales leader sees how stages behave against the design. The cards below describe the analytics surfaces.
The time-in-stage report shows median and 90th percentile time for every stage across the last 90 days. The 90th percentile catches the stuck deals. The median shows whether a stage is running at expected cadence or dragging. The sales leader uses the view to find stage drift.
The stage conversion funnel shows the percent of deals in each stage that advance to the next stage. A Qualify-to-Propose conversion of 85 percent might mean reps are rushing. A conversion of 20 percent might mean the Qualify bar is too high. The admin tunes exit criteria based on the funnel.
The skip detection report flags deals that moved from Qualify to Verbal in one jump, or from Discover to Negotiate. The pattern is almost always a rep behavior that bypasses the discovery or proposal step. The manager addresses the pattern in the 1:1.
The backward-move report flags deals that moved from Propose back to Qualify, or from Negotiate back to Propose. The pattern often indicates a Champion loss or a decision process reset. The flag surfaces on the manager cockpit for immediate attention.
The stage velocity report measures days from stage entry to Won for every stage. For a healthy motion the time from Qualify to Won might be 45 days. If the stage velocity stretches to 90 days the deals are not progressing. The sales leader sees velocity trend over quarters.
The stage-exit coaching report flags reps who move deals through stages without completing the exit criteria (missing MEDDPICC fields, missing next steps, missing discovery call summary). The manager uses the report in the 1:1 to tie coaching to specific behavior.
The comparison below is Strkr pipeline stage configuration versus the typical mid-market CRM stage model.
| Feature | Strkr | Rigid CRM stage configuration |
|---|---|---|
| Stage weight tunable | Per team, per segment. | Fixed defaults. |
| Exit criteria on card | Printed inline. | Buried in playbook deck. |
| Multi-pipeline | New business, renewal, expansion. | Single pipeline typical. |
| Alternative templates | High-velocity, enterprise, PLG, channel. | Default only. |
| Stage-use analytics | Time, conversion, skip, backward. | Basic time-in-stage only. |
| Stage change enforcement | Required fields block advance. | No gate logic. |
| AI drafting per stage | Stage-aware next step suggestion. | Generic draft. |
| Historical close rate math | Team-specific calibration. | Static probability. |
| Flat per-seat pricing | Starter $29, Pro $59, Scale $119. | Credit meters and add-ons. |
The playbooks below are patterns Strkr onboarding sees across pipeline stage design conversations.
A 24-rep team selling into enterprise accounts ran a seven-stage pipeline but the stages did not reflect the legal, procurement, and verbal commit gates typical in enterprise motion. Strkr onboarding configured the nine-stage enterprise template. The forecast accuracy improved because the stages caught the hidden gates.
A 42-rep high-velocity SaaS startup ran the default seven stages but had sub-30-day cycles where stages collapsed into one call. Strkr onboarding configured the four-stage high-velocity template. Rep adoption climbed because the stages matched the real motion.
An 85-rep team ran new business, renewal, and expansion through one pipeline. The CRO could not read the forecast because the motions mixed. Strkr onboarding configured three separate pipelines with motion-specific stages. The forecast rolled up with motion attribution. The CRO got clarity for the first time in two years.
A 48-rep SaaS team ran the default stage weights but their actual close rate at Propose was 55 percent, not 40 percent. Strkr onboarding calibrated the weights to the team-specific historical close rate. Forecast variance tightened by 11 percentage points in two quarters.
A 30-rep PLG SaaS team ran a pipeline that treated signup, trial, and expansion as sales stages. Strkr onboarding configured the five-stage PLG template with product usage signals as stage criteria. Sales-assisted engagement ticked up for accounts in the Qualified stage. Expansion revenue grew 42 percent year over year.
Book a 30 minute call. We will walk through the seven-stage default, the four alternative templates, and the stage-use analytics with your actual deal flow.
Most mid-market B2B teams run between five and nine stages. The seven-stage default (Prospect, Discover, Qualify, Propose, Negotiate, Verbal, Won) fits the median mid-market motion. High-velocity teams run four stages because the sales cycle collapses too fast for seven to be useful. Enterprise teams run nine stages because the legal, procurement, and verbal commit gates deserve their own stages. The right number is the number that reflects the real motion, not the number that fits a playbook.
Yes. Teams running new business, renewal, and expansion can run three separate pipelines with motion-specific stages. New business runs the seven-stage flow. Renewal runs the four-stage renewal flow. Expansion runs the five-stage expansion flow. The forecast rolls up across pipelines with motion attribution. The CRO sees one weighted forecast number with the motion mix.
Strkr prints exit criteria on each stage card so the rep sees what qualifies the stage change. For teams that want hard enforcement the admin can require specific fields (Economic Buyer, Metric value, Decision Process) before a stage change advances. For teams that prefer soft enforcement the stage change allows but flags the gap in the audit log for manager review. Most teams start soft and move to hard enforcement in month three.
After 90 days of Strkr history the weighted forecast adjusts for team-specific close rate on deals that look similar. The admin can tune stage weights explicitly per team or per segment to override the historical calibration. For enterprise teams with sparse data the admin can set weights based on industry benchmarks (Qualify 20 percent, Propose 40 percent, Negotiate 70 percent) and refine over time.
Strkr is HIPAA compliant with a BAA available on request, GDPR and CCPA compliant today, and SOC 2 Type II is in progress with a target of 2026-Q4. Pipeline configuration changes track in the audit log with before and after snapshot. Stage change events on individual deals log with the rep, timestamp, and field changes. 90-day default retention tunable per tenant. SSO via SAML or OIDC is live on Scale tier through Clerk.
Pipeline stage configuration ships at every tier. Starter at $29 per user per month ships the seven-stage default with weight tuning. Pro at $59 per user per month ships multi-pipeline support, alternative templates, and stage-use analytics. Scale at $119 per user per month adds custom role scoping on stage configuration, deeper audit retention, and SSO through Clerk. There is no per-pipeline charge and no stage-count limit.
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.
