Investible Partnerships™

The episode contains some useful strategic guidance about AWS's regional priorities (migrations/modernization, generative AI, SMB focus) and specific market signals (80M VMs on-prem, National Australia Bank's 50% Q for Developer acceptance rate). However, much of the content is high-level positioning rather than actionable insight. There's significant filler with pleasantries, throat-clearing, and repetition of known AWS themes without novel angles or surprising claims that would shift a partner's strategic thinking.

“there's more than 80 million virtual machines still out there and I think roughly 90% of them are still on prem”

“National Australia bank who's been using Q for Developer and has had some really fantastic results in terms of the code recommendations that Q for Developer is positioning to them with over a 50% acceptance rate”

The discussion largely recycles established AWS messaging around partner-led growth, Marketplace prioritization, and the importance of channel relationships. While the regional lens (APJ expansion with Malaysia/Thailand launches) adds some context, the underlying frameworks and talking points are standard channel-vendor conversation. The guest doesn't present contrarian views or first-principles rethinking about partnership models.

“our mission as an organization is to deliver the best experience for our customers to find, procure and use partner solutions to unlock the value of aws”

“we want partners involved in every single one of our accounts and every single one of our use cases across all of the industries”

The guest (Chris) holds a legitimate operational role as the AWS Partner lead for APJ, covering 17 countries and multiple partner types (SIs, ISVs, distributors, startups). This is a high-level position with real decision-making authority over regional strategy and partner investments. However, the guest is presented as a vendor representative rather than a partner operator who has built businesses or executed go-to-market at scale from the partner side, which limits caliber for a B2B operator audience.

“managing the AWS partners, uh, across Asia Pacific and Japan”

“we're cutting across all of our different fantastic partner types. Um, we've got large systems integrators, we've got born in the cloud systems integrators, our uh, distributor partners as well as our ISV partners”

The episode includes a few specific data points (80M VMs, 90% on-prem, National Australia Bank's 50% Q for Developer acceptance rate, 4,000+ ISVs on Marketplace, $1B in startup credits, Buy with AWS Marketplace API capability announced at Re:Invent). However, most claims lack supporting detail. The discussion of partner opportunities, customer segments, and strategic priorities remains largely abstract and categorical rather than supported with named examples, concrete metrics, timelines, or dollar figures that would help partners translate guidance into action.

“there's more than 80 million virtual machines still out there and I think roughly 90% of them are still on prem”

“National Australia bank who's been using Q for Developer and has had some really fantastic results in terms of the code recommendations that Q for Developer is positioning to them with over a 50% acceptance rate”

The host (Des) asks reasonably structured questions and demonstrates knowledge of AWS initiatives (Marketplace, Co-Sell, channel private offers, SMB competency). However, there's limited follow-up pressure or productive pushback. The host accepts broad claims without pressing for specifics - e.g., when Chris discusses 'demand signals' and partner misalignment, Des doesn't ask which partner types or segments are underperforming or request concrete examples of partnerships AWS views as misaligned. The final 'fast five' segment is soft and ceremonial rather than substantive.

“Where do you think partners today in APJ region? Where do you think they're playing? Uh, are they playing in the right places to be part of that or do you see that there's opportunity for partners to rethink?”

“partners struggle to translate the strategy and then create that alignment”