This website uses cookies
Read our Privacy policy and Terms of use for more information.
Then I build on it, whether that's an enterprise content supply chain, a tool for doctors, or a new way to watch football. Same mind, same method: question the obvious, follow the research, ship something real.
It's how I keep my thinking sharp, an idea doesn't really count until someone can put it to use.
Each of these started as a problem I couldn't stop turning over.

A platform for healthcare professionals who want to communicate with scientific rigor without borrowing the tactics of the charlatans they're losing attention to.
I kept watching brilliant clinicians lose the room, so I went deep into the research on how people actually change their minds.
I didn't want to produce another static guide, I wanted the knowledge to be usable in the moment, and that's where AI became the natural fit. I built the tool.
I wanted it free, but real APIs and infrastructure cost money, so it's priced to stay sustainable.

A football-culture brand built around one uncomfortable question: are we watching the game, or are we watching what we want to see?
It began with a way of seeing football I couldn't find anywhere else, and that pushed me into the data, far enough that I ended up building my own performance metrics for players and teams.
Bringing AI in wasn't a strategy; it was the obvious next move once the questions outgrew a spreadsheet. Today it's scout analytics, editorial, and apparel.
These look like different obsessions (football, medicine) but they're the same mind solving the same kind of problem, and it's the one I solve professionally too.
Whether it's an enterprise content supply chain or a side project, I work the same way: understand how things actually run before changing them, fix what's broken before automating it, and bring technology in only once the process underneath is sound.
I call it Fix to Flow (map, fix, flow, prove).
You don't automate a broken process; you automate the chaos.
Everything I build, paid or not, runs on that conviction.
The Signal and Sir Balone are independent projects, unrelated to my current or any past employer. The views here are my own.

I'm Juan Carlos Vásquez. For ten years I've turned complicated, specialized knowledge into content and systems people can actually use, mostly inside large organizations, sometimes in fields I had no business wandering into.
What connects all of it is a single habit: distrust the obvious, popular, accepted answer, find the angle everyone missed, and keep going until the idea works in someone's hands.
The projects here are what that habit produces.
Why PixelDVX? The name carries the cross-disciplinary path behind the work: a trained graphic designer (Pixel), obsessed with experience and how people actually use things (X), grounded in real technical and development knowledge (DV), all of it pointed at one conviction: building things for people, not for their own sake (DVX).