Where is your revenue quietly disappearing?
I’ve been digging into something most SaaS dashboards can’t show: the money you’re quietly losing every month.
So I ran a small experiment with an app I launched: Quiet Cost.
Included in it are 16 quick questions that rank issues by impact, estimate hidden revenue leaks, and give you a simple score.
Here’s what I’m trying to figure out:
- Does the experience make sense?
- Is the messaging clear?
- Are the insights actionable or confusing?
- Any areas where the UX feels clunky or incomplete?
I’d love founder-level feedback before I go too far.
If you’re curious and have 5 minutes to test it, you can try it here (no initial sign-ups required):
[https://quietcost.lovable.app]
Drop a comment with your thoughts, or DM me if you want to dig deeper. Every piece of feedback is gold.
Trending on Indie Hackers
Tested Quiet Cost — the 16-question diagnostic format is smart. Founders answer questions they already know the answers to, and the score makes it concrete.
One feedback point: the framing is strong for cost-side leaks, but some of the biggest revenue losses in SaaS are passive, not cost-based. Failed subscription payments are the clearest example — 5-9% of monthly Stripe charges fail at any given time, and most founders don't see it because it doesn't show up as a cost, just as missing revenue they never expected. MRR just quietly doesn't grow at the rate it should.
The question 'do you have automated recovery for failed subscription payments?' would be a high-impact add to the diagnostic. In my experience it scores low for almost everyone who hasn't explicitly built or bought dunning automation.
Good luck with this — the hidden cost scoring concept has real legs.
This is a great observation. Appreciate you taking the time to run through it.
You’re right that some of the biggest leaks in SaaS aren’t really “costs” in the traditional sense. They’re revenue that quietly never materializes. Failed payments are a perfect example of that — nothing shows up on a cost line, but growth slows and most teams don’t immediately connect the dots.
Adding a question around automated recovery or dunning is a strong suggestion. It fits well with the idea of passive leaks that happen in the background.
Out of curiosity, when you’ve seen founders realize this is happening, where does it usually show up first?
• Stripe payment failure rates
• churn metrics drifting upward
• support tickets about billing
• something else entirely
Trying to figure out where this blind spot typically surfaces.
Thanks again for the thoughtful feedback — exactly the kind of insight I was hoping to get from the community!