The Birth of Reebews: Why I'm Building a Review Platform for Small Businesses

The Birth of Reebews: Why I'm Building a Review Platform for Small Businesses

Drum roll, please...

In my previous blog post, I mentioned I was building a SaaS application. Today, I'm excited to reveal the project name: Reebews – a review acquisition platform designed to help small businesses get more online reviews across various platforms.

But instead of diving into what Reebews does or how it works, I want to share the why behind this project. Because every great product starts with a problem that keeps you up at night.

The Problem That Started It All

My journey began during my startup days when I was selling products on marketplaces like Amazon and Flipkart. Despite having quality products and decent sales, there was one challenge that constantly haunted me: getting reviews.

Here's the thing about reviews – they exist in what I call a "grey area." The rules are subjective and often frustrating, especially when you're competing on major marketplaces.

The Marketplace Dilemma

When you're selling on your own website, getting initial reviews is relatively straightforward. You can gather feedback from family and friends, or write a few yourself to create social proof. It's not ideal, but it's possible.

Marketplaces, however, are a different beast entirely. They have strict compliance rules:

  • No reviews from family and friends

  • No compensating customers for positive reviews

  • No gaming the system in any way

Yet these same platforms boost products organically based on ratings. Along with SEO and coupons, having 4-star or 5-star reviews is crucial for visibility. It's a catch-22 that every small seller faces.

My First Attempts (And Failures)

The Thank You Note Experiment

I started simple. With every order, I included a handwritten thank you note asking customers to leave a review if they liked the product. The results? Pretty much nothing.

I learned that people typically write reviews only when:

  • They believe the product offers exceptional value

  • The product genuinely changes their life

  • They're natural educators who want to help other buyers

The percentage of customers who fall into these categories? Disappointingly small.

Amazon's Built-in Review Request

Amazon allows sellers to send one review request per order, but only after the product has been delivered and 7 days have passed. There are automation tools that make this process easier, but the conversion rate was still abysmal – about 1 review per 100 orders.

For a small business processing 10 orders daily, that translates to roughly 3 reviews per month. Meanwhile, established competitors already had hundreds of reviews, making it nearly impossible to compete.

The Google Forms Breakthrough (Sort Of)

Frustrated with the low conversion rates, I turned to ChatGPT for ideas. The suggestion? Create a Google Form with specific parameters and offer rewards for completion.

The concept was simple: customers would fill out a form confirming they'd left a review, and upon verification, they'd receive compensation.

The Good News

This approach improved our conversion rate dramatically – from 1 in 100 orders to 1 in 10 orders. A 10x improvement!

The Bad News

The system was riddled with problems:

  • Customers entered irrelevant data (random order numbers, fake phone numbers)

  • People claimed to have left reviews that never appeared

  • Form names didn't match actual reviewers

  • Verification became a nightmare

[Side note: I created a compensation card with a QR code leading to the Google Form, promising an Amazon gift card upon completion. The design was professional, but the execution was flawed.]

Discovering the Competition

Determined to find a better solution, I discovered ReviewsCanGo.com – a tool that addressed many of my Google Forms issues with built-in validation and additional features for marketplace reviews.

The problem? Pricing.

Their basic tier started at $29/month for one product, one marketplace, and one campaign. Since I sold multiple products, I'd need their second tier at $70/month for 30 products and 10 promotions.

Spending $70 monthly just to collect reviews felt excessive for a small business already operating on thin margins.

The Developer's Dilemma

After testing their demo (which was admittedly impressive), my developer brain kicked in: "I can build this myself."

And so began my 8-month journey building Reebews.

The Struggle

Initially, I tried working on the project while maintaining my full-time job. Late nights became the norm, and burnout quickly followed. Building a platform from scratch while juggling day job responsibilities proved unsustainable.

I even wrote about the project on LinkedIn but had to pause development due to time constraints and exhaustion.

The Breakthrough

Fast forward to today, and things have changed dramatically. With the advent of AI-powered coding tools and my recent experience building my portfolio website, I'm confident I can complete Reebews in much less time than originally anticipated.

The skills I've developed, combined with modern development tools, have transformed what once seemed like an insurmountable challenge into an achievable goal.

What's Next?

Reebews isn't just another review platform – it's a solution born from real frustration and genuine need. Every feature is designed to address the specific pain points I experienced as a small business owner trying to compete in review-driven marketplaces.

In my next blog post, I'll dive deeper into the technical process, the challenges I'm solving, and the specific features that make Reebews different from existing solutions.

Until then, remember: every successful product starts with someone who refused to accept "that's just how things are."


Building Reebews has been a journey of persistence, learning, and growth. If you're a fellow entrepreneur struggling with similar challenges, I'd love to hear your story. Connect with me on [LinkedIn/Twitter] and let's share our experiences.

S
By Shreyans Jain
Last updated: Jun 19, 2025
Comments
0

Join the conversation

Sign in with Google or GitHub to share your thoughts

Loading comments...