Published pricing detections
Pricing-monitoring pages should show dated public detections, not only narrative claims about monitoring. These examples keep the proof boundary visible inside the workflow.
Fresh public proof is limited for this path right now. Open methodology or the ledger for the full audit trail.
Published example
Detection #004A homepage yield update changed the visible pricing anchor
Brex moved the headline cash-growth claim from 3.68% to 3.69% on the homepage, changing the number buyers compare first.
BrexHomepage yield claimPricing strategy shiftMedium-High
Detected
Mar 17, 2026, 18:15 UTC
Before
Spend, and grow your cash with up to 3.68% from day one.
After
Spend, and grow your cash with up to 3.69% from day one.
Why it matters
Small pricing or yield changes on a homepage can reshape comparison math long before a sales rep mentions them.
Recommended action
Review your own pricing and value-claim hierarchy before a visible yield comparison starts anchoring buyer conversations.
Published example
Detection #002Pricing language corroborated the repositioning move
Mercury restructured pricing-tier language to separate startup-tier and growth-tier messaging after the homepage buyer shift was already visible.
MercuryPricing page tiersPricing strategy shiftMedium-High
Detected
Mar 15, 2026, 11:08 UTC
Before
Pricing and packaging language emphasized a narrower startup-oriented framing.
After
Tier language was restructured to separate startup-tier and growth-tier messaging.
Why it matters
This is the kind of pricing movement that matters before renewal, packaging, and displacement talk tracks get tested in live deals.
Recommended action
Update your renewal and displacement talk tracks now. A pricing reframing is the earliest moment to prepare for changed objection patterns in live deals.
Public pricing proof is stronger when the buyer can inspect the before/after movement, classification, confidence, and recommended action without leaving the workflow.
For the higher-level proof standard and operating boundary, review the methodology page.