When my third-largest customer told me their account manager felt more like a ticket queue than a partner, I realized the person I'd promoted eight months earlier was still thinking like a support rep. I hadn't hired for customer success. I'd just given a support title a new name and hoped the job would follow.
She was my best support rep: fast, accurate, customers loved her. When churn started creeping up and I needed someone dedicated to retention, promoting her felt obvious. She already knew the product, customers already trusted her, and it saved me a six-week external hiring cycle. It was the right call for the wrong reasons, and here's what that shortcut actually cost us.
Why the promotion looked obvious
The math was simple on paper. An external CS hire meant weeks of interviews, a ramp period to learn our product, and a stranger building trust with accounts from zero. Promoting from support meant zero product ramp and a head start on every relationship in her queue. Free speed is hard to say no to at an early-stage company watching every dollar of runway.
What I didn't do was separate two things I'd quietly bundled together: knowing the product, and knowing how to run a book of accounts. She had the first in abundance. The second is a different skill entirely, and nothing in eighteen months of support tickets had ever asked her to use it.
The skill gap nobody warned me about
Support is reactive by design: a ticket comes in, you solve it, you move to the next one. Customer success is proactive: you're supposed to notice the account going quiet before they file a ticket, initiate the hard conversation before the customer does, and make a judgment call about what to offer without checking with the founder first.
The clearest example was renewals. Sixty days out from a contract ending, an experienced CS person opens that conversation on their own initiative. She waited for the customer to bring it up, the same way she'd always waited for a ticket to arrive before acting. It wasn't a confidence problem. Nothing in her job for the previous year and a half had ever rewarded that kind of initiative, so she had no practiced instinct for it.
What I actually got right
To be fair to the decision, some parts worked exactly as hoped. She caught two at-risk accounts in her first month purely because she already knew what normal usage looked like for those customers, something an external hire wouldn't have picked up on for a full quarter. Product knowledge is real leverage, and it's the part of this trade that genuinely paid off.
What I got wrong
The mistakes were all mine, not hers. Three specifically:
- I didn't change how she was measured. For the first two months she was still evaluated on response time and ticket volume, the exact metrics that reward reactive behavior over the proactive behavior the new role needed.
- I didn't give her explicit commercial authority. She had to ask me before offering a discount, a contract extension, or even a goodwill credit, which meant every hard conversation had a built-in delay that a real CS hire wouldn't have.
- I never set a 90-day bar for the promotion itself. I evaluated an external CS candidate against a role definition before hiring them. I evaluated an internal promotion against nothing, because it felt like a reward rather than a hire.
The test I'd run before promoting anyone into this role again
Three questions, run before you write the promotion up, not after:
- Has this person ever pushed back on a customer, not just pleased one? Support roles rarely ask for this. If you can't point to an example, assume the instinct doesn't exist yet.
- Have they ever flagged an at-risk account without a ticket prompting them? This is the single best predictor of the proactive muscle the CS role actually runs on.
- Can they hold a commercial conversation without you in the room? If the honest answer is no, that's not disqualifying, but it means you're committing to weeks of paired coaching, not a title change and a raise.
If someone clears zero or one of these, promote them anyway if the economics still make sense, but budget real coaching time for the first 90 days instead of assuming the skills will transfer on their own. That's the part I skipped, and it's the part that actually costs you a renewal.
Frequently asked questions
Should I promote a support rep into my first customer success hire?
It can work well and is often cheaper and faster than an external hire, but only if you redefine the role, the incentives, and the authority that comes with it. Promoting the title without changing the job is where founders lose the trade.
What's the real difference between customer support and customer success skills?
Support is reactive: solve the ticket in front of you. Customer success is proactive: notice problems before a ticket exists, initiate renewal and expansion conversations, and make commercial judgment calls. They rarely overlap in day-to-day practice.
How do I know if my support rep is ready for a CS role?
Check whether they've ever pushed back on a customer, flagged an at-risk account unprompted, or handled a commercial conversation on their own. If none of these show up in their history, they can still grow into the role, but expect a real coaching period, not an instant transition.
Should I change compensation when I promote a support person into customer success?
Yes. If they're still measured on ticket volume or response time after the promotion, you're paying for the new title while incentivizing the old behavior.
What if the promoted rep has never handled renewals or commercial conversations before?
Pair them with you or another leader on the first two or three renewal conversations rather than handing over full ownership immediately. The gap closes faster with modeled practice than with a title change alone.
Promoting from support is still often the right call. It's faster, cheaper, and the trust head start is real. The mistake isn't the promotion itself. It's skipping the redefinition of the job, the incentives, and the authority that has to come with it.