International expansion without consolidated visibility: the hidden cost of growing without the right systems

Expanding into a new market is one of the most complex decisions that management of a midsize company can make. It requires adapting the value proposition to the local context, building relationships with customers and partners in an unknown environment and managing operations in a market with different regulations, currencies and time zones.

But there is a cost of international expansion that rarely appears in the initial business plan: the cost of managing operations in several countries when information systems are not ready for it.

This article analyzes what that cost is, at what point in the expansion process it becomes more visible and what technical architecture allows it to be solved without the need to implement a Tier I ERP, which most medium-sized companies cannot afford or need.

The problem that appears when the second market starts to work

The first international market for a medium-sized company is usually managed with efficient improvisation: a small local team, lightweight tools and a lot of manual coordination with headquarters. It works because the volume is small and because there are one or two people who are responsible for ensuring that information flows between the local market and Spain.

The problem appears when the second market starts to operate or when the first one grows to a volume level that manual coordination can no longer absorb. At that time, the company has operations in two or three countries, each with its own tools, processes and reporting format. And no one has a consolidated view of what is happening in the organization as a whole.

81 percent of global IT leaders say that data silos block their digital transformation initiatives [2]. In organizations with a presence in several countries, these silos multiply because each market tends to adopt the tools that are most accessible or most adapted to its local context [5], and no one centralizes integration until the problem is already urgent.

The Three Most Costly Operating Problems

Consolidated reporting that does not exist as automatic data

The most basic question that the CEO of a company with a presence in three countries should be able to answer is: what is the operational status of the organization as a whole this week? How many active projects or files are there in each market, what phase are they in and which are at risk of exceeding the committed deadline?

In most organizations with operations in multiple countries, that question doesn't have an automatic answer. 77% of medium-sized companies produce their consolidation reports manually [8], exporting data from each market—with different formats, in different systems, updated with different frequencies—and crossing them into a spreadsheet that someone at headquarters draws up every week or every month.

The process consumes between 10 and 20 hours of work by highly qualified people who should be making decisions, not building reports.

Coordinating distributed teams without common tools

Coordinating a geographically distributed team when there are no common operational tools means that every validation process, every work assignment and every status update requires active communication: an email, a call or a message.

This communication is not free of charge. Professionals lose an average of 9.3 hours per week in coordination and manual monitoring processes [4], and in distributed teams this cost is amplified because time differences add friction to each exchange.

The average company manages 897 different applications, of which only 28% are integrated [1]. In an organization that operates in several countries, each market adds its own tools to the ecosystem and the integration between them is increasingly difficult to manage.

The result is that the information exists—it's in some system in some country—but it's not available to those who need it at the time they need it.

Approval processes that cross borders

Any approval process that requires validation from the headquarters — a commercial proposal over a certain amount, a contract in the local market or an investment in equipment — adds a layer of complexity when headquarters and the local market don't share tools.

The usual process is email: the local team submits the request, headquarters reviews and responds to it, and the local team implements. No traceability, no record of who approved what and when, no visibility of the status of the request in real time.

20% of productivity in organizations with implemented ERP is lost in these workflow lags [6]. In organizations with operations in several countries, that percentage is conservative: approval processes that cross borders are consistently slower, more opaque, and more prone to errors than those that occur within a single market.

Why standard ERPs don't solve the problem

The obvious solution seems to be to implement an ERP with multi-entity and multi-country capabilities that covers all the organization's operations from a single platform. And, for organizations with more than 500 million euros in turnover, that solution can make sense [7].

For the growing medium-sized company —between 20 and 200 million euros in turnover, with two or three active markets—the implementation of a Tier I ERP such as Oracle Fusion or SAP S/4HANA has a cost and complexity that do not match the size of the problem.

And Tier II ERPs, such as Dynamics 365 Business Central or NetSuite, have reasonable multi-entity capabilities for the financial side, but they don't solve operational coordination between markets: work processes, approval flows and real-time operational reporting still need an additional layer.

The composable architecture —ERP central to the financial core and specific tools for operational processes—is the model that Deloitte and TUM identify as the emerging standard for expanding organizations [3]. It's not a solution for the future: it's the model with which the most efficient organizations are already solving the problem.

The cost of international expansion isn't just in local operations. It is also in the time that headquarters spends coordinating, consolidating and validating without tools to automate it. When that time exceeds the equipment's capacity, expansion ceases to be a source of growth and becomes a source of internal friction.

The architecture that allows you to scale without losing visibility

The model that works in practice for organizations in this size and complexity range combines three layers.

A shared operational management layer: a tool that all markets use to manage work processes — files, projects, assignments — with real-time visibility from headquarters.

A consolidated reporting layer: a dashboard that automatically aggregates data from all markets in the format that management and investors need, without manual consolidation work.

And a layer of approval flows: configurable validation processes that automatically flow between the local market and headquarters, with full traceability and automatic notifications.

These three layers are built on the systems that each market already has — without imposing a new tool on local teams that already have their own processes — and are integrated with the headquarters financial ERP so that billing and accounting data flow without duplication.

The result is that headquarters has real-time operational visibility of all markets, and local teams can operate with the autonomy they need without losing connection with the rest of the organization.

Bibliographic references

Methodological note: all statistics have been verified in the original sources before inclusion. The citations in superscript [N] refer to the APA references detailed below.

[1]MuleSoft/ Deloitte Digital/Vanson Bourne. (2025). Connectivity Benchmark Report 2025. https://blogs.mulesoft.com/news/connectivity-benchmark-report/ — The average company manages 897 different applications, of which only 28% are integrated. 95% of IT leaders cite difficulties connecting existing systems with new digital or expansion initiatives.

[2]MuleSoft/ Deloitte Digital/Vanson Bourne. (2024). Connectivity Benchmark Report 2024. https://www.deloitte.com/za/en/services/consulting/perspectives/2024-connectivity-benchmark-report.html — 81% of global IT leaders say that data silos block their digital transformation initiatives. In organizations with operations in several countries, silos multiply because each market usually has its own technological stack.

[3]Deloitte & TUM School of Management. (2024). The Future of ERP: A Study on the Challenges and Opportunities of ERP Systems by 2030. https://image.marketing.deloitte.de/lib/fe31117075640474771d75/m/1/147c324b-c7f5-4884-b3f7-06cf12247406.pdf — 68.8% of respondents believe that Cloud, AI and automation will be significantly relevant to the evolution of ERP in 2030. The composable architecture —central ERP+ specific tools by market or process— is the emerging model for internationally expanding organizations.

[4]McKinsey & Company. (2023). The State of Organizations 2023. McKinsey Global Institute. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-state-of-organizations-2023 — Professionals waste an average of 9.3 hours a week in coordination and manual monitoring processes. In geographically distributed teams, that cost is amplified because coordination between time zones adds additional friction to each validation process.

[5]PanoramaConsulting Group. (2024). The 2024 ERP Report. Panorama ConsultingGroup. https://4439340.fs1.hubspotusercontent-na1.net/hubfs/4439340/Reports/ERP%20Report/2024-erp-report-panorama-consulting-group.pdf — 74% of organizations adopted SaaS solutions in 2024. Companies with a presence in several countries tend to adopt different tools in each market, which multiplies integration silos and hinders operational consolidation.

[6]ERP News. (2024). Electronic Workflow Process Gaps Kill an Estimated 20% of ERP Productivity. https://erpnews.com/electronic-workflow-process-gaps-kill-an-estimated-20-of-erp-productivity/ — Workflow gaps between systems destroy 20% of productivity in organizations with implemented ERP. In organizations with operations in several countries, these gaps also occur in coordination processes between markets: consolidated reporting, resource allocation, documentation validation.

[7]Gartner. (2024). Market Share Analysis: ERP Software, Worldwide, 2024. Gartner Research, Doc. #6654134. https://www.gartner.com/en/documents/6654134 — The global ERP market reached $66 billion in 2024 with growth of 11.3%. The demand for integration tools and consolidated reporting for multi-country organizations is one of the most significant growth levers in the market.

[8]Aberdeen Group. Cited in: FounderJar. (2024). The Ultimate List of ERP Statistics for 2025. https://www.founderjar.com/erp-statistics/ —23% of medium-sized companies use the consolidated reporting features of their ERP for operations in several countries. The remaining 77% produce their consolidation reports manually, exporting data from each market and crossing them into spreadsheets.

‍