top of page
Business & Enterprise
Cloud Technology
Cloud Infrastructure
Akamai
Built the internet’s performance layer by distributing content closer to users, then converted that global edge footprint into security and cloud computing, despite CDN commoditization and hyperscaler competition.
1
MODEL
BUSINESS MODEL
SaaS
- Performance as the initial wedge: Akamai solved slow content delivery by caching and routing content through distributed servers closer to users.
- Global edge footprint: It built a network of servers and points of presence that became difficult for new entrants to replicate.
- Usage-based monetization: Customers paid based on traffic delivered, creating revenue that scaled with internet usage.
- Security expansion: DDoS mitigation, bot management, API security, Zero Trust and web application protection were layered onto the same edge network.
- Cloud computing expansion: The 2022 Linode acquisition and Akamai Connected Cloud extended the platform into distributed compute, storage and databases.
- Portfolio transformation: In 2025, security became the largest revenue driver at $2.24 billion, while delivery remained foundational at $1.257 billion.
1. Identify a performance bottleneck at scale. Find a recurring constraint—latency, reliability, fraud, bandwidth or data transfer—that worsens as the customer grows.
2. Build infrastructure that improves with scale. The solution should become more valuable as more customers, locations or transactions use it.
3. Monetize the constrained resource. Price by traffic, requests, data processed or protected workload so revenue grows with customer usage.
4. Expand into adjacent risks on the same infrastructure. Once you own the traffic path or data flow, add security, observability, compute or compliance capabilities.
5. Move up the stack before commoditization. When the original capability becomes a commodity, use the installed footprint to sell higher-value decision and protection layers.
Avoid: building infrastructure without a differentiated control point; if customers can switch providers through a simple DNS change or API call, retention depends on price rather than workflow depth.
DISTRIBUTION MODEL
Akamai proved that distributed content delivery could become essential internet infrastructure. Founded in 1998 by MIT professor Tom Leighton and student Danny Lewin, with Jonathan Seelig and Randall Kaplan, it used algorithms for intelligent routing and content replication to solve slow, unreliable web delivery. Akamai launched commercially in April 1999 with Yahoo! as a charter customer and grew into a global platform spanning thousands of locations in more than 130 countries. In 2025, it generated $4.21 billion in revenue: security revenue of $2.24 billion, delivery revenue of $1.257 billion and compute revenue of $708 million.
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Direct Sales, Channel Partners, Partnerships, Content Marketing
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Direct enterprise sales: Akamai sold to media companies, e-commerce platforms, banks, gaming companies and global enterprises that needed performance and reliability at scale.
- Technical validation: Solutions engineers, proofs of concept and performance benchmarks helped technical buyers justify deployment.
- Partner ecosystem: System integrators, telecom partners and resellers extended reach into enterprise accounts.
- Security cross-sell: Once Akamai delivered traffic, it could sell DDoS protection, bot management and application security to the same customer.
What worked: Sell to the team that owns the pain—engineering, infrastructure or security—and prove performance with technical evidence; use the initial deployment as the path into adjacent high-value services.
Trap if copied blindly: Infrastructure sales fail when the buyer cannot measure the benefit; without latency, uptime, fraud-loss or cost benchmarks, the vendor becomes a replaceable line item.
| PATTERNS OF THIS MODEL
PATTERNS IN USAGE-BASED INFRASTRUCTURE SAAS:
1. The network becomes the moat. Distributed points of presence, routing intelligence and operational scale create barriers that software alone cannot match.
2. Usage pricing aligns with customer growth. Traffic, requests and compute scale naturally with the customer’s business, but can create bill shock and procurement friction.
3. Infrastructure expands into security. The party that sees or carries the traffic is positioned to detect and stop abuse.
THE WEAKNESS: Infrastructure businesses face capital intensity and commoditization. If the core service becomes interchangeable, customers migrate to cheaper providers or hyperscalers, forcing the vendor to move up into higher-value software and security.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — EDGE AI INFERENCE. The opportunity is to run low-latency AI inference, personalization and content moderation close to users rather than sending every request to a central cloud. The winner will combine distributed compute with model routing, cost controls and governance.
GOLDMINE 2 — API AND BOT DEFENSE. As applications become API-first, the gap is protecting machine-to-machine traffic, credential abuse and automated fraud. Security must operate at the request path, not merely at the network perimeter.
GOLDMINE 3 — DISTRIBUTED DATA PLANE. The opportunity is to process, cache and govern data close to its source for IoT, gaming, retail and industrial workloads. Latency-sensitive use cases need more than centralized cloud.
THE PIT — CDN AS A COMMODITY. Basic caching and delivery have become price-sensitive; a new entrant should not compete solely on bandwidth cost.
THE SECOND PIT — USAGE PRICING WITHOUT PREDICTABILITY. Customers may resist infrastructure bills that vary sharply with traffic; successful vendors pair usage pricing with commitments, controls and transparent forecasting.
MOVE WITH CAUTION: Do not build a global edge network before proving one high-value workload. Capital intensity and operational complexity can consume the company before the differentiated use case is validated.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Akamai entered as the commercial internet was scaling and websites faced slow load times, congestion and unreliable delivery. It created a content-delivery category by distributing content across servers near end users rather than relying solely on origin servers. Yahoo! became a charter customer in 1999, validating the model. The initial buyer was a media or internet company with high traffic and a clear performance problem; the value proposition was faster, more reliable digital experiences.
MARKET TYPE
Emerging Market
ENTRY STRATEGY
Greenfield Entry
WHY THEY WON
Akamai created the commercial CDN market by solving a newly urgent problem: internet content was growing faster than the ability of origin servers and networks to deliver it reliably. It did not merely improve existing hosting; it introduced a distributed delivery layer between content owners and users. Its structural opening was that performance became a business metric as websites, media and e-commerce scaled. The transferable lesson is that new markets emerge when a technological shift creates a bottleneck that incumbents treat as someone else’s problem.
EXECUTION
Akamai entered by creating a new CDN category rather than replacing an established software vendor. The initial bet was that high-traffic internet companies would pay for faster, more reliable content delivery. This was viable because Akamai could demonstrate measurable performance gains and deploy its distributed network for early customers such as Yahoo!. The essential prerequisite was technical proof and reliable operations; the approach would fail if latency improvements were marginal or outages undermined trust.
FOOTHOLD STRATEGY
Beachhead Strategy
Akamai’s first beachhead was high-traffic media and internet companies suffering from slow content delivery. The pain was congestion, slow page loads and poor user experience; these buyers were reachable through technical communities, early internet relationships and direct sales. They could pay because performance affected engagement, ad revenue and customer experience. From media delivery, Akamai expanded into e-commerce, enterprise applications, security and cloud computing.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Akamai’s campaigns moved the buyer from “make the site faster” to “secure and run critical digital workloads on a global platform.”
KEY LEARNING: The non-obvious principle is that infrastructure companies sustain growth by converting a physical or network footprint into higher-value software capabilities; distribution without a decision layer becomes commoditized.
HOW TO USE: If your product owns a critical data path or workflow, identify the risk or decision that travels through it, then build the security, intelligence or automation layer before competitors commoditize the base capability.
KEY LEARNING
THE STANDARD: In a new market, the entrant must prove a newly urgent bottleneck and build the infrastructure that resolves it.
RULE 1 — QUANTIFY THE BOTTLENECK. Latency, downtime, fraud loss or bandwidth cost must be measurable and material.
RULE 2 — TARGET SCALE USERS FIRST. Customers with high traffic or high consequence feel the pain earliest and can validate the infrastructure.
RULE 3 — BUILD A CONTROL POINT. Owning traffic, identity, data or workflow creates the right to expand into adjacent services.
RULE 4 — KNOW WHEN THE CATEGORY COMMODITIZES. If the base capability becomes interchangeable, move up the stack into security, intelligence or orchestration.
MARKET TYPE: New Market (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN TECHNICAL INFRASTRUCTURE SALES:
1. Engineering credibility drives adoption. Technical buyers require benchmarks, architecture clarity and operational reliability before procurement.
2. Proof-of-concept deployments reduce perceived risk. A limited rollout demonstrates performance before an enterprise-wide commitment.
3. Security expands from visibility. Once a vendor carries traffic, it can detect abuse and sell protection.
4. THE WEAKNESS: Technical marketing can attract engineers without procurement power; the vendor must connect performance gains to revenue, risk or cost outcomes.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Greenfield entry is appropriate when the company creates a new solution category for an emerging technical or operational bottleneck.
RULE 1 — Start with a measurable pain. The customer must be able to quantify the cost of the problem in latency, revenue, risk or operational expense.
RULE 2 — Prove the infrastructure works under real load. Early customers should stress-test reliability, performance and security before broad adoption.
RULE 3 — Build a repeatable deployment model. Infrastructure that requires bespoke integration for every customer will struggle to scale.
RULE 4 — Reject greenfield entry when capital requirements exceed validated demand. Do not build a global network before proving that customers will pay for the differentiated outcome.
Example: Akamai created CDN infrastructure; a failure pattern is building edge infrastructure before identifying a workload with sufficient latency sensitivity and willingness to pay.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A beachhead works when one customer group has a concentrated, measurable pain and the vendor can prove superior performance.
RULE 1 — Target customers for whom milliseconds matter. Media, gaming, e-commerce and financial platforms experience direct revenue or engagement effects from performance.
RULE 2 — Use technical buyers as champions. Infrastructure adoption requires engineering credibility, not just executive sponsorship.
RULE 3 — Measure performance and reliability outcomes. Latency reduction, cache-hit rate, uptime and attack mitigation are the metrics that justify renewal.
RULE 4 — Expand through the traffic path. Once the vendor carries or observes traffic, security and compute become natural adjacencies.
Failure pattern: selling infrastructure to customers whose workloads are too small to generate meaningful performance differences.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Akamai monetizes through usage-based contracts tied to traffic delivered, security workloads protected and compute consumed. In 2025, delivery revenue was $1.257 billion, security revenue was $2.24 billion and compute revenue was $708 million. The shift toward security and compute reflects a deliberate move away from traffic-only pricing toward higher-value, more differentiated workloads.
REVENUE MODEL
Usage-Based, Subscription, Service Fee
PRICING MODEL
Usage-Based Pricing, Tiered Pricing, Custom Enterprise Pricing
WHY THEY WON
Customers pay based on traffic delivered, security services used and cloud compute consumed. Contracts may include committed spend, overage pricing and professional services. Revenue scales with customer traffic, attack exposure, application complexity and compute usage; infrastructure, bandwidth and support costs rise with delivery volume.
Akamai prices delivery by traffic volume, security by protected traffic, workload or module, and compute by usage. Enterprise contracts often include commitments and negotiated rates. The pricing model aligns revenue with customer scale but requires transparency and controls to prevent bill shock.
TARGET AUDIENCE
Media and streaming companies (Delivery; want fast, reliable video and content delivery); e-commerce and travel platforms (Security + Delivery; want performance, bot defense and checkout protection); financial services (Security; want DDoS, API and Zero Trust protection); developers and cloud-native teams (Compute; want distributed compute, storage and edge deployment); global enterprises (full platform; want security, delivery and compute from one provider).
CUSTOMER BUYING BEHAVIOUR
The trigger is slow performance, outages, traffic spikes, DDoS attacks, bot fraud, API abuse or cloud-cost pressure. Engineering, security and infrastructure leaders evaluate through benchmarks, proofs of concept, security reviews and procurement. Adoption begins with delivery or security; expansion follows when the customer trusts the platform with more critical workloads.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Customers are not buying bandwidth; they are buying revenue protection, user experience and risk reduction at scale.
RULE 1 — PRICE THE CONSTRAINED RESOURCE. Traffic, requests, protected workloads and compute reflect the customer’s actual consumption of infrastructure.
RULE 2 — SELL OUTCOME, CHARGE USAGE. The buyer cares about conversion, uptime and fraud prevention; usage-based pricing captures the scale of that value.
RULE 3 — USE SECURITY TO ESCAPE COMMODITIZATION. A CDN can be replaced on price; protection of revenue-critical traffic is harder to displace.
RULE 4 — WATCH THE BILL-SHOCK TRAP. Unpredictable infrastructure invoices create procurement resistance; commitments, dashboards and alerts are part of the product.
The buyer is really buying reliable, secure digital performance, proven by latency, uptime, attack mitigation and revenue-critical workload adoption.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
CDN commoditization: Basic delivery has become price-sensitive, with competition from Cloudflare, Fastly, Amazon CloudFront and hyperscalers.
Traffic-based revenue decline: Delivery revenue fell 5% in 2025 to $1.257 billion, showing that traffic growth does not guarantee revenue growth.
Hyperscaler substitution: AWS, Google Cloud and Microsoft Azure can bundle delivery, security and compute with broader cloud relationships.
Capital intensity: Maintaining a global edge network requires ongoing investment in servers, bandwidth, locations and operations.
Security competition: Cloudflare, Zscaler, Palo Alto Networks and Cloudflare compete for overlapping security budgets.
Akamai reported $4.21 billion revenue in 2025, with security at $2.24 billion, delivery at $1.257 billion and compute at $708 million; customer-level churn and gross margin by product are not disclosed in the sources reviewed.
Where the model can break
4
MOTION
motion ge cs
Akamai needed an enterprise motion for global media, e-commerce, financial-services and technology customers with complex performance, security and compliance requirements. Its system included direct account teams, solutions engineering, proofs of concept, partner channels and implementation support. Growth from Yahoo! as a charter customer to a $4.21 billion revenue platform showed an enterprise motion that operated beyond founder-led sales.
GROWTH EXPANSION MODEL
Platform Expansion, Acquisition-Led Growth
HOW THEY EXPAND
Akamai landed through content delivery, then expanded within accounts through security, bot management, API protection, Zero Trust and cloud computing. Platform expansion came through the shared edge network; acquisition-led growth added Prolexic in 2014, Guardicore in 2021 and Linode in 2022. The dependency is the traffic path: security and compute expand when Akamai already carries, observes or protects the customer’s critical workload.
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Against Cloudflare, Akamai differentiated through enterprise scale, media delivery depth and security breadth. Against Fastly, it emphasized global footprint and managed enterprise services. Against AWS CloudFront, it positioned neutrality, multi-cloud support and specialized security. Its advantage was combining delivery, security and distributed compute on one global platform.
GROWTH ENGINE
GTM
Content Flywheel
A customer begins with delivery or DDoS protection, sees performance and risk improvements, then adopts bot management, API security, Zero Trust or compute. More traffic, applications and geographies increase account value and create switching costs. Account teams, solutions engineers and partners expand the relationship. The loop depends on measurable performance, security outcomes and operational reliability; an outage or missed attack breaks it.
Akamai uses a sales-led, technically supported GTM. Direct sales targets infrastructure, security and engineering leaders; solutions engineering validates performance and architecture; partners extend reach; customer success drives module expansion. The primary motion is sales-led because enterprise infrastructure requires security review, integration and procurement, while technical proof-of-concept creates the evidence that supports expansion.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is Akamai’s global distributed infrastructure: servers, points of presence, routing intelligence, security telemetry and operational expertise. This footprint is expensive and time-consuming to replicate, while accumulated traffic and attack data improve performance and threat detection.
| MOAT INTELLIGENCE
THE STANDARD: Infrastructure scale lasts when the physical network, routing intelligence and operational data create advantages that software alone cannot replicate.
RULE 1 — OWN THE TRAFFIC PATH. Carrying customer traffic creates visibility, performance control and security opportunity.
RULE 2 — TURN TELEMETRY INTO PROTECTION. Attack data and traffic patterns improve detection and response.
RULE 3 — DEEPEN WORKFLOW OWNERSHIP. Security, compute and data services increase switching costs beyond basic delivery.
THE SIGNAL: Akamai operates infrastructure across thousands of locations in more than 130 countries and generated $4.21 billion revenue in 2025. The moat does not protect against commoditized delivery, hyperscaler bundling or a competitor with a materially better developer experience.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M REVENUE — VALIDATE DISTRIBUTED DELIVERY. Akamai incorporated in 1998 and launched commercially in April 1999 with Yahoo! as a charter customer.
WATCH: Whether distributed caching and routing produced measurable performance gains.
$1–5M REVENUE — PROVE HIGH-TRAFFIC FIT. Akamai focused on media and internet companies where slow delivery directly affected user experience and revenue.
$5–10M REVENUE — SCALE THE GLOBAL NETWORK. The company expanded its edge footprint and operational capacity to serve growing internet traffic.
$10–50M REVENUE — EXPAND INTO ENTERPRISE APPLICATIONS. Akamai moved beyond media into e-commerce, gaming, travel and financial services.
$50–100M REVENUE — ADD SECURITY. DDoS mitigation, bot management and application security turned traffic visibility into a higher-value business.
$100M+ REVENUE — BUILD A PLATFORM. Prolexic, Guardicore and Linode acquisitions expanded security, Zero Trust and cloud computing; by 2025, Akamai generated $4.21 billion revenue.
Rule: Own a measurable infrastructure bottleneck first; expand into security and compute only when the footprint creates trust, visibility and a durable control point.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Build an infrastructure business by solving a measurable scale bottleneck, monetizing the constrained resource, and expanding into higher-value security or intelligence layers before the base capability commoditizes.
SEQUENCE:
1. Find a bottleneck that worsens with customer scale. Identify latency, reliability, fraud, bandwidth or data-transfer pain that becomes more expensive as the customer grows.
2. Prove performance with a technical champion. Use benchmarks and proofs of concept to establish credibility with the team that owns the problem.
3. Expand into the risk that travels through the infrastructure. Add security, intelligence or compute capabilities only when the platform already owns the relevant traffic or data path.
WORKED: Akamai used content delivery to build a global edge footprint, then converted that footprint into security and cloud computing.
CAUTION: Do not copy usage-based pricing without predictability controls; bill shock creates procurement resistance. Do not build capital-intensive infrastructure before validating a workload where latency, reliability or security creates clear willingness to pay.
bottom of page