Platform-Embedded Distribution: How Stripe Connect, Shopify, and AWS Capture Markets Through Other Companies' Platforms

Companies Using This Strategy

The arms-dealer thesis

Platform-embedded distribution is sometimes called the 'arms dealer' strategy — instead of fighting in a specific market, sell the tools everyone in that market needs. The metaphor reveals the strategic appeal: the arms dealer profits regardless of who wins, while combatants face existential risk. Stripe Connect is the canonical modern example. Stripe doesn't compete with Shopify, Lyft, or Substack — Stripe sells the payments infrastructure all of them need. As any platform grows, Stripe grows.

What makes a platform 'embeddable'

Three properties make infrastructure embeddable: (1) **API-first design** — see API-first distribution strategy. Developers integrate APIs more readily than they negotiate sales contracts. (2) **Margin-friendly pricing** — pricing structure that lets the platform owner pay you a small percentage while keeping their margin. Stripe's per-transaction pricing works because it scales with platform success rather than imposing fixed costs. (3) **White-label or co-brand option** — platform owner can present the infrastructure as their own (white-label) or in partnership (co-brand). Either reduces friction for the platform owner.

Network effects in platform-embedded distribution

Successful platforms develop network effects: (1) **More platforms** → more developer attention → more integrations → easier to build → more platforms. (2) **Standardization effect** — once enough platforms use Stripe (or AWS), 'use Stripe' becomes the default assumption. New platforms join without considering alternatives. (3) **Tooling ecosystem** — third-party tools (analytics, integration tools, expert consultants) emerge around dominant platforms. The ecosystem reinforces the platform's dominance. Network effects in platform-embedded distribution compound across years. Stripe's 2025 position is largely the result of network effects that started compounding in 2012-2015 when Stripe Connect first launched.

Trade-offs vs. direct customer relationships

Platform-embedded distribution has tradeoffs: **Advantages**: scale through platforms instead of direct customer acquisition; durable returns as platforms grow; lower CAC per ultimate end-user. **Disadvantages**: less direct customer relationship (platform owns the user); pricing pressure from platforms that grow large enough to threaten internalization; dependence on platforms making good decisions about their own growth. The right choice depends on category economics. For categories where platforms are the natural customer (payments, cloud, communications), embedded is structurally correct. For categories where end-users are the natural customer, direct is usually better.

Defense against internalization

Major risk in platform-embedded distribution: large platforms grow big enough to build their own version of your infrastructure (internalize). Shopify could in theory build its own payment processing; AWS could expand its own ML services to displace Hugging Face; etc. Defense mechanisms: (1) **breadth of platform customers** — losing one major customer is survivable if you have many; (2) **continuous capability gap** — platforms struggle to match dedicated infrastructure providers because building infrastructure isn't their core competence; (3) **partnership agreements** that contractually limit competitive behavior. Stripe's defense against major platform internalization has been to keep capability significantly ahead of what platforms can build internally.

How to Implement

1. 01Identify the platform layer in your category — who builds on infrastructure like yours?
2. 02Design API-first; eliminate integration friction
3. 03Price as a percentage of platform-generated revenue rather than fixed fees
4. 04Build white-label and co-brand options for platforms that want either
5. 05Invest in ecosystem (third-party tools, expert consultants) that reinforces platform dominance
6. 06Stay ahead of capability that platforms could build internally
7. 07Cultivate partnerships with strategic platform customers as ecosystem anchors

Common Pitfalls

• 01Pricing structures that incentivize platforms to internalize (per-seat or per-month fees)
• 02Insufficient differentiation from what platforms could build themselves
• 03Concentration risk on single major platform customer
• 04Slow integration (loses to faster alternatives)
• 05Direct competition with own platform customers

Sources

• Stripe Connect documentation