Feature · Opportunity Pipeline

Run every opportunity through a pipeline the whole team trusts.

A production-grade opportunity pipeline for enterprise and growth-stage teams. Stage definitions with entry and exit criteria, deal fields, forecast categories, velocity metrics, and the activity history the manager actually needs for coaching.

What an opportunity pipeline actually is

Six observations about the opportunity object.

An opportunity pipeline is not just a Kanban board of deals; it is a serious artifact of the revenue motion. The six observations below ground the discussion. A team that gets the opportunity model right typically runs 20 to 30 percent higher win rates than a team running on a loose lead-and-contact model without an opportunity layer.

Separate from lead

An opportunity is a qualified pursuit.

An opportunity (sometimes called a deal) is a qualified pursuit with a defined buyer, product, and expected close. It is distinct from a lead (unqualified contact) and from an account (ongoing customer relationship). The separation matters because the motion, the metrics, and the ownership differ for each.

Associated with an account

Every opportunity rolls up to an account.

Every opportunity associates to exactly one account. The account carries the ongoing relationship (contacts, past deals, support history, product usage). The opportunity carries the pursuit. The account-opportunity model is standard across enterprise CRMs and reflects real B2B motion.

Multiple opportunities per account

A single account can carry many open pursuits.

An enterprise account typically carries multiple opportunities over time: initial land, cross-sell to a second product, renewal, upsell. Each one has its own stage, amount, close date, and owner. The account roll-up shows the full picture, while each opportunity has a focused lifecycle.

Stage drives motion

The stage definition sets the next action.

Each stage carries entry criteria (what qualifies a deal to enter), exit criteria (what has to be true to move forward), and the expected activities at that stage. A clear stage definition is the difference between a pipeline that reflects reality and a pipeline where every rep guesses what stage means.

Forecast categories

A separate axis for the manager forecast.

Forecast category (Commit, Best Case, Pipeline, Omitted) is a separate axis from stage. A deal at stage Negotiation might be in Commit (the rep is confident) or Best Case (the rep is less confident). The two-axis model gives the manager the forecast picture without conflating with the deal lifecycle.

Owner matters

Every opportunity has a single accountable owner.

Every opportunity has exactly one accountable owner (the account executive). Supporting roles (SDR, SE, deal desk, CSM) attach as additional participants but the owner is unambiguous. The accountability is what the manager coaches against and the comp plan pays on.

The anatomy of a working opportunity stage

Six fields every opportunity stage should define.

A stage that is just a name on a Kanban column is a stage in name only. The six fields below are what a working stage definition carries. The RevOps lead who defines the stages with the sales management team typically ships a documented stage model as part of pipeline rollout.

Entry criteria

What has to be true to arrive here.

Entry criteria define what has to be true for a deal to arrive in this stage. For example, Discovery entry: identified buyer, confirmed pain, scheduled next meeting. The criteria make the stage transition deterministic rather than a judgment call.

Exit criteria

What has to be true to leave.

Exit criteria define what has to be true for a deal to move forward. For example, Discovery exit: budget confirmed, decision maker identified, next-step action booked. Clear exit criteria stop deals from skipping stages or lingering in a stage past its useful window.

Required fields

The data the deal must carry.

Required fields are the data points the opportunity must carry to be in this stage. For example, Negotiation requires contract terms, pricing summary, and legal review status. The required-field enforcement prevents deals from reaching late stages with missing data.

Expected duration

The target time in stage.

Each stage carries an expected duration (median deal spends 12 days in Discovery, 8 days in Proposal). Deals exceeding the median by 2x surface as aging. The duration target gives the manager a signal to coach and gives the forecasting model a prior to adjust against.

Default probability

The win rate at this stage.

Each stage carries a default probability (Discovery deals close at 20 percent, Proposal at 40 percent, Negotiation at 70 percent). The probability feeds the weighted pipeline value. The rep can override on a deal but the stage default anchors the forecast.

Playbook link

What to do while here.

Each stage ships with a playbook (the discovery questions, the proposal template, the negotiation framework, the contract checklist). The rep sees the playbook inline when the deal enters the stage. Enablement moves from a quarterly training to in-flow guidance.

What a mature opportunity pipeline tracks

Six metrics the sales leader actually watches.

The sales leader running an opportunity pipeline needs a metric set. The six below are what Strkr customers run on the executive dashboard. Each one is a lagging or leading indicator of pipeline health; mature teams watch all six.

Pipeline coverage

Open pipeline divided by quota.

Pipeline coverage is open pipeline value divided by the quota for the forecast period. A healthy coverage ratio is 3x to 4x for most B2B motions. Below 2x and the team cannot hit the number no matter the win rate; above 5x and the pipeline is likely inflated with low-quality opportunities.

Win rate by stage

The conversion between adjacent stages.

Win rate by stage shows the conversion from stage to stage (Discovery to Proposal 60 percent, Proposal to Negotiation 70 percent, Negotiation to Won 65 percent). The pattern surfaces the leaky stage; coaching focus goes where the leak is largest.

Sales cycle

Median time from created to closed.

Sales cycle is the median time from opportunity creation to closed-won (or closed-lost). Trending the cycle over quarters surfaces changes in the motion: a lengthening cycle flags a market shift or a product-fit issue, a shortening cycle flags motion improvement or shrinking deal size.

Average deal size

The revenue per won opportunity.

Average deal size tracks the revenue per closed-won opportunity. Trending by product, segment, and quarter surfaces moves in the mix. A rising average with constant volume often reflects enterprise strategy paying off; a falling average often reflects discounting pressure.

Stage velocity

Days in stage versus expected.

Stage velocity compares actual days in stage against the expected duration. Deals aging past 2x the median surface as stuck. The pattern of stuck deals by stage reveals the systemic friction point in the motion.

Forecast accuracy

Commit versus closed-won.

Forecast accuracy compares the Commit forecast at the start of the quarter against the actual closed-won. A gap wider than 10 percent in either direction signals a forecast discipline issue (reps committing too optimistically or sandbagging) that coaching has to address.

What Strkr delivers for opportunity pipelines

Six capabilities that make the pipeline a working artifact.

Strkr ships a serious opportunity pipeline out of the box. The six capabilities below are the ones that make the difference between a working pipeline and a shadow spreadsheet the sales team actually uses. All six ship by default.

Stage model

Configurable per team with inheritance.

Stage models configure per team with inheritance from the organization default. The enterprise team runs a 7-stage model; the SMB team runs a 5-stage model. Both share the forecast category and the executive view. The RevOps lead maintains the models without engineering.

Entry and exit enforcement

Deals cannot skip the discipline.

Entry and exit criteria enforce at the stage transition. A deal missing the required decision maker cannot move to Negotiation. The enforcement is configurable per team; strict mode blocks the transition, soft mode warns and logs. Discipline becomes default rather than aspirational.

Forecast categories

Separate axis from stage.

Forecast categories (Commit, Best Case, Pipeline, Omitted) ship as a separate axis. The manager rolls the forecast up from the Commit calls; the system renders Best Case as the upside; Pipeline carries the long-tail; Omitted removes a deal from the forecast without closing it.

Playbooks inline

Guidance appears in the deal.

Stage playbooks render inline on the deal when the deal is in the stage. The rep sees the discovery questions, the proposal template, the contract checklist. Enablement runs in flow rather than quarterly training sessions.

Velocity surfacing

Aging deals pop automatically.

Deals aging past 2x the median stage duration surface automatically on the manager dashboard and the rep inbox. The manager sees the pattern across the team; the rep sees the list for the one-on-one. Nobody has to pull the aging report every Monday.

Dashboard roll-up

Six metrics on the executive view.

Pipeline coverage, win rate by stage, sales cycle, average deal size, stage velocity, and forecast accuracy roll up to the executive dashboard automatically. The executive view is one URL for the leader; drill-through to the manager or rep view takes one click.

The opportunity pipeline is the beating heart of the revenue motion.

Strkr ships configurable stage models, entry and exit enforcement, forecast categories, inline playbooks, velocity surfacing, and the six-metric executive view out of the box. Start a trial and run your real deals through the pipeline on day one.

Common questions

What buyers ask about this feature.

What is an opportunity pipeline and how is it different from a sales pipeline?

An opportunity pipeline is the pipeline of qualified pursuits (opportunities, sometimes called deals) that a sales team is working. The term opportunity comes from the Salesforce lineage and is standard in enterprise CRMs. A sales pipeline is a broader umbrella term that sometimes includes unqualified leads and sometimes refers specifically to the opportunity pipeline. Most mature revenue organizations separate the lead pipeline (unqualified prospects) from the opportunity pipeline (qualified pursuits) because the motion and the metrics differ. Strkr supports both as distinct objects: leads live in the lead pipeline and convert to opportunities when qualified, while opportunities live in the opportunity pipeline through to closed-won or closed-lost.

What stage model should an opportunity pipeline use?

The stage model depends on the sales motion. A high-velocity SMB motion typically runs 4 to 5 stages (Prospecting, Discovery, Proposal, Negotiation, Closed) with short expected durations and tight criteria. An enterprise motion typically runs 6 to 8 stages (Prospecting, Discovery, Technical Validation, Business Case, Proposal, Negotiation, Legal Review, Closed) with longer expected durations and more rigorous entry criteria. The right stage count is the smallest number of stages that each have distinct entry criteria, distinct exit criteria, and distinct activities. More stages than that create friction without insight; fewer stages lose granularity on the motion.

How do forecast categories work alongside stages?

Forecast categories (Commit, Best Case, Pipeline, Omitted) are a separate axis from stage. The stage reflects where the deal is in the lifecycle; the forecast category reflects the rep confidence in the deal closing in the forecast period. A deal in Discovery is almost always in Pipeline (not yet forecastable). A deal in Negotiation might be in Commit (the rep is confident), Best Case (the rep is less confident but believes it could close), or Pipeline (the rep thinks it slips). A deal in Omitted is in the pipeline but explicitly excluded from the forecast (long-shot, strategic bet, slip to next quarter). The two-axis model gives the manager a clearer forecast picture than conflating stage and probability.

What pipeline metrics should a sales leader watch?

Six metrics matter for most B2B motions. Pipeline coverage (open pipeline divided by quota, healthy at 3x to 4x). Win rate by stage (the conversion between adjacent stages, surfacing the leaky stage). Sales cycle (median time from opportunity creation to closed-won, trending over quarters). Average deal size (revenue per won opportunity, by product and segment). Stage velocity (actual days in stage versus expected, surfacing stuck deals). Forecast accuracy (Commit forecast against closed-won, revealing forecast discipline issues). Mature teams watch all six on a weekly cadence; the executive dashboard rolls them up for the leadership view with drill-through to the deals contributing.

How does Strkr enforce stage entry and exit criteria?

Strkr opportunity pipelines carry configurable entry and exit criteria per stage. Entry criteria define what has to be true for a deal to arrive (identified buyer, confirmed pain, scheduled next meeting for Discovery). Exit criteria define what has to be true for a deal to move forward (budget confirmed, decision maker identified, next-step action booked for Discovery exit). The enforcement is configurable per team: strict mode blocks the transition until criteria are met, soft mode warns and logs the override. The RevOps lead picks strict for critical stages (anything feeding Commit) and soft for early stages where friction would hurt velocity. The audit log captures every override with the actor, the timestamp, and the justification.

Can an account carry multiple opportunities?

Yes. An enterprise account typically carries multiple opportunities over time: the initial land, a cross-sell to a second product, the renewal, the upsell. Each opportunity has its own stage, amount, close date, and owner. The account roll-up on the account detail page shows the full picture: all open opportunities, all closed-won in the past 12 months, all closed-lost with reason codes. The account carries the ongoing relationship context (contacts, support history, product usage, NPS); each opportunity carries the pursuit. The two-level model matches real B2B motion where a single buyer can have multiple active pursuits of different products at different stages.

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.