Bait and Switch
AKA: Feature Hostage · The Moved Goalpost · Retroactive Paywalling
Bureau Classification
What It Does
Bait and Switch in software and digital products works in a predictable cycle: attract users with a generous free tier or a compelling set of features; build dependency through integration, habit, and data lock-in; then progressively restrict, paywall, or remove the features that drove adoption. The "bait" is the original product. The "switch" is the product those users now have, which is worse in measurable ways, more expensive, and harder to leave because the cost of migration increases proportionally to how deeply the product was integrated into users' workflows. Classic execution: Twitter's API was free and open, enabling a rich ecosystem of third-party apps, then became prohibitively expensive, eliminating most of that ecosystem. The users who built on the free API were the bait; the API pricing revision was the switch.
Why It Works
The pattern exploits switching costs, which are real and substantial in software products. A team that has integrated a tool into its workflow, trained its members, stored years of data in a proprietary format, and built automations around its API does not casually migrate when the pricing changes. The cost of switching — in time, money, data loss, and productivity disruption — must exceed the cost of accepting the new terms for the user to leave. Companies calculate this switching cost carefully and calibrate their price increases to stay just below it. Users who recognize the game are trapped by exactly the investment that the original product encouraged them to make.
How To Spot It
Watch for "free forever" promises, "no credit card required" launch offers, and "unlimited" tier marketing from companies that have recently raised venture funding or been acquired. These are the preconditions for a Bait and Switch cycle. Read the terms of service for data export provisions — if your data cannot be fully exported in a standard format, the switching cost has been partially locked in for you. Any product that controls access to your own data is structurally positioned for a Bait and Switch.
Documented Incidents
Twitter/X: free API enabling a developer ecosystem, then $100/month tiers eliminating most third-party apps
Netflix: pioneered password sharing informally, built a culture around it, then retroactively changed policy and added charges
Mailchimp: free tier for small lists that built the brand, progressively reduced and restricted over multiple years
Heroku: free tier that built the developer community, eliminated entirely in 2022 with minimal migration support
Google Reader: built an RSS reader ecosystem, audience and dependency, then shut down the product with 3 months' notice
Body Count
Cory Doctorow's "enshittification" framework captures the structural dynamic: every platform goes through the cycle of being good to users (to acquire them), then good to business customers (to make money), then extractive from both (to satisfy investors). The Bait and Switch is the tactical implementation of this structural dynamic. The bodycount is every user, developer, and company that built infrastructure on a platform that subsequently changed the terms of their access.
Legal Status
Bait and Switch is illegal in advertising law when applied to physical goods — advertising a product at a price, then claiming it's unavailable and steering customers to a more expensive alternative. The digital version lives in a grey zone: changing features of a service is generally covered by terms of service provisions about the right to modify the product. Consumer protection frameworks in the EU and UK have begun scrutinizing retroactive feature restrictions, but enforcement against tech product changes specifically is nascent.
Bureau Verdict
"Bait and Switch is a war crime because it is executed at scale, with full knowledge, after deliberate investment in user dependency. The Bureau observes that "we can change the terms at any time" is a clause written by lawyers who understand that it will be used, not as a protective provision for genuinely unforeseeable changes, but as the enabling mechanism for a planned extraction that was designed when the product was free. The switch was always the plan. The bait was the proof."
— Bureau of Non-Consensual Cookie Bandits
Frequently Asked Questions
Companies Caught Using This Pattern
Full audits available in the Privacy Policy Hall of Shame.