Two axes, two outcomes
| Adoption depth | Adoption breadth | |
|---|---|---|
| Measures | Intensity inside a workflow | Coverage across the product |
| Typical metric | Weekly active users per licensed seat, records processed, share of daily work | Modules live, features enabled, departments using the account |
| Predicts | Renewal and gross retention | Expansion and seat growth |
| Failure mode | One team dependent, no room to grow | Wide, shallow usage that nobody would miss |
Depth creates the switching cost
Switching cost is not a contract term, it is the work a customer would have to redo. An account that closes its month through your product, or runs its weekly forecast review inside it, cannot leave without rebuilding an operating routine that people already depend on. That is what depth buys.
This is also why a shallow account with a high login count reads as healthy and is not. Sessions measure visits. Depth measures dependence, and only dependence survives a budget review.
Breadth is the expansion path, in that order
Sequence matters. Depth in one workflow gives the customer an internal result they can point to when asking for more budget, which is what makes the second module fundable. Selling breadth first produces a bigger contract with no proof underneath it, and the renewal arrives with nothing to defend.
Score both axes separately inside the account health model and use them for different plays. Falling depth in the primary workflow triggers a retention intervention. Stable depth with low breadth triggers an expansion play, and it is the cleanest expansion signal available because it comes from behavior rather than from a rep's optimism.
Held apart this way, the two numbers do real work in the revenue model. Depth explains where net revenue retention is coming from, and breadth tells you which accounts belong in next quarter's expansion pipeline when you forecast revenue rather than guess at it.
Frequently Asked Questions
What is the difference between adoption depth and adoption breadth?
Depth is intensity within a workflow, measured by frequency, volume of records processed, or share of the team's daily work running through the product. Breadth is coverage across the product, measured by how many modules, features, or departments are live. An account can score high on one and near zero on the other.
Which one predicts renewal?
Depth. An account that runs a daily operating process through your product has built switching cost into its own operations, and replacing you means rebuilding that process. Breadth without depth is a set of accounts that logged into six modules once and depend on none of them.
Which one predicts expansion?
Breadth, once depth exists in at least one workflow. A customer already getting a result from one module has the internal proof needed to fund the next one. Selling breadth into an account with no depth anywhere produces a larger contract that churns in a single cycle.
How do you measure both without building a data warehouse?
Define five to eight core workflows and score each account on two axes: how many of those workflows have any activity in the last 30 days, and what share of the account's licensed users touched the deepest one weekly. Two numbers from existing product telemetry beat a perfect model nobody ships.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like adoption depth vs adoption breadth into prescriptive action for your team.
Schedule a Demo