How does Midsummer drive expansion? It reads every customer account overnight: usage changes, new teams, new stakeholders, new priorities. When an account shows room to grow, the move is drafted with the reason attached, and a person approves it before anything leaves.
Expansion signals do not announce themselves
A second team starts using the product. A champion gets promoted. Usage creeps toward the plan's ceiling. None of these arrive as a ticket; they accumulate quietly in accounts the team touches at renewal time. By the time the renewal brief gets written, the expansion window has been open for months.
The customer list, read like a pipeline
Midsummer gives customer accounts the same nightly read as prospects: what changed, who moved, what the usage says, what the thread hints at. The expansion move is drafted when the reason appears, so the conversation starts at the customer's moment, not the quarter's end.
Growth without pressure
Customers can smell a quota. The expansion conversation works when it is about their growth, not your number: the draft is grounded in what the account is actually doing, and your person approves every send. The relationship expands because it is ready to.
Questions about expansion
Where do expansion signals come from?
From the account itself: usage patterns, org changes, new stakeholders, the questions in the thread. The department reads what you already have access to and attaches the reason to every proposed move.
Does it work with our account managers?
Yes. The AM keeps the relationship; the department does the reading and preparing. The AM's day starts with the accounts that moved and the drafts ready, instead of a re-read of the whole list.
How does this show up at renewal?
The renewal brief is prepared with the full worked history: usage, value, open threads, and the expansion signals along the way. The renewal conversation starts from evidence, not reconstruction.
Will it push customers who are not ready?
No. Where the honest read is that the account is fine as it is, the move is to keep serving it, and the log says so. Pressure is how expansion turns into churn.