The Expansion Accounts
Loopwire's account team wants to know which customers have ever signed a second contract. In this database an upgrade is not an edit — the old contract is closed and a new row is written — so a customer who has moved tier at any point leaves two rows behind, and a customer who has never moved leaves one. Those repeat signers are the accounts the team wants to study before writing next quarter's expansion plan.
subscriptions — one row per contract. account_id points at a row in accounts. plan is the tier the customer bought. mrr is what that contract bills every month, in dollars. start_date is the day it began. A contract that has stopped carries the day it stopped in end_date; one that is still running has nothing there, shown as — below and stored as NULL.
| id | account_id | plan | mrr | start_date | end_date |
|---|---|---|---|---|---|
| 1 | 1 | starter | 49 | 2022-11-03 | 2023-02-03 |
| 2 | 1 | growth | 149 | 2023-02-03 | — |
| 3 | 2 | growth | 149 | 2022-12-15 | 2023-06-15 |
| 4 | 3 | starter | 49 | 2023-01-31 | — |
| 5 | 4 | growth | 149 | 2023-02-06 | — |
| 6 | 5 | enterprise | 499 | 2023-02-22 | — |
| 7 | 6 | starter | 49 | 2023-03-01 | 2023-04-01 |
| 8 | 7 | growth | 149 | 2023-03-22 | — |
| 9 | 8 | enterprise | 499 | 2023-04-28 | — |
| 10 | 2 | starter | 49 | 2023-06-15 | — |
The table already exists in the database — there is nothing to create or load.
Task: Write a query that returns one row per account with two or more contracts on file, with columns account_id and subs, subs being how many contracts that account has. Running and stopped contracts both count. Most contracts first; accounts on the same number are listed with the smaller account_id first.
Example output
Shape only — these accounts and figures are invented:
| account_id | subs |
|---|---|
| 12 | 4 |
| 27 | 3 |
Sign in to solve this problem
Reading problems is free for everyone — solving them (Run, Submit, and tracking what you've solved) needs an account.
Sign in