Product Hunt didn't fail me. WordPress did, and I launched on it anyway.
File Transcribe v1: plugins, fragile jobs, CSS hope. Product Hunt v1 brought traffic and three YouTube videos from David Mbugua, public proof the WordPress build existed (and why I had to rebuild). It also brought AppSumo rejection and nights fixing hosting while users waited on transcripts.
Then I rebuilt. Grew to 100 paid subscribers. July 1, 2026 is Product Hunt v2, not to find product-market fit from zero, but to tell the rebuild story publicly with a hundred people already paying.
The headline: 100 paid subscribers before PH v2
Most makers launch PH to get users. I'm launching PH v2 because I already have 100 paid subscribers on Vercel + Supabase + Next.js + Paddle, and the product finally matches the story David saw glimpses of in v1.
This series, How Product Hunt helped me reach 100 paid subscribers**, is the content backbone for that launch.
My Product Hunt v1 story (honest)
PH v1 felt like winning and losing at the same time.
| What went right | What went wrong |
|---|---|
| Upvotes, comments, visibility | WordPress couldn't absorb spike |
| David reviewed on YouTube (3 videos) | Jobs stalled on long files |
| Proof people want transcription | No path to 100 paid subscribers on v1 |
| Motivation to keep building | AppSumo rejected same month |
I wasn't ready. Not because the idea was bad, because infrastructure was PHP on shared hosting with plugin spaghetti.
Timeline: two launches, one founder
Stack
- PH v1 (WordPress)
- WP + PHP + plugins
- Today → PH v2
- Modern full stack
Revenue
- PH v1 (WordPress)
- $87.57 Paddle
- Today → PH v2
- 100 paid subscribers
AppSumo
- PH v1 (WordPress)
- Rejected
- Today → PH v2
- Subscription SaaS
David
- PH v1 (WordPress)
- 3 YouTube videos on v1
- Today → PH v2
- Thank-you + Pro package + v2 update
Infra on spike day
- PH v1 (WordPress)
- Terrifying
- Today → PH v2
- Edge + serverless
Guest try
- PH v1 (WordPress)
- Clunky
- Today → PH v2
- Homepage + `/try/[token]`
PH date
- PH v1 (WordPress)
- v1 era
- Today → PH v2
- July 2026, scale story
What PH v1 taught me
Traffic without infrastructure
PH spike + WordPress long jobs = bad night. Users bounce. You lose the moment.
v2 at 100 subs already survived real load. PH v2 is acceleration, not prayer.
David Mbugua, three videos, one honest WordPress era
David Mbugua featured File Transcribe in three YouTube videos while I was still on the WordPress v1 stack. I'm grateful he did, and I link them on purpose. They're public proof of how rough that version was: real UI, real uploads, real founder energy, not infrastructure that could carry 100 paid subscribers.
- File Transcribe on YouTube, video 1
- File Transcribe on YouTube, video 2
- File Transcribe on YouTube, video 3
Watch any of them if you want the unfiltered WordPress era, plugin UX, hosting stress, the gap between what David's audience saw and what I knew was breaking behind the scenes. Moral support > MRR at the time. v2 is what I'd send without apologizing for UX. Preparing Pro + coupon thank-you for July.
David didn't owe me three videos. He gave them anyway on v1. 100 paid subscribers on v2 is how I say thank you with a product worth recommending, and why Product Hunt v2 isn't "try again," it's chapter two with receipts.
AppSumo rejection
Answer: subscription transcription, generous free tier, not lifetime deal shape. 100 paid subs validates that call.
What I did between PH v1 and PH v2
| Action | Why it mattered for 100 subs |
|---|---|
| Archived WordPress v1 | Stop patching, start rebuilding |
| GFX dashboard on Vercel | Learn deploy discipline |
| Clean Next.js repo | Upload-first homepage |
| Supabase RLS | Private transcripts users trust |
| Paddle webhooks | Billing that scales |
| Daily deploys on Vercel | Fix churn bugs fast |
| 6 stack blog posts | DevRel outreach + SEO |
| Marketing Center | Sibling outreach panels |
PH v2 isn't "try again." It's chapter two with receipts.
v2 ready checklist (at 100 paid subscribers)
| Requirement | Status |
|---|---|
| Try without signup | ✅ Homepage |
| Mobile usable | ✅ Sidebar + playback |
| Paddle billing | ✅ 100 paying |
| Private data safe | ✅ Supabase RLS |
| Blog social proof | ✅ 6 stack posts |
| Team outreach | ✅ Siblings on MC panels |
| Founder ops | ✅ Scrape + reports |
PH v1 vs now, launch readiness
Deploy confidence
- v1
- ⭐⭐
- v2 (100 subs)
- ⭐⭐⭐⭐⭐
Paid base
- v1
- ~$87
- v2 (100 subs)
- 100 subscribers
Story
- v1
- Weak
- v2 (100 subs)
- Full rebuild series
Post-PH support
- v1
- Solo panic
- v2 (100 subs)
- Systems in place
Long file jobs
- v1
- Timeout fear
- v2 (100 subs)
- Background queue
Billing on spike day
- v1
- Plugin roulette
- v2 (100 subs)
- Paddle MoR
July 2026 PH v2 plan (from strength)
| Asset | Purpose |
|---|---|
| Stack blog series | Proof of rebuild depth |
| 100 paid subscribers | Social proof in launch copy |
| David thank-you package | Creator relationship, 3 v1 videos as proof |
| Homepage demo GIF | Show don't tell |
| Compare pages | SEO + clarity |
| Sibling outreach | Warm intros to makers |
I'm not launching to find paying users. I'm launching so the next hundred discover a product that already works.
For Product Hunt / makers reading this
- First launch validates attention, not architecture
- $87.57 → 100 paid subs, rebuilds work if you fix foundation
- Don't launch PH on WordPress long jobs, fix jobs first
- July 2026, follow the launch
File Transcribe · Full stack hub
Rasif Ali Khan