Sales-led AI buys the Salesforce stack; usage-metered AI builds the meter
A company's monetization stack forks on who it sells to. Sales-led, enterprise-contract AI companies buy the standard Salesforce + NetSuite + CPQ revenue stack; usage-metered, developer-facing companies build their own metering pipeline and often name no CRM at all. The split tracks go-to-market motion, not company size — and across the corpus the build-the-meter side now outnumbers the buy-the-stack side roughly two to one.
What's happening — and why
What's happening: across the 252 corpus companies with a classified monetization stack, Salesforce (as a named vendor) appears in 63, NetSuite in 25, and a CPQ layer (Salesforce CPQ, DealHub, or Conga) in 21. But the diagnostic cut is the fork: 45 companies pair a Salesforce vendor CRM with no in-house meter (sales-led), while 89 run their own built meter and name no Salesforce at all (usage-built). The usage-built side now roughly doubles the sales-led side — the developer-facing build-the-meter motion is the corpus majority.
Why: the stack follows the pricing model, and the pricing model follows the buyer. Sales-led companies sell custom-quoted enterprise contracts — they need CRM, quote-approval routing (CPQ), and ASC 606 rev-rec (NetSuite), but very little metering, because the price was negotiated, not computed. Usage-metered companies sell self-serve to developers — their price is computed from usage events, so they build the meter and frequently skip the CRM entirely. As the corpus has grown to 338 companies, the developer-facing cohort has scaled faster, tilting the fork toward build.
How it works
Evidence over time
23 supporting · 5 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Skydio | Jun 2026 | Sales-led: Salesforce + Salesforce CPQ + DealHub + Conga CLM + NetSuite, no metering build — five bought enterprise revenue tools for hardware/defense per-deal contracts. |
| Cohere | Jun 2026 | Sales-led: core GTM platforms Salesforce CRM + Marketo + CPQ with a NetSuite to Salesforce order-to-cash integration; per-token meter is undisclosed/inferred. |
| CoreWeave | Jun 2026 | Sales-led: Salesforce (Sales/Revenue/Service Cloud incl CPQ) + Oracle NetSuite with Advanced Revenue Management; no consumption-billing vendor named despite metering GPUs by the hour. |
| Clay | Jun 2026 | Sales-led: primary Salesforce builder maintaining CPQ and billing workflows inside Salesforce, Stripe for payments — quote-to-cash lives in Salesforce CPQ, no billing-platform build. |
| Cresta | Jun 2026 | Sales-led: dedicated Revenue Technology team building Salesforce Flows/Apex, CPQ and quote approval; per-agent-seat contracts need no usage meter. |
| Harvey | Jun 2026 | Sales-led: Salesforce + NetSuite + Marketo + a CPQ/quote-to-cash layer; 16 RevOps and 53 customer-success reqs, no metering build. |
| Scale AI | Jun 2026 | Sales-led: Salesforce + NetSuite + a CPQ layer (vendor unconfirmed); enterprise data-labeling contracts. |
| Cursor | Jun 2026 | Usage-metered: in-house metering pipeline (events to aggregation to ledger to invoiced amounts in Stripe), no Salesforce named in the stack. |
| Langfuse | Jun 2026 | Usage-metered: in-house ClickHouse meter feeding Stripe Billing, no CRM named — developer self-serve motion. |
| Firecrawl | Jun 2026 | Usage-metered: first-party credit metering and credit-pack/auto-recharge overflow, no CRM named. |
| Tavus | Jun 2026 | Usage-metered: in-house usage metering and billing in the Developer Portal, no Salesforce. |
| Lovable | Feb 2026 | Usage-metered: in-house credit-usage metering ledger feeding Stripe, no CRM named — self-serve PLG. |
| Kustomer | Jun 2026 | Usage-metered: per-conversation usage metering and quota enforcement, Kustomer-operated, no CRM in the stack. |
| Parloa | Jun 2026 | Sales-led: Salesforce CRM + SAP for invoicing/rev-rec + Gong + Databricks, full quote-to-cash. Job ad names the stack — 'Build and maintain Airbyte pipelines that pull data from Salesforce, Gong, HRIS, finance systems'; 'Manage invoicing workflows and revenue recognition accuracy in SAP'. No in-house meter named. (job-boards.eu.greenhouse.io/parloa/jobs/4694390101, /4843389101) |
| Snorkel AI | Jun 2026 | Sales-led: Salesforce spine with a foundational Deal Desk + CPQ + ASC 606 rev-rec buildout — 'assembling order forms, maintaining Salesforce accuracy, routing approvals'; 'Strong working knowledge of CPQ, CRM (Salesforce), and CLM'. No metering build for its gated six-figure Data-as-a-Service contracts. (job-boards.greenhouse.io/snorkelai/jobs/5993298004, /5826769004) |
| Observe.AI | Jun 2026 | Sales-led: textbook CRM spine — 'Leverage a modern sales tech stack (Salesforce, Gong, Outreach, ZoomInfo, 6sense, Clari)'; the per-agent contract is quoted, no billing/metering vendor surfaces. (observe.ai/position?gh_jid=5107653008) |
| PolyAI | Jun 2026 | Sales-led: Salesforce + Gong for renewal forecasting on a gated per-minute model — 'accurate forecasting and pipeline management within Gong and Salesforce'; expansion is ROI-justified renewal, not a self-serve meter. (job-boards.eu.greenhouse.io/polyai/jobs/4873022101) |
| Chroma | Jun 2026 | Usage-built: in-house per-tenant usage meter (CDC off its Postgres WAL to object storage) — 'buffered in memory and aggregated per tenant... flushes its buffered batch of aggregated events to object storage' — buys Orb only for the billing layer, names no CRM. (trychroma.com/engineering/billing) |
| Weaviate | Jun 2026 | Usage-built: in-house meter behind its per-dimension price — 'Vector dimensions are calculated by multiplying the number of objects by the vector dimensionality... multiplied by the replication factor'; Stripe + cloud marketplaces are payment rails only, no CRM/RevOps role on the board. (weaviate.io/blog/weaviate-cloud-pricing-update) |
| RunPod | Jun 2026 | Usage-built (PLG-CRM variant): own credit-ledger meter behind per-second pricing — 'Credits are deducted in real-time... Billing runs every 5 minutes' — payments on Stripe; the named CRM is HubSpot (Salesforce only inferred), the PLG-side variant, now bolting on a Deal Desk + CPQ for enterprise. (docs.runpod.io/accounts-billing/billing; job 5221413008) |
| OpenRouter | Jun 2026 | Usage-built: builds metering, billing and spend-management in-house — 'dashboards, admin tooling, billing and spend management, analytics, onboarding' — for a marketplace whose product IS the meter (credit ledger + 5.5% fee); Stripe is payments only, no CRM named. (jobs.ashbyhq.com/openrouter/0c6bbb7f-ea09-45b6-b185-8a17a8de214d) |
| Salesforce | Jul 2026 | Attacks the fork's premise from the CRM side: Salesforce completed its acquisition of m3ter, the metering-and-rating engine behind Revenue Cloud Advanced. The site banner now reads 'm3ter is now part of Salesforce' with the header lockup and footer copyright both 'm3ter from Salesforce', and the /pricing page is otherwise word-for-word unchanged (four quote components, zero dollar amounts). The fork assumed CRM-buyers-quote and meter-builders-compute were disjoint needs; when the CRM vendor ships usage metering natively, buying Salesforce stops implying you did not buy a meter. |
| HubSpot | Jul 2026 | The build side becoming a vendor, and the PLG-CRM variant selling the meter too: HubSpot's in-house Commerce Hub quote-to-cash shipped as Revenue Hub — a priced sixth Hub at Free / from $95/mo (CPQ quoting, contracts, e-signature, revenue analytics) / from $140/mo (advanced quote approvals) — with HubSpot Payments at 2.9% + $0.50 per card transaction (0.8% + $0.50 ACH, capped at $10) and a flat 0.75% platform fee for sellers who keep Stripe. HubSpot is named as the CRM by 32 corpus companies; it now also sells them the billing layer this fork assumed they would either build or rent from a specialist. |
Counterexamples
- Perplexity AI · Jun 2026 — Carries both halves: Salesforce + NetSuite + a build-over-buy CPQ AND an in-house usage-based billing platform — sells both self-serve developers and enterprise contracts.
- Anthropic · Jun 2026 — Carries both halves: Salesforce + CPQ + NetSuite + Metronome AND a homegrown ledger — frontier-lab scale forces the full enterprise stack plus a custom billing core.
- Vercel · Jun 2026 — Carries both halves: Salesforce (CRM) + NetSuite alongside Orb + an in-house real-time usage pipeline — a usage-metered product with an enterprise sales motion bolted on.
- Orb · Jun 2026 — Runs Salesforce as its only named tool yet sells usage-billing — a billing vendor that buys CRM and dogfoods its own meter rather than building a separate one.
- Nebius AI · Jun 2026 — Carries both halves: buys Salesforce + NetSuite but is building the meter-to-invoice spine in-house — 'Standardize handling of complex deal constructs (usage-based pricing, multi-year deals, custom terms)'; a 0→1 Pricing & Packaging hire bridges self-serve GPU-hours and sales-negotiated commits. (careers.nebius.com/?gh_jid=4885097101, /4868075101)
Trivia
-
Across the 252 classified-stack companies the fork now tilts hard to build: 45 companies pair a Salesforce vendor CRM with no in-house meter (sales-led), while 89 build their own meter and name no Salesforce (usage-built) — the usage-built side roughly doubles the sales-led side, and 18 more carry both halves at once. (Recomputed at 263 classified-stack companies on 2026-07-30: 47 sales-led vs 96 usage-built vs 18 both on the same broad definition.)
-
Salesforce is the single most-named CRM vendor in the monetization-stack corpus — 68 of the 263 classified-stack companies as of 2026-07-30 — with HubSpot (32) and NetSuite (30) behind it; the CRM you buy signals the motion you run.
-
27 companies name a CPQ layer and nearly all of them also run Salesforce — CPQ essentially never appears without a CRM, confirming quote-to-cash is bolted onto the enterprise CRM rather than standing alone.
-
The fork points in OPPOSITE directions depending on one taxonomy field. Counting only stack entries whose category is literally `metering` with basis `in-house`, the 263-company base splits 64 sales-led against 39 usage-built — the buy side leads. Counting any in-house-basis build component, the same base splits 47 against 96 — the build side doubles the buy side. The gap exists because 78 in-house entries across 74 companies are filed under a generic `in-house` category rather than the category that describes them: Baseten's "Frontier Gateway (in-house metering & rate-limiting)" is filed as `in-house`, so a strict read scores Baseten as having no meter at all.
-
Both CRM platforms started selling the meter in the same fortnight, which attacks the fork's premise directly. Salesforce completed its acquisition of m3ter — the metering-and-rating engine behind Revenue Cloud Advanced — on 2026-07-21, and HubSpot shipped Revenue Hub on 2026-07-30 as a priced CPQ/billing/payments product (Free / from $95 / from $140 per month, 2.9% + $0.50 per card transaction, and a 0.75% platform fee on sellers who keep Stripe). "Bought Salesforce" no longer implies "did not buy a meter."
-
The CPQ layer that the sales-led side of this fork buys is turning into a cheap or free SKU. Three corpus vendors productized it within twelve days: HubSpot's Revenue Hub Professional bundles CPQ quoting from $95/mo (2026-07-30), Chargebee gave CPQ Lite away free for the first 50 quotes on every Billing tier (2026-07-22), and Freshworks priced Branded documents/CPQ at $19/user/month (2026-07-21). What used to be an implementation project — the reason a deal desk needed staffing — is becoming a line item.
-
The purest sales-led stack in the corpus is still Skydio: Salesforce + Salesforce CPQ + DealHub + Conga CLM + NetSuite — five bought enterprise revenue tools and zero metering build, fitting its hardware/defense per-deal contracts.
-
The cleanest counterexample to the fork is the frontier lab that carries both halves: Perplexity runs Salesforce + NetSuite + a build-over-buy CPQ AND an in-house usage-based billing platform — selling self-serve developers and enterprise contracts forces it to build the meter and buy the CRM at once.
For buyers
Read a vendor's stack as a tell about how it will sell to you. A Salesforce + CPQ + NetSuite stack means custom-quoted contracts, approval routing, and a sales process — budget for negotiation and expect no public price to anchor against. An in-house-meter / no-CRM stack means self-serve, computed pricing, and a usage bill you can model — and that is now the more common shape in the corpus. The companies that carry both halves (Perplexity, Anthropic, Vercel, Nebius) sell both ways — which means you can often choose the self-serve metered path even when an enterprise sales motion exists.
For vendors
Do not buy the half of the stack your go-to-market does not need. A usage-metered self-serve company adding Salesforce CPQ before it has enterprise deals is premature; a sales-led enterprise company building a metering pipeline for custom-quoted contracts is wasted engineering. The fork is clean enough to use as a planning heuristic: the moment your motion changes — self-serve adding enterprise, or enterprise adding self-serve — is the moment you acquire the other half (which is exactly what the 18 both-halves companies did).
Outlook — what to watch
Logged new in June 2026 and sharpened twice since. The fork holds as long as pricing model tracks buyer — which the broader corpus confirms (the meter tracks the buyer). What has shifted is the balance: at corpus 338 the build-the-meter side (89) roughly doubles the buy-the-stack side (45), where the two were near-even at corpus 190. It blurs only as more companies go both-ways at scale — Perplexity, Anthropic, Vercel and Nebius already carry both halves, and the 18-company dual-stack set is the thing to watch. CPQ almost never appearing without a CRM (18 of 21) remains the most stable sub-pattern.
Bottom line
The monetization stack forks on go-to-market: 45 corpus companies run Salesforce with no meter (sales-led), 89 run a built meter with no CRM (usage-metered) — build now roughly doubles buy. Salesforce is named by 63 of 252 companies with a classified stack, NetSuite by 25, a CPQ layer by 21 — and CPQ almost never stands alone.
FAQ
What software do sales-led AI companies use to bill?
The standard enterprise revenue stack: Salesforce CRM, a CPQ/quote-to-cash layer (Salesforce CPQ, DealHub, or Conga), and NetSuite for ASC 606 revenue recognition. In the corpus, Salesforce is named by 63 of the 252 companies with a classified stack, NetSuite by 25, and a CPQ layer by 21. Skydio runs the purest version — five bought enterprise tools, zero metering.
Why don't usage-metered AI companies use Salesforce?
Their pricing is computed from usage events, not negotiated, so they build a metering pipeline and frequently skip the CRM entirely. 89 corpus companies run an in-house meter and name no Salesforce — Cursor, Langfuse, Firecrawl, Tavus, Lovable, Kustomer, Chroma, Weaviate, and OpenRouter among them — and that build-the-meter cohort now roughly doubles the sales-led one.
Does CPQ ever appear without a CRM?
Almost never. 21 corpus companies name a CPQ layer and 18 of them also run Salesforce — quote-to-cash is bolted onto the enterprise CRM rather than standing alone.
Which companies use both stacks?
Frontier labs and infra vendors that sell both self-serve and enterprise — 18 in the corpus carry both halves, including Perplexity (Salesforce + NetSuite + a build-over-buy CPQ AND an in-house billing platform), Anthropic (Salesforce + CPQ + NetSuite + a homegrown ledger), Vercel (Salesforce + NetSuite alongside Orb + an in-house usage pipeline), and Nebius (buys Salesforce + NetSuite while building the meter-to-invoice spine). The fork tracks motion, so dual-motion companies carry both halves.