I built a preview-first tool for dialogue hidden under background music — feedback wanted
I’m building RemoveBackgroundMusic.com for creators who need to make spoken dialogue easier to hear without reopening an editing timeline.
The product decision is intentionally conservative: users compare a 30-second preview from their own recording before purchasing a full export. For MP4 files, the original video stays on-device and only extracted audio is processed. Dense mixes can still be difficult, so the product frames the preview as the decision point rather than promising a universal result.
I’m tracking upload, preview, checkout, purchase, and delivery with source-safe funnel events. I’d value feedback on whether this preview-first framing feels clear and trustworthy.
Curious how long it took before you saw the first real results?
Helpful post. How did you get your first bit of traction?
Good point. Did you test that with users before committing to it?
Interesting approach. What was the hardest part to get right?
What made you pick this stack over the alternatives?
Great breakdown. What feedback have you had from early users?
Are preview completion and purchase rates telling you whether users trust the result enough to buy, or are drop-offs mainly happening when the preview exposes difficult audio cases?
The preview-first model solves a real problem. Users hear a 30-second sample before they pay for a full export. This removes the guesswork buyers face with most audio tools.
The privacy angle is strong too. For MP4 files, the original video never leaves the user's device. Only the extracted audio gets processed. This detail matters for creators who work with client footage or sensitive content.
The team also avoids overpromising. Dense mixes remain hard to clean up, and the product says so upfront. That honesty builds more trust than a bold claim would.
From a growth perspective, tracking funnel events across upload, preview, checkout, purchase, and delivery gives clear visibility into where users drop off. This is the kind of data-driven build process every SaaS founder should follow.
As someone who builds and optimizes websites for clients across multiple countries, I see this pattern often. Tools that set honest expectations convert better long term, even if short term numbers look smaller.
Good execution on a narrow, useful problem.
Check out the tool here: https://removebackgroundmusic.com/
Check out my work at https://sohaibyounas076.github.io/portfolio/ and https://github.com/Sohaibyounas076/
What made you pick this stack over the alternatives?
What made you pick this stack over the alternatives?
What made you pick this stack over the alternatives?
Preview first is the right call and I think it matters more than the model quality on day one.
We do something similar in a different domain, photo in and recipes out from whatever is in your fridge, and the mistake we made was making people commit to choices before the app had proven it could do the one thing it promises. People left at that screen and never saw the part that works. Your version of that would be any setup step that happens before someone hears a clean line of dialogue.
Will give yours a real test this week. If you want to trade, ours is iOS: https://testflight.apple.com/join/AZm9hsB8
That setup-step trap is real. Any screen before the dialogue preview is a chance for someone to bail before seeing the actual value.
We kept the flow short for that reason. Upload, then preview. No account creation, no configuration screen in between. The preview has to carry the whole pitch.
Your fridge to recipe idea sounds like a good parallel case. The photo in and result out promise only works if people reach the result fast.
Will check out the TestFlight link this week. Appreciate the feedback.
Curious how long it took before you saw the first real results?
Thanks for sharing the numbers, that makes it much easier to follow.
Thanks for sharing the numbers, that makes it much easier to follow.
Makes sense. Are you planning to charge for it, or keep it free for now?
Really solid approach — curious how you're thinking about this, what's been the hardest part to figure out so far?
Helpful post. How did you get your first bit of traction?
Thanks for sharing the numbers, that makes it much easier to follow.
Thanks for sharing the numbers, that makes it much easier to follow.