Growth looks impressive from the outside. New vendor partnerships, larger customers, rising revenue, more employees, additional offices. On LinkedIn, it reads like a steady upward curve. Inside an IT system integrator, however, growth rarely feels like a success story. Much more often, it feels like a sequence of subtle losses of control that appear in stages. Each size category brings its own very typical, often invisible problems that only become obvious once you have lived through them.
The crucial point is this: growth in IT integrators is not a linear process. It is a structural transformation that happens in steps. And in every step, different elements fall out of balance — communication, responsibilities, leadership, sales, delivery, culture, and profitability.If these phases are not consciously managed, the company continues to grow on paper while internally losing clarity, speed, and quality.
From 10 to 50 employees – when the founder loses oversight
In a very small integrator, everything is intuitive. Everyone knows everyone. The founder or a very small core team is deeply involved in sales, technology, projects, and often even purchasing. Decisions are fast. Customers get immediate answers. The organization functions through direct communication and personal relationships.
Once the company reaches 30 to 50 employees, this system breaks for the first time. The founder no longer knows who is working on what. New employees are hired because projects exist, not because the structure is ready. Tasks are distributed, but roles are not clearly defined. Sales sells projects without knowing how busy the technical teams really are. Engineers feel overloaded because they are expected to deliver projects while also supporting presales.
The company is trying to run a 50-person organization with the mindset of a 10-person startup. There are still no clear sales processes, no account structures, no project standards, and no systematic resource planning. The first tensions between sales and delivery appear, even though both sides pursue the same goal. Offers are poorly calculated, projects take longer than expected, and employees begin to feel “left alone” for the first time.
From the outside, the company is growing. Internally, complexity has started to outpace organization.
From 50 to 150 employees – the great misunderstanding between sales and delivery
Between roughly 80 and 150 employees, the classic integrator problem begins to appear. Sales grows rapidly. New vendors are added. New topics such as security, cloud, modern workplace, data, and AI enter the portfolio. The pipeline becomes larger and more promising. However, the delivery structure does not grow at the same pace or in a coordinated way.
Sales thinks in terms of revenue and opportunities. Engineers think in terms of feasibility and quality. Project managers think in terms of time and resources. Controlling thinks in terms of margin. But no one is thinking in terms of overall responsibility for the customer.
Clear key account structures are missing. There may be account managers, but there is no orchestrated collaboration between sales, architects, and delivery. Customers begin to feel that projects are becoming more difficult. Engineers are constantly overloaded. Good delivery staff leave because they are only “putting out fires.” Key account managers lose deals because internally nobody has the time to create proper concepts.The company grows faster than it can organize itself. A gap appears between what is sold externally and what can be delivered internally with quality. In this phase, many integrators begin to lose profitability without fully understanding why.
From 150 to 300 employees — when politics begins
At this size, the company changes again fundamentally. Now there are department heads, team leads, competence centers, and business units. The structure becomes more formal. And with that structure comes something that barely existed before: internal politics.
Not because people are difficult, but because resources become scarce. Every department fights for budget, staff, and priority. The key account manager wants resources for an important customer. The competence center prioritizes other projects. Delivery accepts projects that seem strategically important but are not profitable. Decisions take longer because more people are involved.
The speed that once characterized the company is lost. Employees who have been there since the early days start saying that “everything used to be easier.” Leaders spend more time on internal coordination than on customers or employees. Communication becomes more complex and indirect.At the same time, the distance between management and operational reality grows. Strategic decisions are made that are difficult to implement in daily work. The organization starts to become busy with itself.
From 300 to 2,000+ employees — the corporation in an integrator’s body
At this stage, the integrator has effectively become a corporation. Processes dominate people. Approval loops, budget cycles, reporting obligations, and CRM maintenance consume a large part of daily work. Sales spends more time inside internal systems than with customers. Account managers feel powerless because they can no longer make decisions themselves. Architects lose motivation because they are stuck in bureaucratic structures.
Customers begin to notice that decisions take a long time. They realize they are no longer dealing with an agile integrator, but with a complex organization. The individual customer loses importance because the company starts thinking in structures rather than relationships.A paradox emerges: the larger the integrator becomes, the less it feels responsible for the individual customer. And this is exactly when many customers begin to look for smaller, more agile partners again.
The recurring core problem across all phases
Regardless of size, one problem repeatedly appears: no one feels end-to-end responsible for the customer. Not sales, not delivery, not engineering, not management. Everyone feels responsible only for their own part. This fragmentation grows slowly with each stage of growth.
This is the biggest challenge for integrators during growth phases. They must learn to build account structures that truly connect sales, engineering, and delivery. They need people in leadership roles who can do more than sell. They need orchestrators who understand how to align key account managers, involve architects, coordinate project managers, and develop customers strategically.These profiles are rare, but they are critical for overcoming typical growth problems.
Conclusion
IT system integrators rarely fail because of the market. Demand is there. Technology evolves. Customers continue to invest. Many integrators fail because of their own growth. Not because they are incapable, but because each stage of growth creates new structural crises that only become visible once experienced.
From the founder’s loss of control at 50 employees, to the disconnect between sales and delivery at 150, to internal politics at 300, and finally to bureaucracy at 2,000 — every stage introduces new invisible problems. Those who understand these mechanisms can actively manage them. Those who ignore them lose speed, margin, good employees, and eventually customers.Growth in the integrator world is not a straight upward line. It is a sequence of internal reorganizations. And this is where the real challenge lies.
