I built VideoTestimonials because every founder I know struggles with social proof
Every SaaS founder, course creator, and ecommerce friend I talk to says the same thing: "I have happy customers but no easy way to capture their stories."
Existing tools didn't cut it. Senja's solid but $29+ and missing video editing. Vidyard's enterprise-priced. The DIY route (Loom for recording, Descript for editing, then manual embed code) takes hours per testimonial.
So I built VideoTestimonials. The pitch: collect video and text testimonials in minutes, then turn them into branded social graphics with one click — 50+ image studio templates, 10+ embed widgets (Wall of Love, marquee, masonry, carousel, bento grid). AI handles the boring parts: transcription, highlight reels, stitching multiple video responses together. It also imports existing reviews from 20 platforms (Google, Trustpilot, G2, X, LinkedIn, Apple Podcasts) so you can consolidate everything in one wall.
Full white-label on every paid tier. $24 / $49 / $79 per month, 7-day free trial. Built on Next.js + Supabase + Paddle.
Live at https://videotestimonials.video. A few months in. SEO is starting to kick in (87 long-form posts indexed last week), Product Hunt push coming up, focused on growing the first real customer cohort.
Two questions for the IH community:
What's the one feature that would make you switch from your current testimonial tool?
For founders already using video testimonials — what's broken about your current workflow?
Happy to dig into the build, the stack, or the path so far.
It is a major bottleneck for founders when they finally secure a happy customer's time but then lose the momentum because the recording and editing process is too clunky for someone who isn't a professional video editor.
The real advantage of an all-in-one platform is the removal of "tool fatigue" because being able to import existing reviews from twenty different platforms and instantly convert them into a branded "Wall of Love" saves hours of manual embedding and design work that most small teams simply don't have.
Since you are seeing SEO momentum from long-form content are you planning to add an automated "Video to Blog" feature that turns customer transcriptions into case studies to help feed that search engine growth even faster?
100% — "tool fatigue" is exactly the right framing. The thing customers tell us when they switch is "I had Loom for recording, Riverside for editing, Senja for collection, Canva for graphics, and a CRM for follow-ups, and I still wasn't shipping anything." Compressing that into one workflow was the actual product insight — not just a feature list.
On the Video-to-Blog question: not on the immediate roadmap but it's exactly the kind of feature I want to build next. Right now the AI generates highlight reels and transcripts, but turning a 5-minute customer story into a 1,500-word case study is genuinely valuable — both for your own SEO and for the customer who gets a referenceable artifact they can publish on their own site.
Curious where you see the human-in-the-loop sitting: "auto-publish to your blog" feels too aggressive, but "AI drafts, founder reviews and posts manually" might still feel like work. Maybe a middle ground where AI generates the draft, you tweak the title + intro, and one click publishes? Where do you draw the line?
The "AI drafts, founder reviews" approach is the sweet spot because a case study represents your brand's authority, and fully automated text often lacks the nuanced voice needed for high-tier credibility.
Providing a structured draft that includes the problem, solution, and results based on the transcript saves 80% of the effort, leaving the founder to just add the personal touch that makes a story resonate with humans and search engines alike.
I use this exact balance in my high-tier PR and media placement work where we use AI to synthesize data but rely on human expertise to frame the "hook" that gets a brand featured on major news outlets.
Since you're considering this, would you also include an "SEO Metadata" generator in that workflow so the case study is ready for indexing the moment the founder hits publish?