The product delivers the value. People carry the revenue.
Product-Passive Growth is when revenue keeps climbing, but almost all of it is started by people. The product delivers the value. It rarely starts the next revenue event. Every stage of the motion waits for someone to notice and act.
Early on, people carrying the revenue is the right call. Founders sell, CS saves accounts, reps catch expansion. It works, so it never gets redesigned. The company scales the labor model instead of shifting work to the product. The habit hardens into headcount.
This is the umbrella pattern behind the others. Revenue per employee is where it lands. If every point of growth needs more people to hold it, the business gets bigger. It does not get stronger. Growth stays real. It also gets more expensive and more fragile.
The product starts to carry the work it is best placed to carry. That spans acquisition, conversion, expansion, and retention. People stay in the motion where judgment, context, and trust matter. They stop being the trigger for everything. Revenue per employee is the number that moves when the shift is real.
Product-passive growth is not one failure. It is the parent condition underneath the four specific patterns that show up when a product sits out the revenue motion. Each named pattern is a place where the passivity becomes measurable and expensive.
Expansion Orphans. The product earned the expansion — deeper usage, more teams, rising volume — but no motion collected it. The expansion happens only if a person notices. This is product-passive growth showing up at the expansion stage, and it's where net revenue retention leaks most visibly.
Conversion Black Holes. Customers reach value, but no commercial motion starts. The product knows the account is ready and does nothing with that knowledge, so readiness dies waiting for a human trigger. This is passivity at the conversion stage.
Hollow Usage. Usage rises while the value that actually drives renewal quietly falls. The product reports activity but isn't performing the work of proving durable value, so retention rests on human relationships instead of product-evidenced outcomes. Passivity at the retention stage.
Borrowed NRR. Expansion booked today that the renewal can't sustain — growth the operating model manufactured through human effort rather than product-earned value. It looks like leverage and behaves like debt. Passivity dressed up as a win.
All four are the same root condition expressed at different stages: the product generates value but performs little of the revenue work, so humans carry and initiate the motion. Fix the passivity and the named patterns close. Treat the named patterns in isolation and they reappear, because the parent condition is still in place.
No. PLG is about acquiring and activating users. Product-Passive Growth is the whole revenue motion, including conversion, expansion, and retention. A company can run PLG at the front and stay product-passive everywhere else.
Usually with the failure mode costing the most right now. The Quick Test gives you a fast read on which pattern is heaviest.
Product-passive growth is the condition where revenue is real but people initiate nearly all of it. The product generates the value customers pay for, yet performs almost none of the revenue work — selling, converting, expanding, and renewing. Because humans carry the motion, growth stays tied to headcount instead of compounding through the product.
Ask, at each revenue stage, whether the revenue would still have happened if a specific person hadn't acted. If acquisition depends on a rep going looking, onboarding on a manager walking the customer to value, expansion on a CSM noticing, and renewal on a relationship, the product is passive. Two confirming signals: every new customer creates more work, and revenue per employee stalls while revenue rises.
Because it's the parent condition underneath the four specific patterns — Expansion Orphans, Conversion Black Holes, Hollow Usage, and Borrowed NRR. Each is the same root failure (the product generates value but performs little revenue work) expressed at a different stage. Fix the passivity and the named patterns close; treat them in isolation and they return.
Map where humans initiate revenue work at each stage, then start where the gap between product value and product-performed revenue is widest — usually expansion and conversion. Give the product a specific revenue job at each stage: surface the target, detect the milestone, trigger the conversion, flag the expansion, prove the renewal. Once the product performs the work by design, agents can execute it — creating leverage instead of just running the manual motion faster.
Seven questions. Five minutes. A pattern read on the spot, no call to see it.