Sales Ops Analyst
Design CRM hygiene, pipeline dashboards, routing, territories, commissions, and forecasting when you are the solo founder wearing RevOps.
Overview
Sales Ops Analyst is an agent skill most often used in Grow (also Operate) that applies RevOps rule sets for CRM design, pipeline analytics, routing, territories, commissions, and sales tech integration.
Install
npx skills add https://github.com/ncklrs/startup-os-skills --skill sales-ops-analystWhat is this skill?
- Rule families for CRM architecture, data models, and hygiene (crm-*)
- Pipeline stage definitions, velocity metrics, and analytics guidance (pipeline-*)
- Dashboard and visualization patterns for rep and leadership views (dashboard-*)
- Automation, approval chains, lead routing, and territory design (process-*, routing-*)
- Commission plans, calculation logic, and RevOps stack coverage (Salesforce, HubSpot, Outreach, Gong)
- 6 rule prefix families in rules/: crm-, pipeline-, dashboard-, process-, routing-, commission-
Adoption & trust: 1 installs on skills.sh; 27 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
Your CRM fields and dashboards do not match how deals actually move, so forecasting and commissions are guesswork for a one-person revenue team.
Who is it for?
Founder-led B2B SaaS with an early sales motion who needs pipeline definitions and automation design before scaling reps.
Skip if: Pure product-led growth with no sales pipeline, or teams wanting generic marketing copy instead of CRM and revenue analytics architecture.
When should I use this skill?
User needs CRM workflows, sales dashboards, pipeline analytics, lead routing, territories, commissions, forecasting, data quality, or sales stack integration guidance.
What do I get? / Deliverables
You leave with concrete workflow, routing, dashboard, and comp design guidance aligned to Salesforce- or HubSpot-style RevOps practice.
- Pipeline and stage design recommendations
- Dashboard and metric definitions
- Routing, territory, or commission logic outlines
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Grow is the primary shelf because revenue instrumentation, pipeline truth, and comp mechanics compound users and deals after you have something to sell. Analytics subphase covers dashboards, velocity, forecasting, and metrics that turn CRM activity into decisions—not one-off copy tasks.
Where it fits
Sketch comp and discount guardrails so early deals stay profitable before you formalize plans.
Define stage exit criteria and a rep dashboard that tracks velocity instead of vanity created pipeline.
Design lead routing from marketing form to first-touch owner without duplicates piling up in CRM.
Run a data-quality and field-standardization pass before migrating workflows to a cleaner object model.
How it compares
Use this RevOps advisory skill—not a frontend generator or generic productivity planner—when the artifact is CRM structure and revenue metrics.
Common Questions / FAQ
Who is sales-ops-analyst for?
Solo and indie builders running outbound or sales-assisted SaaS who act as their own sales operations and analytics lead.
When should I use sales-ops-analyst?
In Grow analytics when defining pipeline stages and dashboards; in Operate iterate when fixing data quality; in Validate pricing when comp plans must align with deal economics.
Is sales-ops-analyst safe to install?
Review the Security Audits panel on this Prism page; implementing its advice may require CRM API access and sensitive revenue data in your environment.
SKILL.md
READMESKILL.md - Sales Ops Analyst
# Sales Ops Analyst Strategic sales operations expertise for revenue teams — from CRM architecture and pipeline analytics to territory design and commission automation. ## Philosophy Great sales ops isn't about more data. It's about **actionable insights** that accelerate revenue. The best sales operations teams: 1. **Enable, don't police** — Make it easier for reps to do the right thing 2. **Measure what matters** — Vanity metrics create vanity pipeline 3. **Automate the mundane** — Free reps to sell, not update fields 4. **Build for scale** — Today's workaround is tomorrow's technical debt ## How This Skill Works When invoked, apply the guidelines in `rules/` organized by: - `crm-*` — CRM architecture, data models, hygiene practices - `pipeline-*` — Pipeline analytics, stage definitions, velocity metrics - `dashboard-*` — Sales reporting, metrics, visualizations - `process-*` — Automation, workflows, approval chains - `routing-*` — Lead routing, assignment rules, territory design - `commission-*` — Comp plans, calculation logic, tracking - `data-*` — Data quality, deduplication, enrichment - `forecast-*` — Forecasting methodologies, models, accuracy ## Core Frameworks ### The RevOps Data Hierarchy | Level | What It Measures | Used By | Update Frequency | |-------|------------------|---------|------------------| | **Activity** | Calls, emails, meetings | Reps, managers | Real-time | | **Opportunity** | Deal progress, value | Reps, managers | Daily | | **Pipeline** | Forecast, velocity | Directors, execs | Weekly | | **Revenue** | Bookings, ARR, churn | C-suite, board | Monthly/Quarterly | ### Pipeline Velocity Formula ``` Pipeline Velocity = (# Opportunities × Win Rate × Avg Deal Size) / Sales Cycle Length Example: (100 opps × 25% × $50K) / 90 days = $13,889/day potential revenue ``` ### The Sales Tech Stack ``` ┌─────────────────────────────────────────────────────────────┐ │ ANALYTICS LAYER │ │ (BI Tools: Tableau, Looker, Power BI, Salesforce Reports) │ ├─────────────────────────────────────────────────────────────┤ │ CRM LAYER │ │ (Salesforce, HubSpot, Dynamics 365) │ ├──────────────────┬──────────────────┬───────────────────────┤ │ ENGAGEMENT │ INTELLIGENCE │ ENRICHMENT │ │ Outreach, Salesloft│ Gong, Chorus │ ZoomInfo, Clearbit │ ├──────────────────┴──────────────────┴───────────────────────┤ │ DATA LAYER │ │ (Integrations, ETL, Data Warehouse, CDP) │ └─────────────────────────────────────────────────────────────┘ ``` ### Lead Scoring Matrix | Signal Type | Examples | Weight | |-------------|----------|--------| | **Fit** (firmographic) | Industry, company size, tech stack | 40% | | **Engagement** (behavioral) | Website visits, content downloads, email opens | 35% | | **Intent** (buying signals) | Pricing page views, demo requests, competitor research | 25% | ### Territory Design Principles ``` ┌─────────────────┐ │ BALANCED │ │ OPPORTUNITY │ └────────┬────────┘ │ ┌───────────────────┼───────────────────┐ │ │ │ ▼ ▼ ▼ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ Account │ │ Revenue │ │ Travel │ │ Volume │ │