Back to AI
Rippling's CFO Shock: How Runaway Token Bills Spawned a New AI Cost-Control Product
AI

Rippling's CFO Shock: How Runaway Token Bills Spawned a New AI Cost-Control Product

13h ago0 views

Key takeaways

  • Rippling's AI token costs reached 40% of its R&D payroll budget before triggering an internal crackdown.
  • One employee was spending $50,000 per month on AI tokens; 10–15% of staff drove 60% of total spend.
  • After routing prompts to cheaper models, July token costs fell to 37% of April's bill at similar usage volume.

Rippling unveiled AI Spend Console this week, a product designed to help companies track, analyze, and contain their AI usage costs at the individual employee and team level. The launch comes directly out of a crisis the HR software company experienced earlier this year, when its own internal AI spending spiraled far beyond what leadership had anticipated. The tool links AI token expenditure to measurable work output — things like pull requests and lines of code — so managers can judge whether high spenders are actually delivering results or just generating expensive AI slop.

The origin story is striking. In March, Rippling CFO Adam Swiecicki presented figures to the executive team showing the company was on track to spend the equivalent of 40% of its R&D payroll on AI tokens alone. At the time, token spending was growing at roughly 80% month-over-month, which meant the company was hurtling toward a scenario where token costs could approach 90% of its entire engineering compensation budget within a year. Chief Product Officer Matt MacInnis described the room's reaction simply: 'We were incredulous.'

A subsequent internal audit revealed that 10 to 15% of employees were responsible for around 60% of total AI spend, with one engineer alone running up a $50,000 monthly tab. Rippling moved quickly, negotiating spending caps with tool providers including Cursor, OpenAI, and Anthropic. Executives also identified a structural problem: employees were defaulting to the newest and most expensive frontier models regardless of task complexity, and the inference providers had little motivation to help fix that. MacInnis said those vendors 'have every incentive for it to be a runaway expense.'

Rippling's solution included building its own AI gateway that routes prompts to the most cost-effective model suited for each task. MacInnis noted that cheaper models often perform comparably to frontier options — Rippling CEO Parker Conrad had recently flagged that Z.ai's GLM 5.2 delivered nearly identical coding performance to top-tier models at 85% lower cost. SpaceX's Grok also ranked highly in Rippling's internal benchmarks. The gateway is central to the AI Spend Console; companies using a third-party gateway can still access dashboards and reporting features, but the cost-governance controls require Rippling's own routing layer.

The results have been measurable. Rippling reduced its token spend from roughly 40% of headcount budget down to about 15%, without actually curtailing AI usage volume. In July, internal token consumption hit approximately 600 billion — near the March peak — yet July's total cost was only 37% of what April's bill had been. The company also identified high-performing AI users internally and designated them 'AI captains' to spread effective practices across teams. MacInnis acknowledged that extending smart AI usage beyond engineering remains a work in progress.

The bigger picture

Rippling's experience is quickly becoming a template story for the enterprise AI moment of 2025 and 2026. The company is not alone in having let token spending run loose in the name of productivity — many engineering-heavy firms made the same bet early in the year and are now dealing with the financial hangover. What's notable here is that Rippling turned its own pain into a product, which positions AI Spend Console as something that carries built-in credibility: the team dogfooded a genuine crisis before shipping anything to customers.

The competitive implications are real. Established AI observability and cost management players — along with cloud providers offering their own cost dashboards — now face a dedicated HR platform entering their space from a different direction. Rippling already sits inside companies' workforce data, so layering in AI productivity metrics gives it a vantage point that pure-play observability tools lack. The ability to connect 'this engineer spent $50,000 on tokens' with 'teammates keep rejecting their code reviews' is a specific and pointed claim that rivals will need to match.

The broader signal here is about model pluralism. Rippling's internal decision to route prompts to cheaper models like GLM 5.2 for appropriate tasks — rather than defaulting to Anthropic or OpenAI's flagship offerings — reflects a maturation happening across the industry. Inference providers who built business models around companies defaulting to their priciest models should expect enterprises to get much more deliberate about routing strategy in the months ahead. Any AI gateway or spend-management product that launches now needs to make a strong case against what Rippling is offering with this release.

LagPing's take

We're covering this story because the AI spending crisis Rippling describes isn't a quirky startup anecdote — it's something happening quietly at dozens of companies right now, and very few of them are talking openly about it. The fact that a CFO walked into a meeting with a number that shocked an entire executive team, and that the company's response was to build a product out of it, tells us something real about where enterprise AI adoption actually stands. We think our readers — many of whom work in or around tech companies wrestling with these same budget pressures — will find Rippling's specific numbers more useful than the usual vague productivity claims. The detail about one engineer spending $50,000 a month on tokens is the kind of concrete data point that makes an abstract problem suddenly very tangible. And the model-routing angle matters too: as cheaper models from Chinese AI labs enter serious consideration for enterprise coding tasks, the 'just use the best frontier model' default is eroding fast. This is a story about money, accountability, and what AI ROI actually looks like when someone is forced to measure it.

Shop AI & tech on Amazon

As an Amazon Associate, LagPing earns from qualifying purchases. Product links are affiliate links.

You might also like