
EPC · 7 min read · 2026-05-06
EPC pass-through and the contractor tech gap
Why mid-tier contractors operating under EPC inherit operational complexity their toolkit was never built for — and where the unowned middle of the LATAM software market sits.
The pass-through pattern
In a typical mining or large-civil EPC contract, the asset owner (Anglo, BHP, Antamina, Cementos Argos) hires a Tier-1 EPC integrator. That integrator subcontracts execution to a Tier-2 contractor — your CUMBRA, COSAPI, OHLA, ENAEX, MILICIC. The contractor inherits everything operational: dotación, alimentación, alojamiento, valorización, SSOMA, almacén, transporte, capacitación. The owner audits the outcome; the integrator scopes the scope; the contractor *runs the operation*.
This pass-through is the structural reason why the contractor is the under-served buyer in industrial software.
Why the standard toolkit doesn't fit
ERPs (SAP, Oracle, Defontana) were designed for the asset owner or the integrator — entities that need consolidated financials, asset registers, capital project tracking. They were not designed for the contractor managing 14 fronts, 30 sub-contractors, rotating 20,000 colaboradores across three camps under three different SSOMA matrices for three different mining clients with three different SAP feeds.
Vertical mining-software (Hexagon, Modular Mining, Maptek, Micromine) sits at the geology-and-fleet layer. It tells the owner where the ore is and how the haul trucks are routing. It says nothing about whether the contractor's roster matches the headcount that just billed alimentación.
Global digital-engineering shops (Globant, BairesDev, Encora) treat heavy industry as one vertical of many. They build apps; they do not build operations.
What the contractor actually needs
The contractor needs software that bends to *its* protocols, not the client's reporting format. It needs to absorb heterogeneity — accept that Anglo wants a Power BI feed and Antamina wants a flat-file extract and BHP wants a SAP IDoc. It needs to fold compliance into the workflow so SUNAFIL or NOM or DS594 audits are a query, not a sprint.
That layer doesn't exist as a package. So contractors build it themselves in Excel — until Excel breaks at 4,000 colaboradores.
What sits in the middle
The unowned middle of the LATAM market is the operational software for contractors that the standard ERP doesn't model and the vertical mining stack doesn't reach. It's where Logiflex lives. It's where 20+ projects across CUMBRA, COSAPI, ENAEX, OHLA, La Arena, MILICIC, Hanna, CASA, and similar operators have shipped accelerators that bend to each contractor's reality.
The operational layer doesn't need to be reinvented every project. It does need to be customized every project. That's the bet behind 60% pre-built / 40% customized.
More from the field
Valorización · 6 min read
Why valorización contratista cycles eat your cash
A 5-day delay in the valorización cycle of a 5,000-worker contract under Anglo SAP can absorb a month of operating cash. The hidden cost of mapping every client format manually.
Roster · 5 min read
When Excel breaks: the 4,000-colaborador inflection
Excel scales linearly with formula complexity, then collapses. The exact inflection point we see across mining and construction contractors is somewhere between 3,500 and 4,500 colaboradores per project.