Leadership | Soluntech - The People Responsible for Getting it Right | Soluntech
The Protocol Guardians
System Status: Active

The people
responsible for
getting it right.

Most software fails because the wrong decisions are made too early.
This is the team responsible for making sure that doesn’t happen.

Leadership matters
more than
execution.

Most teams don’t fail because they can’t build. They fail because execution only amplifies decisions. If the decisions are wrong, speed makes it worse.

The wrong thing gets built

Building features that don't solve real problems.

The system doesn’t scale

Architecture that collapses under real-world growth.

Decisions without validation

Guesswork disguised as strategy.

The Mandate

This team is not here
to manage projects.

They are responsible for preventing costly mistakes before they happen. Because once software is built, fixing the wrong decisions is expensive.

01

Solving the right problem

02

Ensuring real-world workflow fit

03

Designing for evolution

04

Preventing costly mistakes

Strategic Alignment

Core Leadership.

Business, execution, and team alignment.

Alejandro Zakzuk

Alejandro Zakzuk

CEO

Primary Focus

Making sure the right problems are being solved before anything is built.

Decision Logic

"If it can't be validated in 4 weeks, it's too complex to build yet."

How he thinks

Most software fails before a single line of code is written — in the decision phase. His role is to remove guesswork and bring clarity to what actually needs to be built.

Risk Mitigation Active

Teams investing in products that don’t deliver real business outcomes.

Fernando Llinas

Fernando Llinas

COO

Primary Focus

Turning validated ideas into reliable execution.

Decision Logic

"Consistency is the only metric that matters at scale."

How he thinks

Execution is not about speed — it’s about consistency and control. A system that works once but fails under pressure is not a solution.

Risk Mitigation Active

Projects that ship but don’t hold up in real-world conditions.

Mariana Veron

Mariana Veron

Head of Human Resources

Primary Focus

Building teams that can deliver consistently, not just once.

Decision Logic

"The best code comes from the most aligned teams."

How she thinks

Software outcomes are a reflection of the people behind them. Strong systems require aligned, accountable, and stable teams.

Risk Mitigation Active

High turnover, misalignment, and delivery inconsistency.

Operational Integrity

Systems & Technology.

Who ensures this works in practice.

Santiago Blanco

Santiago Blanco

Head of AI Engineering

Focus

Turning data into systems that improve decisions over time.

Decision Logic

"AI must compress the time between 'I wonder' and 'I know'."

How he thinks

AI that doesn’t change outcomes is just noise. The goal is not to add intelligence, but to make systems learn from every interaction.

Risk Mitigation Active

AI implementations that look impressive but fail to deliver real operational value.

Diego Barrera

Diego Barrera

Head of UI/UX

LinkedIn

Focus

Ensuring what gets built actually works for real users.

Decision Logic

"Design is not a layer; it's the logic of the system."

How he thinks

A product that looks good but doesn’t fit real workflows will fail. Design is not about screens — it’s about behavior.

Risk Mitigation Active

Software that is technically correct but unusable in practice.

Carlo Riveros

Carlo Riveros

Head of DevOps

LinkedIn

Focus

Designing systems that scale and evolve without constant rebuilding.

Decision Logic

"Build for evolution, not just for today's requirements."

How he thinks

If a system can’t adapt, it becomes a liability as the business grows. Infrastructure must support learning, not just execution.

Risk Mitigation Active

Systems that break under growth or require costly rework.

Estefanía Marin

Estefanía Marin

Head of QA

LinkedIn

Focus

Preventing failures that only appear after launch — when they are most expensive to fix.

Decision Logic

"Quality is the absence of surprises."

How she thinks

Quality is not something you test at the end. It must be built into every step to ensure systems work under real conditions.

Risk Mitigation Active

Hidden issues that turn into costly operational problems after deployment.

Decision Velocity

Faster decisions.
Zero guesswork.

Our leadership structure is designed to compress the time between problem identification and validated solution. We don't just build; we decide with certainty.

High

Capital Efficiency

Eliminating waste through early validation

Critical

System Reliability

Built for high-stakes performance

Rapid

ROI Discovery

Compressing the time to validated truth

Proven

Strategic Success

On every validated roadmap

The Decision Lab

Before any project hits the engineering phase, it passes through our leadership "Decision Lab." Here, we stress-test assumptions, model ROI, and ensure the system is built for long-term evolution.

Assumption Stress-Testing
ROI Modeling & Projection
Architectural Evolution Audit
Workflow Behavioral Analysis

What this
means for
you.

You’re not relying on execution alone. You’re relying on a team designed to prevent failure before it happens.

Decisions made with clarity

Waste reduced early

Systems work in real conditions

Software evolves instead of burdening

Start with clarity.

If you’re unsure what to build next, or whether your current system will scale, starting with validation is the safest decision.