The Oversold Deal

The signal

The health dashboard marks an account as concerning: purchased capacity is well above current use. The first proposed response is more training. The detective pauses. Ruff has found the original rollout plan under a stack of renewal slides.

The dig

In this scenario, the customer bought for a broader rollout, but the next business unit has not joined. The active team still relies on the product. The gap is between the planned deployment and the current business scope, not simply between available features and user knowledge.

The CSM checks the original assumptions with the customer and account team. Is the broader rollout delayed, canceled, or waiting on a dependency? Those are different cases.

A practical response

The team separates the current use case from the future one. It documents what the active team needs, identifies the owner of the rollout decision, and builds an adoption plan only around a confirmed next use case. If the scope has genuinely changed, the commercial owner can discuss appropriate options.

The scenario’s resolution

The case ends with an agreed view of current value and an explicit decision on the next rollout phase. It does not need to end in expansion. A realistic plan, including a potentially smaller commitment, is more useful than pretending every unused entitlement can be trained into use.