Skip to content
FMField noteAugust 10, 2026

The case for boring technology

#platforms#evergreen

“Boring” isn’t an insult here — it’s a compliment with a spine. Boring technology means proven, widely used, and predictable: its failure modes are known, its fixes are documented, and thousands of people can work on it. For most organizations, boring is exactly what to buy.

What boring actually purchases

Rescuability. Nearly every orphaned site we take on is recoverable because it’s boring. A WordPress or Drupal site, PHP on a normal host, a plain database — any competent developer can walk in, find the light switch, and get to work. The clever stack — the custom framework, the trendy build system, the React front end that no longer compiles — is the one where the rescue starts with archaeology. When the person who chose the technology leaves, boring choices forgive; clever ones collect their debt.

A deep help pool. Common technology means competitive rates, answered questions, and no single irreplaceable person. Rare technology means whoever knows it names their price — when you can find them.

Known decay. Boring platforms publish their end-of-life schedules, so even neglect is predictable. New tools die unpredictably — abandoned by a maintainer, dropped by a vendor, out-fashioned in three years.

The test worth running on any pitch

When a proposal includes an exciting technology, ask: “If the person who built this is gone in three years, who fixes it, and what do they charge?” A good answer names the ordinary, findable people who could step in. A bad answer is some version of “it won’t come to that” — and our whole rescue practice exists because it comes to that all the time.

To be fair to clever: sometimes the unusual tool is the honest fit — a genuinely interactive product, a real multi-head content problem. The rule isn’t “never new.” It’s the canoe rule: proven hull, ordinary paddles, and save the experiments for gear that won’t sink the trip. Novelty is a cost. Spend it only where it buys something.