Scalability that holds up in the field
Growth is rarely linear. As demand rises, complexity tends to rise with it—more locations, more devices, more suppliers, more variation. Without deliberate design, scale quickly turns into operational friction: higher support load, slower change, and rising unit cost.
I advise and guide IT executives to design scalable services and operating models that work across distributed environments—so growth stays predictable, reliability stays high, and cost per unit stays under control.
What this looks like in practice
| Key Facts | - Founding of NFON AG (2006)
- Cloud-based phone system as “Software as a Service”
- Today around 55,000 business customers in 15 European countries
|
| Initial Situation | - Newly founded company with an ambitious growth plan in what was then a still young solution category (Cloud PBX)
- Target picture: rolling out and operating large volumes of VoIP endpoints for geographically distributed SME customers
- Customer environment with low / missing network & VoIP operations competence; strong need for simplicity and fast onboarding
|
| Problem Statement | - A scalable rollout and operating model for broad geographic coverage without installation and support costs increasing proportionally
- Common market approaches suffered from manual device configuration, high support intensity, and dependence on qualified partner networks
- Commercial rollout required a fast, simple, and cost-effective way to run on-site customer trials
|
| Guiding Decision | - “Zero-Touch Logistics” strategy, i.e., full automation of delivery and configuration from customer order to the endpoint device (no technical on-site work)
- Consistent prioritization of rollout and support characteristics of endpoint devices in product management and product design
- Deriving hardware and product requirements from process design (not the other way around)
|
| Approach | - Building a fully automated end-to-end process from order capture, PBX provisioning, endpoint shipment via external logistics partners, through to self-configuration of devices on-site
- Eliminating all technical configuration steps on site; shielding all device parameters from users; centrally managing configuration
- Close collaboration with hardware manufacturers to implement the required technical mechanisms
|
| Value Creation | - Transforming deployment from a labor-intensive project/service process into a standardized, repeatable logistics process
- Scaling across the footprint without structural dependence on on-site partners, while reducing rollout error rates and support load
- More than 660,000 endpoint devices in operation, with delivery capacity of up to 50,000 devices per year to end customers
|
| Role | - Founder; CIO and COO
- Responsible for the strategic direction of the platform/operating model and for implementing zero-touch capability as a prerequisite for scaling
|
| Lessons Learned | - In SaaS infrastructure and platform models, scaling is primarily constrained by the “last-mile process”; zero-touch capability is a product feature with direct impact on run costs and growth
- Product management prioritization, engineering quality, test strategy, and operational handover jointly determine operational readiness; deficits materialize as support load and slow down scaling
|
