In the high-stakes world of SaaS, where the pressure to sustain growth amidst shifting market dynamics is constant, companies are increasingly desperate to squeeze more value from their existing customer base. This has led to a burgeoning organizational trend: folding Customer Success (CS) and other post-sales functions directly into the Sales department.
While the theoretical appeal—creating a unified "revenue engine" that carries the customer relationship from initial lead to long-term renewal—is strong, the practical reality is often far more fraught. As industry experts and the SaaStr community have observed, this structural shift often sacrifices long-term customer health for short-term revenue spikes, creating a clash between the "hunter" mentality required for sales and the "farmer" mentality required for retention.
The Chronology of a Structural Trend
The evolution of the Chief Revenue Officer (CRO) role has been the primary driver behind this shift. In the early days of SaaS, the Sales VP was a singular, laser-focused entity: their only goal was the next signature. Customer Success was viewed as a distinct discipline, often reporting to a VP of Customer Success or even the CEO, with a mandate to prevent churn and ensure product adoption.
However, as the SaaS market matured, the industry began to favor the "all-in-one" revenue leader. The logic was that if a single executive owned both the initial acquisition and the renewal, there would be fewer hand-off gaps and a more seamless customer experience.
The Shift Toward Consolidation
- 2010–2015: The "Siloed Era." Sales and CS operated in distinct silos. The hand-off was formalized, and metrics were separated by bookings versus net retention.
- 2016–2020: The "Growth-at-All-Costs Era." As capital became cheap, companies began to prioritize expansion revenue. Sales leaders started encroaching on CS, arguing that they were better positioned to identify upsell opportunities.
- 2021–Present: The "Efficiency Era." Facing higher churn rates and slower growth, many firms are centralizing all revenue-generating activities under a single CRO to drive efficiency. Yet, this has led to a degradation in support quality as the "sales-first" mindset dominates the culture.
The Theoretical Appeal vs. The Practical Reality
The theory behind integrating post-sales into the sales organization is elegant. Proponents argue that by keeping the original salesperson involved, the customer enjoys continuity. The salesperson, having spent weeks or months building a rapport, is theoretically best positioned to ensure that the product is actually used, thereby reducing churn.
However, in practice, this often fails the customer. The fundamental disconnect lies in the psychological makeup of a successful sales professional.
The "Closer" Dilemma
At the heart of the issue is a simple truth: great VPs of Sales are "closers." Their adrenaline is fueled by the thrill of the deal—the hunt, the negotiation, and the win. Once the contract is signed, the "closer" is naturally predisposed to look for the next target.
When you task a sales-driven leader with managing support tickets, onboarding friction, or complex implementation issues, you are asking them to do something that fundamentally contradicts their core skill set. This creates a "distraction effect." The VP of Sales begins to view post-sales duties as an obstacle to hitting their ARR (Annual Recurring Revenue) quota. Consequently, the customer, who was promised a partnership, is often relegated to an afterthought unless an easy upsell opportunity presents itself.
Supporting Data and Organizational Friction
The industry has seen a rise in companies adopting the "Revenue Organization" model, but the success rate of this transition is highly variable. Data suggests that when post-sales functions are subsumed by Sales, three critical areas often suffer:
- Service Quality: Support tickets are often treated as "non-revenue" tasks, leading to slower resolution times and lower CSAT (Customer Satisfaction) scores.
- Cultural Drift: The department culture shifts from "customer advocacy" to "quota attainment," which alienates the very staff members tasked with long-term account health.
- The "Vanity" CRO Problem: Many startups appoint a CRO prematurely. A "true" CRO is an executive capable of managing two distinct disciplines: the high-velocity, short-term sales engine and the relationship-heavy, long-term success engine. Most startups fail here because they promote a top salesperson to CRO without ensuring that person has the capacity or the desire to nurture a CS team.
The result is a "vanity title" where the CRO remains a glorified Sales VP, and the CS team is left to wither in a department that does not understand its function.
Official Perspectives: When Does Integration Actually Work?
There is a specific scenario where this integration works: when the company employs a high-caliber CRO who has the operational discipline to manage two distinct VPs—a VP of Sales (the hunter) and a VP of Customer Success (the farmer).
In this model, the CRO acts as a mediator, ensuring that the two teams remain aligned on the customer lifecycle without the aggressive, short-term tactics of the sales team contaminating the support experience.
However, the consensus among veteran operators is clear: do not force this integration in the early stages. In the early days, you need a dedicated, passionate lead for Customer Success who is solely focused on proving product-market fit and ensuring the first customers are "raving fans." If you force a salesperson to manage those early, fragile relationships, you risk losing the very feedback loops required to iterate on your product.
Implications: The Risks of "Sales-ifying" CS
For companies considering this organizational shift, the implications are profound.
The Erosion of Trust
When a customer realizes that their "Success Manager" is actually an extension of the Sales team, the dynamic of the relationship changes. The customer stops viewing the CS manager as a neutral partner who wants them to succeed and starts viewing them as a salesperson looking to upsell them on features they may not need. This erodes trust, which is the cornerstone of long-term SaaS renewals.
The "Growth Trap"
Companies are often lured into this move by the hope that the sales team will generate more expansion revenue. While this may happen in the short term, the long-term risk is an increase in churn. If the product is not meeting the customer’s needs, an aggressive sales-led approach to "fixing" the account usually fails. You cannot sell your way out of a product-market fit problem.
The Recruitment Challenge
Great Customer Success talent rarely wants to report to a Sales leader. If your CS team feels that their primary function is to serve as a lead-generation arm for the sales team, you will likely see high turnover in your most critical roles.
Conclusion: The Path Forward
Is it a good idea to have post-sales report into Sales? For most SaaS startups and mid-market companies, the answer is a resounding "no."
If you are a high-growth company with the resources to hire a seasoned executive who can balance both sides of the revenue cycle, perhaps you can make it work. But for the vast majority of founders, the risk is too high. The "closer" mentality is a vital asset for acquiring new logos, but it is an liability when applied to the delicate, long-term work of retention and success.
Before consolidating your departments, ask yourself: Are we doing this to make the customer experience better, or are we doing this because we are struggling to meet our growth targets? If the answer is the latter, you aren’t solving an organizational problem—you are simply masking a growth problem. For now, keep your hunters and your farmers separate; the long-term health of your ARR depends on it.
