Fortress / 2020–2026
Keeping the customer promise in view
An account view connecting what was promised, how delivery compared and when the renewal conversation needed to happen.
One account, three connected questions
- The promiseObligations · SLAs · KPIs
- The performanceOperational actuals
- Customer successSalesforce account view
- The renewalCycles & dates
- The economicsARR · TCV
Customer Success could see contractual obligations, SLAs and KPIs.
Read the complete architecture & boundaries
Relationships between information categories, not data-feed connections. No Ironclad transfer mechanism, alert engine or retention result is asserted.
- See the promise. Customer Success could see contractual obligations, SLAs and KPIs.
- Compare performance. Operational actuals were tracked alongside the commitments.
- Prepare for renewal. Renewal cycles, dates, ARR and TCV brought timing and commercial context into the view.
THE PROBLEM
What needed to change.
Customer Success needed to see contractual obligations, delivery performance and commercial context together.
MY CONTRIBUTION
Where I came in.
As Salesforce platform owner, I designed the Customer Obligation Management module around the commitments, performance measures and renewal information Customer Success needed to see.
We built the module in Salesforce to track contractual obligations, SLAs, KPIs, operational actuals, renewal cycles and commercial values.
THE APPROACH
How it came together.
- Capture the promise: contractual obligations, SLAs and KPIs.
- Review performance: compare operational actuals with commitments.
- Understand the account: renewal dates, annual recurring revenue (ARR) and total contract value (TCV).
THE OUTCOME
What the work made possible.
Customer Success could see commitments, delivery comparison, renewal timing and account economics in one module. No automated alerts or measured retention impact are claimed.
Technical & implementation detail
Technologies described in this account: Salesforce.
The module tracked obligations, SLAs, KPIs, operational actuals, renewal cycles/dates, ARR and TCV. These are known information categories, not a verified schema. Contract ingestion, actuals feeds and calculation mechanics require a separate technical walkthrough.
The accompanying visual is a simplified explanation. It is not a production screenshot or a complete implementation specification.