I built a tool that turns every freelance payment into a verified client review — here's what I learned
Hey IH 👋
I'm a solo founder and I just launched UseVouchly (https://www.usevouchly.com) — a tool that helps freelancers collect client reviews automatically, without the awkward follow-up emails.
The problem I kept seeing:
Every freelancer I talked to had the same issue: they do great work, the client is happy, but they never get a testimonial out of it. By the time they send a follow-up email asking for a review, the client has moved on. No review = no social proof = harder to land the next client.
How it works:
- Freelancer creates a payment link with project details
- Client clicks the link and pays via Stripe (money goes directly to the freelancer's Stripe account — 0% platform commission)
- Right after payment, the client sees an AI-drafted review based on the project. They can edit, approve, or skip.
- If approved, a verified "Proof Page" is generated — showing the payment amount, project name, and the client's testimonial with a verified badge.
The key insight: the best moment to ask for a review is right after payment, when the client is still engaged. Not 3 days later via email.
Where I'm at:
- Product is live and fully functional
- Free tier available (1 payment link/month), paid plan at $15/mo for unlimited
- Built with Next.js, Supabase, Stripe Connect, and Gemini API
- Currently working on SEO and trying to find my first real users
What I'd love from this community:
- If you're a freelancer, would you use something like this? Why or why not?
- Any feedback on the landing page or the flow?
- Ideas for reaching freelancers who struggle with collecting reviews?
Happy to answer any questions about the tech stack or the business model. Thanks for reading!
The insight about timing is brilliant. Hooking the review into the payment flow makes so much sense because that’s when client engagement peaks.
As a freelancer, my main question would be about project completion vs. milestones. Sometimes a client pays a milestone invoice, but the project isn't fully wrapped up yet (or there's still QA/handoff friction ahead). Is there a way to trigger the review prompt only on the final invoice, or can the freelancer manually decide which payment link carries the review ask?
The timing insight is the strongest part here. Most testimonial tools treat reviews as a follow-up workflow, but Vouchly is attaching the ask to the one moment where trust, payment, and client satisfaction are already active.
That makes this more interesting than a “review collection tool.” It is closer to a verified proof layer for freelancers: payment happened, work was completed, the client approved the testimonial, and the proof page carries more weight than a random quote on a portfolio.
One thing I’d watch is the UseVouchly name. It explains the review/testimonial angle, but if this grows into a broader freelancer trust and proof-of-work platform, Beryxa.com would feel more like a serious SaaS brand than a tool name tied only to vouchers/vouching.
Really appreciate this — you articulated the core value prop better than I did in the post. "Verified proof layer" is actually a much cleaner way to describe it than "review collection tool." Might steal that framing.
On the name: fair point. UseVouchly made sense at launch because "vouch" captures the trust/endorsement angle, but I can see how it might feel limiting if the product grows into a broader proof-of-work platform. Something to keep in mind as the positioning evolves.
Curious — as a freelancer or someone who works with them, what would make you actually adopt something like this? Is the payment-triggered timing the main hook, or is there something else that would need to be true?
I think the payment-triggered timing is the main hook, but not enough by itself.
For freelancers, adoption probably depends on whether this helps them win the next client, not just collect the last testimonial.
So the proof page has to feel credible enough that a freelancer can send it before a sales call, attach it to a proposal, or use it as trust evidence when a new lead is deciding whether to hire them.
The strongest version is probably not “collect testimonials after payment.” It is “turn completed paid work into verified trust assets that help you close future work.”
That is why the name matters if you go broader.
UseVouchly works for the current wedge because it sounds close to vouching and testimonials. But if the product becomes a proof-of-work layer for freelancers, the brand needs to carry more weight than a testimonial tool.
Beryxa feels stronger for that wider SaaS direction because it is not locked to reviews, vouchers, or one trust mechanic. It can hold proof pages, verified work history, client trust, freelancer reputation, and maybe even marketplace-style credibility later.
I would pressure-test that before the product gets too known as UseVouchly. Once freelancers start sharing proof pages publicly, the name becomes part of their trust signal too.
This reframe is genuinely useful — "turn completed paid work into verified trust assets" is a much stronger positioning than "collect testimonials after payment." It shifts the value from backwards-looking (what the client thought) to forward-looking (what helps you close the next deal).
The proof page being credible enough to attach to a proposal is actually the use case I want freelancers to reach for first. If the page feels like a real trust signal rather than just a screenshot of a review, that's when the product becomes part of their sales process, not just their admin process.
On the brand: I'm keeping it noted. UseVouchly works as a wedge, but you're right that if this grows into something closer to a verified work history layer, the name would need to evolve. Better to know that now than after 10,000 proof pages are live.
Appreciate you thinking through this seriously — it's clarified something I hadn't fully articulated yet.
Exactly. The “10,000 proof pages” point is the part I would not ignore.
Once freelancers start sending those pages to prospects, the product name is no longer just your internal brand. It becomes part of their trust signal.
That is where UseVouchly can start creating a ceiling. It works for the testimonial wedge, but if the product becomes a verified proof layer freelancers use to win future work, the brand needs to feel more serious than a review/vouching tool.
Beryxa fits that wider direction because it can carry verified work history, client proof, trust assets, freelancer reputation, and maybe even marketplace-style credibility later.
I would separate the timing clearly:
You do not need to rebrand tomorrow.
But if Beryxa is genuinely the stronger long-term name, the smart move is to secure the .com before public proof pages, freelancer profiles, shared links, and customer memory build around UseVouchly.
That keeps the option open while the product is still early enough to move cleanly.
I can make Beryxa.com available in a founder-friendly way if you want to lock the name before that public gravity builds. Clean one-time acquisition, secure transfer, no messy process.
Best place to discuss terms is LinkedIn:
https://www.linkedin.com/in/aryan-y-0163b0278/
Thanks for the context — and for the candid feedback throughout this thread. I'll keep the brand question open as the product evolves. Not in a position to make that call right now, but appreciate you laying out the thinking.
Totally fair that you may not be ready to make the full rebrand call today.
But I would separate the rebrand decision from the name-control decision.
You can keep validating UseVouchly while still securing the stronger long-term name before the product creates too much public gravity.
The risk is that the proof-page workflow starts working, freelancers begin sharing links, customers remember UseVouchly, and then the name you actually want for the broader verified-trust layer is either no longer available or harder to justify switching into.
That is why I would treat Beryxa.com as the controlled option for the serious version, not just a naming idea.
If this stays a testimonial wedge, UseVouchly is fine.
But if you genuinely see the product becoming verified work history, trust assets, freelancer reputation, and proof pages that help people close future work, then securing Beryxa now is cleaner than revisiting it after the public layer is already built.
I control Beryxa.com, and I can make it very founder-friendly if the fit is real: $1,500 all-in, clean one-time acquisition, secure transfer, no messy process.
That is not the public retail direction I would normally take for the name, but I would rather see it used by the right early product than sit unused.
Best place to handle it privately is here:
https://www.linkedin.com/in/aryan-y-0163b0278/
Appreciate the persistence and the reasoning. The separation between "rebrand decision" and "name-control decision" is a fair point in theory. For now I'm keeping focus on getting the first real users before making any brand calls. If the product grows into the broader trust layer you're describing, I'll revisit. Thanks for the thread — genuinely useful product thinking even if the timing isn't right.
Hi Sean, one practical thought after our UseVouchly thread.
Since the full Beryxa/domain decision is clearly too early, I would not push that further right now.
But the positioning question still matters for your first-user push: whether freelancers see this as “testimonial collection” or as a verified proof asset they can use to win future work.
I’m doing a few focused naming/positioning audits at $99 while refining the format.
For UseVouchly, I’d make it specifically useful around:
current name/category risk
proof-page trust perception
whether the product reads as admin tool or sales asset
landing page/category framing
where the brand may limit the broader verified-trust direction later
my recommended next move before more freelancers start sharing pages
Not a long consulting thing. Just a sharp written breakdown you can use while getting the first real users.
If useful, connect here and I can put one together for UseVouchly:
https://www.linkedin.com/in/aryan-y-0163b0278/
That is fair, and I respect the focus.
First real users should come before a full rebrand decision.
The only thing I’ll clarify from my side so expectations are clean: Beryxa.com is not reserved unless there is an actual agreement, and the $1,500 founder-friendly offer was based on the product still being early enough to move cleanly.
If UseVouchly starts getting real proof pages, shared links, and freelancer usage, the brand decision may become more expensive later, not just financially but in switching cost and customer memory.
So I’d just treat it simply:
If the product stays a testimonial wedge, keep UseVouchly and move fast.
If it starts becoming the broader verified-trust layer, revisit Beryxa before too much public proof infrastructure builds around the current name.
Appreciate the thoughtful exchange, Sean. Wishing you a strong first-user push.