About

Hi 👋 I’m Jorge, co-founder and CEO of Zentrik. Software teams can now build faster than they can decide what deserves to be built. We’re building Zentrik so product teams can trace a bet to the customer evidence behind it, test it before scope hardens, and carry the reason into Jira and AI builders. I’ve spent more than a decade taking language systems from idea to enterprise production. At Inbenta, systems we deployed answered more than a billion questions before RAG became common shorthand. At Directly, I led AI solutions built around human-in-the-loop training and evolving support models. I also teach generative AI and run hands-on product workshops. Here to meet people who care about better product judgment, useful AI, and what happens after the demo.

Badges

Bright Idea 💡
Bright Idea 💡
Tastemaker
Tastemaker
Tastemaker 10
Tastemaker 10
Tastemaker 5
Tastemaker 5
View all badges

Maker History

  • Zentrik
    ZentrikCustomer signal to products your customers love
    Oct 2024
  • 🎉
    Joined Product HuntMay 30th, 2024

Forums

We made product delivery faster. Then lost the customer reason.

Today we launched Zentrik Product Loops because as our own workflow got 10x faster, it became easy to lose the reason behind the work.

A sales call became a summary. The summary became a backlog item. The item became an agent prompt. By delivery, the customer reason was hard to inspect, and what would count as proof was even harder.

1mo ago

I hired a real engineer to review my vibecoded app, and watched her face while she read it

Paid someone to do a code review last week, first actual engineer to ever see what I'd built. Watched her scroll for a solid two minutes without saying anything. Then: "okay, so, this works, but why does this file talk to three different places to do one thing?"

I didn't have an answer. I'd asked the AI for a feature, it worked, I moved on, asked for the next feature, it worked, moved on again. Never once looked at whether feature three quietly duplicated logic from feature one. The app functioned perfectly the whole time. It just also had, apparently, three slightly different versions of the same idea living in different corners of the codebase.

What got me wasn't that it was bad, she was actually kind about it, said this is completely normal for anything built fast. What got me was realizing I'd been measuring progress purely by "does it work when I click it," and that measurement had been quietly lying to me the entire time.

I don't think the answer is doing it slower from scratch. I think it's that at some point, someone who actually reads code needs to look at the whole thing, not feature by feature.

⚫ The Feedback Black Hole

The feedback black hole in creative projects...
You leave a comment.
Someone makes changes.
A new version appears.
A few weeks later, nobody remembers why that decision was made.
For creative teams, reviewing is not just about adding comments - it s about preserving the thinking behind the work.
Curious:
How and where does your team review images, videos, or creative assets today?
And the bigger question:
Does your review history stay connected to the project?

View more