Zurück zur Bibliothek

Renewal expansion opportunity scan

Reviews an upcoming renewal account for evidence-backed expansion opportunities alongside retention constraints, product gaps, stakeholder coverage, and timing. Use for renewal expansion, account growth review, cross-sell research, whitespace discovery, or renewal planning.

von adlass TemplatesVersion 1Nutzt adlass-ToolsUniversell

Veröffentlicht 21. Aug. 2026 · Aktualisiert 26. Aug. 2026

Hilfreich · 0Rohes SKILL.md ansehen

Voraussetzungen

Map account and renewal fields and add the approved portfolio. Define expansion criteria, guardrails, evidence threshold and confidence rules.

Skill-Dokument

Das vollständige SKILL.md, das dein Agent liest und befolgt.

Renewal expansion opportunity scan

Purpose

Find credible expansion opportunities within a renewing account while protecting the renewal decision. Connect product, usage, business-unit, stakeholder, and contract evidence to a small set of reviewable hypotheses.

Scope

Renewal facts, current products, usage and adoption, eligible units, customer outcomes, support and sentiment, stakeholders, contract limits, open opportunities, and approved portfolio items.

Excluded: upsell outreach, automatic quote creation, changing the renewal forecast, and treating a product gap as customer demand.

Data basis

  • Account, contract, renewal, usage, support, feedback, opportunity, and stakeholder records.
  • Approved product portfolio and expansion criteria.
  • Prior account or success plans.

Result

An expansion-opportunity sheet, renewal guardrail memo, and validation-question set.

Quality criteria

  • Every opportunity has evidence, fit, timing, value hypothesis, and confidence.
  • Renewal risks are shown beside expansion suggestions.
  • Product coverage reconciles to account records.
  • Unknown eligibility is not treated as whitespace.
  • Questions test demand before recommendation.

Instructions

Protect the renewal baseline first. Compare current coverage with documented eligible units and outcomes. Use approved product definitions and commercial constraints. Distinguish evidence of need from a seller's cross-sell idea. Rank only opportunities with enough evidence to justify a conversation.

Adapt before use

Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

  • Map account, renewal, product, usage, support, and stakeholder fields.
  • Define expansion criteria, eligible units, confidence, and guardrails.
  • Add the approved portfolio and current success plan.

Verwandte Skills

  • Account growth plan

    Builds a practical growth plan for an existing account from revenue, product usage, stakeholder, service, contract, and opportunity evidence. Use for key-account planning, expansion planning, whitespace analysis, relationship mapping, or strategic account reviews.

  • Account news scan

    Scans recent public developments about a target account and turns them into dated, sales-relevant talking points with citations. Use before a customer or prospect call for account news, business triggers, company updates, market signals, or timely meeting preparation.

  • Account research brief

    Builds an evidence-backed account research brief from CRM history, firmographic records, public company materials, and prior interactions, with buying signals, stakeholders, risks, and a ranked account plan. Use for strategic prospect research, account planning, territory reviews, named-account preparation, and enterprise sales research.

  • Account technology landscape

    Builds a cautious, source-backed view of the technologies and vendors an account publicly appears to use, with confidence, relevance, and research gaps. Use for account research, technology landscape review, prospect preparation, vendor context, or solution positioning.