In 2008, Alejandro Planas had a problem that now sounds almost antique. His employer needed computing capacity for a temporary project. The conventional answer was to buy servers, install them, use them briefly and then watch the expensive metal gather dust. Amazon Web Services was young, but its proposition was already radical: take infrastructure when you need it and give it back when you do not. Planas saw the immediate fix. He also saw a company hiding inside it.
"If this problem existed for us, other companies surely had it too," Planas later recalled. In 2012, he co-founded Miami-based Escala 24x7 to help Latin American businesses adopt AWS. The bet was not that companies wanted servers in someone else's building. It was that they wanted speed without waste, and would pay for an expert to carry the operational risk between those two words.
That distinction matters. AWS sells computing, storage and a long menu of software services. Escala sells judgment around them: what to move, what to rebuild, what to secure, what to monitor and what to switch off before the invoice arrives. It begins with an assessment and architecture plan, implements the migration, then offers managed operations, security, data engineering, artificial intelligence and cost governance. Projects open the door. Round-the-clock operations keep the relationship alive.
The first failureCloud economics met human habits
The first thing to fail was not the technology. It was the assumption that a migration automatically produced savings. A data center rewards buying enough capacity for the busiest day. A public cloud rewards matching consumption to the hour. Move an oversized server without changing it and the meter simply runs somewhere else. Leave test environments on overnight, duplicate data or ignore idle instances, and the promise of thrift becomes a surprisingly creative bill.
The second obstacle was trust. Planas has said that traditional banks and manufacturers initially viewed the cloud as risky. Their concern was rational: a small efficiency gain means little if a payment system stops, a regulator objects or a plant loses access to operational data. Escala's response was to wrap migration in controls - security assessments, compliance, disaster recovery, governance and 24/7 support - and to accumulate AWS competencies that gave cautious buyers an external signal of delivery experience.
The technology is only an enabler. The hardest part is changing processes, people and the way of thinking about working in the cloud.Alejandro Planas, CEO and co-founder
That is what changed the sales conversation. Instead of asking a chief information officer to believe that cloud was safe, Escala could show how it would be operated. Instead of promising an abstract transformation, it could point to recovery targets, incident rates, deployment times and cost controls. The company's public case library is unusually numerical for a consultancy: an Allianz migration covering more than 200 servers and critical applications; a Chilean workload with a reported 40 percent execution-cost reduction; a Salvadoran banking application with 99.95 percent availability; an energy data platform with near real-time analytics.
What it costsNo menu, because no two messes match
Escala does not publish a rate card, and there is no credible public total for what a typical engagement costs. That is less evasive than it sounds. A price depends on the number and age of workloads, data volumes, required downtime, industry controls, recovery objectives and whether the customer buys a migration or hands over continuing operations. The relevant calculation is total change cost: professional services, AWS consumption, internal staff time, training, parallel systems and the risk reserve for a failed cutover.
The cleanest public evidence of the economic model comes after migration. Establishment Labs, a medical-technology company, moved to AWS with Escala in 2021. A later FinOps project adjusted application virtualization to actual usage patterns and reported a 65 percent reduction in annual operating costs. Another published case reduced infrastructure costs by as much as 42 percent and shortened deployments from hours to minutes. Those are customer-specific results, not a general promise, but they show where the work sits: measurement, architecture and operating discipline, not a ceremonial transfer of machines.
The positionA specialist between the platform and the boardroom
Escala occupies an awkward but valuable layer of the market. It competes with global systems integrators, regional cloud consultancies, AWS's own professional-services organization and customers' internal platform teams. Its difference is concentration. The company spent more than a decade going deep on AWS while building local teams and customer evidence across Latin America. It now claims more than 300 AWS certifications, 14 competencies and over 1,500 implementations.
Its customer list reveals the reason for the focus. Insurers such as Allianz and Grupo San Cristóbal cannot treat availability as a design flourish. Flybondi sells airline seats into sharp traffic peaks. Pampa Energía and industrial groups run systems whose failure leaks into physical operations. Banks and fintech companies face security and compliance constraints while customers expect instant service. These buyers are not purchasing a cloud account. They are purchasing a smaller probability of an expensive surprise.
The portfolio has broadened around that core. Managed Services, including the Cloud EMx offer, covers monitoring, incident handling, governance, vendor escalation and FinOps. Security work spans assessments, remediation and managed controls. Data teams build pipelines and analytics platforms. The newer AI practice combines AWS services with defined jobs: document processing, help-desk automation, contact-center analysis and generative models connected to enterprise systems. This is sensible adjacency, because an AI pilot cannot reach production if its data, identity and operating controls are still improvisations.
Customers can assemble the same capabilities in other ways. A global integrator offers scale and a broad vendor bench. A smaller consultancy may be cheaper and closer to one application. An internal platform team keeps knowledge inside the company, while AWS Professional Services provides direct access to the platform's expertise. Escala is most persuasive in the middle: organizations large enough to need formal controls and continuous coverage, but unwilling to build every specialty in-house across several countries. Its regional engineers can interpret local operating realities while a common AWS practice supplies repeatable methods. The tradeoff is concentration. A buyer pursuing Azure, Google Cloud or a deliberately balanced multi-cloud architecture should test whether Escala's newer partner network offsets its long-standing AWS center of gravity.
The inflectionWhy Stefanini bought 60 percent
By 2023, Escala said it had passed $50 million in revenue. In December 2024 it signed a five-year strategic collaboration agreement with AWS to accelerate cloud and generative-AI adoption in Latin America. Four months later, the global technology group Stefanini acquired a 60 percent stake. The purchase price was not disclosed. Stefanini called it one of the five largest investments in its history, while Escala publicly targeted $100 million in 2025 revenue. That target should not be confused with a reported result.
The logic runs both ways. Stefanini gets a specialized AWS engine, hard-won partner credentials and a route into enterprise cloud work across the region. Escala gets distribution, larger delivery capacity and access to Stefanini's automation, cybersecurity, analytics and customer-experience portfolio. In early 2026, Escala updated its visual identity to align with its parent while stressing that its leadership, autonomy and customer arrangements would remain. Later that year, AWS named it Consulting Partner of the Year for Northern Latin America.
The tension is familiar: the focus that makes a specialist attractive can blur inside a broad services group. Escala's advantage has been a clear answer to “Why you?” - AWS depth, Latin American operating knowledge and engineers accountable after launch. The acquisition works if Stefanini expands the surface area without sanding off that answer.
The stealFour moves worth copying
Escala began with an expense customers could see: idle infrastructure. Concrete waste is an easier opening than a broad transformation pitch.
A migration is episodic. Monitoring, incident response, security and FinOps turn delivery knowledge into a recurring relationship.
Platform competencies, joint selling and reference customers reduced perceived risk in markets that were skeptical of cloud.
Availability, incident reduction, deployment time and cost savings make a technical project legible to an executive buyer.
There is a fifth move beneath the others: expand by following the failure chain. Migration exposes weak governance. Governance exposes security gaps. Cost analysis exposes poor architecture. AI exposes broken data. Each service can be the answer to the problem created or revealed by the previous one. That is a more durable roadmap than adding whatever acronym is fashionable this quarter.
When this playbook does not work
- The buyer is committed to another single-cloud platform and does not want AWS depth.
- The workload is tiny, disposable or well served by commodity hosting.
- Leadership expects savings without changing architecture, governance or user behavior.
- The service provider cannot turn bespoke project knowledge into repeatable operating practice.
- Platform dependence becomes stronger than customer understanding.
Escala 24x7's story is not really about predicting that cloud computing would grow. Plenty of people did that. It is about noticing where the simple story stopped. Renting a server solved the purchase problem. Someone still had to design the system, persuade the risk committee, move the data, answer the alarm at 2 a.m. and explain the bill on Monday. Escala made that unfinished work the product.