Blog / Founders
Share your revenue publicly. Verified.
Building in public works when people trust the numbers. How to share revenue safely, what to show, and how to verify it straight from Stripe or another provider.
· 5 min read
Sharing revenue in public has become a growth channel of its own. Founders who post their numbers attract customers, investors and other builders who want to follow the story. It only works if people believe the numbers.
Why screenshots aren’t enough
A dashboard screenshot is easy to crop, edit or pick from the one good day. Readers know that, so the number carries less weight than it should. The fix is to show a figure that comes from the payment provider itself, updated on its own.
What to share
- Revenue over time, not a single peak: a trend tells the real story.
- What you shipped: a changelog makes the revenue make sense.
- What’s next: a roadmap gives people a reason to come back.
What not to share: anything about individual customers. Totals are enough, and they keep customer data where it belongs.
How to share it safely
Never hand out a full API key. Payment providers let you create restricted, read-only keys that can read data but can’t move money or change anything. Use one of those, store it somewhere encrypted, and revoke it if you stop sharing.
Setuvara’s Builder reads revenue daily from Stripe, RevenueCat, Dodo or Paddle with a read-only key kept encrypted in a vault, and shows it as verified next to your roadmap.
Put it where people meet you
A revenue page is most useful when people already have it: on the card you hand out at a meetup, in your bio, in your email signature. The same page should show who you are, what you’re building and how to talk to you.
See how founders do this with a digital business card that shows verified revenue.
A short checklist
- Create a restricted, read-only key.
- Show a trend, plus what you shipped and what’s next.
- Keep customer details out of it.
- Put the page where people meet you.
