An account went from $1.0M ARR to a $1.4M expansion contract mid-year, but two smaller logos in your book churned for $200K combined and one downgraded $100K. When your CRO asks you to explain your book's NRR versus GRR in a board deck, which framing is correct?
- A. GRR captures the $400K expansion, while NRR strips it out to show only downgrades and churn
- B. GRR excludes the $400K expansion and reflects only the $300K of contraction and churn, while NRR includes the expansion and can exceed 100% ✓
- C. Both NRR and GRR include expansion, but GRR is calculated net of new-logo bookings
- D. NRR caps at 100% by definition, so the $400K expansion is reported separately as new ARR
Correct answer: B. GRR only measures retained revenue net of churn and downgrades (never exceeding 100%), while NRR adds expansion on top of the existing base and can exceed 100%.
You are designing a customer health score and must choose weighting. One team wants to weight NPS heavily because it correlates with renewals in your historical data. As a senior CSM, what is the strongest objection to over-weighting NPS in an at-risk model?
- A. NPS is a lagging, self-reported sentiment indicator that reflects past feeling rather than predicting near-term churn behavior ✓
- B. NPS is proprietary and cannot legally be used inside health scoring models
- C. NPS should be excluded entirely because sentiment never correlates with retention
- D. NPS changes too frequently to be useful, so it adds noise to any weighted score
Correct answer: A. NPS is a lagging, self-reported signal that captures sentiment after the fact, so a predictive at-risk model should lean on leading behavioral signals like adoption and usage trends.
A red account 60 days from renewal has low product adoption, a disengaged champion, and an unresolved P2 support ticket. With limited time, what is the correct FIRST intervention to sequence?
- A. Send a renewal quote early to anchor the commercial conversation before adoption improves
- B. Launch a broad end-user training campaign to lift adoption metrics quickly
- C. Diagnose the root cause by securing an executive-level conversation to re-establish the business outcome and confirm whether value is still wanted ✓
- D. Escalate the P2 ticket to engineering as the top priority since technical issues drive churn
Correct answer: C. With scarce time you must first diagnose root cause and re-anchor on the desired business outcome with a decision-maker, because training or ticket fixes are wasted if the account no longer values the solution.
A customer demands a one-off customization that would require permanent bespoke engineering support. Sales wants the deal closed and the customer threatens to churn. What is the most defensible senior CSM response?
- A. Commit to the customization to save the ARR, since retaining the logo outweighs the engineering cost
- B. Refuse outright and cite company policy, protecting the roadmap from scope creep
- C. Quantify the true cost-to-serve of the bespoke request against the account's LTV and explore whether a configurable or roadmap-aligned solution meets the underlying need ✓
- D. Escalate to Product to add it to the roadmap immediately so the customer sees progress
Correct answer: C. The commercially sound move is to weigh cost-to-serve against LTV and separate the customer's underlying need from the specific ask, since unscalable one-offs erode margin even when they save ARR.
During a QBR with a $2M ARR enterprise account, the customer's new CFO challenges the ROI you claim. Your usage dashboards show strong adoption. What is the most effective way to defend value to this economic buyer?
- A. Present DAU/MAU and feature-adoption depth as proof the product is heavily used
- B. Translate adoption into the customer's own quantified business outcomes, such as hours saved or cost avoided, tied to the goals set at onboarding ✓
- C. Show your NPS and CSAT scores to prove the users are satisfied
- D. Offer a discount on renewal to demonstrate goodwill and partnership
Correct answer: B. A CFO buys outcomes, not usage, so value must be expressed as quantified business impact tied to the originally agreed success metrics rather than adoption vanity metrics.
A key account has gone completely dark: no email replies for three weeks and the renewal is in 45 days. You have one internal contact who still opens your emails. What is the best re-engagement move?
- A. Send a final breakup email stating you will assume they are churning unless they respond
- B. Escalate to your executive sponsor to reach out to their executive sponsor in parallel while multi-threading to other stakeholders you have relationships with ✓
- C. Wait until 15 days before renewal to create urgency, then send the renewal paperwork
- D. Pause outreach entirely to avoid appearing pushy and preserve goodwill
Correct answer: B. When a single thread goes dark near renewal, the correct play is executive-to-executive escalation combined with multi-threading to other stakeholders, since relying on one unresponsive contact is the core risk.
You are building a renewal forecast three quarters out. You categorize a $500K account as 'commit' because usage is strong and the champion is engaged, but you just learned the parent company is undergoing an acquisition. How should this account be staged?
- A. Keep it as commit since the product signals are all healthy
- B. Move it to risk, because an M&A event is a material uncontrollable factor that can override healthy usage signals ✓
- C. Move it to upside, since acquisitions often bring budget expansion
- D. Remove it from the forecast entirely until the acquisition closes
Correct answer: B. M&A introduces vendor consolidation and budget-freeze risk that is largely uncontrollable and can override otherwise healthy signals, so the account belongs in the risk category, not commit.
Three accounts in your book hit crisis in the same week: a $1.5M account after a major outage, a $300K account with a churn threat over price, and a $200K account whose champion just left. With finite hours, how should you triage?
- A. Split time equally across all three so none feels neglected
- B. Prioritize by weighing ARR-at-risk, probability of saving each, and time-sensitivity, generally leading with the $1.5M outage recovery while delegating or sequencing the others ✓
- C. Start with the champion-loss account because relationship gaps are hardest to fix
- D. Handle the $300K price threat first because commercial negotiations have the hardest deadlines
Correct answer: B. Sound triage weights dollar-at-risk against save-probability and urgency, which typically elevates the $1.5M outage account while sequencing or delegating the smaller ones rather than spreading effort evenly.
After a severe outage, a $1.5M enterprise customer's executive is furious and hints at leaving at renewal. In the first executive call, what should you prioritize?
- A. Immediately offer service credits and a discount to defuse the anger
- B. Acknowledge the impact and take accountability, then commit to a concrete root-cause and prevention plan with dated milestones before discussing commercials ✓
- C. Explain the technical root cause in depth to demonstrate transparency
- D. Redirect the conversation to the account's strong ROI to remind them of the value
Correct answer: B. De-escalation starts with genuine accountability and a credible, dated remediation plan; leading with discounts or ROI deflection before restoring trust reads as transactional and deepens the damage.
Your health-score model flags an account as green (high login frequency) but the account churns. Post-mortem review suggests the logins were from a single power user. What model improvement best prevents recurrence?
- A. Increase the weight on total login volume so activity is captured more fully
- B. Add breadth-of-adoption signals like number of active users and departmental spread, since concentrated usage on one person is a hidden single-point-of-failure risk ✓
- C. Replace behavioral signals with NPS as the primary health input
- D. Lower the green threshold so fewer accounts qualify as healthy
Correct answer: B. Login volume concentrated in one user masks fragility, so adding breadth-of-adoption signals like active-user count and departmental spread exposes single-point-of-failure risk that raw activity hides.