Skip to main content
Back to Skill Library
Renewals workflow library

Renewal risk brief

Summarize renewal risk signals, evidence gaps, stakeholder context, and next steps before account reviews.

This is a complete workflow library with 5 individual skills. Download the full library or pick the specific skill folder your team needs first.

Individual skills in this library

Use one skill at a time, or keep the full workflow together.

Some AI tools expect one skill folder per upload. Download the full library when you want the whole workflow, or download an individual skill when you only need one job done.

Skill 1

Renewal evidence intake

Use when renewal risk signals from usage, support, CRM, stakeholder notes, or commercial context need safe intake and confidence grading.

Skill 2

Risk level classifier

Use when renewal risk must be classified from evidence, caveats, and escalation triggers instead of gut-feel scoring or anecdotal sentiment.

Skill 3

Save plan options builder

Use when renewal save-plan options must stay evidence-based, reviewable, and free of unauthorized discounts, credits, roadmap promises, or custom work.

Skill 5

Escalation brief

Use when renewal risk needs leadership, legal, security, product, finance, or implementation review with facts separated from assumptions.

Security fit check

Is the public Renewal risk brief library enough, or does this need deeper review?

Use the public library when the workflow is low-risk, the inputs are already sanitized, and a team member can review the output before it reaches a buyer or customer.

Do deeper review when this workflow touches real tools, data sources, role ownership, approval paths, or customer-facing output.

Renewal riskCustomer SuccessAccount ManagerRevenue Leader

Good deeper-review trigger signals

  • The workflow touches customer, prospect, CRM, proposal, security, pricing, or campaign data.
  • Different teams disagree on the approved source of truth.
  • The AI output could become customer-facing, revenue-impacting, or compliance-sensitive.
  • You need reusable eval checks before asking more people to use the workflow.