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 a metering pipeline and often name no CRM at all. The split tracks go-to-market motion, not company size.
What's happening — and why
What's happening: across the 77 corpus companies with a monetization-stack profile, Salesforce (as a vendor) is named by 29, NetSuite by 11, and a CPQ layer by 11. But the interesting cut is the fork: 20 companies pair Salesforce with no in-house meter, and 17 run an in-house meter and name no CRM.
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.
How it works
Evidence over time
13 supporting · 4 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. |
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.
Trivia
-
The purest sales-led stack in the corpus is Skydio: Salesforce + Salesforce CPQ + DealHub + Conga CLM + NetSuite — five bought enterprise revenue tools and zero metering build, fitting its hardware/defense per-deal contracts.
-
11 of 77 companies name a CPQ layer and 10 of those 11 also run Salesforce — CPQ never appears without a CRM, confirming quote-to-cash is bolted onto the enterprise CRM rather than standing alone.
-
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. The companies that carry both halves (Perplexity, Anthropic, Vercel) 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 both-halves companies did).
Outlook — what to watch
Logged as new in June 2026. The fork holds as long as pricing model tracks buyer — which the broader corpus confirms (the meter tracks the buyer). It blurs as more companies go both-ways at scale: Perplexity, Anthropic and Vercel already carry both halves, and the count of dual-stack companies is the thing to watch. CPQ never appearing without a CRM (10 of 11) is the most stable sub-pattern.
Bottom line
The monetization stack forks on go-to-market: 20 corpus companies run Salesforce with no meter (sales-led), 17 run a meter with no CRM (usage-metered). Salesforce is named by 29 of 77, NetSuite by 11, CPQ by 11 — and CPQ 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 29 of 77 companies, NetSuite by 11, and a CPQ layer by 11. 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. 17 corpus companies run an in-house meter and name no Salesforce — Cursor, Langfuse, Firecrawl, Tavus, Lovable, Kustomer among them.
Does CPQ ever appear without a CRM?
Almost never. 11 corpus companies name a CPQ layer and 10 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 — Perplexity (Salesforce + NetSuite + build-over-buy CPQ AND an in-house billing platform), Anthropic (Salesforce + CPQ + NetSuite + a homegrown ledger), and Vercel (Salesforce + NetSuite alongside Orb + an in-house usage pipeline). The fork tracks motion, so dual-motion companies carry both halves.