Agent skill
sales-operations
Design and optimize sales operations infrastructure including process design, territory planning, compensation structures, forecasting systems, and sales analytics. Use for building sales ops frameworks, optimizing sales processes, designing territory plans, creating compensation models, implementing sales tech stacks, establishing forecasting methodologies, developing sales analytics dashboards, managing sales capacity planning, and scaling sales operations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/sales-operations-jh9282026-manus
SKILL.md
Sales Operations
Design, optimize, and manage the systems, processes, and infrastructure that enable sales teams to generate predictable revenue efficiently.
Overview
Sales operations is a strategic function focused on aligning people, processes, and tools around critical revenue outcomes. This skill provides frameworks for process optimization, territory planning, compensation design, forecasting, analytics, and technology management to drive operational efficiency, revenue predictability, and data-driven decision-making.
Core Objectives
Sales operations centers on four fundamental outcomes:
- Operational Efficiency — Eliminate friction to accelerate deal movement and reduce sales cycle length
- Revenue Predictability — Build forecasting systems for reliable planning and resource allocation
- Data-Driven Analytics — Surface insights for informed decision-making and performance optimization
- Process Discipline — Create standardized workflows that scale across regions, teams, and segments
Six Pillars of Sales Operations
| Pillar | Focus Area | Key Activities |
|---|---|---|
| Process Design | Sales cycle optimization | Stage definitions, exit criteria, workflow automation, bottleneck elimination |
| Forecasting & Pipeline | Revenue prediction | Historical analysis, pipeline management, trend identification, accuracy improvement |
| Technology Management | Tech stack optimization | CRM administration, tool integration, CPQ implementation, automation platforms |
| Data & Analytics | Performance insights | Metrics tracking, dashboard creation, pattern identification, reporting automation |
| Compensation Design | Incentive alignment | Plan structure, quota setting, commission calculation, performance motivation |
| Territory & Capacity | Coverage optimization | Territory design, workload balancing, capacity planning, assignment strategy |
Sales Process Optimization Framework
Process Maturity Assessment
Evaluate current state across five dimensions:
- Documentation — Are processes clearly documented with defined stages and exit criteria?
- Standardization — Do all reps follow consistent qualification criteria and sales plays?
- Automation — Are repetitive tasks automated to free up selling time?
- Measurement — Are key metrics tracked and reviewed regularly?
- Iteration — Is there a feedback loop for continuous improvement?
Optimization Priorities
High-Impact Areas:
- Lead qualification and scoring models
- Sales-to-marketing handoff processes
- Quote-to-cash cycle time reduction
- Deal approval workflows
- Customer success transition protocols
Quick Wins:
- Automate data entry and CRM updates
- Standardize email templates and call scripts
- Implement automated follow-up sequences
- Create sales playbooks for common scenarios
- Establish clear pipeline stage definitions
Technology Stack Architecture
Core Systems
| System Type | Purpose | Integration Priority |
|---|---|---|
| CRM | Central customer database | Critical — foundation of stack |
| Sales Engagement | Multi-touch outreach automation | High — connects to CRM |
| CPQ | Configure-price-quote automation | High — reduces quote time |
| Analytics/BI | Performance dashboards | Medium — requires clean data |
| Enablement | Training and content management | Medium — supports rep productivity |
| Data Enrichment | Contact and firmographic data | Medium — improves lead quality |
| Orchestration | Workflow automation | Low — adds after core systems stable |
Integration Best Practices
- Start with CRM as hub — All systems should connect to and update the CRM
- Prioritize bidirectional sync — Ensure data flows both ways to maintain single source of truth
- Establish data governance — Define field standards, naming conventions, and ownership
- Automate where possible — Reduce manual data entry and handoffs
- Monitor adoption — Track usage metrics and provide training for low-adoption tools
Key Performance Indicators
Pipeline Metrics
- Pipeline coverage ratio (pipeline value / quota)
- Pipeline velocity (time from stage to stage)
- Conversion rates by stage
- Average deal size
- Win rate by segment/product/rep
Activity Metrics
- Calls/emails per rep per day
- Meetings booked per week
- Proposals sent per month
- Response time to leads
- CRM data quality score
Outcome Metrics
- Quota attainment percentage
- Revenue per rep
- Customer acquisition cost (CAC)
- Sales cycle length
- Forecast accuracy
Implementation Roadmap
Phase 1: Foundation (Months 1-3)
- Define vision, mission, and guiding principles aligned with company objectives
- Assess current state maturity across people, processes, technology, and data
- Identify 3-5 strategic priorities with significant business impact
- Secure executive sponsorship and budget allocation
Phase 2: Design (Months 4-6)
- Design operating model and organizational structure
- Document core processes with clear ownership and accountability
- Select and procure core technology systems
- Establish data governance framework and standards
Phase 3: Implementation (Months 7-9)
- Implement chosen technology platforms with phased rollout
- Build sales playbooks and process documentation
- Create training programs and certification paths
- Develop dashboards and reporting infrastructure
Phase 4: Optimization (Months 10-12)
- Measure KPIs and establish baseline performance
- Gather feedback from sales teams and iterate
- Optimize processes based on data insights
- Scale successful initiatives across organization
Common Pitfalls to Avoid
Over-Tooling Before Process Maturity
- Symptom: Buying tools before documenting ideal processes
- Impact: Automating chaos rather than efficiency
- Solution: Document and optimize processes first, then automate
Lack of Executive Support
- Symptom: Sales ops initiatives lack C-suite champions
- Impact: Limited budget, resources, and organizational influence
- Solution: Build business case with ROI projections and secure sponsor early
Ignoring Adoption
- Symptom: New tools or processes have low usage rates
- Impact: Wasted investment and continued inefficiency
- Solution: Involve end-users in design, provide comprehensive training, measure adoption
Data Silos
- Symptom: Multiple systems with conflicting data
- Impact: Inaccurate reporting and poor decision-making
- Solution: Establish single source of truth with clear governance
Overcomplication
- Symptom: Complex processes with too many steps or exceptions
- Impact: Low compliance and rep frustration
- Solution: Start with 80/20 approach, add complexity only when needed
Best Practices for Sales Operations Excellence
Data-Driven Decision Making
- Implement comprehensive data collection through CRM and analytics tools
- Establish clear metrics for tracking sales performance
- Use AI-powered analytics to identify customer behavior patterns
- Create feedback loops for continuous improvement
- Analyze sales data daily to catch problems early
Sales and Marketing Alignment
- Create shared KPIs across both teams
- Implement regular cross-team meetings and planning sessions
- Use integrated platforms for shared data access
- Establish clear lead handoff processes and SLAs
- Develop joint content strategies and buyer personas
Continuous Performance Tracking
- Monitor KPIs such as conversion rates, deal size, cycle length, and response time
- Use revenue intelligence tools to improve forecast accuracy
- Establish scorecards to measure go-to-market initiative success
- Provide simple, clear goals for reps with real-time visibility
- Review and refine strategies based on performance data
Process Refinement and Standardization
- Build repeatable sales motions that scale across teams and regions
- Create sales playbooks with strategies, objection handling, and practice scenarios
- Standardize qualification criteria (e.g., BANT, MEDDIC, CHAMP)
- Define clear stage exit criteria based on buyer actions, not internal tasks
- Reduce guesswork with documented best practices
Using the Reference Files
When to Read Each Reference
/references/process-optimization.md — Read when designing or refining sales processes, eliminating bottlenecks, standardizing workflows, or implementing process improvements. Contains detailed frameworks for process mapping, optimization methodologies, and change management.
/references/territory-planning.md — Read when designing territory structures, balancing workloads, assigning accounts to reps, or conducting territory analysis. Includes territory design models, assignment strategies, and balancing frameworks.
/references/compensation-design.md — Read when creating or modifying sales compensation plans, setting quotas, designing commission structures, or aligning incentives with business goals. Provides compensation plan types, quota-setting methodologies, and incentive design principles.
/references/analytics-reporting.md — Read when building sales dashboards, defining metrics, creating reports, or establishing analytics infrastructure. Contains dashboard design principles, metric definitions, and reporting best practices.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?