Headless WP vs traditional managed: who actually needs it

Headless WP vs traditional managed: who actually needs it
Heard this week: headless keeps getting pitched as the upgrade when most sites should stay boring.
— Traditional managed WP is one stack, one host, one team that knows it
— Headless (Atlas, Faust, Vercel front-end + WP back-end) buys you a fast decoupled front end and a second infrastructure you now babysit
A source tells us the agencies that went headless 'for performance' mostly added cost and a new on-call burden they didn't price in. Word is it only pays off with a real app-like front end or a dev team that lives in React. For a content site, a tuned traditional stack still wins on total cost.
Unconfirmed, but one host is reportedly walking back its headless push after thin uptake.
Watch this: the headless hype cools as the bills come due.