In this episode of Mastering CS: Candid Leader Insights, Irina Cismas talks with Nima Ataei, Senior Strategic Customer Success Manager at Sprig, an AI research platform for product teams. Nima manages a few dozen strategic enterprise accounts across fintech, healthcare, consumer, software, and fashion.
He explains why discovery belongs in every conversation, how to say no to feature requests without damaging the relationship, and why multithreading has to start during onboarding while the product is still new and exciting.
What You’ll Learn
- Why discovery should happen on every call, not just at kickoff
- How to say no to feature requests and turn them into expansion cases
- How to multithread during onboarding before momentum fades
- How to build a value story that makes expansion feel natural
- Why a lean, personal system can beat a heavy tool stack
Key Insights & Takeaways
Every call must deliver value. Customers who dodge meetings are a lagging sign that past calls had nothing to show.
Separate the relationship from delivery. A strong relationship survives a “no.” A transactional one doesn’t.
Turn asks into business cases. Understand how a missing feature affects the customer, then build value around it together.
Multithread while you’re the shiny new toy. Book enablement sessions with other teams during onboarding, even if they’re a month out.
Track every request on a slide. Showing what’s delivered and what’s on the roadmap makes customers feel heard.
Build the value story all year. Expansion is easy when the renewal conversation shows usage, adoption, and ROI.
Podcast transcript
Irina (0:06 – 0:27)
Welcome to Mastering CS Candid Leader Insights, the podcast where we dive into the world of customer success with industry leaders. I’m your host, Irina Cismas, and today I’m joined by Nima Ataei, Senior Strategic Customer Success Manager at Sprig, an AI research platform for product teams. Nima, I’m really happy to have you here.
Thanks for joining.
Nima (0:28 – 0:30)
Thank you for inviting me, Irina!
Irina (0:31 – 0:40)
Let’s start with the very beginning. Paint us a picture of your world at Sprig. Who are your customers and what does the work look like day-to-day?
Inside Customer Success at Sprig
Nima (0:41 – 1:41)
That’s a great question. So Sprig is a product research platform. My customers are primarily product research and design leaders at large enterprise companies who are trying to understand their users faster.
So my book is a few dozen strategic accounts and my industries span from FinTech to consumer, healthcare, enterprise software companies, and even some fashion brands. And so my day-to-day is to keep really three things alive. And that’s one, a value narrative of Sprig, especially with executives.
The second part is really unblocking adoption inside the org and really fostering and accelerating adoption internally. And then the last part, I think is the most important part of customer success. And that is to make sure that we always have more than one point of contact at every single customer relationship.
We call that multi-threading. And I would say that it’s probably one of the most important things to sustaining a healthy long-term client relationship.
Q4 Priorities and Influencing the Roadmap
Irina (1:42 – 2:14)
I’m glad that you mentioned this and want to dive deeper into the multi-threading part because I think it’s easier said than done in practice. So I’m curious how you do it. But before that, I wanna ask you, we are almost at the end of the year.
We are entering Q4. If you guys are respecting the traditional fiscal year. So I’m curious, what’s the number one priority for the end of this year, for Q4 especially?
What are you trying to solve now?
Nima (2:16 – 4:14)
That’s a good question. So our Q4 and most of the companies that I’ve worked at, Q4 usually ends in end of January. And I think the reason why companies do this is so that the go-to-market people have some quality of life around the holidays.
We all deserve to have a nice Christmas, a nice new year and not have to worry about meeting our numbers and our goals. But that does segue me into our priorities, which right now being in startup life is very much about meeting our goals. And our goals are extremely ambitious and they’re aggressive.
And I think they’re also quite manageable at the same time. And so right now our product team is hyper-focused on building products to bring parity to our biggest competitors. And on the CS side, we are providing that feedback and helping product really prioritize what’s gonna move the needle.
As a CSM, our primary value is to make customers feel heard. The best way to do that is to actually meet with them and to be enticing and bring value to the meeting so that customers wanna show up. And to constantly be doing discovery in every single conversation about what is top of mind for you right now?
What are your high priority initiatives? How can we help you move the needle? And if there is some piece of functionality missing, it’s helping prioritize the product roadmap and really triaging those wants and asks, finding viable workarounds so that you’re not overloading the product team with asks for small minute because they can’t give customers every single small feature and detail that they want.
But if there are five really large customers with renewals coming up that have this functionality that it’s absolutely a deal breaker for them, that is our role to really sound the alarm bells with the product of, hey, if this feature isn’t a high priority for you now, maybe it’s time to reconsider. And let’s talk about the impacts that this might have if it’s not.
How to Say No Without Hurting the Relationship
Irina (4:15 – 4:51)
And if it’s not, how do you say no to customers? So that you keep the relationship on a positive vibe as well. And how do you balance?
Because you can’t transform the product into a catch-all. And customers, different customers have different needs. And if you accommodate every feature for every big customer that has a six-figure contract associated, not sure how the product vision changes.
How do you balance this?
Nima (4:52 – 6:59)
That’s a good question. I’m gonna focus on the first part of the question of how do you sustain the relationship? Because some customers, I’m very lucky, some of the customers that I work with are extremely enthusiastic.
And they are very forward with their feedback and their wants and they’re excited and they love our product and they wanna help us be better every day. Like you said, you can’t deliver every single thing that every customer asks for. It’s just not feasible.
Especially when you’re operating lean, which seems to be the theme of today. So I really separate building a relationship based off of delivery. Relationship building is an art in and of itself.
The way that I really sustain that is by prioritizing face-to-face meetings with customers. I think if you’re not getting in front of your customers and really adding that personal touch to those relationships, then things become very transactional, which is not ideal. Because the moment that you have to say no, suddenly you’re tarnishing your relationship and really doing damage.
I think when you have a really healthy customer relationship and a customer comes to you with an ask that you can’t deliver, the first step is, well, walk me through and help me understand by doing some discovery, how is this going to affect you if you don’t have this? How does this affect you now? What are you using?
What is your current workflow? Are you using a different product? Are you trying to consolidate products?
Because I can build a case of an expansion based off of delivering this want to you. So I can help you get what you need, but there has to be a give-take and a push-pull. If you just want me to continue to deliver product just for you to renew flat every single year or every two or three years, then it becomes difficult to build that case.
But it’s very much a build a healthy, solid relationship where they know and trust me as a trusted advisor. And then help me help you. If there’s something that you need, help me build a case around it and help me build value around that case.
And then we can drive this initiative forward. And most customers understand this because this is exactly how their organizations work too.
Why Discovery Happens on Every Call
Irina (7:02 – 7:42)
Tell me more about the discovery process because it seems a very important milestone. And it’s the first time when I hear from CSM that they are running discovery in multiple moments. So not only at the very beginning when you have a handoff between work, but not only in the first meeting with the client.
How often do you do it? When do you do it? When do you receive the signal?
Now I need to dig deeper and try to understand the why behind the ask.
Nima (7:43 – 10:44)
This is a great question. I like this question a lot. Discovery, in my opinion, happens on every call and every interaction.
Every call that’s scheduled with the customer is delicate because if they don’t walk away with value, they won’t wanna meet with you again. And every customer success manager has been through the trials and tribulations of meeting with a customer that is just, or trying to get a meeting with a customer who’s dodging you like the plague. And I think that that is usually, that is a lagging indicator of, hey, the last few times that we met, I didn’t have anything to show for it.
So it’s really important, in my opinion, to get ahead of that. So every call starts with a question of what is my goal as the CSM and the relationship manager for this call? And how do I make sure that I achieve that goal?
And the number one goal is to make sure, for me, that the customer walks away with real value from the conversation. So I think when you start there, it makes sure that you always have a healthy relationship. And if you ever need to ask a question, so back to your question of discovery, it happens every single call because some time has passed inevitably between when we last met.
Priorities have changed. New initiatives have arisen. And working at a small startup, we are constantly delivering new features and functionality.
And I’m trying to see how those features and functionality can serve the customer. So it leads the conversation of discovery around, well, what is your incumbent product for this new feature that we launched? Can we help you consolidate?
We want to expand our footprint. The land and expand motion is very much alive today at most companies, especially smaller ones. So as we’re delivering new product, I want to understand, well, how can this product fit in and serve value to you?
How can I help you consolidate? How can I help you save money? How can I help you gather efficiency?
How can I prevent you from having to live in five different products and narrow it down to one, the one that I’m working with you on? And so that’s leading with discovery. It’s what are your top priorities and your initiatives today?
When it comes to the research that you’re doing, what other products are you using? Why are you using those other products? What unique value are they serving to you?
And then it’s, hey, I just want you to know, we just launched this really exciting functionality. I know you love our product and I know we have a friendly UI. Every single person is using your product, our product in your organization.
And we have an MCP connector, which really is, it differentiates our product from others. So it’s, if you’re very AI forward, most companies are becoming that these days. We can save you time.
You don’t even have to log into our product anymore. If you adopt more and more of these solutions, you can just query your LLM for the research goals and studies that you want to create and your LLM can do the work for you using our tool.
Multithreading from Day One
Irina (10:46 – 11:26)
Okay. There’s a lot. And I like the storytelling behind this.
And ou also answered another question that I didn’t articulate about the value. So I’m not going to insist on this, but I want to ask you about multi-threading and how do you work with different stakeholders inside one organization? Because you are right.
If you manage to infiltrate and if you manage to become the go-to solution for multiple divisions, multiple teams within the team, it’s harder to be replaced as a product. So how do you end up there?
Nima (11:29 – 15:34)
That’s a good question. And that’s very much an art. I think it starts with when you have a customer who’s onboarding, they just bought your tool and you are the shiny new toy.
Every time you buy something new, there is this momentary level of excitement around it. And usually there’s multiple decision makers who are part of that decision-making process to bring the tool in. As a customer success manager, who’s onboarding a new client, you have a very limited window to make sure that you start off successfully.
The first thing is understanding the why behind the buy. And the first couple of meetings, it’s generally not just me, my technical counterpart, the account executive, and one other person on the client side. It’s typically our main stakeholder and champion, the decision maker, and then the technical counterparts that are integrating our solution into their platform and their workflows.
That is the perfect time to really embed and build relationships and trust with those three people. And then the question as we’re onboarding is, who are going to be our end users? Who are going to be our power users?
Are there any other organizations? Once we have the investment and we have stood up our solution and embedded into your systems and workflows, it becomes much easier to adopt. Who else might be interested in this?
Let’s schedule an enablement call with them. Even if it’s a month out, we can do a lunch and learn. We can separate from the power users where we get very deep to the lighter level users who are going to be leveraging a lot of our AI products to help them build out their studies because they’re not professionals in this space.
And they have questions that they need to be answered around their customers’ usage behaviors. And we can separate it out and kind of keep it very light and high level. And then we can also go very deep.
But if we schedule that now, a month out, at least there’s something on the calendar. We have that placeholder and that stake in the ground that we’re laying when the product is new and exciting and we have a lot of backup. If you wait to do this, then you are really climbing an uphill battle.
And you’re usually siloed to one person who’s like the main leader, but you’re begging them to introduce you to other people in the company. And it’s just, it’s like pulling teeth and you can do it, but it’s so much harder to do it then. And sometimes you fall to that point.
I’ve had situations where as we are going through the deal process, the deal cycle is really long. We have all these stakeholders. And then by the time we get the final signature, all of our stakeholders have transitioned out of the customer’s company.
And we’re left with one person who’s like, I don’t really know what I’m doing here. I was told that I own this relationship. I wasn’t part of the process.
And it’s like, well, back to discovery. Okay, cool. Paint me a picture of what your org is looking like.
Who do you roll up to? What are your initiatives right now? What is top of mind for you?
And then it’s the onus falls on us to build out using our imagination of, okay, so this is your current primary use case. And understanding how your organization is structured, you have a design team that suddenly I know doesn’t have user researchers who are doing research for you. So how does the design team know what to design right now?
How do they know what to prioritize? How do they know what their customers want? Chances are they don’t.
So how are they building their roadmap and prioritizing? Well, we can help them understand that with very low lift and without having to be a researcher. So right now, the theme that we’re seeing is the democratization of research as research teams are getting leaner and leaner and they’re expected to deliver more and more.
Our platform is helping enable marketing and product and design teams to run their own studies so that they have a North Star of what they’re working towards actually going to serve their customers’ needs.
Expansion That Doesn’t Feel Like Selling
Irina (15:38 – 16:07)
Now I’d like to dive deeper into the expansion side. How do you tackle it? Tell me more about this expansion part.
How do you do it so it doesn’t feel like you want to add more or inflate the invoice that comes next year? How do you make it in a very elegant way and customer-driven rather than from your side, from a sales perspective for achieving a KPI?
Nima (16:09 – 16:17)
Yeah, absolutely. For me, I don’t ever feel like a salesperson because I feel lucky that- You are a salesperson.
Irina (16:18 – 16:23)
And you were a salesperson in your history, if I’m not mistaken.
Nima (16:24 – 19:53)
I have been in my past and I like to frame myself more as a relationship builder because at the end of the day, we all need things to make our lives easier and better and we’re always shopping for something. It’s just a matter of, is this going to solve for my needs? And so I think expansion motions become really easy and naturally intuitive when you are making your customer feel heard.
So if they’re asking you for a bunch of asks throughout a call, what I do is I make a spreadsheet and I make it into a slide. Every single check-in call has an update of these are the things, these are the additional functionality that you asked us for. And these are the ones that we’ve delivered on so far.
And the other ones are still on our roadmap. Where they are, I may not have a date and a timeline for you, but they’re there. And I make sure that I touch on them every single call.
So when we deliver new functionality and the capabilities of our product have expanded and have made our customers’ lives easier, it becomes natural that we start to gain greater market share where they come to our platform for things that they were going to other platforms for. Suddenly, when the other renewals for their incumbent platforms come up, there’s the question of, are we getting the same value from this as we were before we started adopting Sprig? And so it becomes really natural.
And then at our renewal conversation, it’s look at how much additional utility we have delivered to you. And here are the metrics through our QBRs and our executive business reviews that really show the additional value that you’ve gained. Look at how much your usage has skyrocketed.
Look how many more people are in the platform. These are real ROI and KPI metrics that you can share. And so it becomes a no brainer when you’re asking for more dollars.
I think that if you want to keep everything status quo and ask for more dollars at a renewal or even ask for renewal commitment, you’re asking for way too much. There has to be a value story that you’re able to tell. And as a CSM, you’re building that value story all throughout the year, throughout different stakeholders.
And it’s about knowing your customers, getting in front of them, having that personal relationship, but also keeping it professional. You can’t just wine and dine and send a basket of cookies and expect customers to renew. It’s breaking bread, having a face-to-face conversation, understanding their pain points, actively working to solve them, delivering the value story at the end of a quarter or at the end of a half, well before the renewal, and then starting to build a conversation of asking the hard questions.
Are you planning on renewing with us? Is there any pause? What does your renewal process look like?
Will procurement be involved? Who are the stakeholders? Who are the primary decision makers in this?
Can we get in front of them? Can we talk to them? Can we help you, the champion, the end user, the alleged decision maker?
Can we help you build a case internally of how valuable this product has been because we can do that for you. Let us take as much of that ugly process off your plate. And that really, having the trust in that relationship allows us to unblock those challenges and jump over those hurdles.
And that I think is what leads to healthy and successful expansion internally.
A Lean CS Stack Built Around One Spreadsheet
Irina (19:56 – 20:21)
What is the operational infrastructure behind all the processes and everything that you just described? What platforms are central on how CS actually runs day-to-day at Sprig? Is it, do you also need tools and systems behind all of this?
Or is it more on the relationship building part and you can live only in the CRM?
Nima (20:22 – 24:34)
This is a good question. And I may really upset people with my answer.
I think that ultimately, I’ve worked at really large enterprise organizations. They had every tool under the sun. They had the top tier CRM that was super expensive and they had the ops team that their sole responsibility was to build out and to maintain and manage and continue to optimize these CRM systems that are so sophisticated.
And then we had our sentiment tracking systems and we had our communication systems. And there was just everything under the sun. And all it did was create a lot more work for the CSM because these are all systems that, in my experience, there was no automation.
They were all very manual. And so there was a lot of resentment around, well, am I spending my time in front of customers or do I spend my time updating our CRM system? And coming into the startup world across the two startups that I’ve worked at, I’ve realized that being in a lean operating org where there’s very little internal process and a lot of flexibility for you to manage customers and those relationships and document the way that it’s comfortable for you is way easier.
I spend most of my time in front of my customers. I don’t spend more than five hours a week. If that, updating CRM systems.
We have a CRM system. We have systems that it’s a little bit manual because being at a startup, it’s very bootstrapped. So you don’t have as many systems available to you.
For me, I keep one master spreadsheet with all of my customers. It is extremely involved and I rely on filters to kind of help simplify it down. Effectively, what I do is that master spreadsheet has several tabs.
One is my master account list. Every single customer, who their account executive is and who the technical counterpart is assigned to that team. Then I have a couple more rows and columns.
It is who are our primary stakeholders? What are their email addresses and where are they located? Super important.
I’ll get to that later. Beyond that, I have their primary use cases. I have their expansion opportunities and their biggest challenges, our last conversation, key takeaways and our next steps.
On the next tab, I have an organized list of my current expansion opportunities that are my big bets. What I’m focused on, who the customer is, where we are in that conversation, what are next steps? Then I have my biggest risk accounts.
What is the primary blocker? Where are we? Again, what are next steps?
And then I have my tickets, like my high priority customers, what tickets do they have open now? Are we making progress on solving their challenges? It sounds very manual.
It’s really simple. What I do is I have a weekly meeting with every single one of my account executives. I filter who our customers are and I tackle, do we have a call schedule with these customers coming up?
Where are we? Did my account executive have a conversation with this customer behind the scenes that I wasn’t involved with? What was discussed?
What is the outcome? What’s changed? What do I need to know about?
What do I need to action and execute? And then we divide and conquer. So in our meetings, we are, this is what you own.
This is what I own. This is our North Star. Okay, cool, go.
And that’s how I stay organized. Every single thing, all of my notes, I use Granola as a note taker that goes directly into our CRM. I use an LLM.
It connects to Gong. It connects to Slack. It connects to my email.
It connects to my note taker. And I can quickly query, okay, who do, what customers do I owe follow-ups to? What are those follow-ups?
I block an hour at the end of my day and I just get them done. So that’s how the systems that I use, they’re pretty rudimentary right now. And I’ll say that compared to the times where I had really sophisticated, expensive systems, I actually prefer this because this is my way.
It’s my style. There’s a lot of personal touch to being a CSM. And this is where I’ve found the most success.
Staying Human in the Age of AI
Irina (24:35 – 24:48)
The last question, you’ve been a recruiter, a salesperson and an entrepreneur. Is there a habit, a way of thinking or something you learned the hard way early on that still shows up in how you run accounts today?
Nima (24:52 – 26:29)
This is a good question. I really believe in being old school. I use technology to the point where it makes my life easier and it automates the mundane tasks that I don’t enjoy.
Ultimately, I really enjoy the work that I do because I love working with customers and I love working with people and I don’t want anything to replace that. Everything else is a tool to sustain that North Star of having good, healthy customer relationships. So I use tools to help me deliver and help me wrap a bow around things that I know how to do the hard way.
But then there’s some things like writing emails and sending Slack updates that I actually like to write out manually. I don’t always use an LLM, especially for my communications because there’s something so AI when you read a message that was created by an LLM, you know it’s a little too sterile, it’s a little too perfect. I want the occasional typo that I have to send another email to apologize about every once in a blue moon because it’s like, hey, look, I’m a human and I’m here to build a relationship and with that relationship, I’m going to drive your priorities and your missions forward.
And so those are some of the, that’s my personal North Star. What I’ve learned is the people that are a little bit too tech forward, they tend to have more sterile customer relationships. And I think my customers love working with me because I bring a lot of human aspect to the relationship and that’s why I’m not scared of AI and I’m not scared of technology.
I don’t think it’s going to replace my job because nobody else can be me.
Irina (26:31 – 26:49)
Nima, this was a really great conversation. Thanks so much for taking the time to talk to me today and to share your story and the ins and the outs. We definitely have to schedule a follow-up session because we could have easily spoke for another hour.
Nima (26:50 – 26:56)
Irina, you and I together, we can conquer the CS world together. Thank you so much for inviting me. I really appreciate it.
Irina (26:57 – 27:04)
To everyone listening, thanks for tuning in. Until next time, stay curious, keep learning and mastering customer success.