No receipt, no rank
How proof works
Signing in shows who you are. A proof ties that same person to the company. Every story needs at least one, and a person reviews each story before it goes live. Numbers are self-reported: proof shows the team is real, not that the savings are.
Domain
You get a one-time token. Add it as a TXT record at _replacemrr.yourdomain, or publish it at https://yourdomain/.well-known/replacemrr.txt. Either one passes. Code looks for the token, so check again once the record is live.
Google Workspace
Sign in with a Google Workspace account on the company's domain and it passes straight away. The story then shows the company, not your name. Personal Gmail works for signing in, but proves nothing about a company.
Public repo
A public GitHub repo owned by you or by an organization you're a public member of. Sign in with GitHub so we can match it to you.
Backing up the numbers
Proof shows you're at the company. It doesn't show what you saved, so the numbers stay self-reported. The best way to back them up is a link to a public post where your team states them.
If a number looks off during review, we may ask to see a redacted invoice. Hide anything you'd rather not share. We look at it, delete it after review, and never publish it. We're working on stronger ways to back up the numbers.
After publishing
Six and twelve months after go-live, you can mark a story Running 6 mo or Running 12 mo, which ranks it higher. If you went back to the vendor, say so: the story moves to Reversals.
Changing the numbers on a published story sends it back through review.
Unclaimed stories
We list public "we replaced X" posts with a link to the source and an Unclaimed label. Nobody at the company has confirmed these, and they rank at half weight. Anyone who can prove they're at the company can claim one.
Corrections and removal
Every story has a report link. If a person upholds a report, the story comes down until it's fixed.