In this episode of Mastering CS: Candid Leader Insights, Irina Cismas talks with Bilyana Krasteva, Head of Customer Success at Squirro, an enterprise AI platform serving highly regulated sectors like banking, pharma, and manufacturing. Bilyana joined Squirro to build CS globally and found a function closer to project management than true lifecycle management.
She shares how she cleaned up the data, introduced playbooks for renewals, churn risk, and customer success qualified leads, and moved a small team across three regions from reactive work to owning revenue. She also explains why every joint success plan needs a clear ROI, what she looks for when hiring, and the lesson that has stayed with her since her support days: customers don’t care about your processes.
What You’ll Learn
- Why clean data is the first step in building CS
- How to introduce playbooks for renewals, churn risk, and CSQLs
- How to move a CS team from reactive to revenue-owning
- Why every joint success plan needs a clear ROI
- What to look for when hiring CSMs for complex enterprise products
Key Insights & Takeaways
You can’t scale chaos. Define roles, KPIs, and frameworks before anything else.
Data comes before dashboards. Forecasting and risk reporting only work with clean, consolidated records.
CS is not glorified support. Show the organization that CS is a revenue-generating function.
Coach the right questions. Expansion signals come from curious check-ins, not sales pitches.
Speak in numbers. CSMs should know exactly how much ARR they own, forecast, and have at risk.
Podcast transcript
Irina (0:02 – 0:22)
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 Bilyana Krasteva, Head of Customer Success at Squirro. Bilyana, I’m really happy to have you here.
Thanks for joining.
Bilyana (0:22 – 0:22)
It’s a pleasure.
Irina (0:24 – 0:32)
Let’s start with the very beginning. Paint us a picture of your world at Squirro. Who are your customers and what does the work look like day-to-day?
Bilyana (0:33 – 1:16)
Our customers are a wide variety of customers operating in very regulated sectors, from financial institutions to central banks to big names in manufacturing and the pharma and bio-research sector. So everything and anything that is really operating within all sorts of regulations. And in terms of what the day-to-day looks like, it looks like everything.
Customer success and more. So it is a very dynamic team and organization, and even our environment to operate in, with any company that does AI, especially on the enterprise-grade level. So it’s a very dynamic day-to-day.
Q4 Priority: ROI in Every Success Plan
Irina (1:17 – 1:33)
And right now we are entering, I would say, Q4, if Squirro respects the standard and traditional fiscal year, what’s the one thing you are trying to move the most? What’s on your agenda until the end of the year?
Bilyana (1:33 – 2:55)
Oh, we are in a very exciting period right now because we have as a goal until the end of this year to actually merge and perfect further our platform and service offering. So Squirro about a year and a half ago merged with a company called Synaptica, and Synaptica does taxonomy and ontology management solutions. So in addition to the enterprise AI research platform, the retrieval-augmented generation, we now have incorporating into that offering taxonomy and ontology management.
So this is just the bigger picture, but specifically to CS, the one thing that I’m really trying to push my team as well is to make sure that for all of our accounts we have a very clear return on investment formulated within our joint success plans. So everything and anything that we can at this stage support our clients to really justify ROI on AI, what is it that they are gaining, because this high enterprise stakes that we are operating in, it really is important to have for the sake of customer success and for the sake of our customers, one very easy-to-read document, easy to see plan to consult where the ROI, the goal is clear. So that’s what I’m trying to finalize by the end of this year.
Building CS from Scratch at Squirro
Irina (2:57 – 3:33)
It sounds complicated, or definitely not an easy job. Tell me more about the role of head of CS and what was the journey from the very beginning? I know that you joined the Squirro about a year and a half to build CS globally.
So I’m curious, what did you find when you got there and how did you start? What was the first thing that you did?
Bilyana (3:34 – 6:23)
So when I joined Squirro, there was really, in the traditional sense of customer success practitioner, there were no unified playbooks. There was very infant, I would say the infant stage. So CS at Squirro at that time, just under two years ago, was at its infancy stage, meaning that some CS that was done was more project management, more implementation of projects rather than the traditional customer lifecycle management that you would normally see happening.
Therefore, there was really no consistency between regions around how do we do forecasting for the renewals? How do we flag customers that may be at risk of churning or are at some other risk? How do we make sure that renewals are happening on time?
And therefore we have solid renewal pipeline and the upgrades, upsells, basically growing our customer base. The existing one was also not centralized around one specific framework. So when I joined, it was a little bit all over the place, nothing customer success-specific, nothing put in place, just some general best practices.
So what I had to start looking to, to provide this visibility first for the management, but then of course, for the rest of the organization, for the rest of the company, so that everyone’s very clear what the role of customer success is exactly. That it’s not solely project management. It’s not glorified support.
And I’m sure within the guest conversations you’ve had on the podcast so far, you would have heard time and time again, customer success leaders, professionals saying, CS is revenue generating function. It’s not support. It’s not just whatever, you know, people might try to reduce it to.
So what I started with really was introducing a set of processes and playbooks around renewal management, accounts at risk. How do you flag accounts at risk and how do you manage that? Reporting relating to both the renewal forecasting, the accounts at risk and customer success qualified leads, which was, it still is a process that aims to flag from customer success managers, expansion signals, and then how to work clearly and in a very kind of tight hand in a glove manner with our sales team so that we can either qualify or disqualify these growth signals and basically help our customers grow, not just in ARR, but also in the different applications of the product that they have. So this was first playbooks, forecasting, churn, and CSQLs.
Clean Data Comes First
Irina (6:24 – 6:52)
I’m super curious, what did you need in order to be able to, that was the outcome, but you start from a goal, you describe the outcome, let me know what was the process in between. Where did you, what were the teams that you needed involved or the support from the organization that you needed in order to be able to deliver the outcome?
Bilyana (6:53 – 8:14)
The main need in order to back the building of all these processes was clear, accurate data. And like many customers, many organizations, we also had challenges back then because there was a big cleanup required to be done in terms of updating the records and consolidating them in a way that I can then use to pull reports, to present dashboards, to just have the data readily available rather than scattered around. So the help that I got from the organization was my C-level, specifically the chief customer officer, who is now a chief operating officer.
And she’s been a massive help, along with the finance team as well, finance operations, where we were able to see where the data I needed lives. So Salesforce, reporting, all of that had to be sorted out and built. And specifically for the CSQLs, we had to resort, and I’m very happy that we did that, to using a tool that at the time our sales guys were using mainly HubSpot.
So building out the HubSpot flow for CSQLs was what was super helpful. So we were working with the two in parallel, HubSpot and Salesforce.
Where the Customer 360 View Lives
Irina (8:15 – 8:22)
Okay, but now I assume that you only have one system, which is Salesforce. You migrated it from HubSpot, right? We have both.
Bilyana (8:22 – 8:46)
We have both because they’re being used for slightly different purposes as well. Yeah, not everyone, not each and every function rather in the companies using Salesforce. But what I need for customer success metrics, and again, just having a high level overview of the businesses globally, it’s in there.
HubSpot is being more leveraged by our marketing teams and account executives.
Irina (8:47 – 9:06)
Okay, so, okay, now I have to ask, you have HubSpot, you have Salesforce, and customer success lives in Salesforce. How do you have this 360 customer view?
Bilyana (9:06 – 9:37)
Yeah, it is indeed in Salesforce. When it comes to the ARR, you want to see the different books of businesses, etc. It really predominantly lives in Salesforce.
What we leverage as well, where you can see more details on not just the customer health, but the joint success plans, the account growth plans for the accounts. We leverage Confluence, Atlassian’s product. So it’s in there as well.
But I would say definitely Salesforce and Confluence are our two main things.
Defining Roles Across Three Regions
Irina (9:37 – 10:18)
Okay, okay. And you also have built the health scores and everything related to customer health in Salesforce. Correct.
Yes. Okay. Tell me more about the team and the way you shuffle things around, because I know that you are covering three regions and you have a team of four, if I’m not mistaken.
Who does what? How did you redefine the roles once you had this clear visibility over the data, over the processes? How do you blend it into the resources that you have available into the team?
Bilyana (10:19 – 12:05)
Yeah, we are indeed a small, but very impactful team across the region. That’s for sure. So when I started, there were different specialties of like you were saying, who does what?
Because for example, on the US side, the CS function there has a little bit more of project implementation involved. On the APAC side, some pre-sales, more customer success, it really was varying. So when I started in the first six months, my goal was, in addition or rather in parallel to sorting out the data, the reporting and seeing what we have to also set KPIs and objectives.
And of course that was all coming from and based on what the company’s goals were for the year so that I can coordinate OKRs for the team based on the company OKRs. But this was the first thing, because you basically cannot really scale chaos. You first need to sort everything out so that we’re clear who does what and when.
And even if each and every one of the CSMs did have extra specialty or maybe extra responsibility on different projects, still the core was what I set up to establish later on as the customer success frameworks. And the renewal management, the forecasting, what’s the expectations relative to flagging accounts at risk or working with the account executive in order to develop a certain growth signal. So all of that came, again, within those first six months.
And yeah, even though everyone has slightly different talents and strengths in different areas, now we know exactly what are the expectations that are applicable to everybody.
Moving the Team from Reactive to Revenue
Irina (12:06 – 12:54)
I want to remain on the team lens. And I know that taking CS from reactive to basically owning a number, owning the revenue is a big shift for any team. So I’m curious, how was the process of implementing this shift from generalists to basically owning the revenue, OKRs, making the team responsible for this commercial side of things.
What did you need to change? How did you roll it out into the team? How did you help them basically spot the expansions opportunity?
Bilyana (12:55 – 15:37)
Yeah, well, like any change, this one came with challenges and had to be navigated with a lot of clear communication from the very beginning. It was uncomfortable at first, but then the things that remained consistent are really, OK, let’s brainstorm together and let’s have a little coaching session between us, me and my amazing team. What is it that we need to, when we’re, let’s say, logging a CSQL, Customer Success Qualified Lead, what are the expansion signals that we are interpreting?
What is it that we are asking? And here, a very valuable skill that I see, it’s not new, it’s from the past few years for sure, but more and more success managers are learning to apply, asking the right questions and specific questions when you have your standing customer success check-ins with the champion on the client side. There are a set of questions that if you’re completely oblivious to, would not give you much insight into, are there any potential, not just risks, but could we get introduction to someone else in the company that we can help, either with a product or to have a custom solution or to just have a conversation about how we can be helpful, rather than really framing the conversation about any sales pitch, because ultimately, customer success are not there to sell in the way that account executives do. So coaching, practicing together on the type of questions that can be asked during those CSM check-ins, so that we can then see whether a CSQL is there or not.
That was one aspect of the coaching. The other aspect was during our customer success team meetings, but also the one-to-ones, reviewing the book of business in a very data-driven manner, where each and every CSM would say, this is the size of the portfolio that I own out of this ARR. I forecast that this would be the percentage of my renewals this quarter, or that’s how much ARR I have at risk.
Just framing a conversation around, oh, this is how we talk about customer success now, and purely really basing it on the data. Because before, anyone, maybe a customer success manager who is starting out just now, they’re not really used to having this kind of conversations and speaking with that vocabulary. So that was another aspect of the change, getting the lingo right, so that we each are accountable for how much exactly of ARR we are trying to save, to grow, or they’re just looking after.
Staying Lean and Knowing When to Scale
Irina (15:40 – 16:28)
Now, I want to understand, you are a small, and you mentioned this, being a small team, but super effective. You managed to remain lean. You didn’t grow the head count.
You made sure that you have the right people at the right time in the right roles. Tell me more about when and how do you decide to scale, and what needs to happen so you bring one person into the team or expand it? How do you do the team expansion, I would say?
Bilyana (16:29 – 17:53)
Oh, we very much wanted to expand, but financial situation and other things that had to be taken into account, time zone coverage and all that, we had to remain very, like you said, efficient with our already impactful team. So expansion hopefully will be happening very soon in the future. As it stands right now, this is the headcount we work with.
And again, based on utilizing all of the resources that we have, each and every one of my team members is someone who can look after additional things as well as needed. So as we continue to grow our customer base, that’s the clear go-ahead, of course, for us to grow the team as well. And I think it’s inevitable.
It shall happen. But as it is right now, we are able to fully cover our customers, and all of them are high-touch. So it’s very much of a hands-on role.
We don’t have scaled customer success as such. We don’t have one to many, many, many accounts per CSM. And yeah, with the headcount that we have, we are able to manage.
But the more and more customers who are past POC and who are going live with the product, the more that happens, the more headcount we would inevitably need.
How AI Saves the Team Time
Irina (17:55 – 18:06)
Does AI help you in any way stay efficient, focused, and does it save your team’s time?
Bilyana (18:07 – 19:27)
Oh my god, yes. Of course, it does. And this kind of brings me back to something I mentioned to you at the start of our chat, where we were talking about what exactly the efficiencies are of anyone using AI, right?
It doesn’t matter if it’s a CS professional out there. There are wonderful tools that are AI-powered that can help CRM-based tools, ERP-based tools, or like what Squirro is. We really go through structured and unstructured data so that each and every enterprise has traceable sources of its own internal data without the AI hallucinations.
So for us, inevitably, we use our own tool, of course. But then also, we leverage Claude; we leverage Salesforce. And as I mentioned, the time that we are seeing is saved really comes from the little operational CSM task updates, notes, etc.
All of that time is operational time that we’ve saved before implementing those tools. So for example, something we started leveraging really was Claude Enterprise. Before that, we did spend more time on keeping up with the book of business notes and all of that, whereas now that’s no longer the case, thankfully.
So yeah, very much AI-powered.
What Bilyana Looks for When Hiring
Irina (19:30 – 19:54)
One more question in regards to the team and to the skills that are super important, at least in your case, for the CS team to function. What do you prioritize in terms of skills? What’s more important?
What are you looking at when you do the recruitment and when you bring on board a new person?
Bilyana (19:56 – 22:18)
I would say, without oversimplifying it, but the ownership and to what extent the CSM is invested into really managing the relationship, meaning someone who, and all of our team members have this kind of a profile, someone who is really there to build the relationship and manage it rather than have async interactions with the customer, relying on, let’s say, automated email outreach and so on and so forth. Because for our enterprise-level clients, that just does not work because the product is complex.
The solutions we built out are very complex. And the level of thinking that someone needs to have on the CS side is a big-picture thinker, someone who can confidently map out, like we mentioned, what the return on investment is for these clients. Because I’ve noticed, especially with clients that are legacy clients, they have been with us as a provider for many, many years.
Back in the day, 10 years ago, they may not have had really a CSM practitioner who could put them on the spot and say, OK, let’s agree now and let’s define what will you continue to earn, maybe saving time, maybe saving X amount of millions per year, whatever it might be. Let’s put it down so that you know what your gains are. With customers who have been with us for a very long time, not all of them have had that thinking.
And now in the past year and a half and continuing, we are really trying to put that, let’s agree and let’s put into your joint success plan what is it you’re gaining. So the most important quality, really big-picture thinker, but a relationship owner, someone who can see the commercial outcome and tie it to the relationship itself. Because in customer support, in customer success, everyone, I think it’s just human psychology- everyone is interested in knowing: have you made things easier for them?
Is it clear? Is it easy? Have you helped them really?
So very much like this kind of a servant leadership of the relationship when the CSM is managing it, what have we done to help you? And here, here’s what you have achieved. That’s what our service or tool has helped you reach.
Customers Don’t Care About Your Processes
Irina (22:20 – 22:32)
You started out in support operations. Yeah, I did. And you run service teams.
And now you’ve built CS from the ground up in more than one company.
Bilyana (22:32 – 22:33)
Yeah, three times now.
Irina (22:34 – 22:41)
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 CS today?
Bilyana (22:42 – 23:27)
Yeah, I think it also touches just on what I mentioned, the customers, regardless if you’re from a CS perspective or customer support, no one really cares about your internal processes. Everyone wants to get to either the answer quickly or to the efficiency gain quickly. So I would say thinking time to value, but really thinking about how to make it easy, specific, and clear to the client that this is me helping you.
And this is the result of the help, let’s say from the service or the tool. So it really, that’s what stayed with me throughout the years. Customers don’t care about your processes.
They just want to see really how you have helped them.
Irina (23:29 – 23:36)
Bilyana, this was a really great conversation. Thank you for taking the time to speak with me today!
Bilyana (23:36 – 23:42)
Thank you so much. It was a pleasure. I love the questions.
And yeah, thank you for having me again.
Irina (23:43 – 23:49)
To everyone listening, thanks for tuning in. Until next time, stay curious, keep learning and mastering customer success.