A sales pipeline only forecasts well when every stage reflects what the buyer has agreed to, every field is required at the right moment, and every deal gets reviewed on evidence instead of optimism. Most B2B teams can tell you the names of their stages. Fewer can tell you the conversion rate between each stage, the average time a deal sits in each one, or which stage is the real forecast risk this quarter. The gap between the two is the difference between a pipeline that looks organized and a pipeline that actually predicts revenue. This guide walks through the full build: mapping the buyer journey, writing stage exit criteria, setting coverage targets, installing hygiene rules, running the weekly review, and recalibrating on a quarterly loop. Each step shows exactly how to execute inside Strkr using Pipeline, Flows, Forecasting, and Strkr AI, so you leave the page with a working playbook, not a reading list. You can ship the design in a single working day, but the operating rhythm needs four to six weeks of weekly reviews before the forecast error starts tightening. Plan for the ramp, not just the build.
Time: 2 hours to design, 4 to 6 weeks to stabilize
A pipeline is a model of how buyers actually decide, not a list of seller activities. Before you create a single stage, sit with three recent closed-won customers and three closed-lost deals. Walk through the moments where buyer behavior visibly changed: first meaningful conversation, scoping, proof of value, procurement, signature. Those shifts become your stage boundaries. Avoid the common trap of mirroring internal activities like "demo scheduled" or "proposal sent," because stages built on seller actions decay the moment reps start gaming them. Pipelines built on buyer evidence hold up under scrutiny and feed cleaner forecasts. Six stages is a healthy ceiling for most B2B motions. Transactional segments can collapse to four. Enterprise motions sometimes need seven, never more. In Strkr, you capture this journey in a short discovery doc that gets attached to the Pipeline settings so the whole team can see the reasoning behind each stage, and so the next admin inherits context, not just configuration. Pay particular attention to the moments buyers introduced new stakeholders. Those introductions almost always mark a stage boundary, because a buyer who loops in finance or security has made an internal commitment that the deal is worth their colleagues' time. If your current pipeline has no stage that corresponds to those internal commitments, your forecast is missing a signal that your buyers are already generating for you.
A stage without exit criteria is a wish. Every stage needs a short checklist of observable facts that must be true before a deal advances. Think "economic buyer identified by name and title," not "feels engaged." Keep each list to three or four items. More than that and reps either lie or stop updating the record. Fewer than three and the gates are too loose to filter noise. Store the criteria as required fields on the opportunity in Strkr, not as a wiki nobody reads. When a rep tries to drag a deal forward with blank fields, the stage transition is blocked and the rep sees exactly which fields are missing. That friction is a feature, because it is the single highest-leverage change you can make to forecast accuracy. Strkr Flows lets you layer a second rule on top: if the criteria are met but the deal is above a dollar threshold, send a Slack notification to the deal desk so the big ones get a second set of eyes before they move. Review your criteria quarterly and retire anything reps consistently bypass; evidence that gets bypassed every week is proof the criterion is wrong, not that the rep is lazy. The best exit criteria are written by two reps and one revenue operations partner together, because the people who use the gates daily know which signals are observable in real deals and which signals only exist in theory. If the criteria were written by the admin alone, they will drift from reality within a quarter and reps will either stop advancing deals accurately or will stop advancing them at all. Co-authored criteria last longer because they ship with buy-in.
Each stage carries two numbers that drive your forecast: a win probability and a forecast category. Probability feeds the weighted pipeline math that leaders use to see coverage. Forecast category tells managers which deals belong in Commit, Best Case, Pipeline, or Omit. Do not invent these percentages. Pull them from your own closed-won rate at each historical stage inside Strkr Forecasting, which calculates stage-to-close conversion from live deal history on a rolling basis. If you have no history, borrow benchmark percentages for your motion and segment, then recalibrate after your first full quarter of data. Forecast categories are judgment overlays, not math outputs. A late-stage deal with weak sponsor coverage belongs in Best Case, not Commit, no matter what the probability says. Train your managers to use both signals together. Strkr AI surfaces category drift automatically, flagging deals whose category has not been updated in two weeks or whose activity signals contradict the current forecast call. Probability math alone produces smooth-looking garbage; probability math plus manager judgment plus automatic drift detection produces a forecast you can commit to the board. The right stage probabilities are also moving targets. A stage that converted at 55 percent last year may convert at 42 percent this year if your segment mix shifted or a new competitor entered. Recalculate every quarter from the trailing four-quarter history and update the stage probability in Strkr Pipeline. Store the prior values in the version log so you can trace a forecast miss back to a probability shift when the retro conversation starts six weeks later.
Decide what every opportunity must carry at creation and at each gate: amount, close date, next step, decision maker, decision date, source, competitor, and loss reason on closed-lost. Make the first six required at creation. Loss reason becomes required only on close. Keep the field list ruthlessly short, because every extra field is a tax on rep time and a surface for garbage data. Use picklists over free text wherever a finite set of answers exists. Picklists are forecastable; free text is not. In Strkr, you set required fields and picklist values on the opportunity object through the Custom Fields admin, and you choose which fields fire at creation versus at each stage advancement. Resist the urge to add vanity fields that only one executive looks at twice a year. If a field does not feed a report, a routing rule, or a required decision, it does not belong on the opportunity. When a stakeholder asks for a new field, ask what report it feeds and who reads that report. If the answer is unclear, the field waits. Picklist values also need to be curated. A field with 40 picklist options is nearly as bad as free text because the dropdown becomes a search rather than a choice. Cap picklists at 10 options per field. If a picklist genuinely needs more values, split the field into two orthogonal picklists rather than growing one into a scrollable list. Strkr Pipeline reports treat each picklist option as a filter dimension, so a cleanly structured 10-value picklist produces a more useful report than a sprawling 40-value one.
Coverage is the ratio of open pipeline to the quota you need to hit in a given period. The healthy range depends on your win rate from first stage to closed-won. A 25 percent win rate implies four-times coverage at the start of the period. A 15 percent win rate implies closer to six. Calculate your actual conversion rate inside Strkr Forecasting across the last four quarters, invert it, and that is your minimum coverage. Then set your early-period target 20 percent above that minimum to leave room for slippage. Publish the number. Reps and managers need one visible target that tells them whether to prospect harder or defend what they have. Strkr Pipeline shows coverage per segment, per rep, and per period on a single dashboard, so leadership can see at a glance whether the shortfall is in prospecting, qualification, or late-stage conversion. Coverage is a leading indicator. If the number drops below target with eight weeks left in the quarter, prospecting is the only lever that still works, and that signal needs to reach the team on the Monday it appears, not at the end of the month. Coverage targets also differ by segment and by motion. New business coverage should sit above renewal coverage because renewal conversion is structurally higher, so applying a single coverage number across both masks real shortfalls. Enterprise coverage should sit above SMB coverage because enterprise cycles are longer and more exposed to procurement slippage. Strkr Pipeline lets you set and display segment-specific coverage ratios, which prevents the dashboard-happy failure mode where company-level coverage looks fine while one segment is quietly starving.
Pipelines rot without maintenance. Automate the maintenance so reps cannot avoid it. Flag any opportunity with a close date in the past, any deal with no activity in 14 days, any deal missing required fields, and any deal where the next-step field is older than seven days. These flags surface in a daily rep view and a weekly manager view, not in an email that nobody opens. The point is to make hygiene visible, not punitive. Reps who see their own stale deals will fix them before a manager asks. In Strkr you build these as Flows that run every morning, update a Pipeline Hygiene field on the opportunity, and roll up into a Hygiene Score at the rep and team level. The Hygiene Score becomes the kickoff metric for the weekly pipeline review, so hygiene has a seat at the table instead of being the compliance task nobody owns. Hygiene rules also protect your forecast: a deal with a 30-day-old next step is almost always slipping, whether or not the rep has admitted it to themselves. Treat the Hygiene Score like a credit score for a deal, visible, versioned, and tied to downstream decisions. Hygiene also needs an exit path, which is the "mark lost" workflow. Reps avoid marking lost because losing feels like a scorecard event, but a pipeline where lost deals accumulate as stale actives is a pipeline that lies about coverage. Strkr Pipeline lets you set a weekly nudge on any deal with a close date past 60 days to either push forward with a documented reason or move to lost with a required loss-reason field, which keeps the active pipeline honest without turning marking lost into a punishment.
The pipeline review is where theory meets reality. Hold it weekly, same time, same agenda, no exceptions. Walk every rep through their top five deals and every deal above a dollar threshold you set based on average deal size. For each deal, ask three questions: what has to be true for this to close, what evidence do you have that it is true, and what are you doing this week to prove or disprove it. Do not accept "they said they would get back to me." That is not a next step. A next step is a confirmed calendar event with a named person on a specific date. Managers who enforce this standard see forecast error drop by half within two quarters. Strkr Pipeline includes a Review Mode that pulls each rep into a focused deal-by-deal view with activity timeline, next-step staleness, and category history on one screen, so the manager spends the meeting coaching the deal instead of hunting for context. Record the forecast your reps commit to each week in Strkr Forecasting and track delta from actuals. The delta is your true accuracy signal, and it is the input your coaching conversations should be built on. The pipeline review is also where managers calibrate judgment across reps. If one rep calls every deal Commit and another rep calls every deal Best Case, the team forecast is swinging on bias rather than reality. Review Mode shows the ratio of Commit to Best Case per rep over the trailing 12 weeks, which exposes the bias patterns before they warp the quarter. Address the bias through coaching, not by reclassifying deals in bulk, because bulk reclassification resets the rep's judgment calibration and loses the historical signal you need to coach against.
Once the pipeline is live, leadership needs four numbers every week: average days per stage, stage-to-stage conversion rate, overall win rate, and average deal size. Together they describe pipeline velocity. If velocity drops, something upstream is broken: lead quality, qualification discipline, or stage criteria enforcement. Instrument these in Strkr dashboards tied to live CRM data, not spreadsheets maintained by hand. Spreadsheets drift and lose their definitions within a quarter; dashboards do not. Watch especially for the stage where deals pile up longest, because that is almost always where your real friction lives, and it rarely matches the stage where reps say they are stuck. If average days in your proof stage doubles over four weeks, you have a product-fit signal that needs product and marketing to see, not a rep performance issue. Strkr AI watches velocity signals in the background and generates a weekly narrative on what shifted, why, and what to investigate. Treat that narrative as the hypothesis your team is testing, not the answer. Add two second-order metrics once the primary four are stable: stage regression rate (how often deals move backward through stages) and stage skip rate (how often deals jump multiple stages at once). High stage regression suggests exit criteria are too loose. High stage skip suggests exit criteria are too onerous and reps are papering over the gates. Both are design signals that your pipeline is pretending to be something it is not, and both should trigger an exit-criteria review inside Strkr Pipeline rather than individual rep coaching.
A pipeline is not a static artifact. Buyer behavior shifts, product changes, segments mature, and competitors move. Every quarter, pull the last 90 days of closed-won and closed-lost data from Strkr and ask three questions: did deals actually move through stages in the sequence you designed, did exit criteria predict wins, and did any stage become a graveyard where deals go to stall. If a stage shows a conversion rate below 10 percent, either the gate is too loose or the stage should not exist. If a stage shows above 80 percent, it may be redundant. Treat the pipeline the way a product team treats a shipping product: measured, iterated, and never finished. Strkr Pipeline keeps a version history of every stage change so you can tell whether a conversion dip followed a stage edit or appeared on its own. Share findings with sales leadership before changing anything in production, and never change stage definitions mid-quarter because it breaks historical reporting and confuses the team for a full cycle.
Building a pipeline means designing the stages, exit criteria, required fields, and review cadence that let a team move opportunities from first conversation to closed-won on evidence rather than optimism. The output is a CRM configuration plus a weekly operating rhythm, not just a list of stage names. A well-built pipeline forecasts within 10 percent and surfaces coaching moments early enough to act on.
The 3-3-3 rule is a prospecting heuristic: three touches, three days apart, across three channels before you move a prospect out of the active sequence. It is a useful cadence framework for sales development, not a pipeline design rule. In pipeline terms, 3-3-3 governs how long a lead stays in the top of the funnel before it either converts to an opportunity or exits the sequence.
The 30-60-90 rule structures the first three months of a sales role: learn the product and ICP in the first 30 days, run deals with manager coverage in the next 30, carry a full quota in the final 30. It is an onboarding framework rather than a pipeline construction rule, but it affects pipeline design because new reps need lighter early-stage expectations in their first quarter.
A four-stage pipeline typically runs Qualify, Discover, Propose, Close. Many B2B motions add a fifth stage for proof of value and a sixth for procurement and legal. The right number depends on your sales cycle and buying committee size. Transactional sales do well with four stages; enterprise sales often need six or seven. Avoid going above seven because the maintenance tax exceeds the forecasting benefit.
Most B2B motions perform best with five or six stages. Transactional segments with sub-30-day cycles can run four. Enterprise motions with multi-stakeholder procurement sometimes need seven. More than seven creates maintenance overhead without improving forecast accuracy, and typically signals that seller activities have been mistaken for buyer commitments.
Invert your win rate from first stage to closed-won, then add 20 percent as a buffer. A 20 percent win rate implies five-times minimum coverage, so target six at the start of the period. The specific number matters less than publishing it, tracking it weekly inside the CRM, and treating it as a leading indicator for prospecting intensity rather than a vanity metric.
Use one pipeline per sales motion, not one per rep. If you sell to SMB and enterprise with different sales cycles and buying committees, build two pipelines. If you sell new business and expansion with meaningfully different stages, build two. Fragmenting further than that makes cross-rep benchmarking impossible and bloats the admin surface. Strkr Pipeline supports multiple pipelines per workspace with shared reporting across them, so you can run two motions without losing a unified forecast view.
Treat the first 90 days as a stabilization window and resist changes unless something is clearly broken. After that, review quarterly from the last 90 days of closed-won and closed-lost data. Change stages only when at least one full quarter of data shows a stage trapping deals or passing everything through. Never change stage definitions mid-quarter because it breaks historical reporting and resets the delta-from-last-week signal that the weekly cadence depends on.
Strkr gives you the stage logic, required fields, hygiene automation, and review views you need to run this playbook without stitching three tools together. Build once, review weekly, forecast with confidence.
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.
