Pitch Google's Next Hardware Bet, Its Ecosystem Fit and Year-One US Unit Sales

You have just become the head of Google's hardware division. Pitch the next big product the division should build, show how it fits with the rest of Google's products and services, and estimate its first-year unit sales in the US. ### Clarifying Questions - Should the product be a consumer device, or are enterprise, healthcare and developer hardware also in scope? - Does it have to be a category Google does not sell today, or would a new generation of an existing line such as Pixel, Nest or Fitbit count? - Is the unit estimate expected as a final number, or is a clearly structured formula with stated assumptions enough? ### Part 1 — The product and why Choose the product and argue why Google should build it now. ```hint Sell the why Lead with the user problem and why Google in particular can win it, not with a feature list. A quick look at the candidates you rejected makes the choice more credible. ``` #### What This Part Should Cover - A user problem and target segment that justify a new device - Why Google has a right to win against existing products in the category - A short, confident description of the core experience - The biggest risk to the bet and how to reduce it ### Part 2 — Fit with the Google ecosystem Explain how the product connects with Google's existing devices, platforms and services, and what each side gains. ```hint Count both directions Ask what the device borrows from services Google already runs, and what it gives back to them in usage, data or revenue. ``` #### What This Part Should Cover - Concrete integrations with current Google products rather than a generic promise that everything syncs - What the device adds back to those products and to Google's business - How the experience works for buyers outside Google's ecosystem, such as iPhone owners ### Part 3 — First-year US unit estimate Estimate how many units the product sells in the US during its first year on sale. ```hint Build the funnel Start from the people who could plausibly buy, narrow by need, price and first-year reach with every rate labeled as an assumption, then test the result against an anchor you trust. ``` #### What This Part Should Cover - A clear equation from a population base to units sold - Labeled assumptions for price, eligibility and conversion that follow from the chosen segment - Correct arithmetic, a range, and a sanity check ### What a Strong Answer Covers - One defensible product choice carried consistently through all three parts - Ecosystem links built on products Google offers today - An estimate whose inputs follow from the segment and price chosen in Part 1 - Awareness of the strategic risks: privacy, Google's earlier hardware history, competition and margins ### Follow-up Questions - What price would you set, and how does that price change your unit estimate? - What result after the first year would make you cancel the product? - How would you answer a skeptic who points to Google hardware bets that were later discontinued?