| 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 |
|---|