Product Hunt gave me almost no traffic, so I built a free tool around the problem
I launched my B2B SaaS OS on Product Hunt earlier this month.
The result was basically zero traffic and zero sales.
Instead of adding more features, I started looking at the acquisition problem.
The product is a $249 one-time source-code foundation for developers building B2B SaaS with Next.js, Supabase, PostgreSQL and Stripe.
I realized asking someone to immediately spend $249 on a developer infrastructure product gives them very little reason to trust it.
So I built a free tool as the entry point:
SaaS Production Readiness Check
It checks 10 areas that can cause problems in a multi-tenant SaaS:
Tenant isolation
Supabase RLS
Authorization
RBAC
Stripe webhook authenticity
Stripe webhook idempotency
Stripe state synchronization
API key revocation
Invitation race conditions
Auditability
It's a self-assessment, not an automated security scanner or certification. No account required.
You can try it here:
I'm now testing whether giving developers something genuinely useful first can create a better path to the paid product.
If you're building a SaaS, what production issue would you add to this checklist?
On my case, PH gave me great boost!
Solid lesson. Which channel has worked best for you so far?
One I'd add: what happens when a Stripe webhook fires but your own downstream action against it times out or comes back ambiguous — not "webhook was malformed," but "we got the event, tried to act on it, and don't actually know if that action landed." Idempotency covers duplicate delivery, but it doesn't cover your own side failing silently mid-response. I've been stuck on exactly this for a confirm-before-execute product (action dispatched, result unknown, don't want to blindly retry since retry itself can be the dangerous move) and haven't found a clean answer yet — curious if your "auditability" item already covers that gap or if it's really a separate one.
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Nice progress. What is the next thing you are focusing on?
Thanks for writing this up. Bookmarking it for later.
Clear and practical, thanks. Did anything surprise you along the way?
Really relatable. How much time do you put into this each week?
Makes sense. Are you planning to charge for it, or keep it free for now?
Thanks for sharing the numbers, that makes it much easier to follow.
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
What made you pick this stack over the alternatives?
Appreciate the honesty here, most people only share the wins.
Same pattern here, so I can share how it looks from the inside a bit further along. UtilitySEO's entry point is a free scan (up to 2,000 pages, no account) for exactly your reason: nobody spends real money on a tool from a site with no reputation. But our domain authority is 3 and search sends us about 4 visits a month, so the free tool hasn't solved discovery by itself. It converts attention you already have; it doesn't create it. The checker has to go where your buyers already are. For yours, I'd take the Stripe webhook idempotency item into Supabase and Stripe communities as a standalone post, since it's the one I'd bet most people fail without knowing. Which of the 10 gets the most "fail" answers so far?
Solid lesson. Which channel has worked best for you so far?
Solid lesson. Which channel has worked best for you so far?
Makes sense. Are you planning to charge for it, or keep it free for now?
Solid lesson. Which channel has worked best for you so far?
Makes sense. Are you planning to charge for it, or keep it free for now?
This is useful. How are you finding your first users so far?
That shift from adding features to earning the first bit of trust feels right. For a $249 infra product, I’d keep the checker narrow and show one concrete failure, then let people decide if the paid foundation is worth exploring. Otherwise “production readiness” can become another generic checklist. I’d track which check actually makes people continue, not just how many finish it.
Really good writeup, thanks for sharing it. What's the next thing you're planning to try here?