We are a tech company based out of Patagonia that delivers world-class enterprise and mobile applications to the world. Our mission is a simple yet powerful statement: "To build great software." We do so with passion and a relentless commitment to quality and innovation.

10 - 49
Show all +
Buenos Aires, Argentina
  • Buenos Aires, B
other locations
  • 636 Broadway
    New York City, NY 10012
    United States
  • Patagonia
    Cipolletti, R 8332


Key clients: 
  • IDB 
  • Argentinian Government
  • TVision
  • Messi
  • Connect Americas
  • CAF
  • MoovReeboot with Joe
  • Avantrip
  • Mercado Libre


Sort by

Web Development for Latin American SMB's Platform

"We have had a good collaboration and we can talk openly about topics that are working well and also the ones that aren't."

Willing to refer: 
The Project
2015 - Ongoing
Project summary: 

Patagonian Tech is the main technology partner for the platform. They provide development services, implementation, and deployment of new features using technologies such as Drupal, Grails on Java, and MySQL among others.

The Reviewer
11-50 Employees
Washington, D.C.
CTO, SMB's Platform
The Review
Feedback summary: 

The team demonstrates a good sense of project ownership and commitment. Patagonian Tech performed well in terms of quality assurance, testing, and bug reductions. The visual and functional quality of new modules and functionalities were some of their main contributions to the platform.

A Clutch analyst personally interviewed this client over the phone. Below is an edited transcript.


Introduce your business and what you do there.

I am part of the ConnectAmericas project, a platform that connects small and medium businesses in Latin America and the Caribbean. This program was launched by the IDB [Inter-American Development Bank]. We have different partners in the program like Alibaba, SeaLand, and Google. We have launched this platform to support the internationalization of the SMBs in the region. I am the CTO, leading the software development, infrastructure, and technical support.


What challenge were you trying to address with Patagonian Tech?

The project goals were to implement a software development methodology based on Scrum principles and Agile methodologies that would help us manage the project, all of the software development tasks, and the infrastructure and technological solution adjustments in a more precise and detailed way. They are providing development services, implementation, and deployment of new features within our system.


What was the scope of their involvement?

The team changes depending on the activity backlog because it varies and it is updated every two weeks. The number depends on the required level of effort. We have the flexibility to increase or decrease capacity but we usually work with four developers, one architect, one UI/UX [user interface/user experience] designer, and two other resources for quality control.

We are using Drupal for the core content management part and we did some other custom developments on Drupal as well. We mainly use Grails on Java for the backend and Angular for the frontend. In terms of database, we are using MySQL but we have some other technologies in other platforms.

How did you come to work with Patagonian Tech?

We chose them through an RFP [request for proposal] with the IDB, which was necessary for this type of contract. These are always done through RFP's that are published for international firms. I was not involved in the selection process but different criteria were taken into account, such as the proposed methodology, the assigned resources, proposals for the project, and the company's background or previous experience with the IDB as well as other organizations. We were very careful with the references topic and we found a cost/benefit balance in finding a firm that had more knowledge of the Latin American market in terms of SMB's.

What is the status of this engagement?

We have an ongoing relationship and we've done several renovations. At this time, they are our main partner in terms of technology development.


Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?

Patagonian Tech does quality assurance, testing, and reduces bugs in the production. We had another firm that was previously in charge of this, but Patagonian Tech handles all of it now. This is one of the main insights. Another important contribution was the visual as well as the functional quality of the new modules and new functionalities that were implemented.

How did Patagonian Tech perform from a project management standpoint?

We used JIRA, in which we’ve grouped all activities and epics. Epics are the big functionalities of the system, and from the epics, we define a series of user stories and we have everything located there: the epics, the different impacted users, granular activities, and techniques that are connected to an effective UX execution. In JIRA, we have all of the abilities, testing tickets, and different releases that are going into production. We have documented and organized all products or tickets that are going to be rolled out in every version.

All of the communication is managed through JIRA, even the infrastructure is also there. The business communication is independent.

What did you find most impressive about Patagonian Tech?

The main highlight is the sense of project ownership and the commitment level of all the people participating in the team. They understand the sensibility and other urgent topics and critical aspects of the business.

Are there any areas Patagonian Tech could improve?

The main area of improvement at the moment are the instances that are not within the frame of the project. Since it’s the same team that implements new initiatives and bug fixes, they can better communicate their findings within the platform and attack certain urgent topics that we tend to disregard. Perhaps, we are not communicating the cases in detail, but it is something we can start improving.

Overall Score We've had a good collaboration and we can talk openly about topics that are working well and also the ones that aren't.
  • 4.5 Scheduling
    We are trying to be precise and follow up on panoramas, but priorities are always varying depending on certain necessities.
  • 4.0 Cost
    Value / within estimates
    Their cost is average in the market.
  • 4.0 Quality
    Service & deliverables
    Generally, we are very satisfied. We should pay more attention to some details at visual or functional levels.
  • 5.0 NPS
    Willing to refer