TL;DR
- →A sales workflow has 7 stages: Signal Detection, Signal-Led Outreach, Discovery, Demo, Proposal, Close, and Post-Sale Handoff. Most frameworks start at Stage 2. That gap costs reps their best accounts.
- →Each stage carries admin overhead — 15 minutes to 3 hours per deal, per stage. Across a 50-deal pipeline, that overhead compounds to 200+ hours per quarter in non-selling work.
- →The seams between stages — where context transfers between tools, people, or tasks — are where 60% of deals stall or die. Eliminating manual seams is the highest-value workflow improvement available.
- →Companies with a formal sales process see 18% higher revenue growth than those without one (HubSpot Research, 2025). Defining all 7 stages with exit criteria is the first step to making the process formal.
What are sales workflow stages?
Sales workflow stages are the discrete, sequential phases a rep completes to move a deal from a buying signal to a closed contract and post-sale handoff. Each stage has a defined trigger that starts it, specific tasks the rep completes, and an exit criterion the deal must meet before advancing. A modern B2B sales workflow has 7 stages: Signal Detection, Signal-Led Outreach, Discovery and Qualification, Demo and Presentation, Proposal and Negotiation, Close, and Post-Sale Handoff.
The traditional 7-step sales process — prospecting, preparation, approach, presentation, handling objections, closing, follow-up — dates to the 1980s. It was designed for a world where reps called cold lists, presented to a single decision-maker, and handed off nothing. That world is gone.
Modern B2B deals involve an average of 6.8 stakeholders (Gartner, 2024), a 10.1-month average buying cycle (6sense, 2025), and buyers who complete 57% of their decision process before first contact (Forrester). The workflow has to match that reality or reps lose deals at the seams — the transitions between stages where context disappears and momentum dies.
Two stages most frameworks omit entirely:
- Stage 1 — Signal Detection. Every deal starts with a reason to buy, not with a rep picking up the phone. Detecting the trigger event before outreach is the difference between a warm account and a cold call.
- Stage 7 — Post-Sale Handoff. The deal does not end at close. A weak handoff to Customer Success erases the trust built across stages 1–6 and kills expansion revenue before the contract is 30 days old.
The guide below covers all seven stages with time benchmarks, admin cost estimates, exit criteria, and the specific tasks a rep performs at each step. For the broader strategic picture, read the sales workflow best practices guide as a companion.
Stage 1: Signal Detection
Signal detection is the stage most frameworks skip, and it is the stage that determines whether stage 2 feels like outreach or cold calling. A buying signal is a specific, timestamped event that proves an account just got a new reason to care about your category.
Signals are not intent scores on a dashboard. They are things that happened: a VP of Sales hired last Tuesday, a Series B announced yesterday, a job posting for a Revenue Operations role that lists your tech category in the requirements. Each signal names a specific trigger a rep can use in the first sentence of their outreach.
| Signal Type | Where to Find It | Reply Lift vs. Cold |
|---|---|---|
| Past champion changed companies | CRM + LinkedIn alerts | ~9.6× |
| New VP / Director hired into buyer function | LinkedIn Sales Navigator | ~7.8× |
| Funding round (Series A+) | Crunchbase, TechCrunch | ~4.5× |
| Hiring for role your product supports | Company careers page, LinkedIn | ~4.2× |
| Public post about the pain you solve | LinkedIn search, community feeds | ~3.1× |
| Tech-stack change | BuiltWith, job descriptions | ~2.4× |
| Competitor mentioned negatively | Social listening, G2 reviews | ~2.1× |
Reply lift estimates from Gangly internal rep data, Q1 2026
Time benchmark: 15–30 minutes per morning for a rep covering 50–80 accounts. Three sources cover 80% of signal value at zero cost: LinkedIn Sales Navigator job-change alerts, a Crunchbase industry feed, and a CRM saved view of past champions.
Admin cost: Low when systemized. High when reps do it manually — because they do not do it consistently. Signal detection only works if it happens every morning, not when a rep remembers.
Exit criterion: Account scores 40 or higher on the 5-factor signal model (recency × role match × intent depth × ICP fit × prior relationship). For a detailed breakdown of how to score signals, read the B2B buying signals guide.
Signals decay fast. By day 7, 4–6 competing reps have usually reached the same account. Reps who act on same-day signals book 3.4× more meetings than reps who batch signals into a weekly review (Gangly internal data, Q1 2026).
Stage 2: Signal-Led Outreach
Signal-led outreach is the first touch a rep sends after stage 1 surfaces a scored account. The defining rule: the first sentence of the message must name the specific trigger event. No "hope this finds you well." No "I wanted to reach out because…"
The structure for a stage 2 message is three elements:
- 1 Signal line. Name the event in one specific sentence. "Saw you announced your Series B last week" is too generic. "Saw Acme posted for an SDR Manager in the EMEA market you launched in March" is specific enough that the buyer knows you read the job posting.
- 2 Pain bridge. One sentence that connects the signal to a concrete problem your product solves. The bridge makes the message feel relevant, not transactional.
- 3 15-second ask. A question or micro-commitment the buyer can answer in under 15 seconds. Not "do you have time for a 30-minute call?" Ask something they already know the answer to.
Time benchmark: 5–10 minutes per account when research is pre-loaded from stage 1. 30–45 minutes per account when the rep starts from scratch — which is why stage 1 must happen before stage 2, not during it.
Admin cost: The highest non-selling cost in outbound sales. A rep with 20 accounts to work in a day spends 6–15 hours per week on research, writing, and sequencing if the workflow is manual. That overhead is the primary reason reps avoid prospecting.
Exit criterion: Reply received or meeting booked. After 4 touches over 10 days with no reply, move the account to a nurture sequence and watch for the next signal.
For a full breakdown of signal-based outreach methodology, read the trigger event selling guide.
Stage 3: Discovery and Qualification
Discovery is the highest-value call in the workflow and the one most often rushed. Its purpose is not to pitch — it is to map the buyer's current state, real pain, business impact, timeline, decision process, budget range, and stakeholder map.
Modern B2B buying committees average 6.8 stakeholders (Gartner, 2024). A discovery that surfaces only one champion's perspective is a discovery that will stall at stage 5 when procurement or a skeptical VP appears from nowhere.
Discovery Framework: 6 Categories to Map
- Current state: How are they solving this today? What does it cost?
- Real pain: What breaks when the current solution fails?
- Business impact: What does fixing this unlock in revenue or cost?
- Timeline: What creates urgency? Is there an internal deadline?
- Decision process: Who approves, who blocks, what is the procurement path?
- Stakeholder map: Who else is involved? Who has not been in the room yet?
Time benchmark: 30–60 minutes for the call itself, plus 20–40 minutes for note capture, CRM update, and follow-up email. Reps who delay this admin work lose critical context within 24 hours.
Admin cost: Extremely high in manual workflows. A rep who takes notes during the call, then re-keys them to CRM, then writes a follow-up recap email, spends more time on admin than on the call itself. This is the stage where sales workflow automation delivers the most immediate time savings.
Exit criterion: Pain confirmed and quantified, next step agreed with a specific date, at least one decision-maker identified by name and role, preliminary budget fit.
For the full list of questions that surface real pain vs. surface-level symptoms, read the 50 discovery questions guide.
Stage 4: Demo and Presentation
The demo is not a product tour. It is the moment you prove, with the buyer watching, that your product fixes the specific pain they named in stage 3. Every feature you show that does not connect to a discovery finding is a feature that dilutes the message and adds friction.
Buyers who see irrelevant features in a demo are 2× more likely to stall post-demo than buyers who saw a tightly scoped presentation (Gong, 2025). The instinct to show everything is the instinct that kills deals.
Demo Prep Checklist
- Map each planned demo section to a specific pain from stage 3 discovery notes
- Personalize the product environment with the buyer's company name and realistic data
- Pre-identify the 2–3 moments most likely to cause the "aha" reaction
- Prepare 3 objection responses for the most common friction at this stage
- Confirm all stakeholders who should be in the room before the call
- Define the next step you will propose at the end — specific date, not "let's find time"
Time benchmark: 45–90 minutes total (15–20 for prep, 45–60 for the call, 15–20 for the post-call follow-up email). The follow-up email is not optional — it locks in the next step while the call is still fresh in the buyer's memory.
Admin cost: Medium. The highest-value admin task at this stage is the post-call follow-up email, which most reps write 4–6 hours after the call — by which point they have lost the specific language the buyer used to describe their pain.
Exit criterion: Buyer confirms they saw the specific pain addressed. Internal champion agrees to present internally or advance to proposal within 5 business days.
Stage 5: Proposal and Negotiation
A proposal is not a pricing document. It is a business case. The best proposals quantify three things: the cost of the buyer's current problem, the projected ROI of your solution, and the cost of delaying the decision.
Pricing objections belong in stage 5, not stage 2. The rep who raises pricing before establishing value invites discounting as the primary lever. Negotiate only after earning the right through demonstrated value in stages 3 and 4.
Proposal Structure: 5 Components
- 1 Current state summary — restate the pain in the buyer's own language from stage 3
- 2 Solution scope — map each feature to each pain point confirmed in discovery
- 3 ROI projection — quantify the business impact with conservative and base-case estimates
- 4 Cost of delay — show the financial impact of waiting 30, 60, or 90 days
- 5 Next steps — specific actions, dates, and owners to get to signature
Time benchmark: 1–3 hours depending on deal size. Enterprise proposals with legal redlines and procurement review can extend to weeks. The single biggest time drain at this stage is waiting — for pricing approval, for legal review, for procurement to respond.
Admin cost: Very high. Multi-threaded deals in stage 5 require the rep to track separate conversations with procurement, legal, IT, and the economic buyer simultaneously — all in different threads, often across email and Slack.
Exit criterion: Verbal yes from the economic buyer. Signature process initiated with a specific date for completion.
Stage 6: Close
Close is the stage most reps treat as a moment rather than a stage. It is not a single conversation — it is the final sequence of steps from verbal yes to signed contract to CRM update to CS notification.
Deals die between the verbal yes and the signature more often than most reps track. A competitor gets in during the procurement window. Internal priorities shift. The economic buyer goes on holiday. The rep who sets a specific close date in writing at the verbal yes and drives the signature process actively loses fewer deals at this seam.
Time benchmark: 30–60 minutes for the final call, 15–30 minutes for contract routing and CRM close. The actual signature often takes 2–10 business days from verbal yes, depending on procurement and legal requirements.
Admin cost: Medium. CRM update alone takes 20–30 minutes in most manual workflows because the rep has to reconstruct the deal narrative, stakeholder map, and close details from memory or scattered notes.
Exit criterion: Signed contract and payment initiated. CRM updated to Closed-Won with full deal notes, stakeholder map, and close date. CS team notified with a handoff brief ready.
Stage 7: Post-Sale Handoff
Post-sale handoff is the most consistently neglected stage in the workflow, and the one that determines whether the customer renews, expands, or churns before their first QBR.
A handoff without a written brief means the Customer Success Manager starts from scratch. They ask the buyer the same questions the AE asked in stage 3. The buyer feels like the company does not know them. Trust erodes in the first 30 days — before the product has had a chance to prove value.
Post-Sale Handoff Brief: Required Fields
- Buyer's stated pain (verbatim from stage 3)
- Success metrics the buyer named
- Full stakeholder map with roles and influence level
- Commitments made during the sales process
- Known risks or concerns raised in negotiation
- Agreed-upon implementation timeline
- Internal champion name and contact
- Blockers to watch for in onboarding
Time benchmark: 30–60 minutes to write a proper handoff brief. Reps who skip this are saving 45 minutes and costing the company 3–6 months of relationship-building in CS.
Admin cost: Very high when unstructured. The handoff brief requires pulling notes from the discovery call, the demo, the proposal, and the close conversation — all from different tools, all written at different times. Without a system that captures this progressively, the brief never gets written.
Exit criterion: CS team has the written brief. CS has contacted the buyer within 24 hours of close. Kickoff date is confirmed and on the calendar.
The seams: where reps lose time
The stages themselves are well understood. The seams between them — the transitions where context moves from one stage to the next — are where deals stall and reps lose time. Every seam in a manual workflow is a point where the rep must re-gather information they already have, re-key data into a new tool, or reconstruct context they recorded somewhere else.
A rep with a 50-deal pipeline, losing 25–35 minutes per seam at 6 seams per deal, loses 200+ hours per quarter to seam-related admin. That is roughly 5 full selling weeks per quarter spent re-gathering and re-keying information already captured somewhere.
The fix is not more tools — it is tools that carry context forward automatically. The stage 3 discovery notes should feed the stage 4 demo prep. The stage 4 call transcript should feed the stage 5 proposal. The stage 6 close data should feed the stage 7 handoff brief. Each seam should be invisible to the rep.
How Gangly connects every stage
Gangly is built around the specific problem that stages 1–7 exist but the seams between them do not. It connects signal detection, outreach, call prep, live coaching, note capture, CRM update, and post-sale handoff into a single sequence — so the context captured at stage 1 is still present at stage 7.
| Sales Stage | Gangly Module | What It Does |
|---|---|---|
| Stage 1: Signal Detection | Signal Detection | Aggregates job changes, funding events, hiring data, and CRM history into a ranked morning feed |
| Stage 2: Signal-Led Outreach | Outreach Writer | Drafts a signal-led email or LinkedIn DM in the rep's voice, grounded in the specific signal |
| Stage 3: Discovery | Call Prep + Notes | Pre-loads account context before the call; captures and routes notes to CRM after |
| Stage 4: Demo | Call Prep + Live Coaching | Pre-builds talk track from discovery notes; surfaces real-time guidance during the call |
| Stage 5: Proposal | Workflow Sequencer | Tracks proposal stage tasks, follow-up timing, and multi-thread contacts |
| Stage 6: Close | CRM Update | Auto-captures deal outcome, close date, and stakeholder map from the final call |
| Stage 7: Post-Sale Handoff | Workflow Sequencer | Generates a structured handoff brief from all call notes and CRM fields captured across stages 1–6 |
The result is a rep who spends more time in front of buyers and less time re-keying data between tools. Signal Detection to Outreach Writer to Call Prep to CRM Update: one connected sequence, no manual handoffs, no context lost at the seams. See how the workflow connects →
Get the Gangly Workflow Digest
One practical workflow improvement, every Tuesday. Reps use them the same week. No pitches, no case studies padded to 12 paragraphs.
Stage metrics and exit criteria
Defining stages without measuring them produces a workflow that looks good on paper and breaks in practice. Track four metrics at each stage to diagnose where the workflow performs and where it loses deals.
| Stage | Key Conversion Metric | Benchmark (Mid-Market B2B) | Warning Signal |
|---|---|---|---|
| Signal Detection | Accounts scored per week | 15–25 per AE | Below 10: workflow not running daily |
| Outreach | Reply rate | 8–15% signal-led; 2% cold | Below 5%: signal quality or message quality issue |
| Discovery | Meeting to opportunity conversion | 40–60% | Below 30%: ICP fit problem or qualification failure |
| Demo | Demo to proposal conversion | 35–55% | Below 25%: demo relevance or champion alignment issue |
| Proposal | Proposal to verbal yes | 25–40% | Below 20%: pricing, competition, or stakeholder alignment |
| Close | Verbal yes to signed contract | 70–85% | Below 60%: procurement friction or deal stall |
| Post-Sale | CS contact within 24 hours of close | 90%+ | Below 80%: handoff brief not created at close |
Benchmarks for mid-market B2B SaaS, $15K–$80K ACV, 2026
When one stage shows a conversion rate significantly below benchmark, isolate that stage and audit three things: whether the exit criterion is being enforced before deals advance, whether the rep is completing the defined tasks, and whether the tool that supports that stage is actually being used. Most stage problems are process problems masquerading as performance problems.
For the full list of metrics that predict pipeline performance, read the CRM pipeline stages guide.
Common mistakes at each stage
Every stage has a characteristic failure mode. Most are not skill problems — they are workflow design problems. The mistake happens because the stage lacks a defined exit criterion, a specific task list, or a tool that removes the friction.
- Stage 1
Skipping signal detection entirely
Fix: Start every morning with a 15-minute signal scan: LinkedIn job-change alerts, Crunchbase funding feed, and a CRM saved view of past champions. Signals decay in 14 days.
- Stage 2
Sending generic templates with the signal bolted on
Fix: The signal line must be specific enough that the buyer thinks you spent 5 minutes on them. "Saw Acme raised a Series B" is generic. "Saw you hired three SDRs this month into a market you launched six weeks ago" is specific.
- Stage 3
Skipping multi-stakeholder discovery
Fix: B2B buying decisions average 6.8 stakeholders (Gartner, 2024). One discovery call with one champion is not enough. Map the full buying committee in stage 3, not stage 5.
- Stage 4
Running a product tour instead of a pain-mapped demo
Fix: Every demo feature shown must connect back to a specific pain from stage 3. If it does not, cut it. Buyers who see irrelevant features are 2× more likely to stall (Gong, 2025).
- Stage 5
Sending the proposal before confirming internal champion alignment
Fix: A proposal sent to someone who cannot say yes is a proposal that will sit. Confirm the champion will present internally before you write a single line.
- Stage 6
Waiting for the buyer to initiate the signature process
Fix: Set a specific close date in writing in the meeting where the verbal yes happens. "I will send the contract by 3 p.m. today. Can you confirm Tuesday for signature?"
- Stage 7
Handing off with a Slack message
Fix: Handoff without a written brief means CS starts from scratch. Write a 1-page handoff brief: buyer pain, success metrics, key contacts, commitments made in the sales process.
18%
Higher revenue growth with a formal sales process
HubSpot Research · 2025
6.8
Average B2B buying committee members per deal
Gartner · 2024
10.1mo
Average B2B buying cycle length
6sense B2B Buyer Experience Report · 2025
By Siddharth Gangal