All case studies

Where reduction worked

Basecamp

Says no to most feature requests

A small team runs a product used by millions by refusing features rather than scheduling them, and by keeping what it operates small enough to hold.

Removed: most feature requests — refused rather than scheduled.

Outcome: a small team maintains a product serving millions, because the codebase and the infrastructure stay lean.

Basecamp deliberately limits features and says no to most requests. Their small team maintains a product serving millions because they keep the codebase and infrastructure lean.

The company’s own public commitment is to support a product until the last customer turns off the lights, and to keep applying security updates to products in a legacy phase. That is a promise you can only keep if the thing stays small enough to keep running: every feature you add is a maintenance obligation with no end date.

Source: 37signals, Until the End of the Internet (undated; retrieved 24 October 2026)