The First Review: How a Reddit DM and a Handrun Script Became the Most Validating Moment of My SaaS Building Story (So Far)
This is part of an ongoing series documenting BasinCheck's journey from zero to... wherever this goes.
If you've been following along, you know the origin story by now.
I'm a marketer who spent a year vibe-coding an oil & gas safety audit tool called BasinCheck. First post covered the build. Second post covered the moment a paying customer made it real.
This one is about what came after that, and honestly, it might be the most meaningful milestone yet.
A Reddit Comment That Changed the Product Roadmap
A few months back I was active in r/oilandgas. Not spamming. Just genuinely being useful: answering questions, pointing people toward resources, talking shop with safety managers and contractors who were dealing with real compliance headaches.
I made a comment offering to help anyone struggling with OSHA 300 CSV validation. The ITA portal is notoriously finicky. OSHA's own template has formatting quirks that their submission system rejects silently. It's a known pain point in the industry and I had been working on a solution for it.
Steve saw the comment. He reached out.
The Thing I Did That Didn't Scale
Here's the part I want to be transparent about, because I think it's actually the most important part of the story.
BasinCheck existed at this point, but the CSV validator wasn't fully wired into the product yet. It lived in a custom script on my machine - an early beta version of what I already knew would become a core feature.
So I asked Steve to send me his file.
I ran it through the script manually. Identified the formatting issues. Fixed them. Sent him back a clean CSV. No charge. Just a real user, a real file, and a real test of whether the thing actually worked outside of my own machine.
He submitted it to OSHA's portal. It went through first try.
I wasn't guessing at the roadmap anymore. I had proof of demand wrapped in a solved problem, delivered by hand, to one specific human being who needed it.
Paul Graham calls this "doing things that don't scale." I was living it without fully realizing it.
Then, Weeks Later: A Review I Didn't Ask For
I woke up one morning to a notification. Steve had left a public 5-star review on Capterra. Unprompted (here's the proof)
He wrote about the old process: the finicky templates, the OSHA ITA rejections, the annual headache, and then:
"I exported my CSV and let BasinCheck do the rest. Once they reviewed and validated my file, I was able to submit with zero issues. Knowing what the process was like previously, I can't imagine not utilizing BasinCheck again."
He didn't know, and I hadn't told him, that when he submitted that review, the beta script I had run on his file manually was already live inside BasinCheck as a fully built feature. The future he was describing had already arrived.
That loop closed in a way I didn't plan but will never forget.
Why the First Review Hits Different Than the First Customer
The first paying customer is a transaction. Someone bet money on your idea. That's huge, don't get me wrong.
But a public review is something else entirely. Nobody pays you for it. Nobody reminds you to do it. It's a person sitting down, finding the words, and deciding that what you built is worth talking about publicly.
And Steve wasn't even a paying customer. He was someone I helped for free on Reddit.
He owed me nothing.
When he wrote that review, he wasn't doing me a favour. He was documenting a workflow improvement in his own professional life. I just happened to be the tool that made it possible.
That reframe, from "my user left me a review" to "my user documented their own success," changed how I think about everything going forward.
What This Means for the Build
The CSV validator is now a core BasinCheck feature. It's live. It works. It's been validated by a real workflow, a real user, and a real submission to a real government portal.
More importantly, the method of discovering it, going where the pain is, offering help before asking for money, doing it manually first, is now how I think about every future feature.
The next thing I build for BasinCheck won't start with a Figma mockup. It'll start with a Reddit comment.
BasinCheck is a safety audit and compliance tool built for oil & gas SMBs. We're early, we're building in public, and we're just getting started: basincheck.com
