Sinh Giang's profile on Product Hunt

About

Hi, I'm Sinh 👋 — a solo, AI-native founder. I design, build, and ship products end-to-end with an AI-first workflow that lets one person move like a whole team. Right now I'm building Revova, a tool that automatically recovers failed subscription payments. It's a quiet, unglamorous problem that silently drains 5–10% of revenue from subscription businesses every month — and I'm a little obsessed with fixing it. No code, no awkward emails, no chasing customers: just money won back on autopilot. My goal is to make revenue recovery so simple and affordable that even a solo indie hacker can plug it in and stop losing money in minutes. Always happy to connect with fellow makers — say hi! 🚀

Links

Revova

X (Twitter)

Badges

Tastemaker

Gone streaking

Gone streaking 5

Forums

•

2mo ago

The scariest thing I vibe-coded was the billing logic — how do you sleep at night?

Non-technical founder here, built my whole product with Claude Code. Everyone in this forum keeps saying the same thing UI and analytics get the "looks fine, ship it" treatment, but billing and auth get the paranoid line-by-line review. I've lived that.

Here's the twist though: my product IS the billing edge case. It's a tool that recovers failed subscription payments, so the entire thing lives in the messy world of declined cards expired cards, insufficient funds, bank 3-D Secure/SCA challenges that all look similar in the data but need completely different handling. Vibe-coding something where a wrong branch means someone gets emailed "your card was declined" when it actually went through was genuinely terrifying. I couldn't just trust the vibes.

•

2mo ago

A recovery email that changes based on WHY a payment failed — feedback?

I've been building this solo and wanted to get some honest eyes on it before I get too attached to my own assumptions.

The problem I kept running into: when a subscription payment fails, almost every tool sends the same generic "your payment failed, please update your card" email. But the reason it failed is usually very different an expired or lost card, insufficient funds, or a bank 3-D Secure/SCA verification challenge. Telling someone to "update your card" when their bank just needs them to confirm the charge is not only useless, it makes the whole thing read as impersonal and a bit spammy. Industry-wide, a meaningful chunk of subscription churn is just failed payments that never get recovered, and a lot of that is these avoidable mismatches.

p/emailtemple

•

2mo ago

Which email flow do you know you should be sending, and aren't?

Genuine question. I keep meeting operators with a warm list, a good offer, and no abandoned-cart flow. Or a welcome series that's one email long and just stops.

If that's you which one is it, and what's actually stopping you? The time, the build, or not knowing what email 3 is supposed to say?

Asking because I've been building for exactly this.