2
5 Comments

AI can fake 100 glowing reviews before lunch. Would you pay to prove yours are real?

Something's been nagging me: now that anyone can spin up a hundred 5-star testimonials with one prompt, I think review widgets are quietly developing a trust problem. People see a wall of glowing quotes and part of them goes "...is any of this even real?"

So before building anything, I put up a demo to test an idea: instead of just collecting testimonials, pull your real App Store reviews and prove each one — link it back to its source, fingerprint it on import, show it's unedited and still live. A Wall of Love people can actually verify, not just read.

Live demo (real reviews — click any "✓ Verified" chip to see its record):
https://landing-drab-three-13.vercel.app

Being upfront: tools like Senja already collect testimonials really well (some for free). This is only about the "prove they're real" part — and honestly I'm not sure yet if that's a real pain or just my own paranoia, which is exactly why it's a demo + waitlist, not a product.

Two genuine questions:

  1. Do you actually worry your visitors doubt whether your reviews are real?
  2. Would you pay for verified provenance, or is collecting enough?
posted to Icon for group Ideas and Validation
Ideas and Validation
on June 13, 2026
  1. 2

    I'd be careful with one thing.

    The interesting question may not be whether reviews can be verified.

    It may be whether buyers actually need verification before they trust a review in the first place.

    Those sound similar, but they can lead to very different validation signals.

    That's not a decision I'd make casually from waitlist interest alone.

    1. 1

      Yeah, you nailed the part that actually matters. "Can it be verified" is the easy half — whether buyers genuinely need it is the whole game, and you're right that waitlist interest won't settle that on its own. I'm treating the signups as a weak first filter at best, not proof, and I'll dig into the "do they actually need it" question properly before building anything real. Appreciate you pushing on this — it's exactly the assumption I needed checked.

      1. 1

        That's exactly why I'd still be careful.

        I don't think the difficult part is validating the idea.

        I think there's a bigger decision sitting underneath that question.

        I wouldn't try to unpack that properly in a thread.

        If you'd like the tighter version, drop your email and I'll put it together properly.

        1. 1

          Appreciate that, genuinely. I try to keep these calls out in the open though — partly so other people can poke holes too — so if you're up for sharing the gist of that "bigger decision" here, I'm all ears. Either way, thanks for the sharp nudges, they've been useful.

          1. 1

            That's fair.

            The reason I keep stopping short is that I don't think the interesting part is the answer.

            I think it's the decision that answer ends up driving.

            Those tend to look much clearer in hindsight than they do while they're being made.

            That's the part I'd be careful with.

Trending on Indie Hackers
6 weeks solo, 2 rejections, finally live but nobody told me marketing would be this hard User Avatar 138 comments I spent more time setting up cold email than actually selling. Here is what fixed it. User Avatar 32 comments I just wanted to taste AI coding tools. A week passed. User Avatar 21 comments I built a PDF API because every team I know has a haunted corner of their codebase they never want to open User Avatar 16 comments Building LinkCover – Day 3: Payment is live. No more building, time to sell. User Avatar 15 comments I Was Bypassing Every App Blocker, So I Built One That Fights Back User Avatar 12 comments