Markets hub · Roles
Know who buys, who uses, and what each role runs on.
4,349 roles, organized from module to function, area and focus, with seniority — each with its software spend per seat, the decision makers and what they weigh, its pain points and objections, where it learns, and how exposed it is to automation.
What you can do
Write to the real buyer
Pain points, sales objections and demo must-haves, for messaging that lands.
Map the buying committee
The decision makers behind the software call, what each one weighs, and buying authority by company size.
Size a seat-based market
Software spend per seat and seats by company size, for pricing and territory plans.
Screens in the app
- Overview
- Demand
- Market
- Landscape
- Trends
- Operations
- Compliance
- Economics
- Capabilities
- Pulse
Plans
Included in Starter (when Markets is the hub you pick), Growth and Enterprise. See pricing
Inside the table
What the Roles holds
One row is one role: a focus within an area, a function and a module, at one seniority, such as Sales Operations (Senior).
Measured on 29 September 2026 in the production database, table role_taxonomy.
How we measured
Rows: count(*) FROM role_taxonomy. Levels: count(DISTINCT role_module / role_function / role_area / role_focus), and the distinct module-function and module-function-area paths. Fields: information_schema.columns by registry group; filled = not NULL or empty. Sources: per-field provenance entries. Links: exact counts on contacts, reviews (author_role_fk), job_aliases, positions and the feature_taxonomy links columns on both tables.
What’s in the table
4,349
roles, one per row
4
levels: 28 modules, 173 functions, 872 areas, 2,425 focuses
86
fields per row, in 11 groups
1.4 million
contacts tagged with a role (1,444,385 exactly)
Levels
Each level sits inside the one above it. The counts are measured, not estimated.
| Level | What it is | How many |
|---|---|---|
| ModuleThe broad domain, such as Sales, Insurance or Life Sciences. | The broad domain, such as Sales, Insurance or Life Sciences. | 28 |
| FunctionA function within a module, such as Marketing or Information Technology.Many functions appear in more than one module: 310 counting each module separately. | A function within a module, such as Marketing or Information Technology.Many functions appear in more than one module: 310 counting each module separately. | 173 |
| AreaAn area of work within a function, such as Operations / Sales Support.1,383 counting each function and module separately. | An area of work within a function, such as Operations / Sales Support.1,383 counting each function and module separately. | 872 |
| FocusThe specific role, such as Sales Operations. One row per focus and seniority.4,349 roles in all, each at one of 7 seniority levels from Entry to CXO. | The specific role, such as Sales Operations. One row per focus and seniority.4,349 roles in all, each at one of 7 seniority levels from Entry to CXO. | 2,425 |
What each row holds
Every field belongs to one group. The app’s ten tabs are named after the groups; Identity holds the names and codes that place a row, and Record-keeping is not shown as a tab.
| Field group | What it tells you | Example fields | Fields | Filled on most rows |
|---|---|---|---|---|
| Identity27 fields, 20 filled on most rows | The role's module, function, area and focus, each with a code, a definition and a description, and the role code itself.For example: Role code, Focus definition, Function description, Area | Role code, Focus definition, Function description, Area | 27 | 20 of 27 |
| Demand8 fields, 8 filled on most rows | How the role buys: decision makers, target buyers, buying authority by company size, evaluation criteria, demo must-haves and sales objections.For example: Decision makers, Buying authority by company size, Sales objections, Demo must-haves | Decision makers, Buying authority by company size, Sales objections, Demo must-haves | 8 | 8 of 8 |
| Market4 fields, 2 filled on most rows | Software adoption patterns and workforce figures.For example: Software adoption patterns, Workforce figures | Software adoption patterns, Workforce figures | 4 | 2 of 4 |
| Landscape4 fields, 3 filled on most rows | Career paths, the people around the role, its typical tool stack, and the product features it uses.For example: Career pathways, Stakeholder map, Tool-stack archetype | Career pathways, Stakeholder map, Tool-stack archetype | 4 | 3 of 4 |
| Trends3 fields, 3 filled on most rows | How exposed the role is: automation potential, AI disruption and the risk of AI agents taking over the work.For example: Automation potential, AI disruption potential, AI agent replacement risk | Automation potential, AI disruption potential, AI agent replacement risk | 3 | 3 of 3 |
| Operations7 fields, 6 filled on most rows | The day-to-day: workflow, skills, responsibilities, a day in the life, and where the role learns and whom it follows.For example: Day in the life, Key responsibilities, Skills, Content consumption | Day in the life, Key responsibilities, Skills, Content consumption | 7 | 6 of 7 |
| Compliance1 field, 1 filled on most rows | The compliance rules that shape the role's software.For example: Compliance considerations | Compliance considerations | 1 | 1 of 1 |
| Economics4 fields, 4 filled on most rows | Seniority, software spend per seat and seats by company size.For example: Software spend per seat, Seats by company size, Seniority | Software spend per seat, Seats by company size, Seniority | 4 | 4 of 4 |
| Capabilities9 fields, 8 filled on most rows | The tool stack: common tools, top software categories, must-have integrations, data systems, feature requirements and software pain points.For example: Common tools, Software pain points, Feature requirements, Mandatory integrations | Common tools, Software pain points, Feature requirements, Mandatory integrations | 9 | 8 of 9 |
| Pulse2 fields, 2 filled on most rows | How the role is measured: its KPI tree and productivity metrics.For example: KPI tree, Productivity metrics | KPI tree, Productivity metrics | 2 | 2 of 2 |
| Record-keeping17 fields, 15 filled on most rows | Not shown as a tab: ids, dates, the search index, and the sources, confidence and date behind each field.For example: Sources and confidence per field, Last updated, Search index | Sources and confidence per field, Last updated, Search index | 17 | 15 of 17 |
| All groups86 fields, 72 filled on most rows | A field counts as filled on most rows when more than half the rows hold a value. | 86 | 72 of 86 |
A real row: Sales Operations
- ModuleSales
- FunctionSales
- AreaOperations / Sales Support
- This rowSales Operations
- 14 other roles share its area, among them Deal Desk, Sales Enablement and Sales Commissions.
- 962 contacts hold it, and 1,881 reviews were written by people in it.
- 13 job titles map onto it, and it links to 69 standard features it uses.
- Seniority
- Senior
- Software spend per seat
- $5,200 a year (2026)
- Seats by company size
- 45 in an enterprise, 6 mid-market, 1 in a small business
- Common tools
- Microsoft Excel, Salesforce, Slack, Tableau, Power BI, Clari and Gong, among 12 named
- KPIs
- Forecast variance under 10%; quota attainment of 60–70%
- Automation potential
- Medium
- A sales objection
- “We already have this in Salesforce; I do not want another system for the same data.”
40 of its fields carry a source note, and every one cites its sources: 55 different web addresses in all. They were written between 29 May and 17 June 2026.
How it connects
Contacts
1,444,385 of the 3,383,491 contacts carry a role; 2,080 roles have at least one.
Reviews
2,073,377 reviews record the reviewer's role, across 2,526 roles.
Job titles
23,388 job titles map onto 526 roles.
Job postings
1,618 job postings are tagged with a role, across 23 roles.
Standard features
114,341 links from 1,984 roles to the features they use. From the other side, 498,321 features link to at least one role.
Where it comes from
The four-level hierarchy and the role codes are PYRAMYD's own. The profile fields are written by AI from cited public sources, led by the O*NET occupational database and the US Bureau of Labor Statistics, and nearly every field records its sources, a confidence and the date it was written.
- Source notes on 162,684 written profile fields across 4,261 of the 4,349 roles; 161,186 of them cite at least one web source.
- 596,223 citations to 81,097 different web addresses on 23,896 sites. The most cited are O*NET and the US Bureau of Labor Statistics.
- Fields written
- 29 May – 24 July 2026
- Latest change to any row
- 9 September 2026
- Refresh
- Enrichment is paused, so no refresh is scheduled and the dates above are the latest.
- Measured
- 29 September 2026
In Product Graph
The Roles 360 opens from Markets › Roles, with these ten tabs:
- Overview
- Demand
- Market
- Landscape
- Trends
- Operations
- Compliance
- Economics
- Capabilities
- Pulse
- Search, and filter by module, function, area and focus.
- Track a role: your tracked roles show on the module's first page with their alert counts.
- Each of the ten tabs has its own address, so you can link straight to one.
- APEX, the assistant, works with the record you have open.
Browse sample role pages — no account needed.
More in Markets
See Roles on your own market.
Start free in Workspace, or book a session and we'll walk through it on your competitors, accounts and category.