Appearance
Sales
Sales AI tooling is dominated by per-seat SaaS contracts that already live in your CRM and revenue ops budget. Embedded AI inside Salesforce, HubSpot, and Microsoft is rarely line-itemed separately. Credit-based outbound tools (Clay) are the easiest place to overspend.
What's tracked
| Tool | Vendor | Pricing model | Coverage today | Notes |
|---|---|---|---|---|
| Clay | Clay | Credit-based (enrichment + outbound) | Invisible | Easy to overspend — credits burn fast on automated waterfalls. Track aggressively. |
| Gong | Gong | Per-seat subscription | Invisible | Call intelligence + deal forecasting. Track as contract SaaS. |
| HubSpot AI | HubSpot | Bundled with HubSpot tier | Invisible | Embedded — usually no separate line item. |
| Salesforce Agentforce / Einstein | Salesforce | Per-conversation / bundled | Invisible | Embedded in CRM. Agentforce conversation pricing is unpredictable — model carefully. |
| Apollo | Apollo | Per-seat subscription | Invisible | Track as contract SaaS spend. |
| Outreach | Outreach | Per-seat subscription | Invisible | Track as contract SaaS spend. |
| Salesloft | Salesloft | Per-seat subscription | Invisible | Track as contract SaaS spend. |
What Flowstate misses today
All of it. Sales AI is mostly copilots and embedded CRM features that people use, so it belongs at the finance/SaaS-spend layer, never as worker lines. The exception is Clay — credit-based outbound enrichment can spike with a single misconfigured automation, so give it its own budget line with a deliberately high monthly ceiling and reconcile against actual credit usage monthly.
Salesforce Agentforce is the one to watch: per-conversation pricing means a chatbot rollout can move a six-figure number without anyone noticing. An Agentforce chatbot is an autonomous workload, not a tool a person uses. Model it as an Agent with its own cost line rather than rolling it into the Salesforce subscription.