source avatarBull Theory

Share

BREAKING: A fintech employee just burned $80,000 in AI tokens in one week, building a meme game. Slash, a $1.4 billion fintech startup, had told employees to use AI coding more last week. Nicolas Brillante, the company's head of strategic verticals, took that seriously and spent a full day using Claude to build a playable shooter game called "Brainrot Shooter," featuring meme characters like Skibidi Toilet and Tung Tung Tung Sahur. His token spend hit $81,267 within that week. Brillante called it a genuine accident, saying he underestimated how fast AI usage adds up once you're loading a full codebase context repeatedly during active development. Slash posted about the incident on X, joking that employees should play the game so the company can write it off as a marketing expense. The company is now reviewing its AI coding policy. And After the media coverage, Nick's game appears to have actually found product market fit. In the first 48 hours, it pulled in 6,912 players, 8,986 hours played, a 1.3 hour average session per player, and 437 peak concurrent players, along with 3 inbound ad inquiries. Finance has reportedly moved the project from an expense incident to a strategic initiative. Slash isn't the only one learning this the hard way. Uber burned through a full year's AI budget in just 4 months earlier this year, before adding spending caps of its own.

No.0 picture
No.1 picture
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.