Deal & contract office · Module 2 of 7
Every renewal, ranked by the day the decision dies.
Obligations finds the dates. This one puts money on them. The renewal board reads like: "$348,000 of ARR up for renewal in the next 90 days — and two of them pass their notice window before you would have noticed." That is the shape of the output, not a claim about your book. Ranked by the notice deadline, never the end date, because the notice window is the last moment a decision is still possible.
What this module does
Four capabilities that show up in week one.
01
Value-weighted renewal board
Every renewal carries its contract value and its notice deadline. The board sorts by money at risk in the next 30 / 60 / 90 days, so the biggest silent rollover sits at the top instead of alphabetically buried on a spreadsheet tab nobody opened this month.
02
Sorted by notice, not by end date
A contract ending in 120 days with a 90-day notice window is more urgent than one ending in 45 days with a 30-day window. Sorting by end date gets this exactly backwards, which is how a renewal gets "handled" two weeks after the decision was already made for you.
03
The pre-renewal motion, run
Usage, open tickets, last review, the tone of the last twenty emails in the thread — assembled into a one-page brief before the conversation, with an outreach sequence timed off the notice date rather than the end date.
04
Silent-rollover alarm
Auto-renewing agreements get an escalation ladder that fires against the notice deadline and keeps firing until a human makes a call. A renewal that passes without a decision is logged as a decision you did not get to make, not quietly closed as renewed.
How it works
Renewals runs on top of the obligation register. Each agreement gets its value, its end date, and — the one that actually matters — its notice window. Morthn builds the forward board: what is up in 30, 60 and 90 days, what it is worth, and which ones cross their notice deadline first. Then it runs the motion: the pre-renewal brief, the outreach sequence timed off the notice date, and the escalation ladder that keeps going until someone decides. Works in both directions — the customer contracts you are trying to keep, and the vendor contracts you are trying not to auto-renew.
Integrates with
Compliance + guardrails
Contract values are read from your own billing and contract records, never estimated. Where a value cannot be sourced, the renewal shows as unvalued rather than guessed — a made-up number sorts your board wrong, which is worse than a blank. No outbound message to a customer or vendor sends without your approval for the first 30 days; auto-mode unlocks per segment once you have signed off on the tone. Every outcome (renewed, renegotiated, lapsed, silently rolled) is logged for the monthly report.
Tier availability
Available on every tier
FAQ
Common questions about Renewals & Notice Windows.
We already track renewals in a spreadsheet.
Most people do, and the spreadsheet is usually right about the end dates. What it does not do is rank by notice window, attach the dollar value, chase the counterparty, or make noise when the window is about to close. A spreadsheet is a record. This is the thing that acts on the record.
Does this cover vendor contracts, or only customer contracts?
Both, and vendors are often where the fastest money is. The same notice-window logic that stops you losing a customer renewal stops you auto-renewing a $14,500/mo agreement for something you stopped using in March.
What if the counterparty just does not respond?
You get escalated with time still on the clock, the draft notice already in your queue, and a log of every attempt — which is also the evidence you need if the rollover is later disputed.
The rest of the deal & contract office
⏳
Deadlines & Obligations
⚖
Commission Reconciliation
✎
Proposals & RFPs
🛡
Security Questionnaires
⊘
Bid / No-Bid Qualification
◎
Marketplace Account Health
Module 10 of 15 in the Morthn operating layer · See all 15