Quick Summary: to build a repeatable expansion engine, sales and customer success alignment through shared playbooks, co-ownership of NRR, and a clear RACI model is essential.
Your customer team can’t scale expansion in a vacuum. And neither can your sales team—because expansion depends on signals, relationships, and timing that span pre-sale and post-sale. Operate in silos, and each team loses context, misses buying signals, and creates friction that turns opportunities into churn instead of expansion.
Sales and customer success alignment is the key to hitting your targets and not stepping on each other’s toes—but how?
Sabina Pons and Jeramee Waldum are two revenue leaders who’ve made customer success and sales alignment work, first as peers at Mavenlink (now Kantata), and now at go-to-market growth agency HLX, where they help B2B tech companies scale revenue.
In a recent ChurnZero webinar, which you can watch below, Sabina and Jeramee shared six plays that they rely on to drive coordinated expansion across the customer lifecycle.
It’s a complex challenge that takes a well-engineered framework and careful coordination, but it’s well within your grasp if you’re thoughtful and deliberate. The biggest challenge: shifting incentives and day-to-day behaviors. Each team is built, measured, and rewarded differently, so getting people to trade short-term, individual wins for shared long-term outcomes takes work.
How to crush expansion through sales and customer success alignment.
Read on for six field-tested takeaways—from metrics to ownership to mindsets—that you can apply to unlock more expansion revenue through to sales and customer success alignment.
1: Build a shared expansion playbook for sales and customer success.
Most expansion opportunities follow predictable patterns. If you don’t define those patterns and assign clear roles, both teams tend to waste time or miss their window of opportunity.
A shared expansion playbook turns ad-hoc moves into repeatable, measurable motions so that sales and CS can act on the same signals at the same time. This makes coaching possible, helps your RevOps team determine what works best, and stops the leaky handoffs that cost time and revenue.
Identify your top 3–5 common expansion scenarios. The earliest signs include usage spikes, stakeholder changes, or new teams joining. Focus on scenarios that consistently lead to expansion or missed opportunities, then use them to define your playbook triggers.
Define who leads, who supports, and how the motion gets triggered. Consider matching roles to deal complexity; for example, CS may own a 5-seat license bump, but sales steps in for cross-sells. Triggers can include usage thresholds or CSM-submitted signals. The critical thing is for everyone to know exactly what starts the motion and what their role is.
Document and revisit regularly. Keep your plays in a shared document that you can review tem every quarter, or when product lines or team structures change. Include the enablement leads for both teams to help them design better coaching.
2: Align on shared metrics, including NRR
When sales and CS track different numbers, alignment breaks down almost immediately.
Shared metrics, particularly NRR, help turn team ambitions into a shared scorecard. Because NRR ties together renewals, expansions, and churn, treating it as a joint KPI influences both teams to coordinate their playbooks, handoffs, and forecasting. It also clarifies which plays actually move the business forward, so leaders can resource and reward the right behaviors.
Standardize definitions. Agree on what qualifies as an expansion, churn, or upsell. Write it down, share it with both teams, and use it to resolve disputes before they start.
Build a joint dashboard. Partner with your RevOps team to surface NRR, pipeline status, and expansion signals in one place. Make sure everyone can access and interpret the data.
Review together weekly. Use your dashboard in CS-sales syncs to track gaps, progress, and blockers. This means that you won’t have to wait until QBRs to correct course.
3: Create cross-functional pods to counteract siloing
Pairing your AEs and CSMs into pods helps you fix the messy problems that kill expansion: duplicate outreach, blind handoffs, and expansion signals falling through the cracks.
As stable, accountable units, pods of CSMs and AEs replace one-off interactions with ongoing relationships, shared context, and faster trust. They make expansion signals more actionable because everyone knows what to do. They also speed decisions and coaching, tighten forecasting, and materially improve outcomes with better win rates and predictability, because the same small team owns the customer end-to-end.
Pair AEs and CSMs in stable pods. Group pods by region, segment, or customer lifecycle stage. You can add SEs or BDRs depending on your motion.
Run regular pod syncs. Use a standing agenda: expansion signals, renewals, risks, and QBR prep. Capture each pod’s next steps and share them visibly.
Revisit pairings biannually. Use data and feedback to adjust pairings for performance or team changes. If a pod isn’t working, don’t let it linger—change the pairing instead.
4: Clarify who owns what with a RACI model
When ownership is unclear, expansion tends to fall apart. Use the RACI (Responsible, Accountable, Consulted, and Informed) model to set expectations and reduce the ambiguity that causes customer pain and revenue leaks. A clear RACI restores accountable roles, makes decisions easier, aligns compensation and reporting, and gives managers a concrete framework to coach and onboard their teams around. .
Create a RACI by motion and segment. Spell out roles for renewals, cross-sells, and upsells across different customer types. This eliminates assumptions and creates cleaner execution.
Match ownership to complexity. Your CS team might handle quick wins or transactional add-ons, for example, while larger or multi-product expansions need sales involvement from the start.
Review during planning cycles. Revisit your RACI at least twice a year, or sooner if there’s a major team shift. Crucially, familiarize every new hire with it during onboarding.
5: Track and reward CS-sourced leads
Your CSMs are positioned to uncover the earliest, highest-quality expansion signals, but aren’t always motivated to hand them over to sales.
Tracking those leads makes CS’s contribution visible in the pipeline and fixes attribution and forecasting blind spots. Rewarding them motivates CSMs to hunt signals and hand them off cleanly, driving faster conversions and better customer outcomes over time.
Log CS-sourced opportunities in your CSP. Make it easy for CSMs to flag buying signals in the tools they already use, then sync them to Salesforce or your CRM.
Attribute expansion in pipeline reviews. Review who sourced the opportunity, who’s leading it, and what progress has been made. This reinforces shared ownership.
Reward the handoff. Give credit where it’s due. Spiffs, shout-outs and leaderboard recognition are all effective at making CSMs feel their impact is visible.
6: Reframe the CS-sales relationship with the customer as the center.
Customers don’t experience your company as a collection of departments; they experience it as a single team. Use this perspective to reframe your CS-sales relationship into a single-team mindset.
For the customer, it removes mixed messages and makes every interaction feel coordinated and purposeful. Internally, it creates a smoother path to expansion and retention because everyone is judged by the same outcomes, rather than siloed wins.
Run joint QBRs. CSMs and AEs within a pod should align before the meeting, then present together. This avoids redundancy and sends a strong message to the customer.
Share goals and wins. Bring NRR, expansion pipeline, and customer success stories into team syncs. This helps teams rally around shared metrics.
Celebrate together. When an expansion closes, recognize everyone involved. Everyone in a pod should get the win, publicly.
Related resource: cross-functional alignment for customer leaders.
Alignment is more than a checklist; it’s a practice. This tactical guide focuses on building cross-functional processes, data sharing, and rules of engagement between CS and sales, product, marketing, finance, with a five-point framework and practical steps for making alignment operational rather than aspirational.
