The Sunk-Cost Bait & Switch: Overselling Capacity and Punishing Existing Developers

Like many others here, I chose to build around the Gemini ecosystem. The initial performance and quotas were highly accommodating. But it has become painfully obvious that the platform is severely oversold, and the current management strategy is actively hostile to existing developers.

Instead of transparently managing capacity, there seems to be a clear pattern of favoring new user acquisition while quietly throttling the accounts of those who have already integrated the API. It functions as a textbook exploitation of the sunk-cost fallacy: offer workable limits so we invest the hours writing code.

Once that foundational work is done, the rug is pulled. The assumption seems to be that we’ve invested too much time and resources into the integration to rip out the backend and migrate to a competitor. Even as a paying subscriber on the $20/month AI Pro tier, the service feels degraded. We are essentially being penalized for utilizing the tools we were encouraged to adopt, all so the infrastructure can absorb the next wave of fresh signups.

If the compute capacity isn’t there, we need transparency—not a bait-and-switch that leverages our development time to lock us into a deteriorating service.

3 Likes