Gather Simulated Research
Pre-Research Intelligence
thought_leadership

"What does great customer success actually look like at year two of an enterprise SaaS contract?"

Across 4 simulated interviews, year two is consistently framed as the moment value must be proven, with a shared frustration that vendor-centric usage metrics fail to connect to the business outcomes each role actually cares about.

Persona Types
4
Projected N
4
Questions / Interview
5
Avg Sentiment
4/10

⚠ Simulated pre-research: AI-generated directional signal. Not a substitute for real primary research. Validate findings with real respondents at Gather →

Executive Summary

What this research tells you

Summary

These 4 simulated Exploratory Research interviews (a VP Customer Success, CMO, CFO, and VP of Sales) converge on a core directional signal: at year two of an enterprise SaaS contract, the honeymoon is over and the burden shifts to demonstrating outcomes, not activity. All four distinguish between vendor dashboards/usage stats and the outcomes they personally need to defend — board metrics and NPS (CMO), cost per unit and P&L impact (CFO), renewal and expansion revenue (VP Sales), and account health tied to champion stability (VP CS). Multiple respondents describe a reactive CS posture and a 'black box' or 'autopilot' dynamic between early onboarding and renewal. Champion stability and proactive, outcome-owning CS emerge as repeated themes. Findings are directional only; this is a simulated, non-representative set and no business effects are measured.

Overall Sentiment
4/10
NegativePositive
Confidence
Directional
Interval not established

Predictive accuracy and a statistical interval have not been established for this simulation.

Key Findings

What the research surfaced

Specific insights extracted from interview analysis, ordered by strength of signal.

1

Vendor usage/adoption metrics are seen as misaligned with the outcomes each buyer must defend.

Implication

CS teams may need to map value to role-specific business outcomes rather than product usage — a hypothesis to validate.

moderate
2

Year two is repeatedly framed as the decisive, higher-stakes 'post-honeymoon' phase for renewal.

Implication

Value proof and engagement timing in year two warrant focused attention; test whether earlier intervention changes outcomes.

moderate
3

A reactive or disengaged CS posture between onboarding and renewal is a shared concern.

Implication

Proactive, continuous engagement is a candidate differentiator to test.

moderate
4

Champion stability between year one and year two is a specific, under-addressed risk for the CS leader.

Implication

Tracking champion health may complement usage-based health scores; validate across more roles.

weak
Strategic Signals

Opportunity & Risk

Key Opportunity

Hypothesis to validate: CS that proactively ties its work to each stakeholder's own outcome metrics (e.g., P&L, NPS, expansion) rather than usage dashboards could strengthen renewal confidence. This is an untested hypothesis, not a measured effect.

Primary Risk

Evidence is limited to 4 simulated, role-diverse interviews; it is not a representative or human market sample, and there is no data on how common these views are or their link to actual renewal outcomes. Definitions of success conflict across roles.

Points of Tension — Where Personas Disagree
↔

What counts as the key outcome metric differs by role, with no shared definition of 'good' across the 4.

VP CS emphasizes champion health and green/stable health scores; CMO cites NPS and board metrics; CFO cites cost per unit and P&L; VP Sales cites renewal, expansion, and referrals. Evidence is directional only.

Consensus Themes

What respondents kept coming back to

Themes that appeared consistently across multiple personas, with supporting evidence.

1

Outcomes over activity

All four respondents distinguish vendor dashboards/usage metrics from the business outcomes they personally need demonstrated.

"That's their metrics, not mine. I need someone who understands my P&L well enough to speak my language."
negative
2

Year two as proof point

Respondents frame year two as when value must be proven and the renewal becomes real.

"Year two is really where you find out if you actually delivered on what you sold."
mixed
3

Desire for proactive CS

Multiple respondents want CS to drive insight and engagement rather than react near renewal.

"good looks like a CS team that's proactively surfacing insights I didn't know to ask for"
mixed
Decision Framework

What drives the decision

Criteria respondents described when they evaluate, choose, and commit.

1

Demonstrable outcome linkage (P&L/NPS/cost-per-unit) vs. usage reporting

2

Proactive engagement cadence throughout the year, not just near renewal

3

Peer/industry benchmarking relevant to the customer's context

Competitive Intelligence

The competitive landscape

Competitors and alternatives mentioned across interviews, and what buyers said about them.

Fear of competitive displacement when accounts are treated as 'on autopilot' or go quiet.

Messaging Implications

What to say — and how

Copy directions suggested by the simulated audience responses.

1

Frame CS value in the customer's own business metrics, not product usage.

2

Position CS as proactive and outcome-owning across the full contract year.

Verbatim Language Patterns — Use in Copy
"year two is where the rubber meets the road""quiet can mean satisfied, or it can mean they've stopped caring""champion who signed the deal might have moved on""their champion is selling it internally without us in the room""conversations in year two that should have happened in month three""they bought for one use case and never expanded""we never really understood their internal politics""that middle stretch where your original champion gets promoted, leaves, or just gets deprioritized""moving the needle on renewal confidence or just generating activity""the honeymoon is over""reactive posture from our vendor""I'm the one driving most of the agenda, and that's backwards"
Persona Analysis

How each segment responded

Side-by-side comparison of sentiment, intent, buying stage, and decision role across all personas.

Interview Transcripts

Full interviews · 4 respondents

Complete question-by-question responses with per-persona analysis. Click any respondent to expand.

K
Keisha N.
VP Customer Success · Mid-Market SaaS · Denver, CO
mixed▼
35 yrsB2B Tech$160kchurn-paranoid · QBR-driven · champion builder · health-score focused

Keisha frames year two as the moment of truth for customer success — when honeymoon energy fades and renewal math becomes unforgiving. Her core anxieties cluster around two problems: health score inadequacy (quiet accounts may be satisfied or already gone, and green scores can mask churn risk she calls a hypothetical she fears) and champion instability (original buyers move on, leaving CS rebuilding trust with people who had no say in the purchase). She estimates roughly 40% of accounts still require active value justification at renewal — conversations she believes should have happened in month three. The underlying structural vulnerability she identifies is shallow adoption: customers who bought for one use case and never expanded are fragile whenever a champion leaves or a budget cycle hits. Her unprompted concern is the mid-contract stretch between onboarding and renewal, which she says the industry underexamines, and she measures account health not by usage dashboards but by whether a champion can tell an internal value story without CS present.

1

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Honestly, year two is where I feel like things get real. Year one you're still in honeymoon mode, everyone's excited about the implementation, there's energy around adoption. But by year two the rubber meets the road and you're staring down renewal math that is way less forgiving. What I'm wrestling with right now is how to tell the difference between an account that's genuinely healthy versus one that just looks quiet. Quiet can mean satisfied, or it can mean they've stopped caring and they're already shopping alternatives. My health scores don't always catch that distinction fast enough. The other thing keeping me up is champion stability. By year two people have moved, orgs have shifted, and sometimes the person who bought in is gone and I'm starting from scratch building internal trust with someone who had no say in the original decision.

2

What's the most important thing you need to understand or solve here?

Year two is really where you find out if you actually delivered on what you sold. The honeymoon is over, the champion who signed the deal might have moved on, and now you need to prove the product is embedded enough in their workflow that walking away feels painful. For me it comes down to: do I have a healthy champion, do they have a story to tell internally about what the platform has done for them, and are we tracking metrics that actually map to outcomes they care about, not just our own product usage numbers.

3

What does 'good' look like to you — and how far are you from that today?

So "good" at year two for me is when the customer has fully moved past the honeymoon phase and they're actually running their business on the product, not just using it. Their champion is selling it internally without us in the room, their health score is green and stable, and when renewal comes up it's basically a formality. Where are we from that today? Honestly, we get there with maybe 60% of our accounts at that point in the contract. The other 40% we're still fighting to prove value, which means we're having conversations in year two that should have happened in month three. The gap is usually around adoption depth — they bought for one use case and never expanded, so there's this vulnerability sitting there that makes me nervous every time a champion leaves or a budget cycle hits.

4

What would change your perspective on this entirely?

If I found out that a customer who scored green in our health dashboard actually churned because of something we completely missed, that would shake me. Like if the relationship was strong, they were hitting their usage benchmarks, and we still lost them to a competitor because we never really understood their internal politics or a champion leaving. That would force me to rethink whether the signals we're tracking at year two are actually the right ones.

5

What question are you not being asked that you wish someone would ask?

Honestly, the thing nobody really digs into is what happens to the champion relationship between year one and year two. Everyone asks about onboarding and they ask about renewal, but that middle stretch where your original champion gets promoted, leaves, or just gets deprioritized internally is where I lose sleep. If I can't answer "who inside this account is actively selling the value of our product to their peers right now," that account is at risk regardless of what the health score says.

"If I can't answer 'who inside this account is actively selling the value of our product to their peers right now,' that account is at risk regardless of what the health score says."
Language Patterns for Copy
"year two is where the rubber meets the road""quiet can mean satisfied, or it can mean they've stopped caring""champion who signed the deal might have moved on""their champion is selling it internally without us in the room""conversations in year two that should have happened in month three""they bought for one use case and never expanded""we never really understood their internal politics""that middle stretch where your original champion gets promoted, leaves, or just gets deprioritized"
P
Priya S.
CMO · Enterprise Retail · New York, NY
mixed▼
41 yrsEnterprise$240kbrand-conscious · board pressure · agency veteran · NPS-focused

Priya expresses a mixed but predominantly critical view of her current vendor CS experience at year two of major contracts. Her core frustration is that CS activity — QBR decks, usage stats, stakeholder cadences — is not being connected to the board-level outcome metrics she staked her credibility on. She describes the relationship posture as backwards, with herself driving the agenda rather than the vendor. She acknowledges incremental improvement since year one but signals that renewal confidence depends on whether the CS team can demonstrate real outcome movement, not relationship presence. Her unprompted question — how to know if a CSM is genuinely adding value versus filling calendar time — surfaces as the sharpest unmet need in the relationship.

1

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Honestly, the thing I keep coming back to is whether our CS team is actually moving the needle on renewal confidence or just generating activity. We hit year two on a couple of major contracts and suddenly the conversations shift — the vendor wants to talk expansion, the board wants proof the spend is justified, and I'm sitting in the middle trying to figure if the value we were sold on is actually showing up somewhere I can point to. NPS is one lens but it doesn't tell the whole story to a CFO.

2

What's the most important thing you need to understand or solve here?

At year two, the biggest thing I need to know is whether the platform is actually moving the needle on the metrics I told my board it would move. Not usage stats, not logins — real outcomes tied to our brand and NPS goals. If the CS team can't speak to that clearly, the renewal conversation gets very uncomfortable very fast.

3

What does 'good' look like to you — and how far are you from that today?

Honestly, good looks like a CS team that's proactively surfacing insights I didn't know to ask for — not waiting for my QBR to tell me what I already see in my own dashboard. I want them in the room before the board starts asking questions, not after. We're closer than we were at year one, but there's still too much of a reactive posture from our vendor. I'm the one driving most of the agenda, and that's backwards at this stage of the relationship.

4

What would change your perspective on this entirely?

If the vendor actually owned outcomes instead of just activities, that would shift everything for me. Right now most of what I see at year two is reporting on usage metrics and QBR decks that show me how busy the CSM has been, but nobody is tying that back to my NPS numbers or pipeline influence. If a CS team came to me and said "here's how our work moved your customer loyalty scores," I'd be a completely different kind of champion for them internally.

5

What question are you not being asked that you wish someone would ask?

Honestly, the one I never get asked is "how do you actually know your CSM is adding value versus just showing up?" Like, everyone wants to talk about QBR cadence and stakeholder mapping, but nobody asks me how I'm measuring whether the person assigned to my account is genuinely moving the needle on outcomes or just filling calendar time. At year two, that distinction really matters because the honeymoon is over and I'm making renewal decisions based on real signal, not relationship warmth.

"If a CS team came to me and said 'here's how our work moved your customer loyalty scores,' I'd be a completely different kind of champion for them internally."
Language Patterns for Copy
"moving the needle on renewal confidence or just generating activity""the honeymoon is over""reactive posture from our vendor""I'm the one driving most of the agenda, and that's backwards""reporting on usage metrics and QBR decks that show me how busy the CSM has been""real signal, not relationship warmth""owned outcomes instead of just activities""proactively surfacing insights I didn't know to ask for"
J
James L.
CFO · Mid-Market Co · Detroit, MI
negative▼
53 yrsManufacturing$290kROI-first · skeptical of new tools · headcount-focused · benchmark-obsessed

James is a CFO entering SaaS renewal negotiations with significant skepticism. His dominant frustration is that vendors present platform-centric metrics — adoption rates, feature releases, QBR decks — while he needs a direct, defensible line from tool usage to operational outcomes like cost per unit or throughput. He is not satisfied with year-one performance evidence and is explicitly carrying the burden of investigation himself. He would shift from churn risk to expansion consideration only if a vendor produced a clean, comparable before-and-after on metrics agreed at contract signing, benchmarked against manufacturing peers in a relevant geography. His tone is controlled but consistently critical of vendor CS practices.

1

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Honestly, we're heading into renewal discussions on a couple of our bigger SaaS contracts and I'm trying to figure out whether we actually got what we paid for in year one before I commit to year two. The vendor's CS team shows up with dashboards and usage reports, but I'm not seeing a clear line back to what it's doing for throughput or cost per unit on the manufacturing side. I need someone to connect those dots for me, not just tell me we're hitting platform adoption targets.

2

What's the most important thing you need to understand or solve here?

By year two, I want to know if this thing is actually moving the needle on the metrics that matter to my business, not just the vendor's dashboard. Are my people actually using it, and can someone show me a direct line to a cost reduction or productivity gain I can defend in a board presentation? The frustration is that most CSMs come in talking about adoption rates and feature releases. That's their metrics, not mine. I need someone who understands my P&L well enough to speak my language.

3

What does 'good' look like to you — and how far are you from that today?

By year two, "good" means the vendor can tell me whether I'm getting my money's worth without me having to ask. I want to see my actual usage data, what it's costing me per unit of output, and how that compares to what similar manufacturers are running. Right now we're probably not there — I'm still the one pulling the thread to figure out if this thing is performing.

4

What would change your perspective on this entirely?

Honestly, if a vendor could show me a clean before-and-after on headcount or cost per unit tied directly to their platform at year two, that would stop me cold. Not a case study from a different industry with different margins, something comparable to manufacturing in the Midwest. If they can benchmark me against peers and show I'm measurably behind where I should be without them, that changes the conversation from "why are we still paying for this" to "why aren't we using more of it."

5

What question are you not being asked that you wish someone would ask?

Honestly, the thing nobody asks me is whether the vendor is actually tracking what they promised to deliver against what we're using. By year two I want someone to show me a clear before-and-after on the operational metrics we agreed to at signing, not just usage dashboards and QBR slide decks. If you can't tell me whether my purchase request cycle times or approval SLAs improved because of your tool, I don't know what we're paying for.

"The frustration is that most CSMs come in talking about adoption rates and feature releases. That's their metrics, not mine. I need someone who understands my P&L well enough to speak my language."
Language Patterns for Copy
"whether we actually got what we paid for in year one""connect those dots for me, not just tell me we're hitting platform adoption targets""a direct line to a cost reduction or productivity gain I can defend in a board presentation""I'm still the one pulling the thread to figure out if this thing is performing""a clean before-and-after on headcount or cost per unit tied directly to their platform""something comparable to manufacturing in the Midwest""why are we still paying for this""whether the vendor is actually tracking what they promised to deliver""not just usage dashboards and QBR slide decks"
T
Tanya M.
VP of Sales · Enterprise SaaS · Chicago, IL
negative▼
38 yrsB2B Tech$220kquota-obsessed · comp-plan sensitive · loves social proof · short attention span

Tanya expresses sustained frustration with CS-Sales misalignment, particularly around year-two renewals. Her core concern is that CS engagement drops off between month six and month eighteen, leaving accounts on autopilot precisely when competitor vulnerability is highest. She rates current performance a six out of ten and frames CS as a cost center until proven otherwise with hard data on correlation between CS activity and renewal or expansion outcomes. The 90-day pre-renewal scramble is her primary recurring complaint, and she explicitly ties CS underperformance to her own number and her team's comp.

1

Tell me what's top of mind for you on this topic right now — what are you wrestling with?

Honestly, year two is where I feel like we either win the renewal or we've already lost it and just don't know it yet. What I'm wrestling with is figuring out how early my CS counterparts are actually looped into the account versus just showing up 90 days before renewal to scramble. If a customer can't tell me what value they've gotten, that's a CS failure that lands on my number.

2

What's the most important thing you need to understand or solve here?

Honestly, the thing I care most about is whether my customers are still getting value at year two, because that's when the renewal conversation gets real and my team's comp is tied to it. If CS isn't doing their job and an account churns, that lands on my number too. So what I need to know is what "good" actually looks like at that stage — not just "they renewed" but are they actually expanding, are they advocates, are they sending me referrals?

3

What does 'good' look like to you — and how far are you from that today?

Honestly, good at year two looks like the customer is so embedded that renewal is a non-event. Like the CSM isn't scrambling 90 days out, they're already talking about expansion because the account has hit whatever that one metric was that we promised them in the sales cycle. Where are we today? Probably a six out of ten. The first two years we're usually great at being present and visible, but there's this drop-off where CS starts treating big accounts like they're on autopilot, and that's exactly when a competitor walks in the door.

4

What would change your perspective on this entirely?

Honestly, if I saw hard data showing that CS activity at year two directly correlated with renewal rates and expansion revenue, that would shift how I think about resourcing it. Right now it feels like a cost center to me, not a revenue driver. Show me the comp plan alignment between CS and sales on upsells and I'll start paying attention to what "great" looks like.

5

What question are you not being asked that you wish someone would ask?

Honestly, the question nobody asks me is: what does the customer success team actually do when my renewal is coming up? Like, are they working the account all year or do they just show up 90 days out with a deck? Because from where I sit in sales, I hand off a deal and then it's kind of a black box. If CS isn't staying close to my customers between month six and month eighteen, I'm the one who hears about it when the renewal falls apart.

"I hand off a deal and then it's kind of a black box. If CS isn't staying close to my customers between month six and month eighteen, I'm the one who hears about it when the renewal falls apart."
Language Patterns for Copy
"year two is where I feel like we either win the renewal or we've already lost it""a CS failure that lands on my number""renewal is a non-event""CS starts treating big accounts like they're on autopilot""that's exactly when a competitor walks in the door""it feels like a cost center to me, not a revenue driver""show up 90 days out with a deck""kind of a black box""probably a six out of ten"
Research Agenda

What to validate with real research

Specific hypotheses this simulated pre-research surfaced that should be tested with real respondents before acting on.

1

Which outcome metrics most influence year-two renewal decisions for each buyer role?

Why it matters

Definitions of 'good' conflict across the 4 roles; a shared metric framework is unproven.

Suggested method
Structured interviews across roles plus review of actual renewal decision criteria.
2

Does champion turnover between year one and year two predict churn independent of usage-based health scores?

Why it matters

VP CS flags this as an under-tracked risk; it is currently anecdotal.

Suggested method
Longitudinal account analysis correlating champion changes with retention.
3

Does proactive, continuous CS engagement change renewal/expansion outcomes versus late-stage engagement?

Why it matters

The 'autopilot/black box' concern is raised but effects are unmeasured.

Suggested method
Comparative cohort study or controlled pilot.

Ready to validate these with real respondents?

Gather runs AI-moderated interviews with real people in 48 hours.

Run real research →
Methodology

How to interpret this report

What this is

This report contains simulated audience responses. Use the findings to compare choices, sharpen hypotheses and plan what to test next.

Statistical projection

Quantitative figures describe the simulation. They are not measured market prevalence or observed purchase behavior.

Recommended next step

Use this to build your screener, align on hypotheses, and brief stakeholders. Then run real AI-moderated interviews with Gather to validate findings against actual respondents.

Primary Research

Take these findings
from simulated to real.

Your simulated study identified the key signals. Now validate them with 4+ real respondents across 4 audience types, recruited, interviewed, and analyzed by Gather in 48 to 72 hours.

✦Validated interview guide built from your simulated data
✦Real respondents matching your exact persona specs
✦AI-moderated interviews with qual depth + quant confidence
✦Board-ready report in 48–72 hours
Book a call with Gather →
Your Study
"What does great customer success actually look like at year two of an enterprise SaaS contract?"
4
Respondents
4
Persona Types
48h
Turnaround
Gather Simulated Research · synthetic.gatherhq.com · November 13, 2026
Run your own study →