Move up in stakes.
Every build starts In the Lab. As it earns, it climbs: Micro, Low, Mid, High, Nosebleed. Like a player moving up, you show your numbers as you go.
The stakes
Monthly recurring revenue, or average monthly revenue if you don’t sell subscriptions. Folded a business? It goes to the muck with a post-mortem.
Proving it’s yours
Above Micro, you prove you own the site, the same way Google Search Console does it. Your build page gives you a token. Put it in one place:
- a
<meta name="r2f-verification">tag on your home page, - a file at
/.well-known/r2f-verification.txt, or - a DNS TXT record on
_r2f.yourdomain.com.
Press Check and it’s done in seconds. It’s one-time: once it passes, you can remove the token. Change your build’s site and you verify the new one. High Stakes and Nosebleed also get a quick look from the R2F staff.
Proving the revenue (optional)
Want your numbers to carry real weight? Verify them with Stripe. You create a read-only restricted key (Charges: Read, Subscriptions: Read), paste it on your build page, and we use it once to count MRR and 12 months of charges. We keep the totals, not the key. Delete it in Stripe as soon as it’s done. It’s the same way Indie Hackers and the revenue-dashboard tools verify founders. Verified revenue counts for 60 days; re-run it whenever you move up.
The read
We can’t audit your bank account, so we trust you on the revenue. What we can do is check everything around it. Every build gets a read from 0 to 100, with the work shown on its page:
80+ is a strong read, 60+ solid, 40+ developing, under 40 thin. Reads update every morning.