The typical stack
A representative B2B technology RevOps stack includes: CRM (Salesforce, HubSpot), marketing automation (HubSpot, Marketo, Pardot), customer success platform (Gainsight, Totango, ChurnZero), analytics and BI (Looker, Tableau, ThoughtSpot), data warehouse (Snowflake, BigQuery), ELT/ETL (Fivetran, Hightouch), revenue intelligence (Gong, Clari, Outreach), and enablement (Highspot, Seismic, MindTickle).
The stack is typically eight to twelve tools at mature scale, with additional point solutions for specific use cases. The cost can run into the millions annually for larger implementations.
The integration principle
Tooling is downstream of integration, not constitutive of it. A sophisticated stack with poor integration produces worse outcomes than a simpler stack with strong integration. The integration work is the function; the tools support it.
This principle has direct investment implications. Start with the integration layer (data warehouse, identity resolution, shared definitions, data contracts) before optimising individual applications. Resist adding new applications until current applications are integrated. Treat tool selection as a multi-year architectural decision, not a discrete procurement question.
AI and the evolving stack
AI and revenue intelligence are increasingly material elements of the stack. Automated forecasting, deal coaching, opportunity scoring, operational reporting, and call analytics are moving from differentiating capabilities to table-stakes capabilities. RevOps teams should be deliberate about incorporating AI into the operational backbone rather than treating it as an add-on category.
The principal AI investment question is not which tool to buy but where in the operational workflow AI should sit. AI as a layer on top of the existing operating system tends to under-deliver; AI integrated into the operating system itself tends to be more transformative.