Growth model, metrics and engagement plan for acquiring virtualization SaaS customers

Quick Overview

A product growth case for a virtualization SaaS sold as a monthly subscription with consumption-based pricing. The candidate chooses a growth model to win more customers, names the metrics that show whether acquisition is improving, and designs activities that deepen engagement with infrastructure software.

Growth model, metrics and engagement plan for acquiring virtualization SaaS customers

Company: Airbnb

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are the product manager for a virtualization product delivered as software as a service, competing in the market VMware is best known for. Customers pay monthly on a subscription, and pricing follows a consumption-based model. The goal is to increase customer acquisition. Answer the three parts below as one plan. ### Clarifying Questions - Is the monthly bill a flat plan fee, a metered charge for what the customer consumes, or a base fee plus metered usage? - Who are the target customers: small IT teams that can sign up on their own, or enterprises that buy through procurement and a sales team? - Does "acquisition" mean trial sign-ups, new paying accounts, or new accounts that reach steady usage? - Are most prospects replacing a hypervisor they already run, or setting up new environments? ### Part 1 — Choose a growth model and the actions it implies Which product growth model would you use to increase acquisition, and why does it suit a consumption-priced monthly subscription in virtualization better than the alternatives? Name the concrete actions you would take first under that model. ```hint Map who has to say yes List the people who must approve before a team moves workloads onto a new virtualization platform, then ask which growth model reaches each of them at the lowest cost. ``` #### What This Part Should Cover - Several growth models compared against this product's buyers and its pricing - One chosen model, with the reason it fits - Prioritized acquisition actions that follow from the chosen model ### Part 2 — Pick the essential metrics Which metrics would you treat as essential for knowing whether acquisition is really improving, and which would you watch as guardrails? ```hint Define "acquired" first Lay out the path from first visit to steady paid usage, and decide which step marks a customer as truly acquired when revenue depends on how much they consume. ``` #### What This Part Should Cover - A primary acquisition metric with a precise definition - Funnel and unit-economics metrics that explain why the primary metric moves - Guardrails that reveal growth bought at the wrong cost ### Part 3 — Design activities that deepen engagement What activities would you design to enrich engagement once customers are using the product? ```hint Decide what engaged looks like Infrastructure that works well runs quietly in the background, so describe what a healthy, engaged customer of this product does before designing activities that move customers toward it. ``` #### What This Part Should Cover - A definition of engagement that suits infrastructure software - Activities across onboarding, day-to-day use and the wider user community, each tied to that definition - How deeper engagement feeds back into acquiring new customers ### What a Strong Answer Covers - One consistent story linking the growth model, the metrics and the engagement plan - The consumption-based pricing reflected in every part, from trial design to revenue ramp and bill predictability - A clear view of who evaluates the product, who signs for it, and how each is reached - Risks particular to selling compute-heavy infrastructure, with mitigations ### Follow-up Questions - How would the plan change if most prospects are locked into an incumbent hypervisor under multi-year contracts? - If new customers take several months to ramp their usage, how would you judge whether an acquisition channel pays back? - Self-serve sign-ups double but paid conversion falls: what would you investigate first?

Overview: A product growth case for a virtualization SaaS sold as a monthly subscription with consumption-based pricing. The candidate chooses a growth model to win more customers, names the metrics that show whether acquisition is improving, and designs activities that deepen engagement with infrastructure software.

Airbnb logo
Airbnb
Jan 31, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are the product manager for a virtualization product delivered as software as a service, competing in the market VMware is best known for. Customers pay monthly on a subscription, and pricing follows a consumption-based model. The goal is to increase customer acquisition. Answer the three parts below as one plan.

Clarifying Questions Guidance

  • Is the monthly bill a flat plan fee, a metered charge for what the customer consumes, or a base fee plus metered usage?
  • Who are the target customers: small IT teams that can sign up on their own, or enterprises that buy through procurement and a sales team?
  • Does "acquisition" mean trial sign-ups, new paying accounts, or new accounts that reach steady usage?
  • Are most prospects replacing a hypervisor they already run, or setting up new environments?

Part 1 — Choose a growth model and the actions it implies

Which product growth model would you use to increase acquisition, and why does it suit a consumption-priced monthly subscription in virtualization better than the alternatives? Name the concrete actions you would take first under that model.

What This Part Should Cover Guidance

  • Several growth models compared against this product's buyers and its pricing
  • One chosen model, with the reason it fits
  • Prioritized acquisition actions that follow from the chosen model

Part 2 — Pick the essential metrics

Which metrics would you treat as essential for knowing whether acquisition is really improving, and which would you watch as guardrails?

What This Part Should Cover Guidance

  • A primary acquisition metric with a precise definition
  • Funnel and unit-economics metrics that explain why the primary metric moves
  • Guardrails that reveal growth bought at the wrong cost

Part 3 — Design activities that deepen engagement

What activities would you design to enrich engagement once customers are using the product?

What This Part Should Cover Guidance

  • A definition of engagement that suits infrastructure software
  • Activities across onboarding, day-to-day use and the wider user community, each tied to that definition
  • How deeper engagement feeds back into acquiring new customers

What a Strong Answer Covers Guidance

  • One consistent story linking the growth model, the metrics and the engagement plan
  • The consumption-based pricing reflected in every part, from trial design to revenue ramp and bill predictability
  • A clear view of who evaluates the product, who signs for it, and how each is reached
  • Risks particular to selling compute-heavy infrastructure, with mitigations

Follow-up Questions Guidance

  • How would the plan change if most prospects are locked into an incumbent hypervisor under multi-year contracts?
  • If new customers take several months to ramp their usage, how would you judge whether an acquisition channel pays back?
  • Self-serve sign-ups double but paid conversion falls: what would you investigate first?