Glossary · GTM roles and motions

What is sales operations?

The short answer

Sales operations, or Sales Ops, is the team that keeps a sales organization running: it designs territories and quotas, administers the CRM and its data, builds the pipeline reports and the forecast, and calculates commissions. It owns how the sales team sells, so that account executives and SDRs can spend their time with buyers.

Updated
Read
4 min
Written by
Antoine Blitz
On this page8 sections
  1. Real data
  2. What does sales operations do?
  3. Where does Sales Ops stop and RevOps start?
  4. What are the main sales operations roles?
  5. What tools does a Sales Ops team use?
  6. How does Sales Ops keep territory and account data current?
  7. Related terms
  8. Questions people ask

Real data

What Sales Ops jobs ask for in US postings

US job postings from the 30 days through November 10, 2026 whose whole title is one of eight standard Sales Operations forms, the same forms as on the RevOps page. Then the work and the tools that the 277 descriptions name.

Returned by the BlitzAPI API on

POST/v2/jobs/search

US job postings from the last 30 days, by title

Sales Operations Analyst or Senior Analyst
103
Sales Operations Manager
82
Sales Operations Specialist
64
Director, Head or Senior Manager of Sales Operations
28

The last row also counts "Manager, Sales Operations". One company can post several roles.

POST/v2/jobs/search

The work named in the 277 descriptions

CRM
153
Pipeline
130
Forecast (forecast, forecasts, forecasting)
129
Territory (territory, territories)
62
Quota (quota, quotas)
48
Commission (commission, commissions)
17

One request per task, read from total_results. A posting counts when its description holds one of the words in parentheses.

POST/v2/jobs/search

Tools named in the 277 descriptions

Salesforce
149
SQL
40
Tableau
36
HubSpot
31

A posting counts when its description names the tool, including the postings of the vendors themselves.

What does sales operations do?

Sales operations does the work around selling so that the sales team can sell. Account executives own their deals and SDRs own their first meetings; Sales Ops owns the plans, rules and systems that all of them share.

  • Account executivesDealsFrom the first meeting to the signature
  • SDRs and BDRsFirst meetingsFrom the list to the meeting
  • Sales leadersTargetsThe number, by team and by quarter

Owned by Sales OpsHow the sales team sells

  • Territories and quotasWhich accounts each rep owns, and the number each rep carries
  • The CRM and its dataFields, stages, duplicates, and the accounts that changed
  • Pipeline and forecastThe reports leaders read and the number they commit to
  • CommissionsWhat each rep earned from the deals that closed
  • The sales toolsThe CRM, the dialer, the sequencing and data tools, and how they connect
Each part of the sales team owns its own work; Sales Ops owns the layer they all stand on.

The job postings show where the time goes. Of the 277 US Sales Operations postings in the 30 days through November 10, 2026, 153 mention the CRM, 130 the pipeline and 129 forecasting; territories come up in 62, quotas in 48 and commissions in 17.

Check yourselfTwo account executives call the same company in the same week, each sure the account is theirs. Which Sales Ops system failed?
Show the answer key
  1. The forecastThe forecast reports on deals; it does not decide who owns an account.
  2. Territories and account assignmentEach account should have one owner. Overlapping territories, or the same company entered twice in the CRM, gave it two.
  3. The commission planCommissions pay for closed deals; they come after ownership is settled.
  4. The sequencing toolThe tool sends what it is told to send; the rule about who works the account comes first.

Where does Sales Ops stop and RevOps start?

Sales Ops stops at the edge of the sales team, and RevOps starts where the work crosses into marketing and customer success. A Sales Ops team plans territories and runs the sales pipeline; a RevOps team owns the same work plus the handoffs between teams and the numbers that span them, such as one forecast for new deals and renewals.

Renewals, which usually sit with customer success or account management, appear in only 9 of the 277 Sales Ops postings. In the same window, the eight standard Sales Operations titles counted 277 postings and the eight matching RevOps titles 258. The RevOps page sets the three operations teams side by side, with marketing operations.

What are the main sales operations roles?

The main sales operations roles run from analysis to leadership. In the postings measured, 103 of the 277 are analyst or senior analyst roles, 82 carry the title Sales Operations Manager, 64 are specialists, and 28 are director, head or senior manager roles.

Title What the role usually does
Sales Operations Analyst Reports, dashboards, forecast inputs, the analysis behind territories and quotas
Sales Operations Specialist CRM administration, data cleanup, deal desk and order processing
Sales Operations Manager Runs the function for a team or region: process, tools, planning
Director or Head of Sales Operations Owns the yearly plan with sales leadership and finance

Small companies often have one person who does all four. The work is the same; only the scope changes.

What tools does a Sales Ops team use?

A Sales Ops team works in the CRM before anything else: Salesforce appears in 149 of the 277 postings, ahead of SQL (40), Tableau (36) and HubSpot (31).

Code shows up less often than in the postings of a GTM engineer, the role that builds workflows and data pipelines on top of the same CRM.

How does Sales Ops keep territory and account data current?

Sales Ops keeps territory and account data current by refreshing it from a source instead of fixing records one by one. Territories are only as fair as the account data behind them: a company that moved its headquarters, grew past a size band or changed its domain lands in the wrong patch, and two reps can end up chasing it.

BlitzAPI supplies that data through an API. Company Search builds the account list for a territory from industry, size and headquarters location, Company Enrichment refreshes the record of each account from its LinkedIn URL, and two distribution endpoints count a company’s employees by country and its current positions by department.

The CRM hygiene use case shows how to run the refresh on a schedule.

Sources and method

Written by
Antoine Blitz, Founder, BlitzAPI
Published
API calls run on

The calls ran on November 10, 2026 through the BlitzAPI MCP server, which calls the same endpoints; they are shown here as the equivalent REST requests.

Titles are matched exactly, on the same eight forms as the RevOps page, so the two pages compare like with like. Variants such as "Sales Operations Coordinator" are not counted.

The counts are job postings, not companies or people: one company can post several roles.

Questions people ask

What is the difference between sales operations and sales enablement?

Sales operations runs the systems, data and plans a sales team sells with: territories, quotas, the CRM and the forecast. Sales enablement prepares the people: training, onboarding, playbooks and the content reps use with buyers. Operations changes how the work is set up, enablement changes how well reps do it, and some companies put both under one sales leader.

What does a sales operations analyst do?

A sales operations analyst turns the CRM into numbers that leaders can trust: pipeline and activity reports, dashboards, forecast inputs and the analysis behind territory and quota decisions. Analyst roles are common in US postings: 103 of the 277 measured on November 10, 2026 were analyst or senior analyst roles.

Is sales operations the same as sales and operations planning?

No. Sales and operations planning, or S&OP, is a monthly planning process, run across sales, operations and finance, that matches what a company expects to sell with what it can make, buy and ship. Sales operations is a team that supports the sales organization. The names are close; the work is not.

With BlitzAPI

Put it to work

For your team

For builders

The calls behind the real data on this page, as REST requests. Send them with your API key, from any language or workflow tool.

Count the US Sales Operations postings of the last 30 days

curl -X POST https://api.blitz-api.ai/v2/jobs/search \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "title": {"include": [
        "[Sales Operations Manager]",
        "[Senior Sales Operations Manager]",
        "[Sales Operations Analyst]",
        "[Senior Sales Operations Analyst]",
        "[Sales Operations Specialist]",
        "[Director of Sales Operations]",
        "[Head of Sales Operations]",
        "[Manager, Sales Operations]"
      ]},
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 30}
    },
    "max_results": 1
  }'

API reference

Count the postings that mention forecasting (the same request runs for each task)

curl -X POST https://api.blitz-api.ai/v2/jobs/search \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "title": {"include": [
        "[Sales Operations Manager]",
        "[Senior Sales Operations Manager]",
        "[Sales Operations Analyst]",
        "[Senior Sales Operations Analyst]",
        "[Sales Operations Specialist]",
        "[Director of Sales Operations]",
        "[Head of Sales Operations]",
        "[Manager, Sales Operations]"
      ]},
      "description": {"include": ["forecast", "forecasting", "forecasts"]},
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 30}
    },
    "max_results": 1
  }'

API reference

Count the postings that name a tool (Salesforce; the same request runs for each tool)

curl -X POST https://api.blitz-api.ai/v2/jobs/search \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job": {
      "title": {"include": [
        "[Sales Operations Manager]",
        "[Senior Sales Operations Manager]",
        "[Sales Operations Analyst]",
        "[Senior Sales Operations Analyst]",
        "[Sales Operations Specialist]",
        "[Director of Sales Operations]",
        "[Head of Sales Operations]",
        "[Manager, Sales Operations]"
      ]},
      "description": {"include": ["Salesforce"]},
      "location": {"country_code": {"include": ["US"]}},
      "date_posted": {"last_days": 30}
    },
    "max_results": 1
  }'

API reference

Data shouldn't be
the problem

Grab. Connect. Build.