Why This Handoff Is a Different Problem Than Booking a New Meeting
VA Horizon’s own guidance on the SDR-to-AE handoff for a newly booked meeting is built around a specific problem: getting the context of a cold introduction to travel intact so an account executive is not starting from zero on a first call. A customer success handoff to an expansion rep starts somewhere else entirely. There is no cold intro to solve, since the account already has a signed contract, a working relationship, and a track record inside the product.
That difference changes what the handoff document actually needs to contain. A pre-sale handoff passes along call notes, objections raised, and a read on urgency. A post-sale handoff has none of that to pass along, because the first conversation already happened months or years ago. What it needs instead is evidence of how the account has actually used the product since then.
What Usage and Adoption Data Should Travel With the Account
Feature depth is the first input worth including: which parts of the product an account actually uses regularly, not just which ones it is entitled to. An account exercising a small slice of what it is paying for is a different expansion conversation than one that has adopted broadly and is now pushing against a seat or usage cap.
Login frequency and its trend line matter more than a single snapshot. An account logging in consistently every week tells a different story than one that logged in heavily after onboarding and has quietly tapered off since, even if both show the same total usage over the past year. A handoff that only reports a cumulative number misses exactly the trend that should shape how the call opens.
What Support-Ticket History Adds That a Sales Note Cannot
A list of open tickets tells an expansion rep what is currently unresolved and gives them a reason to check in before pitching anything at all. Calling an account about an upsell while a support ticket sits open and unanswered is a fast way to make the account feel like a number instead of a customer.
Recently resolved tickets carry a second kind of signal worth including even after they close. A ticket resolved two weeks ago about a specific limitation is still live in that customer’s memory, and referencing it directly, acknowledging the friction existed and confirming it is actually fixed, does more for trust going into an expansion ask than any generic opening line could.
The Revenue Case for Getting This Handoff Right
More than 60% of G2’s own gross bookings come from existing customers, a figure G2’s own head of sales disclosed in a podcast excerpt cited by Gainsight. That is not a universal law every SaaS company should expect to match, but it is real, named evidence that a mature company’s growth increasingly runs through the accounts it already has, not only the ones still working through a sales cycle.
The dollar stakes back that up from a different angle. SaaS Capital’s 2026 survey of more than 1,000 private SaaS companies found that companies with net revenue retention of 120% or higher command a median annual contract value of $61,802, more than double the $26,269 median for companies below that line. A handoff that loses context on the way to an expansion call is not a small process gap, it is friction sitting directly on top of the accounts already proven to be worth the most.
Who Actually Makes the Call, and What Travels Either Way
Whether customer success keeps the relationship and makes the expansion call itself, or a dedicated expansion rep takes it over, is a real organizational choice with reasonable arguments on both sides. What does not change based on that choice is the artifact itself: the usage data, the ticket history, and a plain statement of why now is a reasonable moment to ask.
A company that skips building that artifact because it has not yet decided who owns the call is solving the wrong problem first. The handoff content should exist and travel with the account regardless of which team ends up making the actual call.
What Travels With the Account From Here
None of this requires a heavyweight system. A short, standard set of fields, current feature adoption, login trend direction, open and recently resolved tickets, and one line on why this account looks ready now, is enough to keep an expansion call from opening blind. The version that fails is the one that exists only in a CS rep’s head and disappears the moment that person changes roles.
Human + AI SDRs can run the actual outreach once that handoff exists, texting an account based on the real usage and support signal that traveled with it, rather than a blind, generic renewal-season message sent to every account on the same day.
What this means for you
- More than 60% of G2’s own gross bookings come from existing customers, per G2’s own head of sales, real evidence a mature SaaS company can lean heavily on its installed base rather than net-new logos.
- A post-sale handoff needs a different artifact than a pre-sale one: usage and adoption data, and support-ticket history, standing in for the call notes an SDR-to-AE handoff would pass along instead.
- No sourced statistic exists on what data specifically travels in a formal CS-to-sales handoff or how many SaaS companies run one. Treat any specific adoption-rate figure cited elsewhere with real skepticism.
Sources
The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.
- Gainsight, Why Your Customers Are Already Shopping Around (And How to Catch It Early)
- SaaS Capital, What Is the Average Deal Size for Private SaaS Companies