Uber Just Cut Its People Team. CS Could Be Next.
Uber just cut 23% of its People and Places division.
HR, recruitment, workplace, culture. The company ruled out AI as the cause.
The internal memo said the teams had grown “too far from the businesses and partners they support.”
Read that again.
A function that sits far from revenue, and cannot show how close, becomes the cost line. Most CS teams cannot show how close.
And the cost line is the first thing a budget review looks to trim.
So here is the question that decides how that review goes for you.
How much revenue does your team protect this quarter?
Not roughly. The number.
Why the numbers you have do not survive
Ask most CS leaders that question and the answer comes back as CSAT, NPS, or a health score that turns green and red for reasons the rest of the company does not fully trust.
None of those is a number a finance team accepts.
They are not denominated in dollars. They are not tied to renewal dates. They cannot be checked against the contract book.
A CFO discards them on the first follow-up question, and the honest answer underneath, for most teams, is that the revenue figure does not exist.
That gap is what gets a function reclassified as overhead.
When the only number anyone can see is your cost, your cost is what the conversation is about.
The number that survives, and the trap inside it
There is one figure that holds up in a finance review.
The revenue your team is actively protecting, expressed in dollars, tied to the renewals it maps to.
Building it is harder than it sounds, and most attempts fail in a specific way.
The leader sums the ARR under management and walks in with “my team protects forty million dollars.”
The CFO asks one question. “All of it would have churned without you?” The number collapses, and so does the credibility behind it.
The real number is smaller, defensible, and survives the second and third question.
The method is what separates the two.
You have seen what happens to the leader who walks in with the wrong number.
Below is how to walk in with the right one.
A single protected-revenue figure in dollars, mapped to real renewal dates, with a defensible range, and an answer ready for every question a CFO will throw at it.
The budget review stops being the meeting where you defend your headcount. It becomes the meeting where you state a number and the room moves on.
The full method is below
Free editions of The CS Café give you the diagnosis. The pattern, the problem, and the language to name it in your own org.
Paid editions give you the execution.
Today, that is the Revenue-at-Risk Scorecard and the full method behind it.
Across the archive, it is renewal plans that close early, QBRs that end with decisions, and escalations that stop bleeding, each with the templates and tools that make it repeatable.
Two ways to get today’s workbook
Upgrade to The CS Café paid subscription
The Revenue-at-Risk Scorecard is included with your paid subscription, along with every workbook in the archive and every new operating system I publish. You also get direct email review on your renewal plans and exec updates before they reach leadership. Upgrade →
Buy the workbook standalone. Single download. No subscription. $49. Get the workbook →
If you plan to build more than one operating system this year, the subscription pays for itself in the first month.
Leading a CS team? The CS Café offers group subscriptions for teams of 3 or more at 20% off. One invoice, one list to manage, add or remove team members any time. Get the team plan.