A network owner commits assets, an IT-services firm sells delivery capacity, and a software business funds a reusable product. Managing them against the same growth or margin target obscures where the next unit of value comes from. This page is for CEOs, CFOs and boards choosing investment priorities, delivery models or portfolio boundaries.
Return depends on take-up, customer economics and the lifetime cost of network capacity.
Margin depends on realised rate, delivery utilisation, skill mix and controlling scope.
Margin depends on retention, expansion and reusable product economics after support and development.
Return depends on take-up, customer economics and the lifetime cost of network capacity.
A network expansion commits capital before connections and usage convert it into revenue. Broad coverage metrics can hide weak take-up or uneconomic acquisition spending.
Stage investment against cohort economics and a credible path from coverage to paying use.
New capabilities may be added while billing, service and network platforms remain in place. Migration work then competes with growth investment without removing the old run cost.
Make retirement milestones and service continuity part of the investment case from the start.
For the board
Separate asset, delivery and product economics, then make the cross-business commitments explicit in the capital and roadmap decisions.
Explore shared decisions ↓Margin depends on realised rate, delivery utilisation, skill mix and controlling scope.
Time charged to a project does not guarantee that the contract recovers its cost. Unpriced scope changes and quality fixes consume capacity that cannot be sold again.
Review realised contribution and rework by engagement, not utilisation in isolation.
Tools can shorten some tasks while review, integration and accountability remain. A time-based commercial model may hand the productivity gain to the customer unless the work and price are redesigned together.
Test the delivery economics and commercial model on bounded engagements before extrapolating an efficiency target.
Margin depends on retention, expansion and reusable product economics after support and development.
New customers may require implementation, integration and custom features that are not reflected in the subscription price. A growing recurring-revenue line can conceal a service-heavy operating model.
Separate repeatable product revenue from customer-specific effort before funding the next growth wave.
Selling into adjacent segments adds competing development requirements. Fragmented engineering effort can delay the releases needed to retain the core customer base.
Allocate development against segment-level retention and commercial evidence, with explicit choices about what will not be built.
Telecom & Technology · Strategic Decisions
Network infrastructure operator
Telecom & Technology · Operating Model · Cost Out
Telecom operator
Telecom & Technology · Strategic Decisions · Growth & Commercial
Listed media technology company