What is sales operations: structure, scope, and metrics
A plain-language explanation of what sales operations does, how it differs from RevOps, and the structural choices that make the function effective.
Sales operations is one of the most important functions in a modern B2B company, and one of the hardest to define because every org structures it differently. This post is a plain-language explanation of what sales ops is, how it differs from the adjacent functions it gets confused with, and the structural choices that make the function effective.
The one-sentence definition
Sales operations is the function responsible for the systems, processes, data, and analysis that let the sales team run efficiently and leadership forecast revenue reliably.
The two halves of that sentence matter equally. The systems-and-processes half is what reps interact with daily (CRM, pipeline, lead routing, quota management, tooling). The data-and-analysis half is what the CRO uses weekly (forecast, pipeline health, win-loss, rep performance). Teams that do only one half are not actually running sales ops.
What sales ops owns
The scope varies by company, but a well-defined sales ops function typically owns:
1. The CRM
Platform selection, admin, user permissions, custom fields, workflow automation, integrations with adjacent tools. The CRM is the primary system of record for the sales team, and sales ops owns it.
2. Pipeline mechanics and forecasting
Pipeline stage definitions, stage probability calibration, forecast methodology, weekly rep submission workflow, manager roll-up, consolidated forecast.
3. Lead routing and territory management
Rules for assigning leads to reps based on territory, specialty, capacity, and SLA.
4. Quota and compensation administration
Setting quotas per rep, calculating commission, resolving disputes, coordinating payout with finance. Some orgs split this with finance; some keep it fully in sales ops.
5. Sales reporting and analysis
Standard reports (pipeline, forecast, win rate, cycle time, rep performance), ad-hoc analysis (why did we lose that deal, what segments are converting), and the weekly scorecard that leadership runs the business on.
6. Tool stack administration
The sales tool stack beyond CRM (sales engagement platform, dialer, enablement platform, forecasting tool, prospecting tool). Sales ops owns configuration, user management, and integration health across the stack.
7. Process documentation
The sales playbook. Pipeline stage definitions, qualification framework (BANT, MEDDIC, SPICED, or similar), objection handling, deal review template. Keeping it current so reps have a reference.
How sales ops differs from the adjacent functions
Five functions sales ops gets confused with:
Sales ops vs. revenue operations (RevOps)
RevOps is a superset. If your team has both, sales ops is the sales-specific layer; RevOps also owns marketing ops, CS ops, and the cross-functional data layer that joins them. Industry research suggests RevOps adoption has grown rapidly in B2B SaaS. At smaller companies, sales ops is often the only ops function and effectively does RevOps work within its scope.
Sales ops vs. sales enablement
Sales enablement owns the content, training, and coaching that help reps sell better. Sales ops owns the systems, processes, and data. The two are adjacent and often collaborate (enablement produces the content; ops puts it in the CRM where reps can find it). Industry data suggests approximately 90% of organizations now run some kind of sales enablement program.
Sales ops vs. CRM administrator
A CRM admin configures the CRM. Sales ops owns the CRM strategically (what data lives in it, what processes it enforces, what reports it produces) plus everything else listed above. A sales ops lead at a growing company often is the CRM admin until the team is big enough to split the roles.
Sales ops vs. sales management
Sales management is the chain of command: AEs report to managers who report to directors who report to a VP or CRO. Sales management runs the sales team day-to-day. Sales ops supports sales management with systems, data, and analysis. Different roles, different accountability.
Sales ops vs. finance
Finance owns post-revenue data (actuals, recognition, cash). Sales ops owns pre-revenue data (pipeline, forecast). The handoff is the booked deal. Finance also typically owns commission calculation at larger companies; sales ops does it at smaller ones.
When to hire sales ops
A rough staging guide:
- Under 5 reps: the founders or the VP Sales wear the hat. No dedicated ops.
- 5-15 reps: first sales ops hire. Usually a Sales Ops Manager or Analyst. Scope: CRM admin, basic reporting, lead routing, pipeline hygiene.
- 15-30 reps: sales ops team of 2-3. Dedicated specialists emerge (compensation analyst, data analyst, systems admin).
- 30-100 reps: full sales ops function. Director or Senior Director. 3-5+ person team.
- 100+ reps: VP Sales Ops or part of a VP RevOps org. 5-15+ person team split across systems, data, compensation, and analytics.
The first hire is the hardest. You want someone who can think across systems, processes, data, and strategy, not just execute one of them.
Typical sales ops team shape by stage
| Stage | Team size | Common roles |
|---|---|---|
| Startup (5-15 reps) | 1 | Sales Ops Manager |
| Growth (15-30 reps) | 2-3 | Manager + Analyst + Admin |
| Scale (30-100 reps) | 3-5 | Director + 2 Managers + Analyst + Compensation |
| Enterprise (100+ reps) | 5-15+ | VP + Director + Manager tier + specialists |
The metrics sales ops owns
Five metrics a sales ops team should produce weekly or monthly:
1. Weighted pipeline coverage
Weighted pipeline divided by quota. A healthy coverage ratio is typically 3-4x; higher if cycles are long, lower if cycles are short. Falling coverage signals a pipeline problem before it becomes a revenue miss.
2. Forecast accuracy
Submitted forecast vs. actual, measured per rep and per manager over time. The metric that tells you whether your forecasting process is working.
3. Deal velocity
Average days from Qualified to Closed Won, segmented by deal size, segment, and rep. The lever for reducing cycle time.
4. Win rate
Closed Won divided by (Closed Won + Closed Lost), segmented by segment, rep, and competitor. The lever for closing more of what you work.
5. Pipeline hygiene
Count of deals that are stuck (dwell time > 2x median per stage), stale (no activity in 14+ days), or missing required fields. The metric that keeps the CRM data clean enough to run forecasting on.
Teams that produce these five metrics on a regular cadence tend to make better decisions than teams that produce the same metrics on request. Cadence beats depth for operational metrics.
How Strkr fits a sales ops function
Strkr is designed so a Series A sales ops lead can own the full sales ops surface without engineering, admin certification, or a dedicated analyst. Specifically:
- CRM admin on every tier (custom fields, custom objects, pipeline configuration, user permissions)
- No-code flow builder for workflow automation, lead routing, and SLA enforcement
- Formula-based reports for all five of the metrics above, available on every paid tier
- AI-assisted forecasting with weekly rep submission cadence and manager roll-up
- Audit log on every record change for debugging and compliance
The design target: a one-person sales ops function at a 15-rep company should be able to run the full sales ops scope on Strkr without needing a separate BI tool, iPaaS tool, or admin certification.
For teams scaling past 50 reps where sales ops specializes into multiple seats (compensation, data analyst, systems admin), Strkr continues to serve as the system of record while the team adds dedicated tools around it.
Transparent per-seat pricing with per-workspace add-on modules. See strkr.io/pricing.
Related reading: How to choose a CRM: a practical buying framework walks through the broader buying question.
Conclusion
Sales operations owns the systems, processes, data, and analysis that let the sales team run efficiently and leadership forecast revenue reliably. The scope spans CRM, pipeline, forecasting, lead routing, quota, compensation, reporting, tool stack, and process documentation. The structural choice between “sales ops” and “RevOps” depends on company size and whether marketing ops and CS ops report in.
Effective sales ops depends on cadence over depth: produce the five key metrics on a regular schedule and the team makes better decisions than any one-time deep analysis will drive.