Strategy
Strategy
Important Topic
Insight

You don’t build systems in stable environments

In this insight

Most growth plans assume stability. Clear scope. Fixed priorities. Predictable execution. That’s not how growth actually happens.

‍

The False Assumption

When companies design growth systems, they imagine a controlled environment:

  • The organization stays roughly the same
  • Priorities don’t shift dramatically
  • Teams execute against a stable plan

So they build systems optimized for efficiency under those conditions.

And those systems work.

Right up until reality changes.

‍

The Reality: Constant Change

Growth rarely happens in a straight line.

  • New leadership decisions
  • Market shifts
  • Internal restructuring
  • Acquisitions
  • Changing priorities across teams

The moment growth accelerates, stability disappears.

And systems built for stability start to break:

  • Processes slow down
  • Data becomes inconsistent
  • Teams fall out of sync
  • Execution fragments

Not because the system was wrong.

But because it was too rigid.

‍

Case Evidence (AXI)

At AXI, the initial plan was straightforward:

Build an inbound engine.
Estimated timeline: nine months.

What followed was anything but stable:

  • 10 acquisitions announced
  • Co-branding across multiple entities
  • A hybrid CRM environment (Salesforce + HubSpot)
  • Expanding demands from different business units

The environment didn’t wait for the system to be ready.

The system had to evolve while everything else was moving.

And that changed the nature of the work entirely.

‍

The Pattern

This is where most organizations get it wrong.

They design systems for:

  • Control
  • Predictability
  • Efficiency

But growth introduces:

  • Variability
  • Complexity
  • Continuous change

So the system becomes the bottleneck.

Not because it’s poorly designed.
But because it’s designed for the wrong conditions.

‍

The Reframe

A growth system should not be optimized for stability.

It should be designed for movement.

That means:

  • Flexible structures instead of rigid processes
  • Shared logic instead of isolated execution
  • Systems that can absorb change without breaking

Because change is not the exception.

It’s the environment.

‍

Takeaway

A growth system is not defined by how well it works under control.

It’s defined by how well it holds under change.

‍

AXI Case Study

‍

About the author

David De Smedt

Architect of B2B Growth Systems

I lead every stage personally - from interviews and diagnosisto alignment and activation.

Direct access throughout
One accountable partner
Senior involvement at every stage
David De Smedt photo