top of page
Lost by trying to out-build AWS and Azure at their own infrastructure game instead of leaning into the network and edge assets CenturyLink actually owned — a cautionary tale in attacking a market on the incumbent's terrain rather than your own structural strength.
1
MODEL
BUSINESS MODEL
Infrastructure Platform
model bm
HOW THEY BUILT IT
- Built primarily through acquisition: CenturyLink acquired Savvis (2011, ~$2.5B) for enterprise hosting and colocation, then Tier 3 (2013) for public cloud/PaaS capability, assembling 'CenturyLink Cloud' as a bolted-together IaaS/PaaS offering to compete with AWS and Azure.
- Positioned as an enterprise-friendly alternative to hyperscale public cloud, leaning on CenturyLink's existing telecom enterprise relationships rather than developer-first adoption.
- Ultimately could not match the capital intensity and pace of innovation of AWS, Azure, and Google Cloud, and CenturyLink began winding down and divesting public-cloud assets in the late 2010s, eventually rebranding the parent company as Lumen Technologies (2020) to refocus on network and edge infrastructure rather than compete head-on in commodity public cloud.
HOW TO ARCHITECT IT
How to architect this model (or avoid this mistake):
1. Before entering a capital-intensive infrastructure race against hyperscalers, honestly assess whether your actual structural advantage (in CenturyLink's case, a nationwide fiber network) is being leveraged, or whether you're just building a smaller, later version of what incumbents already do at scale.
2. If you acquire your way into a category (as CenturyLink did with Savvis and Tier 3), invest as much in integrating the acquired technology into a coherent product as in the deals themselves — a stitched-together cloud offering competing against AWS's unified platform is a structural disadvantage from day one.
3. Recognize the exit signal early: when a legacy telecom's cloud unit can't keep pace with hyperscaler R&D spend, pivoting to a narrower, defensible niche (network/edge, in Lumen's case) beats continuing to burn capital chasing an unwinnable scale war.
DISTRIBUTION MODEL
Enterprise Sales, Direct Sales
dm
HOW THEY OPERATIONALIZED
- Sold primarily through CenturyLink's existing enterprise telecom account relationships, cross-selling cloud infrastructure to customers who already bought network connectivity — a channel advantage in reach but not in developer mindshare.
- Lacked the developer-first, self-serve, API-driven distribution motion that made AWS the default choice for engineering teams, a structural distribution disadvantage against hyperscale competitors.
HOW TO REPLICATE WHAT WORKED
What worked (narrowly): using existing enterprise telecom relationships to get a foot in the door for early cloud infrastructure deals before the market fully commoditized around AWS/Azure/GCP.
Trap if copied blindly: entering a hyperscale infrastructure race without hyperscale capital or developer-first distribution is close to un-winnable — this case is most useful as a cautionary example of misjudging your actual structural advantage rather than a playbook to replicate.
| PATTERNS OF THIS MODEL
PATTERNS IN INCUMBENTS ENTERING CAPITAL-INTENSIVE RACES THEY CANNOT WIN:
1. BEFORE ENTERING A CAPITAL-INTENSIVE RACE, VERIFY THAT YOUR ACTUAL STRUCTURAL ADVANTAGE IS BEING LEVERAGED — not merely that you have adjacent revenue and a balance sheet.
2. IF YOU ACQUIRE YOUR WAY INTO A CATEGORY, INVEST AS MUCH IN INTEGRATION AS IN THE DEALS. A stitched-together offering competing against a unified platform is disadvantaged from day one.
3. RECOGNISE THE EXIT SIGNAL EARLY. When you cannot match incumbent R&D spend, retreating to a narrower defensible niche beats burning capital on an unwinnable scale war.
4. ADJACENCY IS NOT ADVANTAGE. Owning a related asset does not confer the right to compete in a category with different economics and a decade's head start.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — AUDIT WHETHER YOUR STRUCTURAL ADVANTAGE ACTUALLY APPEARS IN THE PRODUCT.
Standard: CenturyLink's real asset was a nationwide fibre network. The products sold were general-purpose IaaS and PaaS. If your differentiator is not visible in what the customer buys, you are running a smaller, later version of the incumbent's business.
GOLDMINE 2 — INTEGRATION IS THE JOB WHEN YOU ACQUIRE INTO A CATEGORY.
Standard: Savvis (2011, ~$2.5B) and Tier 3 (2013) were assembled rather than integrated. A stitched-together cloud competing against AWS's unified platform starts at a structural disadvantage no sales effort corrects.
GOLDMINE 3 — RECOGNISE THE EXIT SIGNAL AND TAKE IT.
Standard: winding down public cloud and rebranding to Lumen in 2020 to focus on network and edge was the correct decision, made late but made.
THE PIT — CAPITAL-INTENSITY RACES ARE LOST BEFORE THEY ARE ENTERED.
A legacy telecom cannot match hyperscaler R&D and capex from a declining core business. Verizon ran the same play with the same result.
THE SECOND PIT — ENTERPRISE CUSTOMERS MIGRATED OFF A PLATFORM THAT WAS BEING WOUND DOWN.
MOVE WITH CAUTION — ACQUIRING YOUR WAY INTO A CATEGORY REQUIRES MORE INTEGRATION SPEND THAN PURCHASE PRICE.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Consolidated Market
WHY THEY WON
By the time CenturyLink Cloud was assembled, public cloud infrastructure had already begun consolidating rapidly around AWS, with Azure and Google Cloud as the only credible secondary challengers, each backed by capital and R&D spend legacy telecoms couldn't match. CenturyLink entered a market already too consolidated for a smaller, acquisition-stitched player to compete on equal terms. Transferable principle: entering a capital-intensive, already-consolidating market as a smaller player without a genuinely differentiated structural advantage is a losing sequencing, however strong your existing customer relationships.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
CenturyLink assembled its cloud offering entirely through acquisition (Savvis in 2011, Tier 3 in 2013) rather than organic build, the fastest route to cloud capability for a telecom with no existing hyperscale infrastructure — but one that left the resulting platform less architecturally unified than AWS's ground-up build.
FOOTHOLD STRATEGY
fs
Beachhead Strategy
The intended beachhead was existing CenturyLink enterprise telecom customers who could be cross-sold cloud infrastructure alongside their network contracts — a reasonable initial wedge given the existing relationship, but one that never expanded meaningfully beyond that captive base into the broader developer-driven cloud market that ultimately determined category leadership.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
Savvis acquisition (2011): the foundational asset for enterprise hosting and colocation capability.
Tier 3 acquisition (2013): added public cloud/PaaS capability, forming the combined 'CenturyLink Cloud' brand.
Divestiture and Lumen rebrand (2020): the eventual retreat from public cloud competition, refocusing the parent company on network and edge infrastructure where it retained genuine structural advantage.
KEY LEARNING
If you're assessing whether to enter a capital-intensive, consolidating infrastructure category, ask honestly whether your existing assets (network, relationships, data) give you a genuine structural edge in that specific category, or whether you're simply late to a race the leaders are already winning — if the latter, a narrower pivot to your actual strength may be the better long-term bet, as Lumen's later refocus on network/edge illustrates.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: Entering a capital-intensive, already-consolidating market without a structural advantage is a losing sequence, however strong the customer relationships.
RULE 1 — TIMING DETERMINES VIABILITY MORE THAN EXECUTION IN INFRASTRUCTURE. Arriving after consolidation means competing on capex you cannot match.
RULE 2 — ACQUISITION-STITCHED PLATFORMS INHERIT INCOMPATIBLE ARCHITECTURES. Assembling a cloud from purchases produces integration debt that shows in the product.
RULE 3 — ENTERPRISE RELATIONSHIPS DO NOT TRANSFER ACROSS PRODUCT CATEGORIES. Buying connectivity from a vendor does not predispose anyone to buy compute from them.
RULE 4 — THE RATIONAL RETREAT IS MANAGED SERVICES ON OTHERS' INFRASTRUCTURE. Preserve the relationship without the capital fight.
MARKET TYPE: Consolidated Market (public cloud), late entry without structural advantage.
| MARKET ENTRY PLAYBOOK
THE STANDARD: ASSEMBLING A CATEGORY POSITION BY ACQUISITION IS FAST AND PRODUCES AN ARCHITECTURE THAT CANNOT COMPETE WITH A GROUND-UP BUILD.
RULE 1 — ACQUISITION BUYS CAPABILITY, NOT COHERENCE.
Multiple purchased platforms deliver a service catalogue immediately and never unify into a single system.
RULE 2 — IN INFRASTRUCTURE, ARCHITECTURAL UNITY IS THE COST CURVE.
Against competitors with one platform and enormous scale, a stitched estate cannot reach competitive economics.
RULE 3 — RECOGNISE UNWINNABLE CAPITAL CATEGORIES EARLY.
Sustained subscale participation destroys more value than a timely exit.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A captive base is a starting position, not a strategy; if it never expands beyond, it is a ceiling.
RULE 1 — CROSS-SELLING AN EXISTING CONTRACT IS THE EASIEST REVENUE AND THE WEAKEST SIGNAL. Adoption driven by relationship does not indicate competitiveness.
RULE 2 — INFRASTRUCTURE MARKETS ARE DECIDED BY DEVELOPERS, NOT ACCOUNT MANAGERS. A telecoms sales motion never reaches the people who choose.
RULE 3 — CAPITAL INTENSITY REWARDS ONLY THE LARGEST SCALE. Sub-scale infrastructure investment produces neither margin nor competitiveness.
RULE 4 — SET AN EXPLICIT TEST FOR MOVING BEYOND THE CAPTIVE BASE. Without a date and a number, a defensive position quietly consumes years of capital.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Usage-Based, Subscription
PRICING MODEL
Competitive Pricing
WHY THEY WON
Priced similarly to competing IaaS/PaaS offerings — usage-based compute, storage, and network consumption plus subscription tiers for managed services — bundled where possible with CenturyLink's existing enterprise network contracts.
Priced to compete directly with AWS and Azure's published rates rather than establish a premium or differentiated pricing position, targeting enterprise IT buyers already engaged with CenturyLink for network services who wanted to consolidate vendors rather than shop for the cheapest possible compute.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
Enterprise IT departments already buying CenturyLink network/telecom services (buying vendor consolidation convenience); mid-market companies wary of AWS/Azure complexity (buying a simpler, more relationship-driven cloud vendor).
Sales-led and relationship-driven, leveraging existing account manager relationships from CenturyLink's telecom business rather than the self-serve, credit-card sign-up model that drove AWS and Azure's developer-first growth.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Competing on price against hyperscalers without their scale is a losing position, and the category's history proves it.
RULE 1 — SUB-SCALE INFRASTRUCTURE CANNOT WIN A RATE-CARD FIGHT.
Without hyperscaler volume economics, matching prices destroys margin without winning share.
RULE 2 — NETWORK OWNERSHIP IS THE ONLY DIFFERENTIATOR A TELCO ACTUALLY HAS.
Connectivity plus compute, private links and data residency are defensible. Generic virtual machines are not.
RULE 3 — TELCO CLOUD VENTURES HAVE REPEATEDLY BEEN DIVESTED OR REPOSITIONED.
CenturyLink (now Lumen) exited and repositioned its cloud business, as did most peers. Treat any telco-hosted infrastructure commitment as carrying strategic-direction risk.
RULE 4 — ENTERPRISE BUYERS WILL PAY A SMALL PREMIUM FOR ONE CONTRACT, NOT A LARGE ONE.
Procurement convenience is real and modest. It does not fund a competing platform.
An enterprise is buying one accountable supplier across network and compute. That convenience is genuine and cheap — which is precisely why it could not sustain an independent cloud business.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Bundling cloud into existing network contracts eases the sale and hides whether the product competes on its own merits.
Telco-operated cloud faces hyperscalers on both capability and price simultaneously — a position almost universally exited across the industry.
Usage-based pricing means customer optimisation is revenue loss.
Multi-year managed contracts make revenue look stable long after workloads have moved.
Lumen has divested or wound down most cloud and data-centre assets; verify current scope before relying on this entry.
Where the model can break
4
MOTION
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Vertical Integration
HOW THEY EXPAND
CenturyLink attempted vertical integration by combining network connectivity, colocation (Savvis), and public cloud compute (Tier 3) into a single enterprise offering, but ultimately reversed course — divesting cloud assets and rebranding as Lumen Technologies in 2020 to refocus specifically on network and edge infrastructure rather than continue competing across the full cloud stack.
Fast Follower
HOW THEY COMPETE
CenturyLink Cloud positioned itself as a fast-follower alternative to AWS and Azure for enterprise customers wary of hyperscaler complexity, a defensive strategy that ultimately proved unsustainable once it became clear the follower lacked the capital intensity to keep pace with continuous hyperscaler innovation.
GROWTH ENGINE
GTM
ge n gtm
Paid Acquisition Engine
Growth relied on cross-selling into an existing customer base rather than a self-reinforcing viral or network-effect loop, meaning growth was capped by the size of CenturyLink's existing enterprise telecom relationships rather than expanding independently — a structural ceiling that became apparent once hyperscaler competitors captured essentially all new cloud-native demand.
Cross-sell motion through existing enterprise telecom account managers, targeting CenturyLink's installed base of network customers rather than building a new developer-first acquisition channel.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
CenturyLink Cloud's only real moat was distribution through existing telecom relationships, and that advantage proved insufficient against AWS and Azure's combined capital scale and developer-first network effects — a clear example of a moat that looks real on paper (existing customer relationships) but doesn't hold up once the market's underlying mechanism (developer self-serve adoption, hyperscale R&D) shifts beneath it.
| MOAT INTELLIGENCE
THE STANDARD: An existing enterprise relationship does not transfer into a category defined by capital intensity. Distribution advantage is category-specific.
RULE 1 — SUBSCALE CLOUD LOSES REGARDLESS OF CUSTOMER RELATIONSHIPS. Data centre footprint, service breadth and price all compound with scale, and none of them is influenced by an existing contract for connectivity.
RULE 2 — THE BUYER AND THE EVALUATION CRITERIA ARE COMPLETELY DIFFERENT. Selling network capacity to procurement is unrelated to winning workloads from engineering teams comparing managed services.
RULE 3 — EXITING FAST BEATS COMPETING SLOWLY. Divesting a subscale position releases capital into the assets where the advantage is genuine, which is the correct outcome rather than a failure.
THE SIGNAL: a large customer base is not portable optionality. Treating it as strategic entitlement funds losses that a focused competitor never has to carry.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M — ANOTHER TELECOM CLOUD CASE, WITH A DIFFERENT LESSON
Unlike a pure hyperscaler challenge, this was cloud assembled through acquisitions (notably Savvis and Tier 3) bolted onto a network business.
Acquiring your way into a platform category gives you assets without a coherent product, which is worse than starting late.
$1–5M — INTEGRATION DEBT IS THE HIDDEN COST OF A BOUGHT PLATFORM
Multiple acquired stacks produce overlapping products customers cannot navigate.
$5–10M — MANAGED SERVICES ARE A REAL BUSINESS; PUBLIC CLOUD WAS NOT
Hosting and managed infrastructure for enterprises had genuine demand. Competing with hyperscalers on primitives did not.
$10–50M — EXIT THE FIGHT YOU CANNOT FUND
CenturyLink sold its data centre and colocation business to a consortium that became Cyxtera in 2017, retreating from the platform ambition.
Withdrawal was correct; the cost was years of capital and attention.
$50–100M — NOT REACHED IN THE INTENDED CATEGORY
State it plainly: this was a strategic retreat.
$100M+ — NOT APPLICABLE
Rule: you cannot acquire your way into a platform business. Platforms are coherent by construction, and coherence is exactly what M&A does not deliver.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: An existing customer list is not a structural advantage in a capital-intensive category. Misjudging which of your assets actually transfers is the expensive error.
SEQUENCE:
1. Test whether your advantage is genuinely structural or merely relational.
2. If it's relational, sell where relationships close deals — not where economics do.
3. Do not enter a hyperscale race without hyperscale capital and developer distribution.
WORKED (narrowly): Existing enterprise telecom relationships opening early infrastructure conversations before the market commoditised.
CAUTION:
1. ENTERING AN INFRASTRUCTURE RACE WITHOUT THE CAPITAL OR THE DEVELOPER-FIRST DISTRIBUTION IS CLOSE TO UNWINNABLE. This case is most useful as a caution about misreading your own advantage, not as a playbook.
2. RELATIONSHIP-LED ENTRY DELAYS THE MOMENT YOU DISCOVER THE ECONOMICS DON'T WORK.
bottom of page