Back to stories
product launchGenerated by an AI editor from the reporting and web sources listed on this page.

Rippling's AI bill spiraled to 40% of R&D payroll—so it shipped a tool to stop the bleed

After discovering its own engineers were burning millions on AI tokens, Rippling launched AI Spend Console to track per-employee AI costs and flag low-ROI usage.

Published Updated The total reporting and web sources attached to this story.How many attached sources came from wider web research rather than monitored news feeds.The AI editor’s assessment of how strongly the attached sources’ quality and agreement support this article.

What matters

  • Rippling launched AI Spend Console to track per-employee and per-team AI spending and correlate it with productivity.
  • Internally, Rippling was on track to spend 40% of its R&D headcount budget on AI tokens, with spend growing 80% month-over-month.
  • The tool can flag engineers with high AI spend whose peers frequently ask them to redo work in code reviews.
  • The product was born after a March executive meeting where CFO Adam Swiecicki surfaced the alarming spend trajectory.
  • Pricing and full availability details were not disclosed in the source.

What happened

Rippling, the HR and workforce-management software company, this week launched AI Spend Console, a product designed to help companies track, contain, and evaluate their AI spending at the level of individual employees, teams, and roles.

The tool was born from an internal crisis. According to Chief Product Officer Matt MacInnis, Rippling went all-in on AI tooling at the start of the year—what the company internally dubbed "tokenmaxxing"—only to discover that employees were burning through cash at an alarming rate. In a March executive meeting, CFO Adam Swiecicki presented a figure that stunned the leadership team: Rippling was on track to spend 40% of its R&D headcount budget on AI tokens. In other words, the company was spending nearly as much on tokens as it paid 40% of all employees in its engineering-heavy R&D unit—millions of dollars.

Worse, spending was growing at 80% month-over-month. Had that trend continued, the following year would have seen Rippling spend roughly 90% as much on AI tokens as on total R&D compensation.

AI Spend Console is Rippling's answer to that problem, now productized for customers. Among its notable capabilities, the tool can surface "which engineers have high AI spend whose peers frequently ask them to redo work in code reviews," according to the company's blog post—effectively flagging employees whose AI usage generates volume but not quality.

Why it matters

Rippling's experience is a cautionary tale for the broader industry. As companies race to embed AI into every workflow, few have visibility into what they are actually getting for their token spend. The Rippling data suggests that without governance, AI costs can scale to a significant fraction of payroll in a matter of months.

The launch also signals a shift in the AI conversation from adoption to accountability. AI Spend Console's attempt to correlate spending with output quality—not just quantity—addresses a growing concern that AI-generated work can create hidden costs in review cycles and rework. If a tool can distinguish between an engineer who uses AI to ship faster and one who uses it to generate code that peers repeatedly reject, it changes how organizations think about AI ROI.

For Rippling specifically, the move turns an embarrassing internal misstep into a commercial product, leveraging its own painful lesson as a proof point.

What to watch

  • Customer adoption: Whether enterprises will pay for AI spend tracking as a standalone concern or expect it bundled into broader workforce-management platforms.
  • Quality metrics: How effectively the tool can actually measure productivity versus "AI slop"—and whether the methodology holds up under scrutiny.
  • Competitive response: Whether other HR and IT-management vendors (Workday, Deel, etc.) build similar spend-governance features.
  • Pricing and availability: The source does not specify pricing or rollout details, so those remain unclear.

What to do next

Developers

Audit your own AI tool usage and token spend; identify which tools and workflows produce reviewable output versus rework.

Rippling's data shows high AI spend can correlate with low-quality output that peers reject in code reviews—developers should self-assess before management does.

Founders

Set a monthly AI spend budget per team before adoption scales, and instrument tracking from day one.

Rippling's spend grew 80% month-over-month and nearly reached 40% of R&D payroll; unchecked AI costs can become a material expense rapidly.

PMs

Evaluate whether AI Spend Console or similar tools fit your workforce-management stack, and define productivity metrics to pair with spend data.

Tracking spend without measuring output quality is insufficient; PMs need both dimensions to justify AI investments.

Investors

Ask portfolio companies for visibility into AI token spend as a percentage of payroll, and watch for governance tooling as an emerging category.

Rippling's experience demonstrates that AI costs can silently scale to a large fraction of compensation budgets, and spend-governance products are emerging to address this gap.

Operators

Establish internal policies for AI tool usage and review cycles, and flag teams where AI-generated work requires frequent rework.

Rippling's tool specifically identifies high-spend employees whose peers repeatedly ask for redo work, suggesting rework cost is a key hidden expense of AI adoption.

Testing notes

Caveats

  • The source does not provide details on how to access or trial AI Spend Console, pricing, or general availability timeline. Testing instructions cannot be constructed from available information.