top of page
Business & Enterprise
Cloud Technology
Cloud Infrastructure
CenturyLink Cloud
Tried to become the enterprise cloud bridge by combining telecom network reach, managed hosting, and a self-service IaaS platform, despite competing against AWS, Microsoft, and Google with far greater cloud scale and developer gravity.
1
MODEL
BUSINESS MODEL
IaaS
- Acquired Savvis in 2011 to gain managed hosting, colocation, and enterprise IT services.
- Acquired AppFog in 2012 to add Cloud Foundry-based platform-as-a-service capabilities.
- Acquired Tier 3 in 2013 and rebranded its public multi-tenant cloud as CenturyLink Cloud.
- Sold IaaS compute, storage, networking, and virtual machines through a self-service portal and APIs aimed at enterprise IT teams.
- Bundled cloud with CenturyLink’s network, colocation, managed services, security, and disaster-recovery offerings.
- Targeted enterprises with hybrid-cloud needs: workloads that could not simply move to public cloud but required integration with existing data centers and networks.
- Later shifted away from owning data centers, selling the colocation business to Cyxtera in 2017 and refocusing on networking and connectivity.
1. Identify an enterprise segment whose workloads are too regulated, legacy-bound, or network-dependent for a pure public cloud.
2. Build or acquire the infrastructure layer first, then add orchestration and managed services that reduce operational burden.
3. Bundle connectivity, security, and support only when they solve a real integration problem rather than merely packaging existing assets.
4. Target buyers who value a single vendor for network, hosting, and cloud—but do not assume that bundling creates product superiority.
5. Invest in developer experience and ecosystem compatibility; enterprise cloud adoption depends on APIs, automation, and marketplace integrations.
6. Avoid competing head-on with hyperscalers on raw compute price and breadth; differentiate only where you have a structural advantage.
CenturyLink acquired Savvis in 2011 for managed hosting and colocation, AppFog in 2012 for PaaS, and Tier 3 in 2013 for public-cloud IaaS. It rebranded Tier 3 as CenturyLink Cloud and positioned it as an enterprise-oriented alternative to hyperscalers, emphasizing hybrid cloud, orchestration, and managed services; however, it struggled to compete with AWS and Microsoft’s cloud scale and eventually sold its data centers and colocation business to Cyxtera in 2017.
HOW THEY BUILT IT
HOW TO ARCHITECT IT
DISTRIBUTION MODEL
Direct Sales, Enterprise Sales, Channel Partners, Events
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Direct enterprise sales through CenturyLink’s telecom sales organization, targeting CIOs, IT directors, and infrastructure teams.
- Channel partners and resellers extended reach into mid-market and enterprise accounts needing implementation support.
- Industry events and analyst relations positioned CenturyLink Cloud as an enterprise alternative to hyperscale cloud providers.
- Bundled distribution through existing telecom and managed-hosting relationships, using Savvis’s enterprise customer base as an entry point.
What worked: Use an existing enterprise sales force and installed customer base to distribute an adjacent infrastructure product; telecom relationships created access to CIOs who already trusted CenturyLink for connectivity.
Trap if copied blindly: A sales-led distribution model fails for developer-centric cloud products if the product lacks self-service, APIs, documentation, and ecosystem compatibility; enterprise relationships cannot substitute for developer adoption.
| PATTERNS OF THIS MODEL
PATTERNS IN TELECOM-DERIVED CLOUD PLATFORMS:
1. NETWORK REACH DOES NOT EQUAL CLOUD ADVANTAGE. Enterprises may buy connectivity from a telecom, but cloud workloads follow developer experience, ecosystem breadth, and pricing.
2. ACQUISITION CAN ASSEMBLE CAPABILITY BUT NOT COHERENCE. Buying hosting, PaaS, and IaaS does not automatically create an integrated platform; integration debt can slow innovation.
3. HYBRID CLOUD IS A REAL WEDGE BUT A NARROW ONE. Enterprises with legacy systems need bridges to cloud, yet hyperscalers and systems integrators can serve much of that need.
THE WEAKNESS: Telecom-derived cloud providers often face a strategic conflict: their core business is connectivity, while cloud requires product velocity, developer ecosystems, and massive infrastructure investment.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — NETWORK-AWARE CLOUD. The opportunity is to build cloud infrastructure where latency, private connectivity, edge placement, and data sovereignty are first-class product features rather than add-ons.
GOLDMINE 2 — MANAGED HYBRID CLOUD FOR REGULATED INDUSTRIES. Banks, healthcare systems, and industrial companies need governed environments that connect legacy systems, private data, and public cloud with compliance controls.
GOLDMINE 3 — VERTICAL INFRASTRUCTURE. Rather than general-purpose IaaS, build cloud primitives for a specific workload—industrial IoT, media processing, or regulated data—where generic hyperscalers are not optimized.
THE PIT — ME-TOO IaaS. Competing with AWS on generic virtual machines, storage, and compute invites a price and scale war the telecom cannot win.
THE SECOND PIT — ACQUISITION WITHOUT PLATFORM INTEGRATION. Buying hosting, PaaS, and IaaS creates a portfolio, not a platform, if the products do not share identity, billing, APIs, and developer experience.
MOVE WITH CAUTION — Do not assume enterprise sales access converts into cloud adoption. Cloud buying begins with developers and architects; if they prefer AWS, Azure, or GCP, the CIO relationship alone will not sustain the platform.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
CenturyLink Cloud competed against AWS, Microsoft Azure, Google Cloud, Rackspace, and other cloud providers. Its differentiation was enterprise hybrid cloud, managed services, and network integration, while hyperscalers had superior scale, developer ecosystems, and innovation velocity.
MARKET TYPE
Red Ocean
ENTRY STRATEGY
Acquisition
WHY THEY WON
Cloud infrastructure is a Red Ocean dominated by hyperscalers with massive capital, global data-center footprints, developer ecosystems, and continuous price declines. CenturyLink’s structural opening was enterprises with hybrid, regulated, or network-sensitive workloads; its constraint was that it lacked the developer gravity and product velocity to win broad cloud adoption.
EXECUTION
CenturyLink entered cloud through acquisition rather than building a platform from scratch. It bought Savvis in 2011 for managed hosting and colocation, AppFog in 2012 for PaaS, and Tier 3 in 2013 for IaaS. The critical bet was that telecom distribution plus acquired cloud capability could create an enterprise cloud platform. This required integrating disparate products, building developer trust, and competing on innovation; it would fail if acquisitions remained siloed or if the company could not match hyperscaler product velocity.
FOOTHOLD STRATEGY
Beachhead Strategy
CenturyLink Cloud’s early foothold was enterprise IT teams already using Savvis managed hosting, colocation, or CenturyLink network services. These customers had existing relationships, complex infrastructure needs, and openness to hybrid-cloud solutions. Once CenturyLink established cloud credibility with these accounts, it sought to expand into broader enterprise IaaS and PaaS adoption.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: CenturyLink’s price cuts and hyperscale launches show that competing on commodity infrastructure requires matching hyperscaler economics, not merely offering enterprise services.
KEY LEARNING: In infrastructure markets, price competition without a structural cost advantage destroys margin without creating durable differentiation.
HOW TO USE: If you lack scale economics, avoid commodity pricing wars; instead, productize a differentiated constraint—latency, compliance, workload specialization, or integration—that justifies premium pricing.
KEY LEARNING
In a Red Ocean, hyperscalers set the pace on price, breadth, and innovation. CenturyLink’s opportunity was the enterprise hybrid-cloud buyer, but its challenge was that AWS and Microsoft could also serve those needs while offering broader ecosystems. The strategic lesson is that distribution advantage must be paired with product velocity and a defensible economic wedge.
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN ENTERPRISE-SALES-LED INFRASTRUCTURE DISTRIBUTION:
1. INSTALL-BASE CROSS-SELL CREATES INITIAL ACCESS. Existing telecom and hosting customers provided a warm entry point for cloud offerings.
2. ANALYST VALIDATION MATTERS IN ENTERPRISE INFRASTRUCTURE. CIOs and architects rely on analyst research and peer references when evaluating strategic platforms.
3. EVENTS BUILD ENTERPRISE CREDIBILITY. Industry conferences and analyst briefings help position a new platform against established competitors.
4. THE WEAKNESS: Enterprise-led distribution can mask weak developer adoption; without bottom-up usage, the platform becomes a niche managed service rather than a strategic cloud.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Against a large incumbent, enter where its scale is weakest and your structural advantage is strongest.
RULE 1 — IDENTIFY THE INCUMBENT’S BLIND SPOT. Hyperscalers were less focused on deeply integrated telecom-network and managed-hosting needs.
RULE 2 — BUILD OR ACQUIRE THE MISSING CAPABILITY. CenturyLink acquired hosting, PaaS, and IaaS to assemble a cloud portfolio.
RULE 3 — INTEGRATE BEFORE EXPANDING. Acquisitions create value only when products share a coherent platform and customer experience.
RULE 4 — REJECT THE ATTACK IF THE INCUMBENT’S SCALE ADVANTAGE IS DECISIVE. Competing on generic compute against AWS invites a war of attrition.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A foothold is an existing customer segment with infrastructure complexity and openness to an adjacent product.
RULE 1 — START WITH INSTALL-BASE TRUST. Savvis and CenturyLink network customers provided a reachable entry point for cloud adoption.
RULE 2 — TARGET HYBRID WORKLOADS. Enterprises with legacy systems needed a bridge to cloud, not a full public-cloud migration.
RULE 3 — MEASURE FOOTHOLD SUCCESS BY DEVELOPER ADOPTION AND WORKLOAD EXPANSION. A foothold requires workloads moving beyond pilot projects into production.
RULE 4 — ADAPT TO BUYER REALITY. Enterprise IT may sign the contract, but developers and architects determine whether the platform becomes strategic; failure occurs when the product is sold top-down without bottom-up adoption.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
CenturyLink Cloud’s economics depended on whether cloud revenue could offset data-center capital costs, network infrastructure, sales expense, and support costs. Its strategy of competing on price with hyperscalers, while maintaining enterprise sales and managed services, created pressure on margins; the company ultimately divested its data-center and colocation business in 2017.
REVENUE MODEL
Subscription, Usage-Based, Service Fee
PRICING MODEL
Usage-Based Pricing, Competitive Pricing, Custom Enterprise Pricing
WHY THEY WON
Customers paid for IaaS compute, storage, and networking on usage-based or subscription terms, plus managed services, professional services, and colocation. Revenue expanded with workloads and infrastructure consumption, but gross margin depended heavily on data-center utilization, hardware costs, and support burden.
CenturyLink Cloud used usage-based pricing for compute, storage, and network consumption, with custom enterprise agreements for managed services and hybrid deployments. In 2014, it cut prices to compete with AWS and other hyperscalers, reflecting the commodity nature of base infrastructure.
TARGET AUDIENCE
Mid-market and enterprise IT teams (IaaS and managed cloud; want hybrid infrastructure and support); Enterprises with legacy systems (hybrid cloud; want integration with existing data centers and networks); Regulated industries (managed cloud; want security, compliance, and dedicated infrastructure); Developers and architects (self-service IaaS and PaaS; want APIs, automation, and modern application platforms).
CUSTOMER BUYING BEHAVIOUR
A data-center refresh, application modernization, compliance requirement, or network upgrade triggers evaluation. CIOs and infrastructure leaders assess security, support, integration, and total cost; developers assess APIs, automation, and ecosystem compatibility. Adoption often begins with a pilot workload, then expands if operational reliability and developer experience meet expectations.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Enterprises are not buying virtual machines; they are buying a governed path to modernize infrastructure without disrupting operations.
RULE 1 — PRICE THE OUTCOME, NOT THE COMMODITY. Managed migration, compliance, integration, and reliability can justify premium pricing; raw compute cannot.
RULE 2 — MATCH HYPERSCALER PRICES ONLY WITH A COST ADVANTAGE. Without scale economics, price cuts erode margin without creating loyalty.
RULE 3 — BUNDLE ONLY WHERE INTEGRATION CREATES VALUE. Network, security, and managed services must solve a real operational problem, not merely package existing assets.
RULE 4 — WATCH THE UTILIZATION TRAP. Data centers and infrastructure have high fixed costs; low utilization turns growth investment into margin erosion.
The buyer is really buying infrastructure modernization and operational continuity, proven by IT, infrastructure, and transformation budgets.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Hyperscaler price pressure: AWS, Microsoft, and Google continuously lowered infrastructure prices, compressing margins for smaller cloud providers.
Low utilization: Data centers and hardware have high fixed costs; underutilized capacity destroys gross margin.
Developer ecosystem gap: Enterprises adopt cloud platforms where developers, tools, and integrations are strongest; CenturyLink lacked the ecosystem gravity of AWS or Azure.
Strategic conflict: CenturyLink’s core telecom business competed for capital and management attention with a capital-intensive cloud platform.
Acquisition integration risk: Savvis, AppFog, and Tier 3 had different products and cultures; integration debt slowed platform coherence.
CenturyLink was publicly listed; it reported FY2015 operating revenue of $17.9 billion, but CenturyLink Cloud revenue, ARR, and unit economics were not separately disclosed in audited public filings.
Where the model can break
4
MOTION
motion ge cs
CenturyLink Cloud relied on enterprise sales through its telecom organization, targeting CIOs, IT directors, and infrastructure teams with hybrid cloud, managed services, and network integration. This motion suited complex, multi-stakeholder infrastructure decisions but was less effective for developer-led cloud adoption.
GROWTH EXPANSION MODEL
Acquisition-Led Growth, Platform Expansion
HOW THEY EXPAND
CenturyLink expanded through acquisitions: Savvis added managed hosting and colocation, AppFog added PaaS, and Tier 3 added IaaS. Platform expansion sought to unify these into a single cloud experience, while vertical integration bundled network, hosting, and cloud services. The dependency was that integration had to create a coherent platform; otherwise acquisitions remained disconnected products.
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Against AWS and Azure, CenturyLink differentiated through hybrid cloud, managed services, and network integration. Against Rackspace, it competed on enterprise scale and telecom-backed infrastructure. Against niche cloud providers, it used breadth of services and enterprise sales reach.
GROWTH ENGINE
GTM
Content Flywheel
A CenturyLink network or Savvis hosting customer evaluates cloud migration → enterprise sales positions CenturyLink Cloud as a hybrid or managed alternative → the customer pilots a workload → managed services and network integration deepen the relationship → additional workloads and services expand revenue → reference customers support further enterprise sales. The loop requires successful migrations and developer adoption; otherwise the platform remains a niche managed service.
CenturyLink Cloud ran an enterprise-sales-led GTM. Direct sales targeted CIOs and infrastructure leaders through telecom and hosting relationships. Channel partners and resellers extended reach into mid-market accounts. Analyst relations and events built credibility. Self-service portals and APIs supported developers, but the primary motion was enterprise sales rather than product-led developer adoption.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat was CenturyLink’s enterprise distribution, network infrastructure, and installed base of hosting and connectivity customers. Once workloads, data, and network configurations were embedded in CenturyLink infrastructure, switching costs increased—but the moat was weaker than hyperscaler ecosystems because developers and workloads could move to AWS or Azure.
| MOAT INTELLIGENCE
THE STANDARD: An infrastructure moat lasts when distribution, operational scale, and workload dependence reinforce one another.
RULE 1 — INSTALL-BASE ACCESS CREATES INITIAL ADVANTAGE. Existing telecom and hosting customers provided a reachable entry point for cloud offerings.
RULE 2 — NETWORK INTEGRATION CREATES SWITCHING FRICTION. Customers with dedicated connectivity, security, and managed services faced higher migration costs.
RULE 3 — OPERATIONAL SCALE CREATES COST ADVANTAGE. Data centers and networks benefit from utilization, but only at sufficient scale.
THE SIGNAL: CenturyLink acquired Savvis in 2011, AppFog in 2012, and Tier 3 in 2013, then rebranded Tier 3 as CenturyLink Cloud. The moat did not protect against hyperscaler scale, developer ecosystem gravity, or the strategic conflict of running a capital-intensive cloud inside a telecom.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — ACQUIRE THE INFRASTRUCTURE FOUNDATION. CenturyLink acquired Savvis in 2011 to enter managed hosting and colocation; the key move was buying enterprise infrastructure capability rather than building it from scratch.
$1–5M ARR — ADD CLOUD PLATFORM CAPABILITY. AppFog and Tier 3 acquisitions added PaaS and IaaS; the key move was assembling a cloud portfolio through M&A.
$5–10M ARR — POSITION AS ENTERPRISE HYBRID CLOUD. CenturyLink Cloud targeted enterprises with legacy systems and network needs; the key move was bundling cloud with connectivity and managed services.
$10–50M ARR — COMPETE ON PRICE AND BREADTH. Hyperscale launches and price cuts in 2014 tried to match AWS; the key move was competing on commodity infrastructure, which strained margins.
$50–100M ARR — INTEGRATE AND SCALE THE PLATFORM. The company sought to unify products and expand enterprise adoption; the key move was building a coherent platform, but integration debt and developer adoption remained constraints.
$100M+ ARR — REASSESS THE CLOUD STRATEGY. CenturyLink sold its data centers and colocation business to Cyxtera in 2017; the key move was refocusing on networking and connectivity rather than competing head-on with hyperscalers.
Rule: Infrastructure platforms scale when product velocity, developer adoption, and utilization economics reinforce one another—not when distribution alone carries the strategy.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Enter infrastructure through a differentiated wedge—network, compliance, or workload specialization—then build developer adoption and utilization economics before competing on breadth or price.
SEQUENCE:
1. Identify a structural advantage before entering commodity infrastructure. Start with a customer segment where latency, compliance, or integration creates real value.
2. Build or acquire capability, then integrate it into one platform. Acquisitions must share identity, billing, APIs, and developer experience.
3. Scale only when utilization and developer adoption support economics. Infrastructure growth without utilization destroys margin.
WORKED: CenturyLink’s enterprise sales reach and Savvis install base gave it initial access to hybrid-cloud buyers.
CAUTION: Do not copy acquisition-led expansion without platform integration; buying hosting, PaaS, and IaaS does not create a coherent cloud. Also avoid competing with hyperscalers on generic compute price without a structural cost advantage.
bottom of page