DevalueRadar

An OfferStack feed of announced loyalty devaluations, matched against the balances in your wallet, that tells you how many dollars each change costs you and the last day to move points before it hits.

Problem

Bilt announced on 2026-10-01 that its Hyatt transfer ratio drops from 1:1 to 4:3 on 2027-01-01. Chase made the same cut for Sapphire Preferred and Ink Business Preferred holders on 2026-10-01. Someone holding 200,000 Bilt points earmarked for Hyatt has 87 days before that balance buys 50,000 fewer Hyatt points. They only find out if they happened to read the right blog post that week. Even then they have to work out the dollar cost themselves, and decide whether moving early beats keeping the points flexible.

Target user

The Active Optimizer from OfferStack's STRATEGY.md: 5 to 15 cards, balances in several transferable currencies, reads Doctor of Credit and Frequent Miler. They already know devaluations happen. The problem is that announcements land months before the effective date, across a dozen programs, and nothing ties them to the user's own balances. AwardWallet tracks balances but not announced changes. Changelogs like WanderWise's list the changes but don't know what you hold.

MVP scope

• A program_changes table: program, change type (transfer ratio, award chart, category move), old value, new value, announced date, effective date, scope (e.g. "Sapphire Preferred only"), source URL. Rows enter through the existing LIF-049 admin draft-review queue, so a human approves every one.
• Value-at-risk for transfer-ratio cuts, computed from user_loyalty_balances: points lost = balance × (old ratio − new ratio), valued at the user's CPP for the destination program from /points. This is the transfer_ratio multiplier the valuation spec already lists as a known gap. It ships as a versioned spec change with test vectors, not as a new formula.
• A "move-by" date on each affected wallet program: the effective date minus a user-set buffer (default 7 days, because transfers to some partners are not instant).
• Award-chart and category changes appear as dated alerts on programs the user holds. MVP does not price them, because the loss depends on a redemption the app doesn't know about yet.
• A public /devaluations page listing upcoming changes with their sources. It's indexable, works without login, and doubles as SEO bait.
• Dashboard Next Best Actions gets one new action type: "Move N points to X before DATE (saves $Y)".

Monetization

Freemium, inside OfferStack's existing tiers. The public changelog stays free and pulls search traffic. The per-wallet dollar figure and the email reminder before the move-by date go behind Pro ($5–8/mo), which already promises expiring-offer alerts. No new SKU. This is a reason to upgrade, not a product of its own.

Why now

Two of the five big transferable currencies cut the same Hyatt ratio within one quarter. Chase's cut took effect on 2026-10-01 and Bilt's follows on 2027-01-01, so the rest of 2026 is a live window where acting early is worth real money. Hotel charts keep moving as well. Hyatt moved 112 hotels up a category on 2026-05-20, which pushed some of them out of range of the card's free-night certificate, and Wyndham added a 45,000-point top tier on 2026-09-30. On OfferStack's side, STRATEGY.md §4.4 names threshold alerts as the retention engine. The /points page (LIF-058) is built, and the CPP pipeline (LIF-047) is still in backlog. DevalueRadar gives that pipeline a second consumer, and it closes the "transfer ratios not modeled" gap in VALUATION_FORMULA_SPEC.md.

Risks & open questions

• Data quality is the whole product, and the sources already disagree. Milesopedia dates Wyndham's change to 2026-09-15. InsideFlyer quotes 2026-09-30 for the tier restructure and treats 09-15 as a separate annual adjustment. A wrong move-by date is worse than no date, so every row needs the program's own announcement attached before approval.
• Demand: Active Optimizers may already learn about these changes from Reddit within hours. The pitch only works if the dollar figure, not the news, is what they're missing. Test by posting one wallet-specific value-at-risk breakdown in r/churning before building alerts.
• Volume is low. WanderWise logged 26 changes as of 2026-09-20. That's enough to justify alerts, but too few to keep a free user coming back weekly.
• Build: scoped changes ("Preferred holders only, Reserve unaffected") mean the app has to know which card a balance came from. Today user_loyalty_balances doesn't record that. Solving it means a schema change or asking the user.
• Telling someone to move points early is close to advice. It needs the PRD's "informational only" framing, and should show the opposite case too: points moved to Hyatt early lose the option of going anywhere else.

Next step

Hand-enter the five or six live ratio and chart changes into a spreadsheet, run them against 10 real Active Optimizer wallets, and see whether anyone's dollar-at-risk number is large enough to make them act.

Sources

• https://upgradedpoints.com/news/bilt-hyatt-transfer-devaluation/ — Bilt Hyatt 1:1 to 4:3 on 2027-01-01, and Chase Preferred/Ink Preferred at 4:3 from 2026-10-01 (published 2026-10-01)
• https://www.insideflyer.com/posts/wyndham-rewards-adds-fourth-award-tier-2 — Wyndham four-tier chart from 2026-09-30, 45,000-point top tier
• https://milesopedia.com/en/news/programs/wyndham-rewards-devaluation/ — same Wyndham change dated 2026-09-15 (published 2026-09-15); evidence of conflicting effective dates
• https://awardwallet.com/blog/hyatt-pauses-expiration-category-changes-peak-pricing — Hyatt category changes effective 2026-05-20 (112 up, 24 down) and free-night certificate impact
• https://www.wanderwiseguide.com/points-devaluation-tracker — existing static devaluation changelog (26 changes as of 2026-09-20), with no balance personalization or alerts
• D:/AI_Agents/Projects/Mikes_AI_Lab/Repos/Private/Live_Apps/life-hacker/docs/STRATEGY.md — Active Optimizer persona, §4.4 threshold alerts, AwardWallet competitive gap
• D:/AI_Agents/Projects/Mikes_AI_Lab/Repos/Private/Live_Apps/life-hacker/docs/VALUATION_FORMULA_SPEC.md — "Transfer ratios not modeled (1:1 assumed)" known gap
• D:/AI_Agents/Projects/Mikes_AI_Lab/Repos/Private/Live_Apps/life-hacker/docs/EXECUTION_BACKLOG.md — LIF-047 (CPP pipeline, backlog), LIF-049 (admin review queue), LIF-058 (/points)
• D:/AI_Agents/Projects/Mikes_AI_Lab/Repos/Private/Live_Apps/life-hacker/docs/PROJECT_REQUIREMENTS.md — §6.2 user_loyalty_balances schema, §11 financial-advice risk