What to Protect, What to Delegate, and What to Let Go Of as a CS Leader

Are you a customer success leader? If so, I want you to open your calendar right now. Look at this week, look at what’s on it. Now, ask yourself honestly, how much of what’s on that calendar did you put there intentionally? How much of it reflects your priorities as a CS leader? The strategic work, the team development, the thinking time, the things that actually moved the needle, and how much of it just accumulated, meetings that got scheduled because someone needed you, recurring calls that nobody has canceled in 18 months, back-to-back-to-back blocks that leave no room to actually think. For most customer success leaders, the honest answer is that their calendar is a reflection of everyone else’s priorities, not theirs. And the result is a leader who is constantly busy, constantly responsive, and consistently running out of time for the work that actually matters. Your calendar is not just a scheduling tool.

It’s a strategic asset. And if you’re not designing it intentionally, someone else is designing it for you. That’s what this episode is about. So let’s get into it. Welcome to the CS RevSpeak podcast, where we talk about practical insights, strategies, and frameworks that will help customer success leaders who carry a revenue number, drive sustainable growth, maximize customer lifetime value, and crush their numbers. Let’s see what is actually happening here, because I think it’s worth understanding before we talk about how to fix it. Customer success leadership is one of the most cross-functional roles in a SaaS business. You’re connected to sales, to product, to support, to finance, to the executive team. Everyone has something they need from customer success, and because CS is fundamentally a relationship-driven function, there’s a cultural expectation, sometimes explicit, sometimes just absorbed, that a good CS leader is always available, always responsive, always there when someone needs something.

And so the calendar fills up. Customer escalations, cross-functional things, team check-ins, leadership meetings, one-on-ones that run long, and somewhat in the middle of all of that, the strategic work, the work that only you can do as a leader of this function, gets squeezed into the margins, early mornings, late evenings, the gaps between meetings that are too short to do anything meaningful in. Here’s what that actually costs. Not in terms of stress or sustainability, although those are real. In terms of outcomes, when a CS leader is perpetually reactive, the team feels it. Decisions take longer because the leader is never in a focused headspace to make them. Coaching gets rushed or skipped because there’s no protected time for it. Strategic initiatives stall because every time the leader sits down to think, something urgent pulls them back into execution mode. And the function stays stuck at a certain level of performance because the customer success leader never has the bandwidth to lead it to the next level.

A CS leader who designs their calendar intentionally is a fundamentally different kind of leader. They show up to one-on-ones prepared. They have time to think before they have to decide. They can work on the org instead of just in it. And that difference compounds over time into a team that performs at a higher level. So the starting point is this, your calendar is a leadership decision. Every block on it is either something you choose or something you’re allowed. And the first step in designing it well is taking ownership of that distinction. Before I share what I protected in my own calendar, when I was a VP of customer success, I want to acknowledge something. The right calendar structure is not one size fits all. What it looks like depends heavily on where you are in your journey as a CS leader, specifically whether you’re in early stage mode or scaling mode. Because two phases make very different demands on your time.

And what serves you well in one can actually hold you back in the other. In early stage, when you’re building a function, when a team is small, when processes are still being figured out, your calendar is going to be heavily weighted towards execution. You’re in the details, you’re in customer conversations, you’re building playbooks and sitting in on calls and sometimes doing the work alongside your CSMs, because that’s how you understand what needs to be built. That’s appropriate. And that’s right for that phase. But here’s where a lot of CS leaders get stuck. They never recalibrate, the org grows, the team expands, the complexity increases, and the leader is still spending their time the same way they did when the team was three people. Still in every escalation, still reviewing every renewal, still running every customer call that matters. And the team never develops because the leader never creates the space for them to lead.

Scaling mode requires a fundamentally different calendar orientation, less execution, more enablement, less doing, more developing, less being in the work and more designing the systems that make the work run without you. I remember when this shift happened for me. I had built a team that was strong, genuinely capable people who knew their accounts and cared deeply about their customers. And I realized one day that I was selling their work in a way that wasn’t serving them anymore. I was in account reviews, they could have led. I was in calls, they didn’t need me on. And by being there, I was signaling unintentionally that I didn’t fully trust them to handle it, that I needed to be involved for things to go well. That shift I made was to ask myself a different question every time something landed on my calendar. The question was not, can I add value here? The answer to the question is almost always yes.

You can almost always add something. The question was, is my presence here the best use of my time given everything else I’m responsible for? The question produced very different answers. And it started freeing space for the work that only I could do. Let’s get specific because I think the most useful thing I can give you in this episode is a clear picture of what belongs on your calendar as a protected, non-negotiable block. And why? First thing is to protect your strategic thinking time. And I want to be direct about this because I know how it sounds. Blocking time to think feels indulgent when your team needs things and your inbox is full and there are fires to put out. But here’s the reality. The most important decisions you make as a customer success leader, how to structure the team, how to position CS internally, how to respond to a pattern you’re seeing across your book, how to coach a leader on your team who is struggling.

None of those decisions get made well in the margins. They require uninterrupted, focused thinking time. And if you don’t protect it, it won’t exist. What this looks like in practice. I’m talking about two to three blocks per week, maybe 60 to 90 minutes each when you’re not in meetings, not responding to messages and not available. This is where you work on the org, strategy documents, coaching prep, thinking about a difficult decision, reviewing the health of the team’s portfolio with a fresh eye, whatever is most important that week for you to give focused attention to. Protect it like you would protect a customer commitment because it is one, a commitment to leading your function well. The second thing is to protect your one -on-ones with your direct reports. And I don’t just mean having them on a calendar. I mean having them consistently on time fully prepared and never canceling them.

Your one-on-ones are your primary leadership tool. They are where you coach, where you assess performance, where you build the kind of trust that makes a teamwork. When you cancel them, especially when things are busy, which is exactly when your team needs them most, you send a signal. You signal that their development is optional. That when things get hard, the first thing to go is the investment in them. Protect your one-on-ones. Reschedule before you cancel and you show up to them prepared. The third thing to protect is your customer time. Even as you scale and delegate more operational work to your team, you should never fully disconnect from customers. You don’t need to be in every account or every call, but you do need to stay connected somehow to the customer experience and keep it grounded in what your team is navigating. It sharpens your coaching. It gives you credibility in leadership conversations and it signals to your team that customer relationships matter to you.

What this looks like at the VP level is deliberately selective. I’m talking about a handful of strategic accounts, executive relationships, escalation reviews. You don’t have to have a full book. You need a curated presence. The fourth thing to protect is your own recovery time. I’m naming this explicitly because CS leaders are among the most prone to burning out quietly. The work is relentless. The demands are high and the culture of the function rewards responsiveness above almost everything else. You need wide space on your calendar, not as a luxury, as a leadership requirement. A leader who is depleted makes worse decisions, coaches less effectively and models an unsustainable pace for their team. Protect lunch, protect the end of your day, protect at least one morning a week where you’re nodding back-to-back meetings from the moment you open your laptop. Let’s talk about delegation. Delegation is where the calendar conversation gets really hard because most of the things that eat CS leaders’ time are things they genuinely can add value to.

The customer escalation, the renewal that’s at risk, the cross-functional thing that’s going sideways. Being in those things isn’t wrong. The question is whether being in those things is the best use of your time at this stage or whether it’s time to hand them to someone on your team. Here’s the framework I’m wanting to use. There are three categories of work. Work that only you can do. Strategic decisions, leadership team, representation, work design, executive relationships, coaching your direct reports. This is your highest leverage work. It should be the center of gravity of your calendar. There’s also work that your team can do with your input. Account strategy for complex situations, difficult customer conversations, cross-functional escalations that need a senior voice. This is where you’re a resource. You don’t have to be the owner. Your job here is to coach and advise and not to take over.

And then there’s work that your team can own entirely. Operational reporting, standard customer touch points, renewal execution for your healthy accounts, team rituals and meetings that don’t require your presence. This is what gets delegated fully, not partially. The challenge for most customer success leaders is the middle category. They stay too involved in work their team can handle with input because it’s hard to let go of things you’re good at and care about. And I understand that feeling, but staying in the middle category at the expense of your highest leverage work is one of the most common ways CS leaders limit both their own impact and their team’s development. Now here’s the piece most CS leaders miss entirely when they think about delegation. It’s not just about handing off operational work, it’s about delegating strategic initiatives to your CSMs and doing it deliberately. So think about a work that lives on your to-do list that never gets done.

The playbook that needs a full revamp, the onboarding process that’s been patched together and needs a complete rethink. The QBR template that’s outdated, the customer feedback loop that nobody has formalized. These are real strategic projects that matter for the health of your function. And they sit on your list quarter after quarter because you never have the bandwidth to give them the attention they deserve. Here’s the shift. Those projects don’t have to live on your list. They can live on a CSM’s list as a stretch assignment, a development opportunity and a genuine contribution to the function. Delegating a strategic initiative to a CSM does two things simultaneously. It gets the work done and it develops the person doing it. A CSM’s who leads a playbook revamp is building project management skills, cross-functional collaboration skills and the system’s thinking muscle they wouldn’t develop from account work alone.

A CSM who owns a process improvement initiative is learning how to think about the function, not just your book. These are the experiences that build future CS leaders and you create them by giving your team real work with real ownership, not just more accounts. What this requires from you is a very different kind of involvement. You’re not doing the work, but you’re also not fully absent. You’re setting the brief, what problem are we solving? What does success look like? What are the constraints? You’re checking in at key milestones. You’re available as a thinking partner when they get stuck and you’re reviewing the output and giving meaningful feedback. That’s the leader’s role in delegated initiatives. Non-ownership, sponsorship. One practical move I’d recommend at the start of each quarter, do a calendar audit. Go through every recurring meeting on your calendar and ask two questions.

Does this require my presence or could someone on my team lead it? And if I stopped attending this, what would actually happen? You’ll be surprised how many meetings survive that question. And once they don’t, those are your first delegation opportunities. Do the same thing with your strategic project list. For every initiative sitting on your plate, ask, is there someone on my team who could own this with the right brief and the right support? More often than not, the answer is yes. And handing it over with real ownership, not just task assignment is one of the highest leverage moves you can make as a scaling customer success leader. I wanna close this segment with something that took me longer than I’d like to admit to fully internalize. Letting go of things is not a sign that you don’t care. It’s a sign that you trust your team and a team that is trusted to lead, whether that’s an account, a process or a strategic project, develops faster, performs better and ultimately makes you more effective as a leader because they’re carrying more, which means you can focus on what only you can do.

Let’s bring this together. First, your calendar is a leadership decision. Every block on it is either something you chose or something you allowed. Taking ownership of that distinction is a starting point for designing a calendar that actually reflects your priorities. Second, what your calendar looks like depends on where you are. Early stage, you’re close to the work and that’s right. Scaling, the shift is toward enablement systems and developing your team. The leaders who get stuck are the ones who never recalibrate as the org grows. Third, protect the non-negotiables, strategic thinking time, one-on-ones with your direct reports, selective but deliberate customer presence and your own recovery time. These are not optional. They are the foundation of sustainable high-impact CS leadership. And fourth, delegate with intention. Know the difference between work only you can do, work your team can handle with your input and work your team can own entirely and do a quarterly calendar audit to make sure your time is actually distributed the way you intend it to be.

Here’s what I know from being in the VP of CS seat and from working with CS leaders who are navigating exactly this. Designing your calendar well is one of the highest leverage things you can do as a leader. Not because it may be more organized, but because it changes what you’re able to give your team, your customers and your function when you’re operating from a place of intention rather than reaction. If you’re in a season right now where you have the opportunity to be deliberate about how you build your role, or if you’re feeling the weight of a calendar that’s been designed by everyone else’s needs, that’s exactly the kind of conversation I have with CS leaders in my one-on-one executive advisory and coaching program. Well, look at how you’re spending your time, what’s actually driving your highest impact and how to build a rhythm that’s both sustainable and strategic. If that’s where you are, I’d love to work with you.

com forward slash coaching. Thanks for being here. I’ll see you in the next one. com. I specialize in working with customer success leaders who carry your revenue number, and I look forward to helping you confidently run a revenue -generating customer success team. Don’t forget to connect with us on LinkedIn and join our customer success leaders hub for more discussions, resources, and networking opportunities. You can access the links on the share notes. See you next episode.