Sales process workflow template: Prospect to close map

Most sales teams have a process. What they don't have is a process that executes consistently when the pressure is on, when a prospect issues a 60-question RFP with a 48-hour deadline, asks a technical question mid-demo that nobody can answer, or requests a competitive comparison before your SE is available.

The process looks fine on paper. What breaks is execution, the moments where reps hit a wall because the right content isn't at hand, the right person isn't available, or the answer that was written down somewhere three months ago simply can't be found.

This guide gives you a complete, seven-stage sales process workflow template built for B2B revenue teams. More importantly, it identifies exactly where most workflows fall apart during execution, and what it takes to fix that without adding headcount or rebuilding your team from scratch.

What a sales process workflow actually does

A sales process workflow is the structured sequence of stages every deal moves through, from initial contact to closed won or closed lost. It maps buyer behavior to specific seller actions, defining what needs to happen at each stage, who owns it, and what evidence proves a deal is ready to advance.

An effective workflow answers four questions for every active deal: Where is this deal right now? What needs to happen next? What evidence proves it's ready to advance? What content or resources does the rep need to get it there?

Without this structure, sales are reactive. Reps rely on instinct. Managers forecast based on gut feel. Your best performer's habits become tribal knowledge that walks out the door the moment they do. With a documented workflow, new reps ramp faster, forecast accuracy improves, and execution stops depending on who happens to be available.

The seven-stage sales process workflow template

Most B2B sales processes work best with six to seven stages. Fewer stages create gaps in pipeline visibility. More stages create administrative overhead without adding a useful signal. Here's a proven seven-stage structure you can adapt to your business.

Stage 1: Prospecting and lead qualification

Objective: Identify prospects matching your ideal customer profile and determine whether the opportunity is worth pursuing before any significant time is invested.

Key activities: Research the prospect's company, verify ICP fit across size, industry, and geography, identify decision makers, and initiate first outreach.

Exit criteria: Prospect matches ICP. Contact verified. Initial interest confirmed. First meeting scheduled.

Common bottleneck: Time lost on poor-fit prospects because qualification criteria aren't clearly defined or consistently applied. When the bar for moving a deal into stage 2 is vague, reps fill the pipeline with noise instead of signal, and forecast accuracy suffers downstream.

Pipeline probability: 5–10%

‍Stage 2: Discovery and needs analysis

Objective: Understand the prospect's situation, pain points, goals, decision criteria, and buying process in enough depth to tailor everything that follows.

Key activities: Structured discovery call, stakeholder mapping, budget and timeline confirmation, documentation of technical requirements, and confirmation that an active evaluation is underway.

Exit criteria: Clear pain points documented. Budget confirmed. Timeline established. Multiple stakeholders identified. Prospect commits to a defined next step.

Common bottleneck: Surface-level discovery that misses the real decision drivers. When reps ask generic questions and hear generic answers, they walk into the demo without knowing what actually matters to this buyer, and what they present lands flat.

Pipeline probability: 20–30%

Stage 3: Solution presentation and demo

Objective: Demonstrate how your solution addresses the prospect's specific needs — not the generic needs of your average customer.

Key activities: Customized demo focused on their use cases, relevant case studies presented, ROI framework shared, objections addressed, and supporting documentation provided.

Exit criteria: Demo delivered to key stakeholders. Positive feedback received. Technical questions answered. Prospect defines a clear next step.

Common bottleneck: Generic demos that could apply to any prospect in any industry. The most common version of this: a prospect asks for a proof point from their specific vertical mid-demo, and the rep either can't find one quickly enough or defaults to the same three customer examples they use for every deal. The moment the buyer senses a lack of relevance, engagement drops.

The fix isn't more case studies; it's being able to find the right one in seconds rather than promising to follow up. Teams that surface deal-specific proof points in real time, pulling from connected knowledge sources during the conversation, consistently report stronger demo outcomes than those who rely on whatever they remembered to prepare in advance.

Pipeline probability: 35–45%

Stage 4: Evaluation and proof of concept

Objective: Give the prospect direct, hands-on experience with your solution in their environment, removing technical risk before the commercial conversation starts.

Key activities: Trial or POC deployment, technical documentation delivery, scheduled evaluation check-ins, stakeholder feedback gathered, and integration and security concerns addressed.

Exit criteria: POC completed successfully. Positive technical feedback received. Security and compliance concerns resolved. Prospect is ready for commercial discussion.

Common bottleneck: Technical questions that go unanswered for days because the right person wasn't immediately available. A prospect asks about data residency or SSO configuration during the evaluation, a straightforward question with a documented answer, and the deal sits idle while the rep chases down an SE who's supporting five other accounts simultaneously. Extended POC timelines without clear success criteria compound this. Every day of unnecessary delay is a day a competitor can close the gap.

Pipeline probability: 50–60%

Stage 5: Proposal and commercial discussion

Objective: Present a formal proposal and move toward a commercial agreement.

Key activities: Proposal submitted with full pricing and terms, RFP responses completed and submitted on time, security questionnaires answered, ROI analysis provided, and pricing objections addressed.

Exit criteria: Proposal submitted. Commercial terms discussed with the decision maker. RFP responses completed. Verbal pricing agreement reached. Legal review initiated.

Common bottleneck: This is where most deals stall operationally, not because the product isn't the right fit, but because the team can't move fast enough. A 70-question RFP arrives with a three-day deadline. The first day goes to figuring out who owns which section. Responses get assembled from five different sources, are inconsistently worded, and sometimes contradict each other. The submission goes out late or is incomplete.

The teams that handle this stage most effectively have stopped treating RFP responses as one-off assembly projects. They work from a connected, verified knowledge base, product documentation, security certifications, approved Q&A libraries, and past submissions, which generate first-pass responses automatically and route the exceptions to the right reviewers. 

• Sirion handles 1.5x more RFPs per month using this approach, while cutting 48 hours off their average response SLA. As Gordon Thompson, EVP Presales & Business Strategy at Sirion, put it: "Every function, from sales to legal, deserves the speed, precision, and insight that only AI can deliver."
• Rocketlane cut turnaround time by 50%, giving their solutions engineers back bandwidth that was previously consumed entirely by document work. "Our goal is to always be the first team to submit an RFP, so we can be the first team to present," said Kaushik Shankar, Sales Team Lead at Rocketlane. 

Pipeline probability: 65–75%

Stage 6: Negotiation and legal review

Objective: Finalize contract terms, clear legal requirements, and remove the last remaining obstacles to signature.

Key activities: Contract term negotiation, legal redlines and compliance review, security documentation provided, procurement and legal team coordination, and implementation timeline confirmed.

Exit criteria: Contract terms agreed. Legal review completed. Security and compliance approved. Procurement sign-off obtained. Signature process initiated.

Common bottleneck: Missing compliance documentation or incomplete security responses that delay procurement approval, content that already exists in the organization but can't be located or verified quickly enough. When this slows a deal that has otherwise reached verbal agreement, it creates unnecessary risk. Champions lose momentum. Competing priorities emerge. Deals that should close in a week to a month.

Pipeline probability: 80–90%

Stage 7: Closed won or closed lost

Objective: Formalize the win or extract learning from the loss to improve future performance.

Closed won activities: Execute the contract, schedule the customer success kickoff, transition account ownership with full deal context intact, and begin onboarding.

Closed lost activities: Document the loss reason, competitor, budget, timing, or no decision. Conduct a structured loss review with the relevant stakeholders. Update CRM. Keep the relationship warm for future cycles.

Pipeline probability: 100% or 0%

‍What slows down execution at every stage

The workflow above tells your team what to do. The harder problem is eliminating what stops them from doing it.

Across stages 3 through 6, the stages where deals are most often won or lost, four execution gaps show up consistently:

Content that exists but can't be found. The right case study, the correct security certification, the approved compliance language, all of it exists somewhere in the organization. But when it's spread across Drive, Confluence, Slack, and email threads, finding it during a live deal takes hours that most reps don't have. The gap isn't the content. It's the access.

RFP and questionnaire bottlenecks. Manual RFP response is one of the most consistently expensive activities in the presales workflow. When reps spend two to three days assembling a response that could have been generated in two hours from verified sources, they're not just slow, they're also more likely to produce inconsistent, error-prone submissions. The teams that handle this stage most effectively have moved from manual assembly to automated response generation through SiftHub’s AI RFP software — first-pass answers populated from trusted, connected sources such as your content repositories, CRM, call transcripts, sales enablement tools, etc., with only the exceptions routed to SMEs for review.

ActivTrak cut its average RFP cycle from two weeks to three to four days and has maintained a 100% submission hit rate since moving to an automated response workflow. The shift also changed how the team operates internally; associate sales engineers now complete 90% of questionnaires independently, freeing senior engineers for high-value enterprise accounts. As Jose Diaz, Principal Sales Engineer at ActivTrak, put it: "Our reps know the software. What SiftHub gives them is the story, the right customer example for the right industry, told in the right language, every single time. That's not a small thing. That's what wins technical deals."

Tribal knowledge bottlenecks around SMEs. In most presales organizations, a small number of people hold the majority of the technical and product knowledge. When junior reps encounter unfamiliar questions, security, compliance, and integration specifics, they either interrupt those people or guess. Both paths are costly. The first drains SE bandwidth. The second creates errors that resurface at stage 6 and delay contract sign-off.

Competitive positioning gaps. A prospect mentions a competitor evaluation. The rep lacks current positioning, battlecards that were written last year for a product that's since changed, or competitive intel that exists but isn't findable in a live conversation. Prepared competitors win comparisons that unprepared teams never even know they lost.

These aren't workflow design problems. They're knowledge access and execution problems, and they're the reason a well-designed process still produces inconsistent results.

Sales process workflow best practices

Define exit criteria as evidence, not optimism. "Prospect seemed engaged" is not an exit criterion. "Demo delivered to the economic buyer and technical evaluator, both confirmed a defined next step." Deals advance when specific conditions are met, not when reps feel good about a conversation.

Map content requirements to each stage before deals reach them. For every stage in your workflow, identify what a rep will need: relevant case studies, competitive battlecards, security documentation, and ROI frameworks. If that content doesn't exist or can't be retrieved quickly, it will create friction at the exact moment deals need momentum.

Track time in stage, not just conversion rates. Knowing what percentage of deals advance from demo to proposal matters. Knowing how long they sit before advancing tells you where the real friction is. Deals that stall for three or more weeks in one stage almost always point to a content gap or an SME bottleneck, not a qualification problem.

Enforce stage discipline across the team. One rep running a custom three-stage process undermines pipeline visibility and forecast accuracy for everyone. Process integrity requires consistent behavior, which means exit criteria need to be clearly communicated and consistently applied, not left to individual interpretation.

Review and update the process quarterly. Buyer behavior changes. What worked at 15 reps often breaks at 40. Update exit criteria and content requirements based on win-loss analysis, not habit.

Measuring workflow effectiveness

Stage conversion rates: Track the percentage of deals advancing from each stage. Useful benchmarks: 20–30% from discovery to demo, 50–60% from demo to proposal.

Average time in stage: The single most useful signal for identifying where your process breaks down in practice. A long average time in stage 5 almost always points to proposal and RFP friction. A long time in stage 4 usually signals unanswered technical questions.

Stage regression rate: High backward movement from later to earlier stages indicates deals being advanced before exit criteria are genuinely met. Tighten the criteria.

Forecast accuracy: A well-enforced workflow with clear exit criteria directly improves forecast reliability. If your forecasts are consistently off, the workflow is usually the first place to look, not the last.

Content utilization: Which case studies, competitive cards, and response templates are actually being used? What's never retrieved? This reveals content gaps before they show up as lost deals.

Conclusion

A sales process workflow template makes revenue generation repeatable. When every rep moves deals through the same stages, applies the same qualification criteria, and uses the same evidence to advance opportunities, results become predictable and scalable.

But documentation alone doesn't close deals. The teams that execute most effectively combine a clear process with the ability to actually follow it, finding the right proof point during a live demo, responding to an RFP the day it arrives, answering a security question without waiting three days for the one person who knows the answer.

Download the complete workflow template below to get started. Map your stages, define your exit criteria, and build your content requirements for each stage. Then look honestly at where your team hits walls in execution; those are the moments where deals are won and lost.

Frequently asked questions