# Digital architecture: why tool sprawl is not maturity

**Digital architecture tool sprawl** does not measure a company's maturity. Every growing small business accumulates digital tools one at a time: an accounting system, a CRM, a shared spreadsheet for inventory, a few email automations. Each tool answers an urgent need at the moment it appears, which is a natural path. The problem emerges somewhere else.

## What the integration data shows

According to the Digital Innovation Observatories of Politecnico di Milano, produced with AssoSoftware, only 26% of Italian SMEs rely on a single vendor for their management tools. The majority choose different solutions for different areas, which is often the right decision, because no single product covers every need well. The figure that matters more is another: application integration between these tools rose to 38%, from 29% the previous year, and remains at a contained level. 43% of companies have no automatic data exchange between their systems and third-party systems. The gap tells a precise story. Tools are often chosen well, and few companies stop to design how they should talk to each other before introducing them. The accounting system knows everything about payments and the CRM knows everything about customers, while neither knows the other exists. The missing element is a project that holds the pieces together, regardless of how many applications are in use.

The phenomenon is not limited to Italy. An international survey by BetterCloud of more than 500 IT professionals found that the average number of applications in mid-market companies grew 41% in a single year, driven in part by the speed of AI tool adoption. Only 56% of those applications are formally approved by IT departments, and 90% of organisations report no structured automation between applications. Adoption speed has outrun the ability to govern it.

## The real risk of adding tools

The risk for a growing small business lies here. Every new tool introduced without an overall vision adds a point of friction: a piece of data to re-enter by hand, a check to perform twice, a decision taken on partial information because nobody has combined the numbers from different sources. The cost rarely appears as a single line in the accounts. It accumulates silently in hours of work, transcription errors and delayed decisions. Understanding how the business process actually works, where data is generated, who uses it and where it is lost when moving between systems, is the most effective starting point, before deciding which tools to replace or introduce. Generalist suites rarely resolve this friction, because they are designed for a broad user base rather than the specific flows of one company. Vertical tools tend to remain isolated precisely because they are built to do one thing well. Only after the mapping does it make sense to decide which connections to build, which automations to introduce and which tools to keep as they are.

## An architecture needs care over time

The work requires dedicated time listening to processes before writing code, and it rarely ends with a single implementation. A company's flows change when the market changes, when a large customer arrives, when a second location opens. A well-designed digital architecture needs to be followed over time, updated and corrected when something stops working as expected. For an owner, knowing how many software products the company uses matters less than asking whether anyone, at any point in recent years, stopped to look at the whole picture before adding the next piece.

The same question applies to the offer. A connected product can carry [a recurring service built on the connected product](/en/ecorner/2026/product-to-service-recurring-revenue.html), and that changes what the company sells and for how long. The same design question applies to [device connectivity as part of the architecture](/en/ecorner/2026/iot-connectivity-lpwa-satellite.html).

Each tool added to the stack widens the attack surface, and [the security of WordPress plugins](/en/ecorner/2026/wordpress-plugin-security.html) is where that surface is most often left unmanaged.

Sprawl also fragments information, and [information silos in document management](/en/ecorner/2026/document-management-information-silos.html) are the cost that surfaces later.

## Frequently asked questions

**Is using many different software products a problem for a small business?**
Not by itself. Different tools for different needs are often the sensible choice. The problem arises when they are introduced one at a time without anyone designing how they exchange data.

**How do you recognise that fragmentation is already costing money?**
Common signs include data re-entered by hand several times, duplicate checks between systems and decisions based on partial numbers because information is not combined.

**Where should a company start to connect systems without replacing them all?**
Start with a mapping of the real process: where data is born, who uses it and at which step it is lost or duplicated. Then decide which connections to build.

**Is system integration a one-off project?**
Rarely. Processes change with the market, new customers and new locations, so a well-designed architecture must be maintained and updated over time.

## Sources

Osservatori Digital Innovation — software management in SMEs — https://www.osservatori.net/
AssoSoftware — Italian software industry — https://www.assosoftware.it/
BetterCloud — State of SaaS report — https://www.bettercloud.com/
European Commission — digital strategy — https://digital-strategy.ec.europa.eu/en