About Daniel Mendiola

Building enterprise software since 1999.

I am Daniel Mendiola, CTO and co-founder at AGo ERP. Working directly with companies shaped how I understand technology: software should follow how the business works, not the other way around.

I work remotely from Montevideo, Uruguay, and I am open to international collaboration with teams and companies that need technical judgement and continuity.

Role
CTO · AGo ERP
Since
1999
Base
Montevideo, Uruguay
Modality
Remote · international
DM

Daniel Mendiola

CTO and co-founder at AGo ERP

How the work connects

Business

How the company sells, buys and collects

Systems

ERP, CRM and integrations that sustain the operation

Decisions

Traceable information to decide with the company's own data

What I work on today and how I approach it, without an inventory of tools.

What I work on

Six fronts that hold an enterprise system together

This is not a list of loose technologies: these are the responsibilities I take on when a business depends on its software every day.

01

Enterprise software

ERP and CRM built for daily work: sales, purchasing, stock, collections, invoicing and customer service. The system has to serve the person using it for eight hours a day.

02

Cloud on AWS

Infrastructure that can be explained: what runs where, what it costs and what happens if something fails. No black boxes or services nobody on the team understands.

03

Integrations

Connecting what already exists instead of replacing everything: APIs, external services and data that today is copied by hand between systems.

04

Traceability

Every operation leaves a record: who, when and with what result. It is the basis for being able to audit and to improve the process.

05

Continuity

Modernising in stages without stopping the operation: backups, separate environments and partial deliveries that coexist with what works today.

06

Data and applied AI

Scoped, measurable use cases with the company's own data. The concrete problem first; the tool afterwards, with a person reviewing what matters.

Leadership

A CTO also organises the work, not only the architecture

Running technology in a company that operates every day involves decisions that never appear in a diagram: what gets priority, what gets postponed and who is accountable for sustaining it. These are the rules I work by.

01

Decisions close to the people who execute them

Whoever serves a customer, sells or goes out into the field knows where the process gets stuck. Listening to that first avoids building the wrong solution with a lot of technical tidiness.

02

Document so nothing depends on one person

A system only its author understands is an operational risk. Writing down decisions and procedures is part of the job, not an extra task.

03

Modernise in stages, without stopping the operation

I do not propose shutting down what works to start from zero. I prefer partial deliveries that coexist with the current system and can be validated in real use.

04

Automate the repetitive, not the judgement

AI contributes when it classifies, summarises or answers what is already resolved. Sensitive decisions still have a person behind them, with the context in view.

What I expect from a team and what I offer

I work with people who ask before assuming, who speak up when something does not add up, and who leave the code and the processes a little better than they found them. On my side, the commitment is to hold the direction, explain the reason behind each technical decision and not change priority every week.

My background starts in software development and applied mathematics, and grew into architecture, integrations and data work with a business reading. I am open to international CTO roles and to collaborating with teams that need technical continuity.

Role
CTO & co-founder · AGo ERP
Since
1999
Base
Montevideo, Uruguay
Modality
Remote · distributed teams
View background on LinkedIn

Next step

If your business depends on a system that no longer keeps up, let's talk

Tell me how the operation works today and which decisions you need to make. I answer with an honest diagnosis, even if the answer is that nothing needs to change yet.