Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Alan Chhabra maps AWS like Game of Thrones: some kingdoms report to Amazon's Andy Jassy, others to AWS's Matt Garman. He shows this top-level org chart to reveal the power base before pursuing a partnership, because different components have different interests. That map changes the pitch.

Related Insights

To overcome political hurdles and NVIDIA's dominance, Cerebras partnered with AWS by creating a joint architecture that combined its chip with AWS's own Tranium IP. This turned a potential internal competitor into a champion and gave AWS a unique, competitive offering.

The primary barrier to AI adoption in large companies is not technological but organizational. Success depends on understanding the 'real' org chart—the informal network of influencers who control data and approve projects, which often differs from the official hierarchy.

Amazon's strategy emphasizes infrastructure over proprietary models. By focusing on AWS cloud dominance, custom chips like Trainium, and key partnerships (OpenAI, Anthropic), Amazon is positioning itself as the essential, neutral compute provider for the AI industry, regardless of who builds the winning model.

Alan Chhabra says Cerebrus won AWS by pairing AWS Tranium for pre-fill with Cerebrus for decode, so AWS uses its own chip IP while competing with Nvidia. The architecture also let AWS protect its Nvidia supply relationship while adopting a faster, price-performance play. That turned a chip pitch into a political deal.

The host reveals a key heuristic: a company's organizational structure (e.g., functional, divisional) is a map of its priorities, internal tensions, and likely points of failure. Understanding the org chart provides an immediate, deep insight into a business's operational challenges without needing to know anything else.

Alan Chhabra says a CEO hiring a partner leader should ask the candidate to explain the company's partner landscape and the top partner's org chart. If they cannot do that, they have not done the homework. He treats this as more valuable than jumping into pipeline activity.

Alan Chhabra flew to China seven times to crack Alibaba while building MongoDB's hyperscaler deals. He says AWS and Azure did not want MongoDB to have a strong Chinese partnership before them, so the rival deal created urgency and neutralized enemies. That is political leverage, not product speed.

Alan Chhabra says a champion in one situation can become an enemy in another. An enemy does not mean personal hostility; it just means doing X with you is not in that person's best interest, while Y might be. So partner leaders must map interests, not likeability.

AWS CEO Matt Garman's emphasis on "customer choice," combined with Jeff Bezos's philosophy of being customer-obsessed rather than competitor-obsessed, suggests AWS might offer Google's TPUs in their data centers if customers demand them, despite the direct competition.

AWS structured itself as independent P&Ls, like AWS Marketplace. This autonomy allowed teams to make decisions and ship code with startup-like speed, avoiding corporate bureaucracy and fostering rapid innovation, even within a large organization.