Optimize Revenue Operations & GTM Strategy
A skill for revenue operations - stage-by-stage funnel metrics, tech stack architecture, and named handoff playbooks.
Maintainer of this project? Claim this page to edit the listing.
1.0.0Add to Favorites
Why it matters
Align sales, marketing, and customer success teams to drive revenue growth through strategic GTM planning, process optimization, and integrated tech stacks.
Outcomes
What it gets done
Design and optimize Go-To-Market (GTM) strategies, including revenue modeling and market segmentation.
Streamline lead management, opportunity management, and forecasting processes.
Architect and manage RevOps tech stacks, ensuring data hygiene and seamless integrations.
Establish unified metrics and dashboards for key revenue stages.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-revenue-operations | bash Overview
Revenue Operations Expert
This skill aligns sales, marketing, and customer success around one revenue engine, with stage-by-stage funnel metrics, tech stack architecture, and named lead, forecast, and handoff playbooks. Use it when designing or optimizing the operational alignment between sales, marketing, and customer success, not a single team's isolated process fix.
What it does
This skill provides revenue operations strategy aligning sales, marketing, and customer success across three competencies: GTM strategy (revenue model design, GTM motion optimization, market segmentation, territory design, capacity planning), process optimization (lead management, opportunity management, forecast methodology, deal desk operations, handoff processes), and systems and data (tech stack architecture, CRM administration, data hygiene, integration strategy, analytics infrastructure). The core revenue engine tracks a funnel from Marketing through SDR, AE, CS, to Expansion, with named metrics at each stage - MQL, SQL, Close, and NRR - and four alignment areas: a single source of truth for data, seamless handoffs for process, an integrated stack for technology, and unified metrics for goals.
When to use - and when NOT to
Use it when designing or optimizing the operational alignment between sales, marketing, and customer success - not for a single team's isolated process fix. It is not a generic org-design framework: every recommendation is scoped to the specific revenue-engine stages (marketing, SDR, AE, CS) and their handoffs.
Inputs and outputs
Given a revenue operation to optimize, it benchmarks against a fixed metrics dashboard: MQLs at the marketing stage, an 80% SQL/meeting conversion target at the SDR stage, a 25-35% win rate at the AE stage, greater than 110% net revenue retention at the CS stage, and an overall CAC:LTV ratio of at least 3:1. It maps the tech stack into core systems (CRM such as Salesforce or HubSpot, marketing automation, sales engagement, revenue intelligence) and supporting tools (data enrichment, analytics/BI, CPQ, contract management, a customer success platform), and runs named process playbooks: lead management (capture and scoring, routing rules, SLA definitions, a recycling process), a forecast process (weekly pipeline review, commit categorization, coverage analysis, accuracy tracking), and four specific handoffs - MQL to SDR, SQL to AE, Closed Won to CS, and Expansion back to AE.
Who it's for
RevOps leaders and GTM teams who need concrete stage-by-stage targets and named playbooks rather than abstract alignment principles - covering the full funnel from lead capture through renewal and expansion.
Source README
Revenue Operations Expert
Strategic and operational expertise in aligning sales, marketing, and customer success.
Core Competencies
GTM Strategy
- Revenue model design
- GTM motion optimization
- Market segmentation
- Territory design
- Capacity planning
Process Optimization
- Lead management
- Opportunity management
- Forecast methodology
- Deal desk operations
- Handoff processes
Systems & Data
- Tech stack architecture
- CRM administration
- Data hygiene
- Integration strategy
- Analytics infrastructure
RevOps Framework
The Revenue Engine
Marketing → SDR → AE → CS → Expansion
↓ ↓ ↓ ↓
MQL SQL Close NRR
Alignment Areas
- Data: Single source of truth
- Process: Seamless handoffs
- Technology: Integrated stack
- Goals: Unified metrics
Key Metrics Dashboard
| Stage | Metric | Target |
|---|---|---|
| Marketing | MQLs | Varies |
| SDR | SQLs/Meetings | 80% conversion |
| AE | Win Rate | 25-35% |
| CS | NRR | >110% |
| Overall | CAC:LTV | 3:1+ |
Tech Stack Components
Core Systems
- CRM (Salesforce, HubSpot)
- Marketing Automation
- Sales Engagement
- Revenue Intelligence
Supporting Tools
- Data enrichment
- Analytics/BI
- CPQ
- Contract management
- Customer success platform
Process Playbooks
Lead Management
- Lead capture and scoring
- Routing rules
- SLA definitions
- Recycling process
Forecast Process
- Weekly pipeline review
- Commit categorization
- Coverage analysis
- Accuracy tracking
Handoff Processes
- MQL → SDR
- SQL → AE
- Closed Won → CS
- Expansion → AE
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.