Sales AI Skill

Deal Stage Automation

Automatically advance deals through pipeline stages based on buyer actions and milestone completion. Use when configuring automated stage progression, setting up deal milestone tracking, establishing stage-gate criteria, or creating stage-specific automated...

Deal Stage Automation & Progression

Automatically advance deals through your sales pipeline based on milestone completion, buyer signals, and stage-gate criteria — ensuring accurate, data-driven pipeline visibility.

Workflow

  1. Define stage-gate criteria for each pipeline stage (required milestones, signals, and data).
  2. Monitor deal activities and milestones across all communication channels.
  3. Evaluate stage progression rules when milestones are met or signals are detected.
  4. Auto-advance deals with appropriate probability and close date updates.
  5. Notify sales rep and manager of stage changes with context and reasoning.
  6. Trigger stage-specific workflows (tasks, emails, approvals, notifications).
  7. Alert on stalled deals or stage regression patterns.

Pipeline Stage Framework

STANDARD B2B PIPELINE STAGES
══════════════════════════════════════════════════════════════════════

Stage 0 — Identified:
  Definition: Target account identified but no active engagement
  Entry Criteria: Account added to target list or territory
  Probability: 5%
  Average Duration: 30–90 days (or until first contact)
  Required Data: Account name, industry, size, assigned owner
  Exit Criteria: First meaningful contact established
  Stage-Specific Workflows:
    → Trigger account research automation
    → Add to territory prospecting cadence
    → Generate ideal contact list (buying committee)
  Exit Gates:
    ☐ First contact reached (email reply, call connection, meeting booked)
    ☐ Contact confirmed as potential stakeholder (role verified)

Stage 1 — Discovery:
  Definition: Initial conversation completed; pain points and needs assessed
  Entry Criteria: First meaningful contact or discovery meeting scheduled
  Probability: 15%
  Average Duration: 14–30 days
  Required Data: Primary contact, pain points documented, budget range
  Exit Criteria: Qualified opportunity with clear need and next steps
  Stage-Specific Workflows:
    → Send discovery follow-up email with recap
    → Create discovery summary in CRM
    → Generate meeting preparation brief for next stage
  Exit Gates:
    ☐ Discovery meeting completed (30+ minutes, pain points documented)
    ☐ Budget confirmed or estimated (within ±25% of expected)
    ☐ Timeline identified (specific quarter or date range)
    ☐ Decision process understood (key stakeholders identified)
    ☐ Next step agreed upon (demo, technical review, executive meeting)

Stage 2 — Qualified (Qualification Complete):
  Definition: Opportunity meets full qualification criteria (BANT/MEDDIC)
  Entry Criteria: All Stage 1 exit gates met
  Probability: 25%
  Average Duration: 7–14 days
  Required Data: BANT complete, champion identified, next steps set
  Exit Criteria: Solution demonstrated or technical evaluation initiated
  Stage-Specific Workflows:
    → Update opportunity with full qualification data
    → Notify manager of qualified opportunity
    → Begin competitive intelligence gathering
  Exit Gates:
    ☐ MEDDIC qualification complete:
        Metrics: Quantified business impact defined
        Economic Buyer: Identified and engaged
        Decision Criteria: Documented (technical, financial, timeline)
        Decision Process: Mapped out (steps, stakeholders, timeline)
        Identify Pain: Specific pain points documented and validated
        Champion: Internal advocate identified and confirmed
    ☐ Or BANT qualification complete:
        Budget: Confirmed or committed
        Authority: Decision-maker engaged
        Need: Documented and validated
        Timeline: Specific close date identified

Stage 3 — Proposal/Demo:
  Definition: Solution demonstrated; proposal or formal offer created
  Entry Criteria: All Stage 2 exit gates met
  Probability: 40%
  Average Duration: 14–30 days
  Required Data: Proposal sent, pricing agreed (or in discussion), technical validation
  Exit Criteria: Proposal accepted or contract negotiation initiated
  Stage-Specific Workflows:
    → Auto-generate proposal document from CRM data
    → Send proposal tracking link (view tracking)
    → Schedule technical review if needed
    → Begin executive alignment activities
  Exit Gates:
    ☐ Demo completed with all key stakeholders present (≥ 3 attendees)
    ☐ Proposal sent and viewed (tracked via proposal software)
    ☐ Technical validation complete (security review, integration assessment)
    ☐ Pricing discussed and generally agreed (within ±10% of final)
    ☐ Contract review initiated (legal or procurement engaged)

Stage 4 — Negotiation:
  Definition: Formal negotiation of terms, pricing, and contract language
  Entry Criteria: All Stage 3 exit gates met
  Probability: 60%
  Average Duration: 14–21 days
  Required Data: Contract in review, legal engagement, final pricing
  Exit Criteria: Contract signed (or lost documented)
  Stage-Specific Workflows:
    → Auto-generate contract from approved terms
    → Route to legal review if needed
    → Enable e-signature workflow
    → Notify finance team of expected revenue
  Exit Gates:
    ☐ Contract sent to customer for signature
    ☐ All pricing terms agreed and documented
    ☐ Legal review complete (both sides)
    ☐ Implementation plan agreed

Stage 5 — Closed Won:
  Definition: Contract signed; deal officially won
  Entry Criteria: All Stage 4 exit gates met
  Probability: 100%
  Required Data: Signed contract, implementation start date, revenue recognized
  Stage-Specific Workflows:
    → Trigger customer onboarding workflow
    → Notify finance for revenue recognition
    → Create handoff package for Customer Success
    → Log win data for win/loss analysis

Stage 6 — Closed Lost:
  Definition: Deal lost (documented reason required)
  Entry Criteria: Customer chose alternative, budget cancelled, or timeline expired
  Required Data: Loss reason, competitor (if applicable), lessons learned
  Stage-Specific Workflows:
    → Trigger loss analysis workflow
    → Capture competitive intelligence
    → Add account to re-engagement nurture (if applicable)
    → Update territory forecast

Stage Progression Rules Engine

AUTO-PROGRESSION RULES
══════════════════════════════════════════════════════════════════════

Rule Type 1 — Activity-Based Progression:
  → 3+ emails exchanged with prospect → Auto-advance from Identified to Discovery
  → Discovery call logged (30+ minutes) → Auto-advance from Discovery to Qualified
  → Demo meeting logged → Auto-advance from Qualified to Proposal/Demo
  → Proposal document sent (tracked via PandaDoc/Proposify) → Auto-advance
  → Contract sent for e-signature → Auto-advance to Negotiation
  → E-signature completed → Auto-advance to Closed Won

Rule Type 2 — Signal-Based Progression:
  → Budget mentioned in email/call → Update Budget field; if ≥ $50K, advance
  → Timeline mentioned with specific date → Update Close Date; advance if ready
  → Competitor mentioned → Flag competitive deal; advance if engagement deepening
  → Stakeholder added (new contact at account) → Increase probability 5–10%
  → Executive engaged (VP+ involvement) → Increase probability 10–15%

Rule Type 3 — Milestone-Based Progression:
  → Security review requested → Advance to Proposal stage (technical evaluation)
  → Legal review requested → Advance to Negotiation stage
  → Reference call completed → Advance (social proof milestone achieved)
  → Pilot/trial completed with positive results → Advance to Proposal
  → Budget approval confirmed → Advance to Negotiation

Rule Type 4 — Time-Based Alerts (NOT auto-progression):
  → Deal in same stage > average duration × 1.5 → Alert rep and manager
  → Deal in same stage > average duration × 2.0 → Escalate to sales leadership
  → Close date in past → Flag for review (advance or close lost)
  → No activity in 30+ days → Stale deal alert
  → No activity in 60+ days → Auto-suggest close lost or re-engagement

Stage Regression Rules (Moving Backward):
  → Champion leaves company → Drop 1 stage + reduce probability by 20%
  → Budget cancelled or reduced → Drop to Discovery stage
  → Competitor wins technical evaluation → Drop to Proposal stage
  → Stakeholder lost (no replacement identified) → Drop 1 stage
  → Engagement drops (no contact for 14+ days) → Alert; no auto-drop

Probability and Close Date Auto-Updates:
  → Probability: Auto-update based on stage + deal health score
    Formula: Stage Base Probability + (Health Score Adjustment)
    Example: Proposal stage (40% base) + Health score +10% = 50% probability
  → Close Date: Auto-adjust based on engagement velocity
    Formula: Current Date + (Stage Average Duration × Engagement Multiplier)
    Fast engagement (> 2 touches/week): 0.7× multiplier
    Normal engagement (1–2 touches/week): 1.0× multiplier
    Slow engagement (< 1 touch/week): 1.5× multiplier

Stage-Specific Workflow Triggers

STAGE-SPECIFIC AUTOMATED WORKFLOWS
══════════════════════════════════════════════════════════════════════

On Entry to Discovery Stage:
  → Email to rep: "New discovery with [Account] — here's your research brief"
  → Create task: "Complete discovery call within 7 days"
  → Generate account research brief (company data, news, tech stack)
  → Identify buying committee (LinkedIn/org chart look up)
  → Add to weekly pipeline review queue

On Entry to Qualified Stage:
  → Notify manager: "New qualified opportunity: [Account] — $[Amount]"
  → Create task: "Schedule demo within 5 business days"
  → Generate demo preparation brief (pain points, stakeholders, objectives)
  → Begin competitive intelligence gathering
  → Add to monthly forecasting report

On Entry to Proposal/Demo Stage:
  → Email to rep: "Demo time! Here are the top 3 case studies for [Industry]"
  → Create task: "Complete demo and send proposal within 7 days"
  → Auto-generate proposal template (pull data from CRM)
  → Schedule technical review with Solutions Engineer (if needed)
  → Update forecast with revised probability

On Entry to Negotiation Stage:
  → Notify manager and VP Sales: "Deal entering negotiation: [Account]"
  → Create task: "Send contract within 48 hours"
  → Route to deal desk for pricing/terms approval (if non-standard)
  → Notify finance team: "Expected revenue: $[Amount] by [Close Date]"
  → Begin implementation planning (pre-sale)

On Entry to Closed Won:
  → Trigger customer onboarding workflow (Customer Success handoff)
  → Notify finance: "Revenue to recognize: $[Amount] on [Start Date]"
  → Create task: "Schedule kickoff call within 5 business days"
  → Log win data (deal characteristics, win reasons, timeline)
  → Send congratulatory message to rep + team
  → Update territory and quota attainment dashboards

On Entry to Closed Lost:
  → Create task: "Complete loss reason within 3 business days"
  → Trigger win/loss analysis workflow
  → If competitive loss: Capture competitor intelligence
  → If budget lost: Add to re-engagement nurture (6–12 month follow-up)
  → Update forecast and territory coverage reports
  → Send coaching prompt to rep (if loss pattern detected)

Edge Cases

Integration Points