Estimation: Working Back From G Suite Revenue to a User Count
Company: Google
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Other
You are told that G Suite, Google's paid suite of email, documents, storage and meeting tools for organizations (now called Google Workspace), has revenue of US \$7B. Starting from that figure, estimate how many users G Suite has.
Reason from assumptions you state aloud rather than from looked-up figures, show the arithmetic, and give both a point estimate and a range.
```hint Price one seat
Work out what one paying seat brings in over a year before you divide, and be explicit about how far realized prices might sit below list prices.
```
### Clarifying Questions
- Is the \$7B yearly revenue, and is it worldwide or for one region?
- Does "users" mean paid seats, or also people on free or discounted editions, such as schools and nonprofits, who bring in little or no revenue?
- Is all of the \$7B per-seat subscription revenue, or does it include add-ons and other products?
- Should the answer count unique people or seats, given that one person can hold several accounts and some purchased seats sit unassigned?
### What a Strong Answer Covers
- A stated definition of "user" and of the revenue's period and scope
- A plan or tier mix turned into a weighted revenue per seat, with every price and share labeled as an assumption
- Correct unit handling and arithmetic from revenue to a seat count
- A sanity check, and a range showing how sensitive the result is to the revenue per seat
### Follow-up Questions
- How would you estimate users on free education or nonprofit editions, which this revenue figure cannot reveal?
- If revenue grows next year, how would you separate growth from new seats versus price increases or plan upgrades?
- How many paying organizations does your seat count imply, and what does that suggest about the customer mix?
Overview: An estimation question that supplies G Suite's revenue and asks candidates to work back to its number of users. It tests defining users versus paid seats, building a weighted revenue per seat from a plan mix, handling monthly and yearly units, and sanity-checking the result.