Hi everyone,

I just released McPlugins, a suite of 4 audio compressor plugins I've been building for the past couple of years.

Hi PH community!

I m the founder of VirtualSpaces, and we re on a mission to fix the single biggest bottleneck in residential design: the "visualization gap."

Hey Product Hunt

I m the founder of ProspectB2B.com, a platform I m building to help B2B teams discover, qualify, and organize prospects more efficiently.

One thing I kept seeing in B2B prospecting is that teams don t just need more leads. They need better-fit companies, cleaner data, and a faster way to know who is actually worth reaching out to.

With ProspectB2B, we re focused on making that process simpler: helping founders, sales teams, agencies, and growth teams identify relevant companies and contacts without spending hours jumping between spreadsheets, search tools, and outdated databases.

They know you use AI.

You know you use AI.

Hi everyone!

Excited to share that my product Vocabri just launched on Product Hunt

Check it out here

You describe the workload it runs.

No picking 4090 vs A100.
No region debates.
No infra overhead.

Launching April 28 (12:01 AM PDT):
https://www.producthunt.com/prod...

Curious what s been breaking for you when running AI workloads.

Hey everyone

I didn t think I d get into an accelerator. I had no team, just an idea, VertoX. And then I got accepted. So I did what felt right at the time: I started building a team. That turned out to be my mistake.

I spent around 3 months trying to build a local team. Around 8 10 people joined and left during that time. Some did very little, some did nothing, and overall progress was almost zero. At the same time, the accelerator expected fast results, but VertoX is not a simple product; you don t build real-time voice AI in a few weeks.

In the end, I didn t pass the accelerator. But I learned something important from that experience. Early decisions matter much more than you think. I was limiting myself by focusing only on local hiring, and that slowed everything down.

I ve been building PageLens AI after seeing the same thing over and over again with AI-built websites and apps.
The product looks done .
But then you look properly and find the stuff that gets missed when people are shipping fast:
Missing security headers
Weak mobile CTAs
Poor accessibility basics
Broken social previews
SEO basics not set up

Analytics/consent problems
Confusing copy
No clear trust signals
Logged-in routes that nobody has properly reviewed
I don t think this is because builders are careless.
I think tools like Cursor, Lovable, Bolt, Replit and v0 have made it incredibly easy to build quickly, but most founders still need a proper launch-readiness pass before sending real users, investors or paid traffic to the site.
So I m building PageLens AI as launch QA for AI-built websites and apps.
The idea is:
1. Scan your site
2. Get a ranked report of what s hurting trust, SEO, accessibility, security, mobile UX and conversion
3. Export the fixes as Markdown for Cursor / Claude / Lovable / Bolt
4. Fix the issues
5. Re-scan and prove it improved
I d love feedback from other makers here:
Do you run any kind of launch QA checklist before sharing a new product publicly?
Or are most people just shipping and fixing issues after users notice them?
For context, this is what I m building:
https://www.pagelensai.com
Not looking for upvotes here, genuinely interested in whether other makers see this same gap.

Hello everyone,

I ve spent the last few weeks building Pika Review, a CLI tool designed to shorten the feedback loop for code audits.

While cloud-integrated review bots are great, they trigger after code is pushed. I wanted to shift that intelligence to the local terminal, acting as a gatekeeper for staged and unstaged changes before they ever reach a remote repository.

Key Capabilities