Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hc.pillargtm.com/llms.txt

Use this file to discover all available pages before exploring further.

Renewals

Renewals track upcoming and historical contract renewals. Each renewal carries a multi-variable risk score and follows a structured disposition lifecycle.

Core Information

FieldDescription
AccountParent account
ARRAnnual Recurring Revenue at stake
Renewal DateContract renewal date
DispositionCurrent renewal lifecycle state
Risk Score0-100 renewal risk (higher = riskier)
Risk LevelLow, medium, high, or critical
OwnerRenewal owner (CSM or AE)
Auto-RenewWhether the contract auto-renews
Save PlayActive save play if risk is elevated

Risk Scoring

Renewal risk is computed from 8 weighted variables covering engagement trends, stakeholder stability, support health, contracting activity, executive sponsorship, customer satisfaction, payment patterns, and market context. See Renewal Risk for details.

Disposition Lifecycle

NOT_YET_DUE → APPROACHING → URGENT → SAVE_IN_PROGRESS → RESOLVED/RENEWED/CHURNED
DispositionDescription
NOT_YET_DUERenewal is far out
APPROACHINGRenewal is approaching (30-90 days)
URGENTRenewal is imminent (under 30 days)
SAVE_IN_PROGRESSActive save play running
RESOLVEDRisk mitigated, renewal expected
RENEWEDContract renewed (terminal)
CHURNEDCustomer lost (terminal)