the person behind kleosvic.
where it started
it started with a small program written in batch. it was called dan. dan appeared on screen, showed a few options, and when you pressed 1, it opened the corresponding program. it was rudimentary, but it was the first time the computer did something that existed because i had imagined it.
that pattern would repeat for years. if something did not exist, the instinct was to try to build it.
the projects
dan
a batch launcher. a handful of options on a screen. the first thing that existed because i wanted it to.
gamedev
the motivation was simple: i liked playing games and wanted to make the kind i would want to play.
mathora
i liked mathematics and wanted to build a game that made learning them more fun. it became too big for one person, but it was the first time i dealt with a real product — websites, https, seo, infrastructure.
elcafé
i had seen newsletters like morning brew and saw a gap in spanish. i wanted to create something i myself would want to read. it reached about 30 subscribers before it stalled. it taught me about seo, consistency, teams, and the real cost of maintaining a product.
the shift
for a while, the approach was: find an idea with a market and turn it into a project. over time, that stopped being enough.
the change was not technical. it was a different question. instead of asking what could work, i started asking: would i use this? that pattern had been there from the beginning — games i wanted to play, mathora because i wanted to learn differently, elcafé because i wanted that newsletter in spanish. kleos is the conscious continuation of that pattern.
why i build
“would i use this?”
that question is now the starting point for everything. not whether it has a market, not whether it could grow, but whether it is something i myself would want to exist. it is a simple criterion, but it changes what gets built and why.
technology
there is a feeling that part of technology lost something. the technology that appeals to me is simple, curious, experimental, direct — made because someone wanted to make it. there is too much software built around subscriptions, artificially locked features, and experiences designed around the business model rather than the product.
the user should not be artificially limited just because they do not pay a recurring fee. if a premium tier exists, it should add real value, not simply strip away what the product could already do.
contradictions
building for yourself means you understand the problem deeply — because you are the user. but it also means you might assume that what you want is what everyone wants.
i enjoy building much more than marketing. that has meant that many projects get built but never quite reach the people they were made for. that is something i am still working on.
there is a lot of trust in my own judgment. that can be a strength, but it can also become a blind spot.
kleos
kleos is not just another project. it is the place where everything i have learned so far comes together.
after several projects, the criterion became clear: build things that matter to the people who use them. not because they need to be big, not because they need to be a success story, but because something that is genuinely useful to someone else is worth building.
i want kleos to be the first thing i can truly be proud of. not in a loud way. in the quiet way of something that works and that someone, somewhere, actually uses.
now
currently in 1st of bachillerato, heading toward mathematics and computer science. still building, still learning, still figuring out how far this can go.
i do not want to build things just to say i built them. i want to reach a point where i can look at what i made and think: this is useful to someone.