36Learners on our language app avoid speaking practice. Design an AI conversation partner, and decide which plan gets it.▼mediumNewDuolingoGoogle◆ premiumSpeaking is the skill learners avoid and value most. Design short, scenario-based calls at the learner's level with one correction per turn, and move it into the main paid plan once the cost per minute allows.Practise this question →Read answer →
15Should we include AI features in our existing plans, or sell them as a paid add-on?▼mediumNewNotionAtlassianCanva◆ premiumA packaging decision with adoption, revenue and margin pulling in different directions. The interviewer wants the trade-offs and a structure that captures value without stalling adoption.Practise this question →Read answer →
25A new AI research capability could become a feature or a standalone product. Which would you choose?▼expertNewGoogleMicrosoftAmazon◆ premiumCompare the customer job, buyer and distribution advantage before choosing a separate brand, interface or P&L.Practise this question →Read answer →
37A year after launch, 4% of eligible seats have bought our AI add-on. The CFO asks if it's failing. What do you measure before deciding?▼mediumNewMicrosoftGoogle◆ premiumA low attach rate can mean few accounts buy, or buyers don't use it, or the denominator is wrong. Measure penetration inside buying accounts and active use of paid seats before changing the packaging.Practise this question →Read answer →
35We're adding hosted web search and code execution to our API. Do we price them per call, per token, per container-hour, or bundle them?▼mediumNewAnthropicOpenAIGoogle◆ premiumEach tool has a different cost driver: search licences per query, retrieved content as tokens, containers by time. Price each on its driver, decide whether retrieved text is billed, and bundle cheap tools with expensive ones.Practise this question →Read answer →