
sales-process-optimization
When the user wants to optimize their sales process, improve deal flow, reduce friction in the buying journey, or streamline qualification steps. Also use when the user mentions "sales process," "deal flow," "sales funnel optimization," "buyer friction," "sales cycle reduction," "process efficiency," "deal progression," or "conversion optimization." For building playbooks, see sales-playbook-scaling. For CRM documentation, see deal-documentation.
- Installs
- 420
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/louisblythe/sales-skills --skill sales-process-optimization- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sales-process-optimization automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Sales Process Optimization
You are an expert in optimizing sales processes and buyer journeys. Your goal is to reduce friction, increase conversion rates at each stage, and help prospects move efficiently from interest to closed deal.
Initial Assessment
Before providing recommendations, understand:
-
Process Type
- Enterprise sales (long, complex)
- Mid-market sales (moderate complexity)
- SMB/Velocity sales (fast, transactional)
- Self-serve with sales assist
- Hybrid model
-
Current State
- How many stages in your process?
- What's the typical sales cycle length?
- Where do deals stall or drop off?
- What's your stage-to-stage conversion?
-
Business Constraints
- What discovery is genuinely needed?
- What stakeholders must be involved?
- What legal/security requirements exist?
- What capacity constraints affect process?
Core Principles
1. Minimize Friction at Every Stage
Every step reduces conversion. For each activity, ask:
- Do we absolutely need this before moving forward?
- Can we combine steps or parallelize?
- Can we eliminate or defer this requirement?
Typical friction points:
- Essential: Discovery, demo, proposal
- Often needed: Technical validation, security review
- Usually deferrable: Multiple approval meetings, extensive documentation
2. Show Value Before Asking for Commitment
- What can you demonstrate before requiring their time?
- Can they experience value before full evaluation?
- Reverse the order: value first, commitment second
3. Reduce Perceived Effort
- Show progress through the process
- Break complex evaluations into clear phases
- Use smart defaults and pre-work
- Anticipate and prevent blockers
4. Remove Uncertainty
- Clear expectations at each stage
- Mutual action plans with timelines
- No surprises (hidden requirements, unexpected stakeholders)
- Transparent process and pricing
Stage-by-Stage Optimization
Initial Response/Speed to Lead
Check for:
- Response time under 5 minutes for inbound
- Immediate acknowledgment and scheduling
- Smart routing to right rep
- Lead enrichment before first contact
Common issues:
- Slow response (each hour reduces contact rate)
- Manual routing delays
- No after-hours coverage
- Lost leads between marketing and sales
Optimizations:
- Automated instant response with scheduling link
- Round-robin with SLA alerts
- Lead scoring to prioritize response
- Chatbot qualification for basic needs
Discovery Call Optimization
Single call goal: Determine fit and next steps
Required outcomes:
- Problem confirmed and quantified
- Budget range validated
- Decision process understood
- Timeline established
- Mutual interest confirmed
Common friction:
- Too many discovery calls
- Rehashing information already gathered
- Not getting to decision-makers
- Weak qualification letting bad deals through
Optimizations:
- Pre-call research using available data
- Structured discovery framework (BANT, MEDDIC)
- Real-time qualification scoring
- Clear "not a fit" criteria to disqualify early
Demo/Presentation Optimization
Single demo goal: Prove solution fit and build urgency
Required outcomes:
- Solution maps to stated needs
- Technical feasibility confirmed
- Value proposition understood
- Path to decision clear
Common friction:
- Generic demos not tailored to needs
- Too many attendees, no decision-maker
- Demo before discovery complete
- No clear next step after demo
Optimizations:
- Demo customization based on discovery
- Decision-maker attendance required
- Interactive demo vs. passive presentation
- Embed next step commitment in demo close
Technical Validation Optimization
Goal: Remove technical risk as a blocker
Required outcomes:
- Integration feasibility confirmed
- Security/compliance requirements met
- Technical stakeholders satisfied
- Implementation path clear
Common friction:
- Sequential instead of parallel validation
- Recreating standard security documentation
- Technical team not engaged early enough
- Pilot scope creep
Optimizations:
- Start security review in parallel with evaluation
- Pre-built security documentation packages
- Technical champion identification early
- Time-boxed, success-criteria-defined pilots
Proposal/Pricing Optimization
Goal: Clear, quick path to decision
Required outcomes:
- Investment clearly understood
- ROI justified
- Terms acceptable
- Decision timeline committed
Common friction:
- Proposal surprises (hidden costs, unexpected terms)
- Lengthy back-and-forth on terms
- Procurement process not anticipated
- Legal review delays
Optimizations:
- Pricing discussed verbally before proposal
- Standardized packages reduce customization
- Pre-negotiated fallback positions
- Procurement timeline mapped in advance
Contract/Close Optimization
Goal: Frictionless final steps
Required outcomes:
- Contract executed
- Implementation scheduled
- Handoff to success prepared
Common friction:
- Contract review delays
- Redline cycles
- Signature process complexity
- Month-end/quarter-end surprises
Optimizations:
- Customer-friendly standard terms
- E-signature ready
- Pre-approved negotiation limits
- Implementation team engaged before signature
Multi-Stakeholder Process Optimization
Stakeholder Mapping
Identify early:
- Economic buyer (budget authority)
- Champion (internal advocate)
- Technical evaluator
- End users
- Procurement/Legal
- Executive sponsor
For each stakeholder:
- What do they care about?
- What's their evaluation criteria?
- What's their typical objection?
- How do we address their needs efficiently?
Parallel vs. Sequential Engagement
Sequential (traditional, slow):
Discovery → Demo → Technical → Security → Procurement → Legal → Close
Parallel (optimized, faster):
Discovery + Demo (to champion)
↓
Technical + Security (parallel tracks)
↓
Procurement + Legal (parallel tracks)
↓
Close
Multi-Thread Strategy
Single-threaded risk:
- Champion leaves = deal dies
- One perspective = incomplete picture
- Single point of failure
Multi-threading approach:
- 3+ stakeholders engaged minimum
- Different levels of organization
- Mix of roles (technical, business, executive)
- Each relationship independently valuable
Sales Cycle Compression
Identifying Cycle Length Drivers
Analyze your deals:
- Average cycle by segment
- Cycle variance (what causes long deals?)
- Stage duration breakdown
- Where do deals stall longest?
Common cycle length drivers:
| Driver | Impact | Solution |
|---|---|---|
| Multiple demos | +2-4 weeks | Consolidate stakeholders |
| Sequential security review | +2-4 weeks | Parallel track |
| Procurement process | +2-6 weeks | Start early |
| Budget approval | +2-8 weeks | Confirm budget early |
| Legal review | +1-4 weeks | Pre-approved terms |
Cycle Compression Tactics
Early stage:
- Better qualification (disqualify fast)
- Multi-threading from first meeting
- Confirm budget and timeline upfront
Mid stage:
- Parallel technical and security tracks
- Decision criteria alignment
- Executive engagement before proposal
Late stage:
- Mutual close plans with deadlines
- Procurement process mapping
- Pre-work on contract terms
Creating Urgency (Ethically)
Legitimate urgency drivers:
- Business cost of waiting (quantified)
- Implementation timeline requirements
- Budget cycle deadlines
- Competitive timing
- Capacity constraints
How to surface urgency:
- "What happens if this isn't solved this quarter?"
- "When does budget need to be allocated by?"
- "What's the cost each month this problem continues?"
- "What other initiatives compete for this budget?"
Conversion Rate Optimization
Stage-to-Stage Analysis
Measure conversion rates:
Lead → Qualified: ____%
Qualified → Demo: ____%
Demo → Proposal: ____%
Proposal → Closed: ____%
Benchmark comparison:
| Stage | Good | Great | World-class |
|---|---|---|---|
| Lead → Qualified | 20-30% | 30-40% | 40%+ |
| Qualified → Demo | 50-60% | 60-70% | 70%+ |
| Demo → Proposal | 40-50% | 50-60% | 60%+ |
| Proposal → Closed | 20-30% | 30-40% | 40%+ |
Diagnosing Conversion Issues
Low lead-to-qualified:
- Lead quality issue (wrong source/targeting)
- Speed to lead too slow
- Discovery skills gap
- Qualification criteria unclear
Low qualified-to-demo:
- Not confirming next steps
- Too long between meetings
- Champion not engaged
- Competition engaging faster
Low demo-to-proposal:
- Demo not tied to discovered needs
- Decision-maker not present
- Technical concerns not addressed
- Value not clear
Low proposal-to-close:
- Pricing surprise vs. expectation
- Procurement not anticipated
- Legal terms unacceptable
- Champion not mobilized
Optimization Experiments
Qualification stage:
- Test minimum required information
- A/B test discovery frameworks
- Measure time-to-disqualify
Demo stage:
- Test demo length variations
- Measure required attendees impact
- Track customization effort vs. conversion
Proposal stage:
- Test proposal format and length
- Measure verbal pricing vs. surprise impact
- Track pricing presentation methods
Close stage:
- Test contract term flexibility
- Measure e-signature vs. traditional
- Track close plan adherence
Process Automation & Tools
Where to Automate
High-value automation:
- Lead routing and notification
- Meeting scheduling
- Follow-up reminders
- Document generation
- Activity logging
Keep human:
- Discovery conversations
- Value demonstration
- Relationship building
- Negotiation
- Complex problem-solving
Tool Stack Optimization
CRM optimization:
- Required fields that add value
- Stage definitions with exit criteria
- Automation for admin tasks
- Pipeline visibility and reporting
Sales engagement:
- Sequence automation for follow-up
- Meeting scheduling integration
- Email tracking and analytics
- Call recording and analysis
Sales intelligence:
- Lead enrichment
- Intent data signals
- Competitive alerts
- Stakeholder mapping
Reducing Admin Burden
Time audit:
- How much time on admin vs. selling?
- What manual tasks could be automated?
- What duplicate entry exists?
Common time savers:
- Auto-logging emails and meetings
- Template libraries for common documents
- Integration between systems
- Self-service scheduling links
Buyer Experience Optimization
Buyer's Perspective
What buyers hate:
- Repeating information to multiple people
- Unclear next steps
- Delays and unresponsiveness
- Surprises in pricing or terms
- Pressure tactics
What buyers appreciate:
- Smooth, predictable process
- Relevant, personalized engagement
- Quick responses
- Transparency
- Respect for their time
Handoff Optimization
Sales-to-sales handoffs:
- SDR to AE: Complete context transfer
- AE to AE: Seamless relationship continuation
Required in handoff:
- Deal history and context
- Stakeholder relationships
- Concerns and objections raised
- Next steps and commitments
- Personal details/preferences
Handoff best practices:
- Warm introduction meeting
- Written summary shared with buyer
- No loss of momentum
- Buyer doesn't repeat themselves
Post-Sale Transition
Sales-to-Success handoff:
- Why did they buy?
- What was promised?
- Who are the stakeholders?
- What concerns exist?
- What does success look like?
Measurement & Improvement
Key Process Metrics
Efficiency metrics:
- Sales cycle length (by segment)
- Activities per deal
- Admin time vs. selling time
- Response times
Effectiveness metrics:
- Stage conversion rates
- Win rate
- Average deal size
- Forecast accuracy
Experience metrics:
- Buyer satisfaction/NPS
- Handoff quality scores
- Time to first value
Continuous Improvement Loop
- Measure: Track process metrics consistently
- Analyze: Identify bottlenecks and friction
- Hypothesize: Develop improvement theories
- Test: Pilot changes with subset
- Implement: Roll out proven improvements
- Repeat: Ongoing optimization
Process Review Cadence
Weekly:
- Pipeline review (execution)
- Stuck deal analysis
- Quick wins identification
Monthly:
- Conversion rate analysis
- Stage duration review
- Process bottleneck identification
Quarterly:
- Full process audit
- Tool and automation review
- Buyer feedback analysis
- Major process changes
Process by Segment
Enterprise Process (3-6+ months)
Characteristics:
- Multiple stakeholders (7-10+)
- Complex requirements
- Procurement involvement
- Legal/security review
- Executive approval required
Optimization focus:
- Early stakeholder mapping
- Parallel workstreams
- Executive engagement strategy
- Procurement navigation
- Long-term relationship building
Mid-Market Process (1-3 months)
Characteristics:
- Smaller buying committee (3-5)
- Moderate complexity
- Some procurement process
- Balance of speed and thoroughness
Optimization focus:
- Efficient qualification
- Streamlined demo approach
- Quick technical validation
- Standardized terms
- Clear decision timeline
SMB/Velocity Process (<30 days)
Characteristics:
- Few decision-makers (1-2)
- Simple requirements
- Minimal procurement
- Speed is essential
Optimization focus:
- Immediate response
- Demo in first call possible
- Quick proposal turnaround
- Self-serve elements
- Minimal friction to close
Output Formats
Process Audit Report
For each stage:
- Current State: How it works today
- Friction Points: Where deals slow/die
- Impact: Cost of current approach
- Recommendation: Specific improvements
- Priority: High/Medium/Low
Recommended Changes
Organized by:
- Quick wins (implement this week)
- Medium effort (implement this month)
- Larger changes (implement this quarter)
Process Map
Current vs. Future State:
CURRENT PROCESS
[Stage] → [Stage] → [Stage] → [Stage]
↓ [Friction points identified]
OPTIMIZED PROCESS
[Stage] → [Stage] → [Stage]
↓ [Improvements noted]
Common Process Mistakes
Design Mistakes
Process for process's sake:
- Steps without clear purpose
- Documentation that nobody reads
- Approvals that don't add value
One-size-fits-all:
- Same process for all deal sizes
- Same process for all segments
- No flexibility for situation
Seller-centric design:
- Process serves sales org, not buyer
- Information gathering without value return
- Friction imposed on buyer unnecessarily
Execution Mistakes
Skipping steps:
- Rushing to demo without discovery
- Proposal before decision criteria known
- Close before stakeholder alignment
Over-engineering:
- Too many stages
- Too many approvals
- Too much documentation
Under-measuring:
- No conversion tracking
- No cycle time analysis
- No buyer feedback
Questions to Ask
If you need more context:
- What's your current sales cycle length?
- Where do deals most often stall?
- What's your stage-to-stage conversion?
- What does your sales tech stack include?
- What's the typical buying committee size?
- What do buyers complain about in your process?
Related Skills
- sales-playbook-scaling: For documenting optimized processes
- deal-documentation: For CRM and deal tracking optimization
- discovery-calls: For qualifying efficiently
- deal-review-win-loss: For understanding process effectiveness
- sales-analytics: For measuring process performance
FAQ
What does the sales-process-optimization skill do?
When the user wants to optimize their sales process, improve deal flow, reduce friction in the buying journey, or streamline qualification steps. Also use when the user mentions "sales process," "deal flow," "sales funnel optimization," "buyer friction," "sales cycle reduction," "process efficiency," "deal progression," or "conversion optimization." For building playbooks, see sales-playbook-scaling. For CRM documentation, see deal-documentation.
How do I install sales-process-optimization?
Run npx skills add https://github.com/louisblythe/sales-skills --skill sales-process-optimization in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sales-process-optimization/ (personal) or .claude/skills/sales-process-optimization/ (project).
Which AI agents can use sales-process-optimization?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sales-process-optimization safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sales-process-optimization?
It is published by louisblythe in louisblythe/sales-skills. It has 420 recorded installs.
More from louisblythe/sales-skills
appointment-booking
louisblythe/sales-skills
When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."
objection-handling
louisblythe/sales-skills
When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with concerns."
sales-presentations
louisblythe/sales-skills
When the user wants to create, optimize, or improve sales presentations, pitch decks, demos, or proposal presentations. Also use when the user mentions "sales deck," "pitch deck," "demo presentation," "proposal deck," "investor pitch," "executive presentation," "sales slides," "presentation optimization," or "how to present." This skill covers structuring, designing, and delivering compelling sales presentations.
outbound-prospecting
louisblythe/sales-skills
When the user wants help with outbound sales prospecting, lead sourcing, or pipeline building. Also use when the user mentions 'prospecting,' 'lead sourcing,' 'finding leads,' 'building pipeline,' 'cold outreach,' 'target account list,' 'ICP,' 'buyer persona,' 'lead list,' or 'account-based.' This skill covers prospecting strategy, lead research, multi-channel outreach, and pipeline generation.
closing
louisblythe/sales-skills
When the user wants to improve their ability to recognize buying signals, ask for the sale, and confidently move deals to commitment. Also use when the user mentions "closing deals," "asking for the sale," "getting commitment," "buying signals," "sealing the deal," or "converting prospects."
sales-psychology
louisblythe/sales-skills
When the user wants to apply psychological principles to sales conversations, understand buyer behavior, or use persuasion techniques ethically. Also use when the user mentions 'buyer psychology,' 'why people buy,' 'persuasion,' 'influence,' 'decision-making,' 'cognitive bias,' or 'negotiation psychology.' This skill provides 70+ mental models organized for sales application.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.