A ground-truth field study of the go-to-market and revenue-operations software actually running inside LeanScale's customer base — reconstructed not from a survey, but from delivery logs, call transcripts, and live systems, then verified tool-by-tool for provenance.
Salesforce owns the record. HubSpot owns the marketing layer. And the choice between them is decided by headcount, not preference.
Most "state of the stack" reports are self-reported surveys. This one is reconstructed from what these companies actually operate — and adjusted for a distinction surveys miss: the tools a company owns versus the tools a vendor runs on its behalf.
Finding 01 · The CRM line
Salesforce is the CRM of record in 63% of companies, HubSpot in 21%. HubSpot runs in 77% of stacks — but doing two different jobs: the CRM for 33% of companies, and a marketing layer under Salesforce for 44% more. Split it apart and Salesforce is the only near-universal CRM; HubSpot's real reach is its marketing engine.
Finding 02 · The size crossover
Below 200 employees the split is a dead heat — 38% Salesforce, 38% HubSpot. Cross 200 and it isn't close: 85% Salesforce in the 201–1,000 band, and 100% above 1,000. Size, not sector, is the deciding variable.
Finding 03 · The ubiquity floor
Separate HubSpot's two roles and only Salesforce (72%) is near-universal as a single tool. Below it, a tight cluster clears 40%: HubSpot-as-marketing (49%), Clay (44%), Gong (40%). Enrichment as a category reaches 70% of companies; conversation intelligence, 51%. Everything else is a choice.
Finding 04 · The metering gap
Among companies that bill on consumption, virtually all meter usage — but only ~20% run a purpose-built metering engine (Metronome, Orb, Lago, Ordway). The rest meter through the warehouse and Stripe. Zero subscription-only companies touch metering at all.
Finding 05 · Clay's quiet takeover
Clay is in 44% of stacks as a customer-owned tool — and once you add the instances a partner runs on their behalf, its reach approaches two-thirds. No enrichment incumbent (ZoomInfo 35%, Apollo 26%) comes close on trajectory.
Finding 06 · The AI-native tell
The leanest, youngest AI-native companies skip the incumbents entirely for Attio, and treat Clay plus a warehouse as the operating core rather than the CRM. It is the clearest leading indicator of where new stacks start.
Finding 07 · Depth scales with stage
The median company runs 10 GTM tools; the largest run 25+. The categories that separate them — CPQ (30%), lead-to-account routing (26%), intent/ABM (21%) — switch on when a company starts selling up-market.
Every claim here traces to primary evidence. Where the record was thin, we say so.
The sample. Every company in the study is — or recently was — a customer of LeanScale, a revenue-operations engineering firm. That is the study's strength and its bias: these are B2B software companies serious enough about GTM to hire a specialist partner. Read the findings as "the stack of companies investing in revenue operations," not a random market draw.
The evidence. For each company we mined four internal sources — thousands of delivery-project comments, customer call transcripts, shared Slack channels, and Salesforce firmographics — then corroborated against public web research. Tool presence was drawn from things you can't fake in a survey: access-provisioning checklists, integration channels, and implementation work.
The provenance rule. The discipline that separates this from a keyword count: every tool was tagged as customer-native, partner-introduced (run by LeanScale on the engagement), or the company's own product. Only customer-native tools count toward the stack statistics — so a partner's Clay instance, or a martech vendor's own product name, never inflates the numbers.
The caveats. Adoption is a floor, not a ceiling — true penetration runs slightly higher than reported. Figures are point-in-time (H1 2026) and several companies are mid-migration. Confidence is graded; only confirmed-and-likely signals populate the charts.
A survey tells you what buyers say they use. Delivery logs tell you what they've actually provisioned, integrated, and paid an engineer to configure. This is the second thing.
A panel of 50+ B2B software companies, weighted toward Series B–C, mid-market-and-up, and North America — with a heavy AI-native and security/fintech tilt.
By Sector
By Headcount
By Funding Stage
By Revenue Model
By GTM Motion
By Region & Profile
Share of companies with each tool in their own stack — customer-native only, partner-run instances excluded. Category shown for context.
Most-adopted GTM & RevOps tools
% of companies · customer-native, confirmed & likely
HubSpot is split into its two roles — CRM vs marketing platform — because blending them overstates it (see "HubSpot's two jobs" in the CRM section). Operational tooling (Slack, Zoom, Okta, Google Workspace, Notion) is excluded — near-universal and not GTM-specific. "Clay" counts only companies that own their instance; an additional cohort runs Clay through LeanScale (see the LeanScale Lens).
The market has two near-universal tools and a long tail. After HubSpot and Salesforce, adoption falls off a cliff — only Clay and Gong clear 40%. Category standardization stops at the CRM.
The CRM decision anchors everything downstream. It's not a coin flip — it's a function of company size, and increasingly a layered decision rather than an exclusive one.
CRM of record
Primary system of record · % of companies
HubSpot's two jobs
HubSpot runs in 77% of stacks — but as two different tools
For 33% of companies HubSpot is the system of record; for 44% it's purely a marketing-automation layer beneath Salesforce. Only a couple use it for both. Counting HubSpot once — the way most stack reports do — blends a 33% CRM and a 44% marketing tool into a single misleading "77%." This study keeps them separate everywhere.
CRM choice by company size
% of each headcount band on each CRM as system of record
Bands exclude the dual-CRM cohort, so rows need not sum to 100%.
Salesforce wins the record; HubSpot wins the footprint. Salesforce is the system of record in 63% of the base, but HubSpot shows up in 74% of all stacks — the single most common tool in the study — because most Salesforce companies still run HubSpot as their marketing engine.
The crossover is at ~200 employees. Below it, HubSpot and Salesforce are tied. Above it, Salesforce takes 85–100%. Companies inherit their CRM from their scale and their enterprise-sales ambitions.
A small cohort runs both as genuine dual-CRM — mid-migration, or a hardened sales-vs-marketing split that now depends on a brittle two-way sync. The costliest architecture in the study, and rarely a choice anyone made on purpose.
"Salesforce vs HubSpot" is the wrong frame. The modern default here is Salesforce as CRM with HubSpot as the marketing layer beneath it — more than 40% of companies run exactly that. HubSpot didn't lose the CRM war; it changed which war it's fighting.
For each GTM/RevOps category: what share of companies have adopted it, and which tools own the share. Coverage is the headline number; the bars are the leaders within.
The questions this study was built to answer: do bigger companies skew Salesforce? Do usage-based companies meter? What does an AI-native stack look like?
Usage-based pricing vs metering tooling
Consumption/hybrid sellers vs subscription sellers
Size predicts CRM. The cleanest relationship in the data: Salesforce share rises monotonically with headcount, from a tie under 200 employees to a near-monopoly above 1,000. Ask a company's headcount before its sector.
Usage-based companies meter — but haven't bought metering. Consumption is now the majority pricing model (56% usage or hybrid), and virtually all meter. Yet only a fifth run a dedicated metering engine; the rest stitch together the warehouse and Stripe. The clearest white-space gap in the modern stack.
AI-native ≠ more tools. The AI-native companies don't run bigger stacks — they run different, leaner ones: next-gen CRM (Attio), warehouse-as-source-of-truth, and Clay as the automation core, often skipping the enterprise RevOps layer entirely.
Stacks aren't random — they cluster. These five patterns are overlapping lenses, not exclusive bins; a company can live in two. Membership is rule-derived from the data.
Because provenance was tracked, the study reveals its own instrument: the tools LeanScale introduces into a customer's world — held separate from the customer-native numbers above.
LeanScale-introduced tooling
% of engagements where each partner-run tool appears
Vasco reaches nearly half the base. LeanScale's own BI product is deployed into 47% of engagements — a reminder that a services relationship is also a distribution channel for the partner's software.
Clay is the partner's power tool. Beyond the 44% who own Clay, LeanScale runs Clay on behalf of others — which is why a naive keyword count badly overstates customer-native Clay adoption. Separating the two is the whole point of the provenance rule.
AI arrives through the partner. Claude, Fireflies, Loom and n8n show up as delivery infrastructure — the mechanism by which AI-assisted RevOps diffuses into companies that wouldn't have adopted it on their own yet.
The reason to read a study of other companies' stacks is to calibrate your own. Based on adoption, stage, and where the frontier is moving, here is how the 176 tools sort into three tiers.
Tier 1 · Table stakes
Tier 2 · Adopt with the motion
Tier 3 · Frontier & white space
Buy Tier 1 regardless of stage. Add Tier 2 when the motion demands it. Watch Tier 3 for where your next competitor starts. The metering gap is the one place the market is visibly under-tooled today.
Want this run on your stack?
We'll reconstruct your GTM & RevOps stack the same way — from what you actually operate — and show you where you stand against the field.
Talk to LeanScale →