this post was submitted on 29 Sep 2024
170 points (100.0% liked)
TechTakes
1427 readers
114 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay what the fuck is a "VP of customer success" though, that's a title so made up money laundering has to be involved, no?
"Customer success" has been creeping into biztalk lately. According to Ed Zitron it refers to that subspecies of salescritter that works with SaaS ~~victims~~customers to ensure they keep expanding their buying.
Basically, yeah. At my last job working in vendor support the "customer success" team was entirely sales-focused. Support (as in "my product isn't working as expected please help") was under a different department that would sometimes get badgered by the customer success guys if it seemed like a case was making it harder to upsell, or if the customer's problem was that they wanted to do something their current purchase didn't cover.
The industry called it “field engineering” previously, and “customer support” prior to that; renames happened every time the execs heard how this portion of their business is only a cost center and can easily be done by chat bots (to which the customer success people would say, good luck with that).
It's like how "marketing" became "UX research/design"
Marketing has not become UX research/design, you can't possibly know what UX design is and say that.
Ok, you’ve convinced me
Usually it's the part of the org that is directly interacting with big, corporate customers. Those customers can and often do directly shape how a product works. It's like a sales team, but focused on existing customers with big contracts (that might be expanded), rather than acquiring new customers.
But admittedly, this has just been my experience. I'm sure it's probably not universally true.
in a startup model where product directly implements function requests from clients, it'd be the head of deciding which functions, sprints, priorities etc.
And/or ensuring that clients are handled well enough so they're not at risk of churn at the q3/q4 turnaround.