The product earned the expansion. Nobody collected it.
An Expansion Orphan is an account that has earned more revenue and never been asked for it. The usage is deeper. The dependency is growing. A new team or use case has shown up. No expansion motion has started, because no one has noticed yet.
Expansion is often treated as a customer success job. A CSM runs a review, sees broader usage, and starts a conversation. That works when the customer base is small. At scale it turns expansion into a capacity problem. The revenue shows up only when a person catches the signal.
NRR has no real ceiling when expansion waits on a person noticing. If expansion runs on CS capacity, part of your NRR is really a staffing number. Add customers faster than you add CS, and the orphans pile up. The revenue is real. It sits in the behavior, waiting for someone to act.
More CS headcount does not fix this. The product has to surface the expansion signal itself. Then the motion starts when the behavior appears, not when a person looks. The human still runs the conversation and brings the judgment. The product decides when the conversation should start, and hands over the context.
No. Tools can store the signal. The gap is that no motion starts when the signal appears. That is a design question, not a software-purchase question.
Churn risk is value slipping. An Expansion Orphan is value already won and never billed. Opposite direction, same root cause: the motion depends on a human noticing.
Seven questions. Five minutes. A pattern read on the spot, no call to see it.