A few days ago, I came across a post on the r/CustomerSuccess subreddit that stopped me mid-scroll. Someone had just moved from Customer Support into a Junior CSM role and was asking a question I’ve heard in different forms dozens of times over the years: Is this normal?

But the detail in their situation was anything but ordinary. Within their first month, they were managing 5–10 regular clients, an enterprise account with a complex setup, and a co-authoring book project the client had proposed. No other CSMs. No project manager. No clear roadmap. And a manager transitioning into sales and handing over all CSM responsibilities. They were doing it all alone, still on their support-level salary, still in onboarding.

I read the whole post and thought: I know exactly how this person feels. And I also know that what they’re interpreting as a crisis might actually be the most important career moment they’ll ever have — they just can’t see it yet.

I decided to write this post because I suspect there are a lot more junior CSMs out there feeling the exact same way — overwhelmed, under-supported, and quietly questioning whether they made the right move. This one’s for all of you.

---

Let me be honest with you about something I wish someone had told me when I was sitting where you are right now — anxious every Monday morning, questioning every decision, wondering whether I had made a catastrophic career mistake.

You haven’t. Not even close.

But I understand why it feels that way. You moved from Customer Support into a Junior CSM role. You’re still in onboarding, still on the same salary. And somehow, within weeks, you’re leading client meetings, coordinating content teams, PR, and product, managing 5–10 regular clients and an enterprise account with a complex setup — including co-authoring a book with the client. Your manager is transitioning into sales and gradually handing everything over to you. There’s no project manager for the book. No other CSMs. No account manager. No clear roadmap. Just you, a Slack channel, and a growing list of responsibilities that would challenge someone with five years of experience.

And you’re asking: Is this normal?

Here’s my honest answer: No, it’s not typical. But it is something far more valuable than typical. And by the time you finish reading this, I hope you’ll understand exactly why.

First, Let’s Validate What You’re Feeling

Before we get into the opportunity, let’s be clear: your frustration is completely legitimate. The anxiety you feel on Sunday nights isn’t weakness. It’s the natural response of a capable, conscientious person who cares deeply about doing their job well — while being asked to operate without the structural support that most professionals take for granted.

Most junior CSM roles follow a predictable ramp: shadow a senior CSM, take on a handful of low-risk accounts, learn the internal tools and processes, and slowly increase your portfolio size over 6–12 months. You get a playbook. You get a manager who walks you through it. You get guardrails.

You got none of that. And you’re right to notice it.

What you’re describing — being the sole CSM, coordinating multiple internal teams without clear ownership, managing an enterprise client mid-onboarding with a complex creative project attached — is objectively closer to a mid-level CSM, an Implementation Manager, or in some organisations, a Customer Success Director. The fact that you’re doing it within your first month, without the title, the experience, or the compensation, is a lot to carry. Anyone who tells you otherwise has either never been in your shoes or has forgotten what it felt like.

So no, you’re not complaining. You’re being honest. And honesty is the first quality of a great CSM.

Now, Let’s Talk About What’s Actually Happening Here

Your company didn’t hire you to fill a seat. They hired you because someone — your manager, a founder, a hiring decision-maker — saw something in you that made them believe you could handle more than the job description suggested. That’s not me being motivational for the sake of it. That’s a rational interpretation of what’s happening.

Think about it from their perspective. They have an enterprise client. That client has proposed something genuinely unique — co-creating a book as part of a SaaS implementation program. That’s not a standard deliverable. That’s a creative, high-visibility, high-stakes initiative that requires someone who can think beyond a playbook, who can build relationships, manage ambiguity, and lead without a script. They gave that to you.

That’s not a mistake. That’s a bet. And they placed it on you.

Your manager is moving into sales — which means the CSM function is genuinely being built around you. You’re not inheriting someone else’s playbook. You are writing the first one. That is an extraordinarily rare position for anyone to be in, let alone someone in their first year of CS.

Why the Chaos Is the Curriculum

Here’s something they don’t put in any CSM job description: the most formative experiences in this career almost never come from structured environments. They come from moments exactly like the one you’re in right now — where there’s no roadmap, no one above you to defer to, and no choice but to figure it out.

I’ve spoken to hundreds of Customer Success professionals at every level — individual contributors, VP of CS, Chief Customer Officers — and when you ask them what shaped them most, they almost never cite the perfectly run onboarding program or the clearly documented process. They talk about the chaotic quarter when everything was on fire. The client relationship that nearly collapsed. The moment they had to stand in a room of senior stakeholders and say, “Here’s my plan,” when they weren’t sure it was right.

That’s where the real skill gets built. Not in the safety of structure — in the discomfort of figuring out what structure should look like.

You are currently learning things that most junior CSMs won’t encounter for two or three years:

• How to manage cross-functional teams without formal authority
• How to hold an enterprise relationship together when the internal structure is unclear
• How to lead a client initiative that has no established precedent
• How to communicate upward to senior colleagues when you’re the most junior person in the room
• How to create ownership and accountability in an ambiguous environment
• How to define requirements for complex projects without a PM or technical lead

These are senior CSM skills. And you’re developing them now.

The Book Project Is Not a Burden — It’s a Career-Defining Credential

Let’s talk specifically about the book, because I think this deserves its own section.

In ten years of Customer Success, I have never heard of a junior CSM being handed a co-creation project with an enterprise client in their first month. It doesn’t happen. Books, white papers, co-branded content initiatives — these typically sit with senior account managers, VP-level relationships, or dedicated partnership teams. You have been entrusted with something genuinely unusual.

When this project is done — and it will be done, because you’re going to see it through — you will have something almost no other CSM at your level has: a completed, real-world example of leading a complex, creative, enterprise client initiative from scratch. That’s not a bullet point on a resume. That’s a story you’ll tell in every interview for the rest of your career, and people will lean forward when you tell it.

The question isn’t whether this project is too much. The question is: what kind of structure can you build around it so it runs smoothly?

And that brings us to the most important shift in mindset I want you to make.

Stop Looking for the Playbook. Start Writing It.

You said your manager doesn’t give you a clear roadmap. You get answers when you ask specific questions, but no overarching structure. That’s frustrating — but it also tells you something important: the structure doesn’t exist yet. Which means you have the authority, and the opportunity, to create it.

This is one of the most valuable things a CSM can do for a growing company: build the operating system that didn’t exist before they arrived. If you can document how the enterprise client relationship works, define the internal coordination process for cross-team projects, create a project charter for the book initiative, and establish a cadence of communication that keeps stakeholders aligned — you will have created institutional value that outlasts your time in this role.

Here’s a practical framework to start with:

1. Build a One-Page Project Charter for the Book

Right now, nobody owns the book project. Nobody knows the milestones, the decision-makers, or the success criteria. Change that. Draft a single page that defines: what the book is, who is responsible for what (even if you have to assign ownership yourself), what the key milestones and dates are, and what “done” looks like. Share it with your manager. Ask them to approve it. Once it’s approved, you have your mandate.

2. Create a Weekly Stakeholder Update Template

You mentioned that when you post updates in Slack, people seem to expect you to tell them what to do. That dynamic — confusing as it is — is actually confirmation that you’ve already established yourself as the person who has the clearest view of what’s happening. Lean into it. Create a structured weekly update: what happened this week, what’s happening next week, what decisions are needed, and who needs to make them. Send it every Friday. Consistent, structured communication from you will gradually replace the chaos with clarity.

3. Schedule a “State of the Role” Conversation with Your Manager

Your manager is transitioning into sales and handing CSM responsibilities to you. That transition needs to be explicit, not gradual and assumed. Ask for a dedicated conversation — not about a specific client — about the shape of your role. What does full ownership look like? What decisions do you have authority to make alone? What do you escalate? Getting clarity on this isn’t a sign of weakness. It’s exactly what an experienced CSM would do.

4. Reframe Your Relationship with Senior Colleagues

You’re worried about annoying senior people with basic questions. Here’s a reframe: you are not asking basic questions. You are gathering the context you need to do your job effectively. That’s not a junior behaviour — it’s the behaviour of every skilled project manager and senior CSM you’ll ever meet. Ask fewer questions if you must, but make them precise. “I’m working on X, I’ve considered A and B, and I’m leaning toward B for this reason — does that align with how we typically handle this?” That’s not a basic question. That’s a professional seeking alignment. There’s a big difference.

On the Salary and the Title: Have the Conversation

You mentioned you’re still on the same salary as your support role, and you’re wondering why they didn’t hire someone more experienced. It’s a fair question — and one you deserve an honest answer to.

My view: the company made a calculated decision. They could hire a senior CSM at a much higher cost, or they could bet on someone with the right foundation — strong client-facing experience, company knowledge, and the right attitude — and grow them into the role. That bet costs less up front. The risk is on you, and so is the reward.

Give yourself 60 to 90 days of documented impact — client health metrics, the book project milestone, internal process improvements you’ve driven. Then go back to your manager with a specific, evidence-based conversation about compensation. Not a vague request for more money. A clear articulation: “Here is what my role actually encompasses. Here is what I’ve delivered. Here is where I believe my compensation should reflect that scope.” Companies that are growing fast respond to that kind of initiative. If they don’t, that tells you something equally important.

Is the Role Right for You? Here’s How to Know

You asked whether this role is even right for you. That’s the most honest question in your whole post, and it deserves a real answer rather than generic encouragement.

Customer Success, at its core, is about navigating complexity in service of a relationship. It requires you to hold ambiguity without panicking, coordinate people without authority, and make decisions with incomplete information — all while keeping the client’s experience at the centre of everything. If you read that description and it makes you feel excited even through the anxiety, you’re in the right field. If it makes you feel only dread, that’s worth sitting with honestly.

Based on everything you’ve written, my read is that you’re in the right field, in the wrong structure, at the right time to build the structure yourself. The anxiety you feel isn’t because the work doesn’t suit you. It’s because you care about doing it well and you don’t yet have the tools or the framework to feel in control. Those things are learnable. And you’re learning them faster than almost anyone else in your position would be.

What I Would Tell My Younger Self in This Exact Situation

Take a breath. Then take ownership — real, deliberate, documented ownership — of everything on your plate.

Don’t wait for someone to hand you a process. Build it, share it, and ask for feedback. Don’t wait for someone to give you authority over the book project. Draft the project charter, present it to your manager, and ask for sign-off. Don’t wait to feel ready to lead client meetings. You are already leading them. The confidence comes after the repetition, not before it.

Document everything you do. Every decision, every framework you create, every client update template you build. This is your playbook. In six months, when the company hires the next CSM, you will hand them a document that saves them months of confusion. That is an extraordinary thing to have built.

And on the days when the anxiety is loud — and there will be those days — remember this: you are not struggling because you’re not good enough. You are struggling because you are doing something genuinely hard, without the resources most people would expect to have. That’s not a reflection of your limitations. It’s a reflection of your courage in saying yes to something difficult and then showing up for it every day.

The Bottom Line

Is this level of ownership and coordination normal for a junior CSM? No. It’s not normal. It’s exceptional — and I mean that in the most literal sense. It is outside the ordinary. Most junior CSMs will spend their first year shadowing, learning, and slowly taking on more. You are being asked to build the function from the ground up, lead an enterprise relationship, and drive a genuinely novel client initiative — all at once, in month one.

That’s not a burden to escape. That’s a platform to rise from.

The CSMs who look back on their careers and say “that year changed everything” almost always point to a moment exactly like the one you’re in. Messy. Unclear. Way more responsibility than they felt ready for. And looking back, they wouldn’t trade it.

You asked for honest feedback. Here it is: stay. Build the structure that doesn’t exist yet. Deliver the book project. Document your playbook. Have the compensation conversation in 90 days. And let this chaotic, overwhelming, unreasonably demanding chapter be the foundation of a Customer Success career that most people only read about.

You’re not behind. You’re ahead — you just can’t see it yet.

---

This post was inspired by a real question posted on the r/CustomerSuccess subreddit. I came across it and felt strongly that there are many more junior CSMs out there feeling exactly the same way — isolated, overwhelmed, and unsure if they’re alone in this. You’re not. If this resonated with you, share it with someone who needs to read it, or drop your own experience in the comments below.