In October 2025, at Dreamforce in San Francisco, I had a conversation with a success leader at a mid-sized tech company. They’d previously used a dedicated Customer Success Platform, or CSP, but after doing a tech stack audit they realized their CSP was pulling almost everything it showed them straight from Salesforce, except for a health score that their data team could easily replicate. They were wasting six figures on a UI. They moved their Customer Success team onto Salesforce in weeks and were happy with their decision. As I boarded a flight back home, the story stuck with me.
One example doesn’t make a trend, but since then, I’ve gone on a listening tour and I’ve heard versions of this story from dozens of companies at different sizes and stages. Series C startups. Frontier AI companies. Enterprise cybersecurity firms. I’ve talked with Chief Customer Officers and Customer Success Managers. The details vary but the same driving factors led all of these teams to consolidate their teams on Salesforce.
It’s worth asking whether this shift to Salesforce as a Customer Success Platform is a coincidence or a real change in the industry. So to help answer this question, I’ve talked with multiple leaders who’ve made the move to Salesforce as their dedicated customer success platform for other leaders thinking through a similar move. I’ve grouped these anecdotes into three sections:
- Why: The reasons so many teams are rethinking a separate CSP
- How: The practical ways these teams have made Salesforce act as their CSP
- What Next: How you can think through making a move to Salesforce for success
Let’s start with what a Customer Success Platform is. CSPs offer a way to manage customer records for a post-sales success team. CSMs typically use CSPs to manage customer implementation timelines, goals, activities like QBRs and outreach, and track product usage data. They also track customer health in both manual and automated ways. There’s nothing fundamental about these concepts that requires a specific system. After talking with several success leaders and operators, I’ve found several key themes that cause teams to move to Salesforce for customer success.
Customer 360
The goal of every CSP project tends to be to create a customer 360 view, but it tends to be in a silo since most success teams struggle with getting sales or support teams to collaborate in a separate platform. Salesforce is centrally positioned to create a customer 360 view since it’s natively designed for sales, marketing, and support teams. Here’s what Cameron, a customer success operations leader at Superhuman, says about creating a 360 view:
“Everything begins and ends with ensuring Salesforce is our single source of truth… I would rather just have it all in Salesforce because then I can actually give reps the view that they need to have to do their workflow within the place that they’re actually working versus having to have 10 tabs open in order to do their job. So the more we can consolidate into one tool, the center of that being Salesforce, the better.”
Cameron Whitman
Senior Manager, RevOps – Post Sales & CS at Superhuman
Redundant Technology
One of the uncomfortable realities about dedicated CSPs is that some of them also aren’t actually separate platforms in any meaningful sense. Many effectively act as a wrapper on top of Salesforce to pull account data, sync activity, and read opportunity records. There are advantages to this approach, but there are additional management costs and latency issues that teams encounter. Here’s what John Choi, who leads Customer Success operations at Apollo, on what a separate CSP was actually delivering:
“Generally speaking, I am not a big fan of layering a CSP onto Salesforce. There’s latency issues. I have some of the best Salesforce guys on the planet, and having them learn a different tool? I’m just not a fan of it… I also don’t want to have to nickel and dime for platform fees on something that should really just live in Salesforce.”
John Choi
Director of Customer Operations, Apollo.io
Unified Go-To-Market
The enterprise technology landscape has been changing in the past few years with economic shifts and the rise of AI. Sales teams are more focused than ever on customer success to help land and expand customers, like through using pilots, running QBRs, and working in lockstep with CS to grow customer relationships. On the flip side, CS teams are evolving too and are more revenue-driven than ever.
Salesforce is designed for teams to manage new logo, expansion, and renewal opportunities. These capabilities translate extremely well for CS teams so they can collaborate better on deals and forecast renewals and expansion deals. Here’s what Cameron from Superhuman says about how Salesforce supports the evolution of customer success:
“We’re not a CSM team that’s just focused on value and usage and adoption …That’s why Salesforce works in our context …We live and die by the opportunity record in CS, specifically renewal opportunities.“
Cameron Whitman
Senior Manager, RevOps – Post Sales & CS at Superhuman
Double Licensing
There’s also a financial cost to having a separate CSP that’s effectively a window into Salesforce data while your CSMs are already licensed with Salesforce. Here’s what one GTM technology specialist said about using a separate CSP:
“We were grossly overpaying for our [CSP] contract with… zero utilization or nearly zero. …And it was essentially just glorified Salesforce.“
Ryan Stiskin
GTM Analyst, Sensor Tower
Salesforce is a very customizable platform, so I also took the time to ask these leaders and operators about the specific elements of the platform they chose to utilize. Success teams in Salesforce rely on a few common features that are already utilized by sales and support teams like Accounts, Contacts, Opportunities, Cases, and Activities. Features like list views, dashboards, and reporting allow for success leaders to get a view of their entire portfolio and track how customers are progressing through lifecycle stages. But there are several use cases that are unique to customer success that are worth calling out.
Product Usage Data
Access to product usage data is more or less required for customer success teams. Usage data lets CSMs understand product adoption as a key indicator of whether customers are realizing value with their investment. John from Apollo and Ryan from Sensor Tower say the following about surfacing product usage data in Salesforce:
“I’m allergic to having too many sources of truth for logic, health scoring, heuristics, and other KPIs. So we push data into Snowflake data models for source of truth reporting and analysis, and then bring those metrics into Salesforce.”
John Choi
Director of Customer Operations, Apollo.io
“We take a snapshot of each account and their amount of usage per product, daily active users, weekly active users per product, and as well as monthly active users per product. And then we have all that data being sent to …the account.”
Ryan Stiskin
GTM Analyst, Sensor Tower
There are a variety of methods to bring in product usage data to Salesforce, but if your team stores product usage data in a centralized data warehouse like Snowflake, BigQuery, or Databricks, then your Salesforce admin team can now bring in that data via Salesforce’s zero copy strategic partnerships to enrich customer records, trigger automations, and surface top product users and trends over time. Paul Wilson previously worked at Slack and Mural in GTM systems and operations, and he’s currently a tech industry advisor at Coastal, a technology consultancy:
“Standing up a pipeline to get product usage data in front of your CS team used to be the price of admission… Data 360 changes the math with zero copy, so you build where the data already lives instead of moving it, and Agentforce sits on top as the reasoning layer so CS leaders act on usage signals in real time instead of waiting on a report.”
Paul Wilson
Senior Industry Advisor TMT, Coastal
Playbooks and CTAs
One of the most important elements that came across in multiple interviews was having a streamlined way to track playbooks for CS teams. Using standard tasks and events usually isn’t sufficient for success teams, since leadership needs to have a more structured understanding of activities, like whether specific types of playbooks like QBRs are correlated with better customer outcomes like spikes in usage, renewals, or expansion deals.
Customers solve this in a variety of ways. Some success teams set up an object to track engagements, and others use third party project management tools from Salesforce’s app marketplace, AgentExchange. More recently, Salesforce included an out-of-the-box module to manage playbooks in the platform called Action Plans. John Choi describes Apollo’s approach to handling CS playbooks in Salesforce. Note that Apollo’s post-sales teams are called GTM Engineers, not CSMs:
“From an infrastructure perspective, we have an object called the customer engagement object so our teams can have a standard workflow that integrates with our AI call recording tool. We also use dashboards to track these engagements and AI agents to optimize the customer experience… We also have intervention program, which basically takes signals from Snowflake and reverse ETLs that data into Salesforce to create intervention records. And so all that is a similar framework to what you would expect out of a call to action in a CSP which would then be dispositioned by the GTME.“
John Choi
Director of Customer Operations, Apollo.io
Platform Administration
Enterprise-grade technology doesn’t just involve turning on a switch; technology requires management. This came up as a theme in several conversations. Vendors of Customer Success Platforms claim that these platforms are purpose built for post-sales teams and that CRMs struggle to handle these use cases. On the contrary, multiple CS leaders I talked to struggled with complex CSP implementations and integration issues. Some had to hire dedicated admins to customize the platform after running into multiple bandwidth issues to manage customizations.
The overall feedback I received is that for many success teams, Salesforce offers stronger governance options than traditional CSPs like sandboxes and deployment pipelines, enabling multiple teams to build and test new customizations. The platform itself is also fairly scalable, offering a more customizable UI, and more powerful data and automation options for CS teams to build with.
Connected Applications
Integrations are another good reason to look at scalable platforms like Salesforce. Salesforce has robust APIs for teams to connect to, and over 9000 connected applications in its app marketplace, AgentExchange. This results in teams being able to better utilize tools connected to Salesforce like Slack, call recorders, sequencers, enablement tools, and more, leading to a better user experience and faster time to value since they can avoid custom workarounds. The next few practical tips center around applications connected to Salesforce.
Slack & Salesforce
One common theme for CS teams in Salesforce is utilizing a collaboration tool like Slack, a Salesforce company. With account channels, CSMs can see Slack conversations on each account record in Salesforce, and they can see account details in a dedicated Slack channel to bring collaboration into a system of record. Workflows and alerts let success leaders get alerts and signals in Slack, and teams can easily keep their data up to date with Salesforce lists. This lets success teams work in lockstep with executives, sales teams, and support teams that might not log into a traditional CSP. Here’s what Paul says about Slack:
“With channels tied to accounts and Slack lists tracking the work, your CS team runs renewals and escalations where the conversation already happens instead of toggling into a separate tool to log what happened after the fact.“
Paul Wilson
Senior Industry Advisor TMT, Coastal
Analytics & Salesforce
Many of the problems that CSMs face in the modern era are around better understanding customer usage and adoption of individual features to determine the next best action. At the portfolio or company level, success executives need to make data-driven decisions about where to invest and how to better optimize the customer journey. This means that properly utilizing enterprise intelligence is crucial for success teams.
Salesforce’s native analytics solution is Tableau, a leader in business intelligence and data-driven decision-making. Tableau is a compelling option for success teams to consider since teams can embed Tableau natively inside of Salesforce and Slack. To better understand how Salesforce, Tableau, and Slack can work together to support customer success use cases, Tableau leaders recently hosted a webinar for success leaders: Proactive Customer Success in the Agentic Era.
Agentic AI
Every company is becoming an Agentic Enterprise, and that means success teams need to be on top of AI. After talking with several customer success leaders and operators, I learned that success teams benefit from AI in a variety of ways. They frequently utilize call recording tools to make it easier to track next steps and build an understanding of the overall customer relationship. They use AI tools like Slackbot, Claude, and ChatGPT, and AI workflows to make recommendations on next-best actions. Architecturally, Salesforce has an advantage here since third party AI tools have easy access to Salesforce data through APIs and Headless 360. Meanwhile, Salesforce-specific AI tools like Slackbot, Agentforce, and Tableau Agent add significant value for success teams since they’re embedded directly into the platform and user experience.
AI also makes it easier to customize and build on Salesforce. Success operations teams who might have been deterred from building on the Salesforce platform in the past now find it easier than ever. Since Salesforce is so customizable, AI development tools like Agentforce Vibes and third party solutions like Claude work extremely well with the Salesforce ecosystem. Success teams can get a bespoke experience that far exceeds the experience of traditional CSPs in hours, when it previously took working with a separate development team. Salesforce’s UI supports custom components via its Lightning framework as well as open source frameworks like React, and Salesforce has more powerful automation options like Flow, a no-code builder, as well as a pro-code option, Apex.
Scaled success teams have an even larger advantage when it comes to Agentic AI. For a scaled success motion to support smaller customers, success teams can build AI agents with Agentforce that can be embedded directly inside the product or help center to provide help when it’s needed. For a more proactive motion, a tech-touch success motion can utilize Agentforce to nurture champions, advocates, and product users over email and other channels, and complement a high-touch success team. Agentic AI is constantly evolving and shifting, and this space will undoubtedly continue to evolve over time.
Should My Team Use Salesforce as a Customer Success Platform?
Salesforce isn’t the right solution for everyone. Choose a dedicated CSP if your CS team is small, if you have a limited Salesforce footprint, or if your current CSP is working great. If these factors are true, then changing for the sake of changing is a bad idea.
But if you’re already paying for Salesforce licenses and your CS team is siloed from the rest of your revenue teams, the consolidation case is usually pretty straightforward. And if you have a CSP whose data story is mostly “we sync from Salesforce,” it’s worth asking what you’re actually paying for. The best CS platform is the one your whole company will actually use. That’s the question worth asking.
If I Want to Make the Move, How Do I Get Started?
If you want to learn more about Salesforce as a success platform, reach out to your Salesforce Account Executive and Solution Engineer to learn more. If you’re ready to get started on your journey with Salesforce for customer success, there are several options. Several technology consultancies have prepackaged offerings for companies migrating from a CSP onto the Salesforce platform, like Coastal.
“We’ve packaged together what most teams try to build from scratch: Salesforce and Tableau for CS orgs delivering a standalone platform, scoped to your environment after a data architecture review, live in 8 to 12 weeks.“
Paul Wilson
Senior Industry Advisor TMT, Coastal
If you choose to take on the project yourself, you can work with your internal Salesforce admin team to collaborate on customizing Salesforce for success and setting up a sandbox for pilot users. And if you want to get started faster, there are also preconfigured solutions on the platform offered by partners like Certinia’s Customer Success Cloud, an enterprise-grade solution available for success teams built natively on Salesforce.
Closing Thoughts
The success leader I met at Dreamforce didn’t make a decision based on individual features or price. They just followed the clues. Their data was already in Salesforce, and their sales and support teams were already treating it as their source of truth. Important decisions and collaboration happened in Slack, and account channels made Salesforce and Slack a natural fit for the success team. More and more teams are landing in the same place, not because Salesforce is perfect, but because driving real customer success has always been a team sport, and it’s better to be playing on the same field.
What are you running for Customer Success? And if you’ve made a move like this, what did it change? Connect with me on LinkedIn – I’d love to chat!