| name | renewal-radar |
| description | Find renewal risk; missing usage remains unknown. |
| metadata | {"short-description":"Surface renewal risk and action windows"} |
Renewal Radar
Outcome
A time-ordered renewal view with commercial, relationship, adoption, and service evidence.
CRM-neutral operating contract
- Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
- Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
- Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
- Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
- Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.
Workflow
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Contracts or renewal opportunities, dates and notice periods, value, products, usage or success signals, activities, stakeholders, cases, sentiment, commitments, and payment context when authorized.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Calculate action windows from actual renewal, notice, procurement, and budget-cycle dates.
- Assess relationship coverage, value realization, adoption, unresolved service issues, commercial change, competitor signals, and executive alignment.
- Separate confirmed risk, leading indicator, missing data, and positive evidence.
- Highlight expansion signals only when connected to verified needs or usage, not merely contract size.
Required output
- Renewal timeline
- Risk and opportunity table
- Evidence and confidence
- Critical dates
- Recommended owner actions
Actions and boundaries
Remain read-only unless the user approves specific tasks or renewal-record updates.
