Knowing where you stand
A renewal reminder is not a renewal process.
It arrives, it is read, and nothing about the week changes — because the thing that actually gets worked is the pipeline, and the renewal is not in it.
So at sixty days it becomes a deal.
The runway
Two sources, five marks, and two of them do something.
Seeded from subscription periods and contract terms, four months out, with the value normalised to a twelve-month figure so a monthly plan and an annual one are comparable on one list.
At ninety days your default playbook applies. At sixty, a deal opens — marked as a renewal, in the renewals pipeline, and created through the same path a person would use, specifically so the automated one still produces stage history and an audit row. An earlier version wrote the row directly and skipped both.
- Each mark fires exactly once —
Tracked per renewal, so re-running the overnight pass sends nothing twice.
- One bad record cannot abort the night —
Every renewal gets its own savepoint — and so does every reminder, every deal-open and every playbook run inside it.
- A churned outcome does not mark the deal won —
Three of the four outcomes mirror onto the linked deal. The fourth deliberately does not.
Discounting
Above your threshold, it stops being a field and becomes an approval.
Crossing the figure you set opens a real approval with a clock — to the owner, escalating to their manager by adding them rather than reassigning, then a sign-off. The submission carries the computed value impact rather than a bare percentage.
It fires only on a genuine crossing, not on every subsequent edit. And an approval that is cancelled or times out deliberately leaves the request pending, so a person decides what happens next rather than the silence deciding for them.
- Rin Takahashiowns the renewal48 hourswaiting
- + their manageradded when the clock runs outon breach
- Customer success leadsign-off48 hoursafter step one
- Playbooks do six real things —
Create a task, log a planned activity, send an email to the account's primary contact, notify the owner, open a success plan, or schedule a review — each reusing what already exists rather than creating a second one.
- A run snapshots the playbook —
So editing it next quarter does not rewrite what happened.
- An email step with nobody to send to fails visibly —
Naming the reason rather than silently doing nothing.
›Does marking a renewal renewed extend the term?
No. It records the outcome. The period itself advances on the billing cycle, separately — treat them as two acts rather than assuming one follows the other.
›Can a playbook run on something other than a renewal?
Not today. Other kinds can be authored and stored, and only the renewal path executes. Nothing auto-applies one when an account turns red.
›Does the forecast convert currencies?
No — it groups by currency and shows a line each rather than adding unlike units.