What is sales operations?
Sales operations (SalesOps) is the function responsible for the systems, processes, data and analytics that support a sales team. It owns CRM configuration for sales, pipeline management, forecasting, territory and quota planning, sales enablement tooling, and the reporting layer that tells leadership how the team is performing.
In smaller businesses SalesOps is often a single person reporting to the head of sales. In larger businesses it becomes a team and increasingly sits inside revenue operations.
What does a sales operations team do?
A sales operations team owns six areas: pipeline and forecasting, CRM configuration for sales, territory and quota, sales tools and integrations, sales enablement infrastructure, and sales analytics. Together these remove the operational burden from reps and managers so they can spend more time selling.
| Area | Typical responsibilities | HubSpot touchpoints |
|---|---|---|
| Pipeline & forecasting | Stage definitions, deal hygiene, forecast methodology | Deal pipelines, forecasting tool, custom properties |
| CRM config (sales) | Properties, layouts, automation, permissions for reps | Sales Hub, record customisation |
| Territory & quota | Account assignment, quota allocation, capacity planning | Teams, ownership rules, deal splits |
| Sales tools | Sequences, prospecting, call tooling, integrations | Sales Hub Pro/Enterprise, integrations |
| Enablement | Playbooks, training, onboarding | Playbooks tool, knowledge base |
| Analytics | Pipeline reports, conversion analysis, leaderboards | Custom reports, datasets, dashboards |
Sales operations vs revenue operations
Sales operations supports a single function: sales. Revenue operations supports the whole revenue team: marketing, sales and customer success. SalesOps execution sits inside the sales org; RevOps governance sits above it. In smaller businesses one function does both; in larger ones SalesOps remains as the execution layer while RevOps owns shared definitions, data and tooling.
How to build a sales operations function on HubSpot
Build a SalesOps function on HubSpot in a defined order: pipeline definitions first, then deal hygiene, then forecasting, then enablement, then advanced analytics. Skipping ahead almost always produces forecasts no-one trusts.
- Define deal stages tied to buyer actions, not seller activity. Document the exit criteria for each stage.
- Set required fields by stage so reps only see what is needed at each step.
- Implement a deal hygiene policy with workflows for stuck deals, missing fields and stale next steps.
- Stand up a forecast methodology with weighted and best-case views, plus a weekly forecast call cadence.
- Build a sales enablement library covering ICP, objection handling, pricing and competitive positioning.
- Layer in advanced analytics: stage conversion, velocity, win-loss, leakage and rep performance.
What KPIs should sales operations own?
Sales operations owns three KPI categories: forecast accuracy (variance vs actual), pipeline health (coverage ratio, velocity, stage conversion) and rep productivity (activity metrics, ramp time, average deal size). These KPIs make SalesOps measurable and tie the function to commercial outcomes.
When do you need a dedicated sales operations hire?
Hire a dedicated sales operations person once you have five or more quota-carrying reps, a multi-stage pipeline, a forecast that the CEO needs to trust, or integrations between HubSpot and other revenue systems. Below that scale, a HubSpot partner subscription delivers SalesOps outcomes faster and at lower fixed cost.
Project36 delivers sales operations as part of our Flow™ subscription, covering HubSpot engineering, reporting and enablement under one accountable team.
Keep reading