Mostly efficient but padded with explanation Claude already knows (the basic NRR formula, generic churn definitions, and large benchmark tables) that could be tightened. It does not score 3 because much of the exposition does not earn its tokens, and not 1 because the bulk is structured reference material rather than rambling prose.

Provides concrete, specific guidance: NRR-keyed decision framework, expansion trigger matrix with timing/owner, save plays with success rates, and point-based scoring models. Though instruction-only, the guidance is directly executable. It would not score 2 because details are complete rather than pseudocode-level.

Multi-step processes (renewal timeline, onboarding milestones, churn playbooks) are sequenced, and the 'Before Starting' questions with an inference fallback act as a soft checkpoint, but explicit validation/verification steps are missing. It does not score 3 because checkpoints are implicit rather than enforced, and not 1 because clear sequences exist.

A single ~460-line file with all content inline and no bundle files or external references; benchmark tables, playbooks, and tech-stack could be split into reference files. It scores above 1 because sections are well-organized, but not 3 because everything remains monolithically inline rather than split one level deep.

Lists multiple concrete actions ('reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention') rather than vague language.

Explicitly answers both what (expansion and retention systems) and when ('When the user wants...' / 'Also use when the user mentions...'), with explicit trigger guidance and exclusions.

Strong coverage of natural user terms including 'churn,' 'retention,' 'upsell,' 'NRR,' 'closed-lost,' 'renewal,' and 'land and expand'.

Clear post-sale revenue niche with a 'Do NOT use for technical implementation, code review, or software architecture' clause that prevents misfiring onto adjacent skills; uses third-person voice.