CorviDet
Stripe Metrics for indie hackers
I've been running Corvidet , a Stripe revenue intelligence SaaS, and in the process I've talked to a lot of bootstrapped founders about their metrics.
Almost every one had the same problem: they didn't actually know their real numbers. Not because they were lazy. Because the tools are either too expensive, too complex, or overkill for where they are right now.
Baremetrics is $49/month. ChartMogul is $99/month. For a founder doing $1K–$5K MRR, that's a significant chunk of margin going to a dashboard.
So I built one in Excel.
It's called Founder Dashboard PRO. Here's what it calculates automatically from a Stripe CSV:
→ MRR (properly prorated — annual subs ÷ 12)
→ ARR
→ NRR and GRR
→ Cohort retention matrix (M1 through M12)
→ Churn analysis (logo + revenue)
→ Revenue segmentation by plan and country
→ SaaS Health Score (0–100 across 5 dimensions)
→ Bear/Base/Bull scenario planner
→ Runway calculator
→ Industry benchmark comparison
You paste the CSV, set your month in one cell, and all 23 sheets update.
Two tiers:
→ STARTER — $19 (19 sheets, core metrics)
→ PRO — $29 (23 sheets + scenario planning, runway, benchmarks, future updates)
Both live on Lemon Squeezy and Gumroad:
https://yazanbenedit.gumroad.com/l/StripeSysDash pro
https://corvidet.lemonsqueezy.com/checkout/buy/59c4b360-3fb4-4af2-8290-54d1cac13780 pro
https://yazanbenedit.gumroad.com/l/lrprcl starter
https://corvidet.lemonsqueezy.com/checkout/buy/254f8366-5753-4821-b3dc-e4afed6761b9 starter
The honest context:
I'm a solo founder building in public. Day 1 of selling. I'm posting everything here as I go, what works, what doesn't, what I learn.
If you're a bootstrapped founder who wants to know your real metrics without the monthly subscription, this is for you.
Happy to answer any questions about the metrics calculations or how it's built.
Hey IH,
I’ve been building something quietly for a while, and before talking about the product, I want to talk about the moment that pushed me into this path.
A few months ago, I hit a personal low.
Not a dramatic one.
Just the kind that empties your chest a little.
I had just failed an important exam — one of those that’s supposed to “open doors” in the traditional sense. And even though I tried to play it cool, it hurt. Everyone around me was moving along a straight path, and mine suddenly bent sideways.
But here’s the part I didn’t expect:
In the weeks that followed, something started to grow in the empty space where the disappointment was sitting.
A quiet urge to build something that mattered.
Not something “big.”
Not something for investors.
Not a unicorn dream.
Just something useful — especially for people like me:
independent builders, solo founders, the ones trying to create value with almost no resources except stubbornness and curiosity.
⚡ The Difficulty Nobody Talks About
I started noticing how many of us are building alone, trying to juggle:
dev work
marketing
pricing
retention
user feedback
accounting
and… life
And there’s this hidden layer of uncertainty:
“Is my project actually growing, or am I fooling myself?”
I felt it myself.
I saw friends feeling it too.
We all had Stripe dashboards open… yet no real clarity.
That feeling — the fog around numbers — was actually preventing people from improving their products.
Painful truth:
You can work for months without knowing whether your decisions are helping your business or killing it slowly.
That stuck with me.
🛠️ So I started building. Not to create a tool… but to create clarity.
Not a fancy startup.
Not a toolbox of 100 features.
Just a simple way for indie founders to understand what’s really happening in their business:
What’s growing?
What’s shrinking?
What’s stable?
What’s bleeding?
What deserves attention?
Nothing transforms a project faster than honest metrics.
But honest metrics are rare when you’re building alone.
So I built something to help with that — quietly, late at night, debugging code while the rest of the house was asleep. Because I realized that clarity is not a luxury; it’s the difference between continuing and quitting.
🚀 The Objective Behind the Project
My goal isn’t to “launch a SaaS.”
The internet already has enough of those.
It’s to make this community stronger.
To help solo founders feel less blind.
To help bootstrappers make decisions with confidence.
To help one-person startups survive long enough to become real businesses.
If even a handful of founders get a little more clarity…
If a few people avoid burnout because they finally understand their metrics…
If someone pivots early and saves themselves months of frustration…
Then this project will have served its purpose.
💬 Why I’m Sharing This Here
Not to promote.
Not to pitch.
But because IndieHackers has always been the one place where people understand what it means to build from nothing.
And maybe someone here needs to hear this:
You don’t need a perfect path.
You don’t need permission.
You don’t need a title.
Sometimes the thing you build during your lowest moment becomes the thing that lifts you out of it.
That’s what happened to me.
And I’m still building — slowly, quietly, determined.
If any of this resonates with you, I’d love to connect, learn from your journey, and give back in any way I can.
We’re all building in the dark.
At least here, we don’t have to do it alone.
I failed my exam, but I passed the real test: choosing the harder road, the one where you build instead of wait.
Hey IndieHackers 👋
I want to share a story I’ve been hiding for months — the real reason I started building my first SaaS.
A few months ago, I was preparing for the biggest academic step of my life: my university entrance exam.
Everyone around me expected me to succeed — teachers, family, friends. And honestly… I wanted to make them proud.
But something was happening inside me at the same time:
I was falling deeply, obsessively in love with building.
While others were revising chapters, I was learning Supabase RLS.
While my classmates memorized formulas, I was debugging Stripe OAuth
until 3AM.
While everyone told me “study first, build later,”
I could only think “No. I want to build NOW.”
So I failed the exam.
Not because I wasn’t capable…
But because I was already somewhere else mentally — in my own universe, writing code, learning faster than any class could teach me.
For weeks, I felt ashamed.
I thought failure meant I wasn’t good enough, that I had disappointed everyone.
But with time… a new perspective emerged.
🔥 That failure didn’t stop me — it freed me.
It pushed me to build something real. Something useful. Something for people like me.
🚀 That’s how RevPilot was born
A simple, focused Stripe analytics tool built for:
• indie founders
• bootstrappers
• solo devs
• small teams who need clarity, not enterprise dashboards
Stripe gives you numbers.
RevPilot gives you understanding.
MRR, churn, ARPU, LTV, subscriber history — all in one clean, actionable dashboard.
Every feature I built came from personal frustration:
“Why is it so hard to see my real revenue trends?”
“Why is churn hidden behind 10 clicks?”
“Why can’t Stripe show metrics founders actually need?”
So I built the tool I needed.
💥 The Unexpected Lesson
Building RevPilot taught me something school never did:
Failure is a direction, not a definition.
Failing my exam pushed me to create my own path.
It made me bet on myself.
It forced me to learn faster, solve harder problems, and grow into the builder I always wanted to be.
I realized:
The world doesn’t reward you for staying on the safe path.
It rewards you for shipping.
🧪 I’m still building… and learning
RevPilot is not perfect.
I’m improving the onboarding flow, testing with real Stripe accounts, fixing bugs, and polishing metrics. Every single day.
But it finally feels like I’m building something that matters.
🙏 If you’re an indie founder using Stripe, I’d love your feedback
I’m preparing my soft launch.
If you want to try it, review it, or give honest feedback:
👉 comment below
👉 DM me
👉 or check the early preview: revpilot-net.vercel.app
Your insights could make the product 10× better.
❤️ Thank you IH
For me, IndieHackers has become the university I never got into —
but the one I actually needed.
If you’re building, struggling, pivoting, failing, trying again…
I’m right here with you.
This is just the beginning.
A few months ago, I had one of those weeks where MRR went up… and I couldn’t tell you why.
Not exactly a big spike. Just +3.1% or something. But the point is — I couldn’t explain the story behind it.
And that bothered me more than the growth itself.
I had dashboards. I had charts. I had retention cohorts.
But when I opened them, I didn’t feel clarity.
I felt… guessing.
Was the growth caused by:
A good onboarding email?
A specific user segment?
A random coincidence?
Just noise?
I realized I didn’t want more metrics.
I wanted the meaning behind the metrics.
So I did something simple, almost stupidly simple:
I opened a spreadsheet and started writing plain-language weekly summaries of what actually changed. Not numbers. Narratives.
The moment I wrote it, something clicked.
Everything started making sense.
Decisions got clearer.
And I thought:
Why isn’t my analytics tool just telling me this?
So I built RevPilot.
It connects to Stripe and gives founders a weekly revenue briefing in plain English:
What changed in MRR
Why it changed
Which customers were involved
And what to keep an eye on next
No dashboards to interpret.
No data models to configure.
No “yet another metric.”
Just clarity.
Not trying to pitch here — just sharing the why behind the project.
If you’ve ever stared at your metrics and felt like you were guessing, I think you’ll understand why I built this.
If you’re curious, I’m happy to generate a free personalized revenue summary for your SaaS — just reply “summary.”
I’ll answer every comment.
Comment