TimedSubs got Featured on Product Hunt, but the real lesson was distribution
Yesterday I launched TimedSubs on Product Hunt.
It got Featured, which was a nice surprise.
But I also saw the limitation pretty quickly: I’m a solo builder without a big audience, newsletter, or community to share it with, so the vote count didn’t really keep growing after the first wave.
The website data was still useful though:
- 62 visitors
- 65 visits
- 173 pageviews
- 2.66 pages per visit
- 102s average visit duration
- Product Hunt was the main traffic source
- The day before launch, the site had 5 visitors
TimedSubs is a pretty specific tool.
It’s for creators who already have a finished script and a matching voiceover. Most subtitle tools start from audio and generate a transcript. TimedSubs starts from the approved script and creates timed subtitle files from that.
So the question I’m trying to answer is:
Do people understand why “script-first” is useful, or does it sound too niche/confusing?
The most useful signal from Day 1 was that people didn’t only land and leave. Some opened the sample result page, pricing, contact, and sign-in pages.
The numbers are still small, but at this stage I care more about real feedback than more votes.
If you build narrow workflow tools, how do you explain the difference without making the page feel like a tutorial?
The PH numbers are interesting, but I’m more curious about what happened before you built it.How did you first find the “script-first” problem? Was it something you experienced yourself, something users kept complaining about, or did you validate it with creators or agencies first?Did you talk to real users or test the workflow manually before building, or did you mostly go straight into the product?
Right now the data shows people were curious enough to look around, but it’s still hard to tell whether the core problem itself was validated before launch.
Totally fair question. It started with my own workflow.
I was making faceless long-form YouTube videos, and after the script and voiceover were already locked, subtitles were still the part that kept breaking. Timing would drift, words would be missing, some tools would quietly rewrite what I had written, and the exported SRT files often needed a lot of cleanup.
For my videos, the timing has to be exact because the subtitles are used for visual sync. And the text needs to come from my original script, especially because I work with languages like Spanish, German, and French where accents and wording really matter.
For a 20 or 30 minute video, checking everything by hand is the painful part. I already had the words. I just needed accurate timing, a QA pass, and clean exports. I couldn’t find a tool that handled that well, so I built one.
that makes a lot of sense. feels like the original problem came from a very specific workflow — locked script, recorded voiceover, and subtitles that need exact timing without rewriting the text.
what I’m curious about now is whether you’ve seen the same workflow from other creators or teams too.
are you tracking the full loop? like real script uploaded, audio matched, SRT exported, and then actually used in a published video.
that feels like the signal that separates “this fixed my own workflow” from “this is a repeatable user problem.”
That’s a fair distinction.
The original pain definitely came from my own faceless video workflow, but I agree the stronger signal is whether other creators complete the same loop: upload a locked script, match it with recorded audio, export the SRT, and actually use it in a published video.
I’m starting to think of that full loop as the real validation metric, not Product Hunt traffic by itself. SEO and distribution can help bring in people who already have the problem, but the product proof is whether they trust the exported subtitles enough to publish with them.
That full-loop metric makes sense.
If you’re already getting PH traffic, one practical way to use it is to pick 3–5 creators from that traffic and actually follow them through the flow instead of just looking at aggregate numbers.
For each one, you can quickly check:
did they upload a locked script,
did they try matching it with their recorded audio,
did they export the SRT,
and did they end up using it in a real video?
You don’t need a big sample — even a few real sessions will show you where people drop off. If most of them stop before exporting or don’t use the subtitles in a published video, that’s probably where the trust or usability gap is.
If you do see a couple of them actually publish with your subtitles, that’s already a much stronger signal than PH traffic or signups alone.
What stood out to me wasn't the Product Hunt traffic.
It was this:
"Do people understand why script-first is useful?"
Because that's a very different question from whether people understand what the product does.
A lot of narrow tools get mistaken for explaining problems when they're actually making a much bigger decision about who they're for.
Yeah, that’s exactly the point.
Script-first is useful when the script is already final and the words can’t drift. In my case, I was making faceless long-form YouTube videos, and I didn’t need another transcription tool. I already had the script. I needed accurate timing, a QA pass, and clean exports.
So TimedSubs is really for people who care about keeping the approved script intact, not just generating “good enough” subtitles from audio.
That's the part I find interesting.
The moment a founder can explain who a product is not for, a few other questions usually show up right behind it.
Hard to get into those properly in a comment thread.
If you're curious, send over your email and I'll share the fuller thought.