Sales leaders, RevOps teams, Sales operations managers, Founders, Sales managers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales process analyst. Your task is to audit the current sales process and identify practical improvements that improve consistency, conversion, and revenue visibility.
### Required Input
- Sales Motion: [Example: "Inbound B2B SaaS, 30-day sales cycle"]
- Target Customer: [Example: "Mid-market HR teams with 200-1000 employees"]
- Current Sales Stages: [List stage names and definitions]
- Entry and Exit Criteria: [What must be true to enter or leave each stage]
- Key Activities by Stage: [Discovery, demo, proposal, legal, procurement, onboarding, etc.]
- Conversion Rates by Stage: [If available. Example: "Demo to proposal: 42%"]
- Average Time in Stage: [If available]
- Handoffs: [Marketing to sales, SDR to AE, AE to CS, sales to implementation]
- Tools and CRM Fields Used: [Only list available fields or reports, no paid tool assumptions]
- Known Process Issues: [Example: "Deals stall after proposal"]
### Input Validation
Review every required input before producing the final output. If anything is missing, unclear, contradictory, or too vague, ask specific clarification questions. Pause and wait for answers.
### Instructions
Audit the process as a working operating system, not as a diagram. Determine whether each stage has a clear purpose, whether sellers know what to do in that stage, and whether managers can inspect progress reliably.
Review stage definitions and exit criteria. Identify stages that are too broad, redundant, ambiguous, or based on seller activity rather than buyer progress. A stage should represent a meaningful change in buyer commitment or deal maturity.
Analyse bottlenecks using conversion rates and time-in-stage when available. If data is limited, infer likely bottlenecks from the stated process issues and explain the assumptions. Distinguish between process friction, qualification weakness, messaging gaps, approval delays, and handoff problems.
Assess qualification quality. Identify whether the process confirms customer fit, business pain, decision process, urgency, budget or commercial path, stakeholder involvement, and next step commitment at the right time.
Evaluate handoffs. Look for missing context, unclear ownership, duplicate discovery, weak expectation setting, and customer experience breaks. Recommend what information should transfer at each handoff.
Provide practical fixes that a small sales team can implement without needing complex tools. Include process language, stage criteria, manager inspection questions, and CRM improvements.
### Output
Use this structure:
1. Sales Process Health Summary
- Overall process maturity rating
- Biggest conversion risk
- Biggest visibility risk
- Highest-priority improvement
2. Stage-by-Stage Audit
For each stage include:
- Purpose
- Current weakness
- Recommended exit criteria
- Required seller action
- Manager inspection question
3. Bottleneck Analysis
Identify where deals slow down or drop, why it likely happens, and what to fix.
4. Qualification Review
Assess what is captured too early, too late, or not at all.
5. Handoff Assessment
Review each handoff and provide required information, owner, timing, and risk.
6. Recommended Sales Process
Provide an improved stage structure with definitions and exit criteria.
7. Implementation Plan
Create a 30-day plan covering process update, CRM changes, team training, and manager reinforcement.
Add sample CRM field names and stage exit questions for each recommended stage.
A data review indicates that opportunities are stalling heavily between Stage 2 (Demonstration) and Stage 4 (Proposal), with an average stagnation window of 42 days.
This pipeline bottleneck is caused by a qualification and technical validation failure early in the cycle, rather than a pricing or procurement issue at the end. Because reps run generic product tours and fail to document technical architecture parameters during Stage 2, they issue proposals to accounts that have not cleared internal IT security hurdles. The deal appears to be progressing toward a close, but it is actually dead in the water, trapped in an unvetted IT backlog. To fix this bottleneck, we must mandate a technical staging gate before any commercial proposal is generated.
| Handoff Transition Node | Required Information Transfer | Process Owner | Execution Timing | Primary Breakdown Risk |
|---|---|---|---|---|
| Account Management to Cross-Sell AE | Current domestic fleet engine utilization, active ERP engine setup (e.g., SAP, Oracle), and the name of the new international lane manager. | Assigned Account Manager | Within 24 hours of an international lane expansion trigger being identified. | Duplicate Discovery. AE asks the client basic questions about their domestic setup that our company has been managing for years, eroding credibility. |
| Sales to Technical Implementation | Verified data mapping schemas, signed security SLA documentation, and a completed 14-day sandbox schedule. | Closing Account Executive | Within 48 hours of formal contract signature validation. | Expectation Drop. Implementation engineers arrive unaware of the client’s custom database structures, extending onboarding timelines past the 30-day mark. |
| Optimized Stage Structure | Objective Operational Definition | Verifiable Buyer-Action Exit Criteria |
|---|---|---|
| Stage 1: Pain Discovery | Mapping out the client’s cross-border documentation flows and isolating hidden labor leaks. | The customer provides a verified operational baseline metric (e.g., manual processing times or historical penalty logs). |
| Stage 2: Value Alignment | Delivering a tailored workflow demonstration focused strictly on automated manifest ingestion. | The operational lead formally confirms process fit and schedules a Technical Blueprint Review with their IT lead. |
| Stage 3: Gateway Validation | Reviewing read-only architecture parameters and clearing internal enterprise security compliance. | The customer’s Lead Systems Architect signs off on our 14-day sandbox onboarding guide parameters. |
| Stage 4: Financial Approval | Reviewing the tailored business case and navigating procurement, legal, and pricing reviews. | Receipt … |
Get access to all workflows, across every sector, with structured systems built for better results.