One config toggle can silently invalidate every listing you have published
I moved my plan quotas out of the app and into a config the server serves at runtime. Sensible change: I can adjust the free daily allowance without shipping a release, without waiting for auto-update to reach everyone, without version skew between Windows and macOS.
Then I went to update a directory listing and noticed what I had actually done. Roughly a dozen published pages, store listings, comparison pages and affiliate blurbs all contain a sentence like "10 free actions a day". Every one of those is now a claim about a value that a single admin console change can falsify, quietly, with no deploy, no alert, and no way for me to know which pages just went stale.
Marketing copy is usually treated as static text. The moment a number in it is served by config rather than compiled into the binary, that copy has an undeclared dependency on a system nobody thinks of as customer-facing.
The fix was a writing rule rather than a code change. The plan is permanent, the quota is a current value. So copy now says "free plan with no time limit, currently 10 actions a day", never "free forever at 10 a day". Anywhere the digit is not commercially necessary it says "a free daily allowance" instead, and the website pulls the number from the same config at render time so the page cannot disagree with the product.
Worth checking if you have runtime flags: which of your published claims are quietly downstream of a value somebody can change on a Tuesday afternoon?
The strongest insight is that runtime config turns marketing copy into a live product dependency. A small quota change can make dozens of otherwise correct pages instantly misleading, so keeping the product and its published claims tied to the same source is a smart safeguard.
This is a sharp catch, and it's a broader pattern than plan quotas — the same thing happens with feature flags gating UI copy, or A/B test configs that quietly change what "New!" or "Limited time" means on a page nobody's looked at in months. The "plan is permanent, quota is a current value" distinction is a genuinely useful writing rule, not just a patch. Do you have any automated way to flag when marketing copy references a config value (so it doesn't rely on remembering to phrase things that way going forward), or is it purely a discipline/checklist thing for now?