The product shipped three versions. The homepage did not.
Somebody set up the marketing site before the first round. It runs on a stack one engineer understands, and every copy change is a pull request behind six roadmap items. So the pricing page still describes a tier you retired, and the homepage describes the product you launched with rather than the one you sell.
first full draft back
what a change costs you
engineering tickets
Why it is always the oldest thing you own
A marketing site competes for engineering time against the product, and it loses every sprint, correctly. The result is predictable: the site is accurate on the day it launches and drifts from that morning onward. Nobody decides to let it go stale. It goes stale because the cost of a one-line change is a ticket, a review and a deploy, and nobody spends that on a paragraph.
What the drift costs
A pricing page describing a retired tier produces support tickets and lost trials in the same week. A homepage describing an old version makes a buyer who already heard about you from someone else wonder whether they have the right company. The compounding cost is search: pages that never change stop being crawled often, and the competitor publishing monthly takes the position.
How askotter handles it
askotter builds the marketing site and hosts it on your domain, separate from your application, so nothing here touches your product or your deploy pipeline. Changes go in as a plain message. A draft and a preview link come back showing the finished page, a person on askotter's side reviews it, and it publishes when you reply yes. Rollback stays available afterwards and every change is logged with who asked and who approved.
Real-time detection in action.
Ready to fix this?
The free audit shows what on your site is out of date or costing you work.