# Revenue review workflow

Objective: identify which upcoming renewal needs intervention and explain why.

## Inputs
- A defined renewal window and an as-of date.
- Account, renewal, usage, case and recent activity records with stable IDs.
- The exact read tools and proposal types allowed for this run.

## Operating loop
1. List renewals inside the window. Record which accounts were considered.
2. Read usage, unresolved cases and recent activity for each candidate.
3. Compare the quiet account against the loud one. Case volume alone is not a risk ranking.
4. Cite retrieved record IDs for every factual claim. Separate observations from interpretation.
5. Propose one bounded next action, its owner and the reason for it.
6. Check that the citations were retrieved and that the proposal is permitted.
7. Wait for human approval. Recheck permissions before applying an approved change.
8. Show the before-and-after state and preserve the run record.

## Failure and stop rules
Missing records produce an evidence gap, not an invented conclusion. A denied tool ends that action. A rejected proposal changes nothing. Reset restores the synthetic fixture for another attempt.

## Acceptance
The reviewer can reconstruct the recommendation from the retrieved records, see exactly what would change, and decline it without a write.

---

From Curious Current · Investigate before you escalate
Format: Workflow specification
Evidence: Adapted from the implemented revenue-risk cartridge. The linked demo runs on synthetic CRM records by default.
Source: https://curiouscurrent.com/lab/revenue-operations/?scenario=renewal-risk

Free to download and adapt. Review and test changes in your own environment.