The revenue engine stack

Two of the four tools, Gong and Salesforce Einstein / Agentforce, are quote-based enterprise platforms with no list price; Clay and Claude have published tiers. The 03 COSTS table above breaks down each vendor's published pricing. Three meters climb with use: Clay's credit-metered enrichment, which tracks the rows and data sources you run; Gong's bill of platform fee plus per-seat licences, with onboarding costs confirmed only at the sales-quote stage; and Agentforce's per-conversation consumption inside Salesforce. Budget the procurement cycles as much as the spend, and the operator's time alongside the licences: Clay punishes unbounded experimentation, which shows up on the invoice.

Rarely, and the numbered steps are workflow order, not the order you buy in. Claude and your Salesforce estate carry the early load: Einstein's forecasting works best with unified customer data, so that foundation comes first, with Claude threading through from the start. Add Gong once call volume is worth mining for coaching and deal-risk signal, and Clay when outbound industrialises and someone owns the workflows.

Your Salesforce subscription already holds the customer record, the pipeline and the permissions the stack reads from. Einstein and Agentforce are add-ons licensed through that same estate: forecasting, scoring and next-best-action on data you already own, which works best once that data is unified through Data Cloud. What Salesforce alone never sees is conversation truth: Gong adds that, and Claude writes the messaging the CRM only stores.

Clay and Gong both feed the pipeline with intelligence, where they appear to overlap. The dividing rule is timing. Clay owns everything before contact: waterfall enrichment across providers, scoring and personalisation that decide who to approach and how. Gong owns everything after: what was said, the deal risk buried in it and the coaching signal it carries. Data quality upstream, conversation truth downstream, and neither substitutes for the other.

Often, and this tier admits it. A revenue engine only repays its procurement cycles and operator overhead at real organisational scale, where go-to-market runs as a system across many hands. Gong's platform fee wants a real sales floor; Clay wants a dedicated operator; Einstein assumes a unified Salesforce estate. A team without all three, reaching for industrial tooling a smaller kit would carry, wants the competitive tier, the professional sales stack.

Governance is set by the strictest member, Gong. It records customer conversations, so before confidential material enters this stack, put Gong on an enterprise DPA, confirm recording consent in two-party jurisdictions especially, and settle retention and cross-border terms with counsel. Keep client material out of Claude until Team or Enterprise, where conversations are excluded from training. Clay's review must cover the third-party providers it waterfalls, not Clay alone. Consent to record is standing, not a one-time setting.