Skip to content
RevStackGet in touch →
The stack map

The RevOps stack, mapped by the job each tool does

91 tools12 categories in 5 groupsA map, not a ranking

Every category here is one job a revenue stack has to do. The Franken-Stack score reads how many of these tools one posting hands to a single person, how much they overlap, and whether the posting says how they connect.

The catalog is the reference for the tools named in job descriptions. It does not rank vendors, and the record does not yet store which category each named tool falls in, so nothing on these pages claims how often a tool appears. How tools are categorized when scored.

3.2

tools named in the average scored posting, out of 1,451 postings.

21%

of scored postings name five or more tools. See the distribution.

37.1

average Franken-Stack, last collected 22 April 2026. What it measures.

91 tools, listed alphabetically within each category

01

System of record

Where accounts, contacts, and pipeline live. Every other tool reads from it or writes back to it.

02

Create demand

Bring buyers in: campaigns, target accounts, and the first conversation on the website.

03

Work the pipeline

Find the right people, reach them, and learn from what happens on calls.

04

Close and keep revenue

Turn a deal into a quote, an invoice, and a customer who renews.

05

Move and measure data

Connect the tools, store the history, and report on what happened.

Twelve categories here, eleven in the parser

The scoring parser files every tool it finds under one of eleven keys. Ten of those keys have a category on this map. The map adds two the parser does not have, ABM & Intent and Conversational, for browsing; their tools still count toward a posting’s tool total under one of the parser’s keys. The eleventh key, other, catches spreadsheets, SQL, Slack, Jira, and anything else, and has no page here.

Every parser key, defined · How the parser uses them