Minotoro Founding Team

Building Minotoro Together: Welcoming Our Third Founder and CTO

Every product has a moment where vision meets reality.

For Minotoro, that moment is now.

What started as a conviction – that fans deserve a better, fairer way to participate in sports – has grown into a functioning platform, a first test phase, and a fast-growing community. But as our system matures, one thing has become clear: to build fan finance at scale, technology is not just an enabler. It is the foundation.

That’s why today we’re taking the next step in Minotoro’s journey.
We’re welcoming a third founder and Chief Technology Officer to the team.

This isn’t just a new hire. It’s a strategic and cultural milestone.

 

Why a CTO – and Why Now?

Minotoro was never built to be a quick experiment.

From the very beginning, the ambition has been clear: create a regulated, transparent, and scalable alternative to traditional sports betting – one that is rooted in real performance, not odds or chance.

Our first phase proved the concept. Fans engaged. Tokens reacted to performance. The model worked.

Now the challenge shifts.

The questions are no longer “Does this idea make sense?”
They are “Can this system scale?”, “Can it remain robust under regulation?”, and “Can it deliver trust and reliability over the long term?”

Those are not marketing questions.
They are deeply technical ones.

To answer them properly, Minotoro needed technical leadership at founder level, someone who doesn’t just execute a roadmap, but helps define it.

 

From Two Founders to Three

Minotoro was founded by Thekla and Dominik with a shared belief: that fans should be participants, not products.

One founder brought the vision, the strategy and industry insight.
The other brought business development and operations.

Together, they shaped Minotoro’s philosophy: no betting, no odds, no exploitation – just real performance, real participation, and clear rules.

As the platform evolved, it became obvious that technology could no longer sit behind the vision. It had to sit next to it.

That’s where our third founder comes in.

 

Meet Our New CTO (and Co-Founder)

Armen joins Minotoro as Chief Technology Officer and Co-Founder.

We’re intentionally keeping the spotlight on why this role matters before listing titles or achievements because what defines this partnership is alignment, not CV lines.

That said, Armen brings over a decade of experience in IT development, consulting and project management. Alongside this, he has spent more than ten years working as a full-stack developer, building and scaling digital products across different industries.

Beyond his technical expertise, Armen has also founded and led multiple companies, gaining hands-on experience in building teams, shaping product strategy, and turning ideas into operational realities.

What stood out to us wasn’t just technical excellence – it was his mindset.

 

Technology as Trust Infrastructure

At Minotoro, technology is not just about features.

It’s about trust.

Fans need to trust that performance data is accurate, token mechanics are transparent, systems behave predictably, and rules don’t change mid-game.

That requires more than fast development cycles. It requires thoughtful architecture, clear assumptions, and long-term thinking.

Armen shares this perspective deeply.

From the first conversations, it was clear that we weren’t just discussing how to build features: we were aligned on why they should exist and how they should behave under pressure, scale, and regulation.

That’s the kind of thinking Minotoro needs as we move into the next phase.

 

What Changes With a CTO at Founder Level?

Bringing a CTO into the founding team changes the dynamic, in a good way.

Product and technology become one conversation.
Decisions about UX, performance metrics, and system behaviour are now made with technical reality built in from the start.

Scalability is designed, not added.
Instead of retrofitting infrastructure later, scalability becomes part of the core design philosophy.

Regulation is built into the system.
Compliance isn’t treated as a constraint, it’s treated as a design parameter.

The team gets clear technical direction.
Engineering culture, tooling, and standards are shaped early, not patched later.

In short: Minotoro becomes more resilient.

 

Building This With You

Minotoro has always been built in public – with feedback, testing phases, and an engaged early community.

Welcoming a third founder doesn’t change that.
It strengthens it.

We’re excited to build what comes next and we’re glad you’re part of the journey.

This is just the beginning. Let´s tackle this together!