Getting the numbers for API-driven transformation to add up
summary
Argues that API investment must tie to what teams can control and gives a fictional acquired online learning platform to show measurable asks: time to onboard new accounts falls, course completion rises and sales support cost drops for customer teams; engineering cuts onboarding-to-competency and raises code quality using co‑pilot/gen‑AI; architecture tracks API reuse across the organization and governance pass rates; product measures direct API revenue and less than a third deliver revenue uplift warns of evaporating business cases unless outcomes are scoped tightly.
AI-written summary · about
chapters (11)
- 0:00API investment justification
- 2:15API business cases matter
- 6:15API needs by team
- 9:45Customer team priorities
- 13:03Product team goals
- 15:13Engineering team security
- 16:58Architecture team governance
- 18:21API monetization strategies
- 21:10API value connection
- 23:26Avoiding business case loss
- 24:54Key takeaways
related talks
27mGetting the numbers for API-driven transformation to add up.
28mImpact Intelligence for APIs
26mMastering API Strategies for Digital Transformation
26mThe Business of APIs
29mTransform Your Business with Strategic API Management
26mAPIs & the three pillars of digital transformation
21mInnovation and Impact - Adopting APIs for enterprise transformation.
22mLeading the future: AI and APIs, a powerful duo