An ideal sales process is a written contract between sales, revenue operations, and the buyer. It names what happens at each stage, what evidence a rep must produce to advance, and how long the stage should take. This guide walks you through the full definition: mapping the buyer journey, specifying required artifacts, locking exit criteria, estimating days per stage, and publishing the result to your CRM as the mandatory baseline every rep works from.
Time: 2 hours
Before anyone writes a stage name, align the team on three distinct artifacts. The sales process is the stage-by-stage definition of what must be true for a deal to progress. The pipeline is the data representation of that process inside the CRM, with stages, probability, and forecast categories. The playbook is the tactical layer: scripts, discovery questions, objection handling, and talk tracks. Teams that conflate the three end up with process documents that drift from the CRM, playbooks that contradict the stages, and reps who follow none of them. Write the distinction on a single page and share it with every stakeholder before the first working session. The process defines the what. The pipeline enforces the what. The playbook teaches the how.
Pull three recent closed-won and three closed-lost deals and reconstruct what actually happened. Interview the rep, the champion if reachable, and anyone from customer success who inherited the account. Walk the timeline moment by moment and mark where buyer behavior visibly shifted: first substantive conversation, scoping, proof, procurement engagement, legal review, signature. Those shifts become candidate stage boundaries. Resist the temptation to describe seller activities like scheduled a demo or sent a proposal. Those describe your workflow, not the buyer. Processes built on seller actions decay fast because reps game them. Processes built on buyer commitments hold up because the buyer, not the rep, controls when they advance. Keep the output short: a timeline with four to seven buyer-side transitions is plenty for most B2B motions.
Translate the buyer journey into named stages. Most B2B motions settle at five or six: Qualified, Discovery, Evaluation, Proposal, Procurement, Closed. Transactional segments can collapse to four. Enterprise motions sometimes need seven, but never more. For each stage, set an estimated days target based on historical median duration, not the average, which is distorted by stuck deals. The estimate is not a deadline for the rep. It is a signal for the system: when a deal exceeds the target by fifty percent, Strkr flags it for manager review. Publish both the stage name and the day target in the CRM so every rep sees the same baseline. Teams that skip this step end up with pipelines where the same stage means forty days for one rep and four for another, and no forecast survives that variance.
An artifact is the physical evidence that a stage has actually happened. Not what the rep believes. Not what the buyer implied. The written, logged, attached, or linked proof. Discovery requires a documented pain statement in the opportunity notes. Evaluation requires a signed mutual action plan or shared success criteria. Proposal requires a sent quote with a version and date. Procurement requires a legal or security contact on the record. Each artifact must be observable in the CRM, not stored in someone email folder. Reps resist this early because it feels like paperwork. Reps thank you for it six months later because deals stop ghosting, forecasts stop missing, and managers stop asking the same questions in every one-on-one. Artifacts are the single highest-leverage input to a process that holds up under pressure.
Exit criteria are the binary tests that must be true for a deal to leave a stage. They differ from artifacts. An artifact is the proof. The exit criterion is the fact the proof demonstrates. Economic buyer identified by name and title is a criterion. The business card, meeting invite, or email thread naming them is the artifact. Keep each list to three or four criteria. 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 picklist fields on the opportunity. When a rep tries to advance a deal with any field blank or set to Unknown, Strkr blocks the save. The block is the point. It converts the process from a document nobody reads into a system every deal passes through.
A process that lives in a slide deck is a wish. A process that lives in the CRM is a system. Open Strkr admin, create or edit the stage model for the relevant sales motion, and populate four fields per stage: name, estimated days, required artifacts, and exit criteria. Mark the entire model as the tenant baseline so every rep inherits it the moment they open a new opportunity. Strkr AI then watches each deal against the baseline and flags drift the moment it appears: a stage that advanced without a required artifact, a deal sitting past its day target, a criterion left on Unknown. The baseline is not a suggestion. It is the floor every rep works from, every manager reviews against, and every forecast draws from. Teams that publish and enforce a baseline cut forecast error roughly in half within two quarters.
A process rolled out without training lands as surveillance. A process rolled out with training lands as support. Hold two sessions. The first walks reps through every stage, artifact, and exit criterion with a worked example from a real won deal. The second walks managers through how to run a weekly review against the published process: what to ask, what to accept as evidence, what to escalate. Record both sessions and attach them to the process page in Strkr so new hires inherit the same baseline. Give reps a two-week grace period where the validation rules warn instead of block, so they can clean up open deals without penalty. On day fifteen, flip the rules to blocking. Teams that skip the grace period see adoption revolt. Teams that stay in grace forever see adoption drift. Two weeks is the sweet spot.
The buyer changes. The product changes. The segments mature. The process must change with them, or it stops being ideal and starts being inherited. Every quarter, pull the last ninety days of closed-won and closed-lost data and ask four questions. Did deals move through the stages in the sequence you designed? Did exit criteria predict the win? Did any stage become a graveyard where deals sit for twice their day target? Did any artifact become performative rather than diagnostic? Convene sales leadership, revenue operations, and two frontline reps to walk the answers. Change at most two stages per quarter. More than that and reporting breaks, training backlogs, and reps lose faith that the baseline is stable. Treat the process the way a product team treats a shipped product: measured, iterated, versioned, and documented every time it changes.
The sales process is the stage-by-stage definition of what must be true for a deal to progress: buyer-journey mapping, required artifacts, exit criteria, and estimated days. The pipeline is the data representation of that process inside the CRM, with stages, probability, and forecast categories. One is the blueprint, the other is the running system. You define the process first, then build the pipeline to enforce it.
The sales process defines the stages, artifacts, and exit criteria that every deal must satisfy. The playbook is the tactical layer that teaches reps how to execute inside those stages: discovery questions, objection handling, demo scripts, email templates. Process is the what and when. Playbook is the how. A good playbook strengthens a good process; neither one replaces the other.
Most B2B motions perform best with five or six stages. Transactional segments with sub-thirty-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.
Sales leadership owns the content of the process: the stages, artifacts, and exit criteria. Revenue operations owns the implementation inside the CRM and the enforcement rules. Enablement owns the playbook that teaches reps to execute inside the process. Shared ownership without clear boundaries is the leading cause of processes that drift within two quarters of launch.
Review quarterly and change at most two stages per quarter. Pull the last ninety days of closed-won and closed-lost data, audit stage sequence, exit-criteria predictive power, duration, and artifact quality, then version the baseline with a dated changelog. Annual reviews are too slow; monthly reviews break reporting and training. Quarterly is the cadence that keeps the process honest without destabilizing the team.
Allow skipping forward only with manager approval and a logged reason captured in the opportunity. Never allow silent skipping. A deal that jumps from early qualification to late-stage negotiation is either a genuine fast-track or a rep hiding missing diligence; the approval requirement surfaces the difference. Skipping backward should be routine and encouraged, since it reflects honest reassessment rather than erosion of the process.
Strkr lets you define every stage, required artifact, exit criterion, and estimated day target in one place, publish it as the mandatory tenant baseline, and let Strkr AI flag drift the moment it appears. Define once, enforce automatically, review quarterly.
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.
