Vipin Maurya

I ve been working on ReviewCook ( or Review Cook) and it started with a problem I kept noticing with local businesses: getting customers to actually write a Google review is often harder than getting them to have a good experience.

So we re trying a different approach.

Instead of asking customers to figure out what to write, they can scan a QR code, share their experience by voice or text, and our app turns that into a review draft that they can edit and submit themselves.

What I m most interested in right now is the friction between I had a great experience and I ll actually write a review.

Doing one of these because I get more from reading what others are building than from any newsletter.

I'll start.

We re all builders here, which usually means at some point we looked at something clunky, slow, or frustrating and thought, there has to be a better way. Most products don t start with a grand vision; they start with irritation, curiosity, or firsthand pain.

I d love to learn more about how others here have navigated that journey:

How did you uncover the problem you decided to work on?
What signals told you this problem was worth solving?
How did you validate (if at all) whether people would actually pay for a solution?
Has your product stayed true to the original problem, or did it evolve into something different?
What surprised you the most along the way?