Built around a bet on architectural depth.
We are an engineering company built on the conviction that systems — not tools — determine whether software delivers lasting value.
The founding thesis
We were founded in 2022 in Montevideo, Uruguay, by four partners who had worked together in the technology sector since the late 2000s and wanted to build an organization focused on high-complexity software solutions — combining technical depth, product vision, and close operational collaboration with clients.
From the start, we specialized in end-to-end software engineering services: web development, Internet of Things, and embedded collaboration with client teams. Our operating model is to integrate directly into a client’s team and participate across the full product lifecycle: solution design, implementation, evolution, and long-term maintenance.
Over our first years, we worked with clients in the United States, Europe, and Latin America on technically demanding systems — cloud-based bioinformatics platforms, IoT-based neurocognitive training systems, and real-time field asset management solutions. That work built long-term relationships and established us as a trusted technology partner for organizations that need strong execution, flexibility, and technical judgment.
That track record is what positioned us to build Dap when the AI moment arrived.
The founders
Martín Fernández
CEO
Martín sets Crunchloop’s overall direction and leads the company’s client relationships. He is responsible for the strategic bet on a platform-enabled service model: combining the delivery team’s judgment with Dap as a compounding asset. His focus is on making Crunchloop the kind of partner that owns outcomes rather than staffing hours.
Iván Etchart
CTO
Iván leads Crunchloop’s technology and platform architecture. He is responsible for the technical decisions that make Dap safe, observable, and integratable with real client delivery flows. His background is in building production-grade systems where correctness and maintainability matter more than novelty.
Damián Arrillaga
COO
Damián runs Crunchloop’s operations and delivery discipline. He makes sure the company’s embedded collaboration model scales without turning into a generic staffing practice. His focus is on the operational rigor that lets senior teams work as an extension of a client’s team.
Santiago Doldán
Engagement Leader
Santiago leads how Crunchloop engages with clients day to day: onboarding, team integration, and the continuous work of aligning engineering output with business outcomes. He is the bridge between the client’s context and the Crunchloop engineers who operate inside it.
The team behind it all
Our delivery team is made of senior engineers, architects, and product-minded builders who work as embedded members of client teams. They are not interchangeable resources; they are people who take ownership of a codebase and stay with it long enough to understand its implicit context.
Dap was built from the constraints our team hit in real delivery work — and it makes the team sharper in return. The platform gives our engineers the tooling to move faster without losing oversight; the team gives the platform the judgment it needs to operate safely. Neither works as well without the other.
How we work
Our values aren't a list for show. They are the operating principles that keep us from becoming a generic engineering services vendor. Each one is tied to what a client actually experiences when working with us.
Commitment
We commit to outcomes, not just hours. When Crunchloop integrates into a client’s team, the commitment is to make the system better — to leave it more legible, more maintainable, and more agent-ready than we found it.
Ownership
We act like owners of the systems we touch. That means raising problems before they become incidents, making architectural decisions that outlast the current sprint, and taking responsibility for the long-term health of the codebase.
Motivation
We stay motivated by hard problems. The work that matters is the work that requires judgment: untangling implicit context, making implicit constraints explicit, and building systems that remain coherent as they grow.
Excellence
Excellence is the standard we apply to our own work before anyone else sees it. It shows up in the quality of the code, the clarity of the documentation, the rigor of the tests, and the discipline of the delivery process.
Trust
Trust is the currency of every client relationship. We earn it by being transparent about what we know and what we don’t, by shipping work that holds up under scrutiny, and by building Dap so that every agent action is observable, auditable, and reversible.
Where we work
We have offices in Montevideo, Uruguay; Buenos Aires, Argentina; and La Plata, Argentina. These locations are not a cost story dressed up as strategy; they are a deliberate operating choice. Time-zone overlap with the United States and Europe makes real-time collaboration with client teams practical, and the depth of engineering talent in the region is the reason we can embed senior engineers in complex client systems.
We have worked with clients across the United States, Europe, and Latin America from these bases. The operating model is the same regardless of geography: integrate with the client’s team, share context, and own the outcome.
- Montevideo—:—
- Buenos Aires—:—
- La Plata—:—
How Dap emerged
As we matured, we saw that the operational knowledge gained through delivery work could become a proprietary asset. The strategic evolution led to Dap.
This is an evolution in our business, not a replacement. We are moving from a pure services model to a hybrid model where delivery knowledge becomes intellectual property and a scalable new source of value. That does not replace our identity as an engineering partner; it deepens it.