Crafting your CSM story
Having a solid track record is more than just about rattling off numbers. It's about telling compelling stories that make hiring managers sit up and take notice. Let's walk through how to capture your wins in a way that'll make your next job search so much easier.
When you're interviewing for that next CSM role, you need more than just "I handled X accounts" or "I hit my renewal targets." You need stories that show exactly how you think, how you work, and the real impact you've had. This matters because:
It gives you concrete evidence to back up everything you're claiming
You'll feel way more confident walking into interviews
You can negotiate better pay because you have proof of your value
You won't be stuck trying to remember details when you're put on the spot
You'll stand out from other CSMs who just list their responsibilities
This guide will show you how to use the EPIC framework, a helpful way to turn your experiences into stories that land.
Turning Your EPIC Wins Into Interview Stories
Here's the thing about CSM interviews, everyone can list what they've done, but the ones who land the best jobs know how to tell compelling stories about their wins that resonate with the hiring manager. The EPIC framework is your secret weapon for turning your experiences into stories that showcase your strategic thinking and execution skills.
Event (Setting the Scene)
This is your opener, the moment you grab their attention and set up the stakes. Don't just state facts; paint a picture of the situation and why it mattered. Think about it like setting up a movie, you want the interviewer to immediately understand the challenge and why it was crucial to solve it.
Weak: "We had an enterprise customer with low adoption rates, and they were thinking about leaving us."
Good: "Our $2M enterprise customer's usage had dropped to 45% and their executive sponsor was openly discussing moving to a competitor at renewal in 90 days."
Great: "After inheriting our largest account ($2.8M ARR), I discovered usage had plummeted to 45%, their executive sponsor had left during a merger, and their new CTO had given us 60 days to prove value or they'd switch to a competitor. With 10,000 users across 12 countries and our main technical champion resigning, we were at serious risk."
Performance (Your Actions)
Here's where you show how you think and work. Don't just list what you did. Explain your strategy, decision-making process, and how you approached the challenge. This is your chance to demonstrate your problem-solving skills and strategic thinking.
Weak: "I created a plan to improve adoption and met with stakeholders to understand the issues."
Good: "I launched a 30-60-90 day rescue plan that included stakeholder mapping, custom success metrics, and a new training program aligned with their business goals."
Great: "I took immediate ownership by: mapping decision-makers across all regions, creating a rapid response team with product and engineering, developing custom success metrics tied to their post-merger KPIs, implementing daily usage monitoring with automated alerts, and building a champions network with leaders in each region."
Impact (The Results)
Numbers tell, but stories sell. Yes, you want to share the metrics, but also show the broader impact on the business relationship and any lasting effects on your organization. This is where you prove your value in concrete terms.
Weak: "The customer's usage improved and they renewed their contract."
Good: "Within 60 days, adoption increased from 45% to 85%, and we secured a two-year renewal with a 20% expansion."
Great: "By the 60-day mark, we'd driven adoption to 92% across all regions, secured a three-year renewal at $3.5M (25% increase), gained them as a beta partner for new enterprise features, and had their CEO agree to keynote our user conference. The account has since generated three referrals worth $2M in new business, and our rescue playbook became the global standard for at-risk accounts."
Conclusion (The Learning)
Don't just end with results - show reflection and growth. This demonstrates self-awareness and your ability to turn experiences into repeatable success strategies. It's what separates strategic CSMs from tactical ones.
Weak: "I learned that stakeholder management and communication are really important."
Good: "This experience helped me develop a proactive risk monitoring system that I now use across all enterprise accounts."
Great: "This situation transformed my approach to enterprise customer success. I developed a proactive risk monitoring system, gained deeper insight into post-merger dynamics, and learned to balance tactical fixes with strategic relationship building. These lessons helped me maintain 100% renewal rate across my portfolio for the following year, and my approach has been adopted as our team's standard playbook."
Pro Tips:
ve 3-4 stories ready that showcase different skills
Practice telling each story in under 3 minutes
Focus on your specific actions and decisions
Always connect the impact to business value
Show how you've applied the lessons since then
Remember: The best stories show both your ability to handle immediate challenges AND your capacity to turn those experiences into repeatable success strategies. That's what separates strategic CSMs from tactical ones.
Gather Your Wins
When interviewing for that next CSM role, you need more than just "I handled X accounts" or "I hit my renewal targets." You need stories that show exactly how you think, work, and create impact. This matters because:
It gives you concrete evidence to back up your claims
You'll feel more confident in interviews
You can negotiate better pay with proof of value
You won't struggle to recall details when put on the spot
You'll stand out from CSMs who just list responsibilities
Here are three areas to focus on: revenue impact, customer victories, and leadership.
Revenue Impact
Let's start with the money stuff because this excites hiring managers. Here's what to look for in your experience:
Times you saved a customer from churning
Write down any time you spotted a customer heading for the exit and turned it around. I'm talking about situations like when you noticed dropping usage rates, dealt with an unhappy executive, or had to handle a major service issue.
Don't just write "prevented churn" - get into the specifics: What were the warning signs? How much ARR was at risk? What exactly did you do? For example, maybe you noticed a key champion left and immediately scheduled executive briefings to rebuild relationships, or you created a 30-60-90 day rescue plan that saved a $500K account. These are gold in interviews because they show you can protect revenue.
Big expansions you landed
Look for any time you grew an account beyond the initial deal. But don't just focus on the final dollar amount; document your expansion strategy. Did you map out use cases across different departments? Did you run a pilot program that proved ROI?
Include details like how you identified the opportunity (maybe through QBR data analysis or stakeholder interviews), how you built the business case (like running ROI calculations or building joint success plans), and how you navigated the approval process. Even better if you can show how you developed these opportunities yourself rather than just processing orders that fell in your lap.
Creative ways you found upsell opportunities
This is different from regular expansions. These are the times you thought outside the box. Maybe you noticed customers were using a workaround and suggested a premium feature that would work better. Or you spotted a trend across several accounts and proactively reached out to similar customers with a solution.
Document your thought process: How did you spot the opportunity? What data did you use to back it up? How did you pitch it? For instance, maybe you analyzed support tickets, found a common pain point, and created a business case for an add-on module that solved it.
How you helped customers save money
This might seem counterintuitive when talking about revenue impact, but showing how you helped customers optimize their spend often leads to longer-term revenue growth. Document cases where you helped customers get more value from their existing investment.
Maybe you helped them consolidate licenses, showed them how to use advanced features they were paying for but not using, or implemented automation that reduced their operational costs. Include specific metrics about time saved, resources optimized, or processes improved. The key is showing how this built trust and ultimately led to them investing more with you.
For each of these, remember to capture:
The size of the account/deal in revenue
The timeframe you achieved it in
Any specific blockers or challenges you overcame
The exact steps you took (your personal contribution)
The final outcome (both in numbers and relationship impact)
Any relevant tools or processes you used
Who you worked with (both internal teams and customer stakeholders)
Long-term impact beyond the immediate win
The secret sauce here is showing both the "what" and the "how." Anyone can say they saved a customer from churning. You need to show your specific approach and thinking. That's what sets you apart in interviews.
The Stories That Show Your Strategic Impact
These wins are about more than just making customers happy - they show how you can solve complex problems and drive real business impact. Let's break down what to capture:
Major problems you solved
Every CSM has those "fire-fighting" stories, the big challenges that seemed impossible at first. Don't just focus on technical issues; look for situations where you had to manage multiple stakeholders, navigate competing priorities, or turn around a deeply frustrated customer.
Get specific about:
What was broken when you stepped in? (Paint the scene)
Who was impacted and how severely?
What had others tried before that didn't work?
How did you approach the problem differently?
What resources did you pull together?
For example, maybe you walked into a situation where a customer's team was ready to quit because their workflows were so broken. Document how you mapped their processes, identified the bottlenecks, brought in the right technical resources, and rebuilt their entire approach. Include the before/after metrics, like "Reduced workflow time from 4 hours to 30 minutes" or "Eliminated 90% of manual data entry."
Big projects you got off the ground
These are the strategic initiatives that transformed how customers use your product. Think about times you:
Launched a new use case across their organization
Led a complex migration or upgrade
Implemented a new integration
Rolled out a change management program
Don't just list what the project was - document your project management approach:
How did you get executive buy-in?
What was your rollout strategy?
How did you handle resistance to change?
What processes did you create?
How did you measure success?
For instance, if you led a global rollout, break down how you handled different regions, languages, time zones, and cultural considerations. Show how you created templates or playbooks that could be reused.
Times you made things work better
This is about process improvement and optimization. Show how you didn't just maintain accounts but actively improved them. Look for examples where you:
Streamlined customer workflows
Improved data quality or reporting
Created better ways to measure success
Fixed broken internal processes
The key here is to show both the immediate and long-term impact. Maybe you noticed customers were struggling with monthly reporting, so you built a dashboard template that:
Cut report creation time by 75%
Improved data accuracy by 90%
Got adopted by other customers
Became part of your standard onboarding
Customers you turned into raving fans
This goes beyond just "good relationships." These are the customers who actively advocate for you. Document how you transformed standard customers into vocal champions:
What was the relationship like when you started?
What specific actions did you take to build trust?
How did you identify and develop internal champions?
What opportunities did you create for them to share their success?
The real win is showing how you systematically built these relationships. Maybe you created a customer marketing program that:
Identified potential advocates based on specific criteria
Developed a path to turn power users into champions
Created opportunities for them to showcase their expertise
Resulted in X number of referrals or case studies
For all these victories, remember to capture:
The initial state (what was the situation when you started?)
Your specific contribution (what did YOU do?)
Key metrics (both hard numbers and soft benefits)
Stakeholder impact (who benefited and how?)
Long-term results (how did this keep delivering value?)
Reusability (how did you scale this success?)
Pro Tip: Keep a "wins" folder in your email where you save messages from happy customers or internal stakeholders praising your work, emails, metrics screenshots, and presentation decks. These make great supporting evidence when you're preparing for interviews.
Leadership Moments
These wins show you can think bigger than your own accounts and drive change across an organization. Here's what to look for and how to document it:
Projects where you took charge
Look for times when you spotted a problem and stepped up to fix it (not just when you were assigned to lead something). For example, maybe you noticed customers struggling with onboarding and took the initiative to rebuild the whole process.
Example: "I saw our enterprise customers all hitting the same onboarding roadblocks. Instead of just dealing with it account by account, I analyzed data across 50+ accounts, presented findings to leadership, and led a cross-functional team to create a new framework. Ended up cutting time-to-value by 60% and it became our standard enterprise onboarding approach."
Processes you fixed or created
This shows you're a system thinker who can spot inefficiencies and build better solutions. For instance, if you revamped how your team handles QBRs, break it down.
Example: "Our QBR process was a mess - everyone did their own thing and spent way too much time on prep. I gathered feedback from the team, created a standardized template with automated data pulls, and built in best practices we'd learned. Went from 5 hours of prep time to 2 hours, and our completion rate jumped from 60% to 95%. Now every CSM uses this approach."
Times you helped others grow
Leading without authority isn't just about processes. It's also about developing people.
Maybe you:
Started an informal mentoring program where you worked with new CSMs
Created playbooks for common scenarios
Ran coaching sessions to help others learn from my mistakes.
Whatever the case, these are great stories to save and share.
New programs you started
These are initiatives that changed how your team operates.
Example: "Built our customer advocacy program from scratch. Noticed we were missing opportunities to leverage customer success stories. Created a simple framework to identify potential advocates, developed a path to turn power users into champions, and built in rewards for their participation. Generated 15 new case studies and 20+ reference calls in the first six months."
When documenting leadership wins, focus on:
The problem or opportunity you spotted
Your specific contribution
How you got others on board
Measurable results and lasting impact
How it scaled beyond the initial scope
The best leadership stories show both your strategic thinking AND your ability to execute. Anyone can say they led something - you need to show how you spotted the opportunity, built support, and delivered results that stuck.
Frequently Asked Questions
Let's tackle the questions CSMs preparing their success stories.
Q: I can't remember exact numbers from my past wins. What do I do?
A: Not having precise metrics doesn't mean you can't tell compelling stories about your impact. Here's how to handle this situation professionally:
Start with what you know for sure. If you managed enterprise accounts, you likely remember the general size range or tier of customers. You might say "This was a strategic enterprise account in our top revenue tier, typically $1M+ in ARR."
Use context to frame the impact. Instead of exact percentages, describe the scope and scale: "The solution we implemented affected all enterprise users - about 40% of our customer base at the time."
Compare results to baselines. When exact numbers escape you, show relative improvement: "Before my intervention, onboarding typically took 8-12 weeks. We brought that down to consistently under 4 weeks."
Document going forward. Start keeping a simple success journal where you note key metrics and wins. Even a quick email to yourself with "Just finished the ABC account expansion - $450K upsell, 3 new departments onboarded" will give you reliable numbers for future interviews.
Q: How many stories should I have ready for interviews?
A: Quality beats quantity when preparing interview stories, but you need enough examples to showcase your full range. Here's a practical breakdown of what to prepare:
Build your core story bank. Aim for 6-8 well-crafted stories that demonstrate different skills and situations. Include:
Two customer rescue stories showing how you identified risks and turned around struggling accounts
Two growth stories about driving expansion or upsell opportunities
Two strategic initiative stories where you improved processes or launched new programs
One leadership story where you influenced without authority
One challenge story showing how you handled setbacks and learned from them
Prepare different versions of each story. Structure them in:
A 30-second highlight for quick examples
A 2-minute version for standard behavioral questions
A detailed 5-minute version for in-depth technical discussions
Focus on recent wins. While you might have great stories from five years ago, prioritize examples from the last 2-3 years unless your older story demonstrates something uniquely valuable. Recent experience carries more weight with hiring managers.
Q: A lot of my wins were team efforts. How do I talk about them without taking too much credit?
A: Talking about collaborative wins requires a delicate balance between showcasing your leadership and acknowledging team contributions. Here's how to handle it effectively:
Lead with your specific contributions first. Start by clearly stating your unique role.
Example: "Our renewal rates were dropping across enterprise accounts. I analyzed our customer health data and discovered a pattern in product usage that predicted churn. Based on this insight, I designed an early intervention program and brought in our product and technical teams to help implement it."
Use "I" and "we" strategically. Be precise about ownership.
Example: "I created the expansion strategy for our mid-market segment. Once approved, we as a team rolled it out across 200 accounts. I owned the strategic framework and success metrics, while our technical team handled the implementation. This combination led to a 25% increase in revenue."
Highlight your coordination role. Often your value lies in bringing people together.
Example: "When we had a major service outage, I took charge of coordinating our response. I set up a daily standup between support, engineering, and customer success, created a shared dashboard for tracking affected accounts, and managed all customer communications. This structure helped us resolve issues 30% faster than our previous outages."
Show how you amplified others' work. Demonstrate leadership through enablement.
Example: "After noticing our support team solving the same integration issues repeatedly, I documented their troubleshooting process. I turned their expertise into a playbook that reduced resolution time from 2 days to 4 hours. The team now uses this guide to train new hires."
A bit of caution I’d offer here… don’t use stories where you were a minor character in the solution. Interviewers pick up on embellishment of involvement quickly and shining a light on the rest of the team doesn’t really serve you in the interview process. If you are having trouble explaining your personal impact, even if it was a great win, it probably shouldn’t be used.
Q: What about projects that didn't go as planned? Should I just avoid mentioning those?
A: The strongest candidates don't shy away from discussing setbacks, they use them to demonstrate growth and adaptability. The key is framing these situations as learning opportunities that made you better at your job.
The fact is, you will probably be asked at least one question about a past failture. You should have a few examples ready. Here's how...
Lead with context and be direct about what happened. Briefly explain your goal, what didn't work, and why. For instance: "We aimed for 80% adoption of a new feature across our enterprise segment within 90 days. We hit 60% because we underestimated the complexity of rolling out changes across multiple global offices."
Then focus on your response and learning. The meat of your story should be about how you adapted and what insights you gained. Maybe you discovered the need for localized training materials, or realized different regions needed different change management approaches.
Most importantly, connect it to future success. Show how you've applied these lessons to improve your approach. For instance, "Now before any global rollout, I create a cultural impact assessment first. My last three international launches all exceeded adoption targets using this framework."
Interviewers aren't looking for perfection - they want to see resilience, self-awareness, and the ability to learn from experience. A well-told story about managing through challenges often makes a stronger impression than a simple success story.
Q: My numbers don't look as impressive as some industry benchmarks. Should I skip those stories?
A: Raw numbers never tell the whole story. Context and relative impact matter more than absolute figures.
Here's what matters:
Focus on value created, not just size. Maybe you kept a small but strategic customer that opened up a new market. Or perhaps you improved processes that had ripple effects across the organization. Example: "My biggest win wasn't the $2M expansion - it was turning around a $200K account that became our first foothold in the healthcare sector, leading to $5M in new business."
Highlight relative improvement. Your impact often shows better as a percentage or relative change. During an economic downturn, maintaining flat renewal rates might be more impressive than growth during boom times. A 40% improvement in a mature product can be more challenging than doubling metrics for a new one.
Consider your scope of control. If you inherited underperforming accounts or worked in a challenging market segment, steady improvement might represent exceptional performance. Be ready to explain your operating environment and constraints.
Good hiring managers care more about how you approach problems and create value than about hitting arbitrary benchmarks. They want to understand your thinking and see evidence of consistent improvement.
Q: Some of my best work was about preventing problems. How do I tell stories about things that didn't happen?
A: Prevention stories can be powerful evidence of your strategic thinking and risk management skills. The trick is framing them around your proactive approach rather than the avoided crisis.
Tell it as a detective story: "After analyzing our churn data, I spotted a concerning pattern - customers who missed two consecutive QBRs had a 70% higher risk of non-renewal. Instead of waiting for escalations, I built an early warning system and playbook for at-risk accounts."
Quantify the potential impact you prevented:
Revenue protected from risk
Time saved by avoiding crisis management
Resources preserved through early intervention
Customer satisfaction scores maintained
Back it up with comparison data. Show what typically happened before your intervention versus after. "In the previous year, we lost six enterprise accounts that showed these warning signs. After implementing my monitoring system, we identified and stabilized eight accounts with similar patterns, protecting $2.8M in ARR."
Pro tip: Document your prevention wins in real-time. When you spot potential issues and address them, take quick notes about the situation, your actions, and the likely impacts you prevented. This makes it easier to tell these stories later with specific details and data points.
Think of it this way...a doctor who prevents a health crisis is just as valuable as one who treats emergencies. Your preventative wins show you can think ahead and solve problems before they impact the business.
Q: What if I'm interviewing for a more senior role? Which stories should I focus on?
A: For senior roles, focus on stories that demonstrate:
Strategic thinking and program creation
Cross-functional leadership
Scale and repeatability of your solutions
Business impact beyond individual accounts
For example: "Instead of just fixing escalations, I analyzed two years of customer data to identify common failure points. This led me to rebuild our entire onboarding framework, reducing time-to-value by 40% across all enterprise accounts."
Q: How should I handle confidential information in my success stories?
A: This is crucial since many CSMs work with sensitive customer data. You can:
Focus on percentage improvements rather than absolute numbers
Use industry or company size instead of names
Describe situations in general terms while keeping specific actions and outcomes
Highlight your process and approach without revealing proprietary details
Last updated
