I built a Stripe analytics tool for SaaS founders. Remetry is live.
Hey IH - first post here, first product I've shipped. Would love your eyes on this.
The problem I kept hearing
A few months ago I was talking to a SaaS founder about how his team tracks revenue. Their setup: Stripe → Google Sheets → Slack, updated manually. The part he hated most wasn't pulling the numbers — it was writing the commentary. Every week, someone had to look at the sheet and type out "MRR is up 4%, mostly from upgrades, churn ticked up slightly in the Pro tier" , in plain English, for people who don't want to stare at a dashboard.
Around the same time I ran into a builder doing something adjacent — mirroring Stripe data into Notion for MRR tracking. He mentioned a detail that stuck with me: if you calculate MRR from invoices instead of active subscriptions, your numbers quietly drift wrong over time. Nobody tells you that until you've shipped it.
Two different people, same underlying complaint: Stripe has all the data, but turning it into something you'd actually send to a co-founder or investor is still manual work.
What I built
Remetry connects to your Stripe account (OAuth or a restricted API key, your choice) and turns raw Stripe data into:
- Clear MRR, churn, refund, and plan-performance reports
- AI-generated plain-English summaries of what changed and why it matters
- Downloadable PDF reports
- Scheduled email delivery — pick your frequency, local time, and timezone, and it just shows up in your inbox
The pitch, in one line: instead of manual spreadsheets or digging through the Stripe dashboard, Remetry turns your revenue data into a report you'd actually forward to someone.
Stack, for the curious
Next.js (App Router) + Supabase (Postgres/Auth/RLS) + Stripe Connect OAuth + Groq for the AI summaries + Resend for email + react-pdf for the PDFs + Vercel + cron-job.org for scheduling. All free tier for now — I'll upgrade once there's revenue to justify it.
Where it's at right now
It's live at https://remetry.app. No billing on my end yet (that's next), so right now it's free to connect and try. I'm not looking for a launch-day spike — I'm looking for a handful of SaaS founders willing to connect their real Stripe account and tell me honestly whether the reports are actually useful, or just another dashboard nobody opens.
If you're running a SaaS on Stripe and currently doing any version of "manually check MRR and explain it to someone" — I'd genuinely value you trying it and telling me what's wrong with it.
Happy to answer anything about the build or the product itself.
The report is useful, but the handoff is probably the real test. I'd ask early users to record a one-minute voice note explaining the metric change, then compare it with the report they'd normally send. I built DictaFlow because typing that context takes a surprising amount of founder time. If the report gives them a clean first draft without losing the judgment behind it, that's more compelling than another dashboard.
That's a really good test, actually — I like the idea of comparing the report against what they'd naturally say out loud. My guess is the AI summary is decent at the "what changed" part but probably still misses some of the judgment/context a founder would add themselves (like "MRR dipped but that's because we lost one big annual customer, not a trend"). Might actually try your voice-note comparison with a few early users to see how big that gap really is. Appreciate the framing, hadn't thought about testing it that way.
Stripe analytics is a crowded space, but giving users the OAuth vs. restricted-API-key choice is a nice trust signal; most tools just ask for full access. I'm curious how you're handling MRR calculations around plan changes and proration, since that's usually where these tools quietly get the numbers wrong. Did you build your own reconciliation logic or lean on Stripe's own reporting APIs as the source of truth?
Yeah, this was one of the trickier parts. We built our own reconciliation rather than leaning on Stripe's reporting APIs — those are solid for retrospective reports but not real-time enough for a live dashboard. Every webhook event re-fetches the full subscription object from Stripe, and we diff it against what we had stored to catch plan changes, seat changes, discounts, etc. Each of those becomes an MRR delta classified as expansion/contraction.
One deliberate call: we don't try to reconstruct mid-period prorations. That's where a lot of tools quietly start guessing. We use the normalized monthly rate and record the change when the webhook fires — feels more honest than a precise-looking number that's actually a guess.
Plan changes and proration are exactly where a reporting layer needs more than a one-time export. We built SyncStaq around keeping Stripe billing data available in Google Sheets so teams can review the numbers alongside formulas, labels, and notes. Different end point than a narrative report, but maybe there's a partnership opportunity here.
Stripe's dashboard is fine until you want to ask a question it did not anticipate, which is most of them. Are you reading the API live or syncing into your own store? That choice usually decides how far you can take the product later.
Both, honestly. Every webhook triggers a live call to Stripe to get the current state of the object, then that gets synced into our own Postgres store. Dashboard reads hit the local store so it's fast, but it's never stale since webhooks keep it current.
Main reason for going this route: it lets us answer questions Stripe's own dashboard doesn't — MRR trends by plan, churn attribution, refund-to-plan linking, that kinda thing — without giving up accuracy on current state. Full history gets backfilled on connect so it's not an empty dashboard on day one either.
Super clean stack—using Groq for fast, lightweight summaries is a great call instead of dragging in heavy LLMs. Also, offering restricted API keys alongside OAuth is really smart; founders are always super cautious about granting third-party apps access to their live Stripe data.
Yeah, exactly. Founders can connect their Stripe account whichever way works best for them. Pasting an API key is a bit more manual, cuz with restricted API keys, they also need to configure the webhook secret to make sure Remetry can track live events properly.
The strongest part is that Remetry isn't really selling another Stripe dashboard. It's turning revenue data into an explanation someone can actually forward. The key question is whether founders trust the AI-generated “why” enough to use it in investor or team reporting.
Yeah, that's the real bar it has to clear. Right now the summary always sits next to the actual numbers/chart, not instead of them, so it's more "here's what changed" than "trust me blindly." Long term I think the way you earn that trust is the summary being right often enough, consistently, that people stop double checking it. Not there yet, but ofc that's the direction.
That makes sense. I’d be interested to hear how you think about that trust problem as usage develops. Happy to continue over email if useful — what’s the best email to reach you on?
Yeah, sure. My email is [email protected] . I’d be happy to chat more about it. I’m still pretty early with Remetry, so I’m figuring out that trust piece as real users start using it.
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.
Congrats on shipping! How are you planning to get the first 10 active users? I found that commenting on peers' posts (like this one) and building a warm list before launch day moved the needle more than any launch post. Rooting for Remetry.
Thanks! That's actually where most of my effort is going right now. I'm trying to find founders who already have some kind of manual Stripe reporting workflow and start conversations from there. Curious what worked best for you when you were getting your first 10 users?
For my first 10 users, the only thing that worked was commenting on peers' posts — not launching, not ads, not cold email.
I found 20-30 founders building in public on IH and Twitter (50-500 followers range, not the big accounts), left genuine comments on their Day X updates, and 3-4 of them eventually clicked through my profile to try the tool.
The second channel was Quora answers — no links in the text, just detailed replies to thumbnail-related questions. My profile does the rest.
What didn't work: posting "look at my product" threads, commenting under top accounts (@naval, @dhh), and any paid channel.
Hope that helps — rooting for Remetry!
Yup, Thanks! I will also be doing it. Spending my most of the time on reddit, X, here and other such platforms and building a kind of warm network. Hope I will get some early users for it. Let's go🔥
Thanks for the reply! Love the warm network approach — that's exactly what moved the needle for me too.
Quick ask: I'm launching ThumbRank on Product Hunt tomorrow (Tuesday, Aug 25 at 10 AM Kyiv / midnight PT). If you have a minute in the morning, would mean a lot if you could check it out and drop feedback. No pressure at all — just thought you'd want to see it since you're in the same boat.
Here's the link: https://www.producthunt.com/products/thumbrank
Happy to return the favor when Remetry launches. Let's keep building 🔥
Yeah sure, why not. Let's just support each other.