Build a Revenue Strategy for Google Assistant

Google Assistant is free to use on phones, smart speakers, smart displays and other devices. As its product manager, propose how Google should make money from it: who could pay, which option you would pursue first, and how you would know it is working. ```hint Anchor revenue in what people ask Before listing revenue ideas, sort the main things people ask the Assistant to do on each device. Every payer you propose should attach to one of those moments. ``` ### Clarifying Questions - Does success mean new direct revenue, or do stronger Search, hardware sales and other Google services count too? - Should the plan cover every surface, from phones and speakers to cars and TVs, or start with one? - Can the paying side be businesses, device makers or developers, or only the people who use the Assistant? - Are paid results acceptable in spoken replies, where the Assistant usually gives a single answer? ### What a Strong Answer Covers - Why Google offers the Assistant at all and what monetization has to achieve, stated before any idea - The possible payers and the user moments each would pay for, compared on explicit criteria that account for a voice interface - One prioritized first bet with a launch scope, plus what is deferred and why - Success metrics with guardrails, and how the effect on Google's other businesses is accounted for - Risks specific to an assistant that lives in homes, cars and pockets, such as privacy, partner conflicts and the cost of serving each request ### Follow-up Questions - If the Assistant moves onto a large generative model with a much higher cost per request, how does your plan change? - How would you detect whether a monetization feature makes people rely on the Assistant less over the following months? - Which of your options would put Google at odds with device makers or merchants, and how would you handle it?