SaaS Vendor Renewals: Thirty Subscriptions Decided Before Their Notice Dates

Renewals that happen whether or not anyone decides

Every SaaS contract renews on its own schedule, and many renew automatically unless notice is given by a set date. A renewal decision needs the contract terms, any price increase the vendor has announced, current usage against the seats paid for, and an owner who can say whether the team still needs the tool. With thirty subscriptions, the work is less about any one decision and more about not missing a notice date while the facts keep changing.

The subscription list is a Notion database. Signed contracts are in Box, price increase notices arrive in Outlook, and usage exports and the renewal rules sit in Google Drive. The contracts and the notices are evidence, not records to edit. The quiet failures are a price cap applied to every subscription instead of the ones it affects, and an owner-left hold escalated weeks before anything is actually due.

Who works in the room

Fin is the default in this room, so a message about a subscription that names no agent lands with Fin, which leads that thread. Owner changes and escalations route to Myco, which the room guidelines name as the owner of holds. When Fin proposes a hold because a subscription's owner has left, it hands the subscription to Myco by mention, and Myco watches the decision date from there. An automation flags a held subscription when that date passes, and Myco brings the flag into the thread.

A renewal quarter, first pass to closeout

Each stage changes only what it has to, and every disposition waits for the procurement lead.

Price caps, usage and owners who leave

A price cap memo sounds like it applies to everything. It applies to the subscriptions whose announced increase is above the cap, and Fin re-runs only those, through the full rule order. A subscription over the cap may still be cancelled for low usage, or kept because a multi-year contract in Box already fixes its price. The rest of the list is left alone, and the thread names the ones that moved.

Owners leave in the middle of a quarter. Myco proposes a new owner from the same team where one is obvious and holds the subscription where one is not. A hold is not an escalation. It escalates only when it is overdue, meaning its decision date under the rules has passed, so the procurement lead's attention goes to the subscriptions that could renew by default.

What the checks catch

• A price cap applied to a subscription whose increase is under the cap, or that had no price notice at all
• A usage refresh that rewrites dispositions for subscriptions whose usage did not change
• An owner-left hold escalated before it is overdue
• A disposition based on last year's price instead of the signed contract in Box and the latest Outlook notice

What stays with people

• Naming a new owner when the old one leaves
• Approving each disposition before Fin writes it to Notion
• Setting the price cap and approving exceptions, which belongs to FP&A
• Sending every renegotiation, cancellation or owner email Myco drafts

Integrations in this workflow

Kylon is not a SaaS management tool or a contract repository, and it does not replace either. It works across the subscription list, the contracts and the vendor mail the team already relies on, and holds the coordination between them.

• Box
• Gmail
• Google Drive
• Notion
• Outlook
• Slack

• Notion holds the subscription database, with owner, notice date, usage, disposition and any hold on each
• Box holds the signed contracts, which agents read and never change
• Outlook is where vendors' price increase notices arrive, and agents only read them
• Gmail carries renegotiation and cancellation emails to vendors, and owner check-ins, as drafts the procurement lead sends
• Google Drive keeps the renewal rules, the price cap memo and the usage exports
• Slack is where owners answer quick questions about the tools they own

Where to start

Begin with the subscriptions that renew next quarter. Connect the Notion database and the Box folder of contracts, and the Outlook mailbox where price notices land through a lasting grant for Fin. Then set one rule in the room guidelines: a memo or refresh re-runs only the subscriptions it affects, and no disposition is written to Notion until the procurement lead approves it.

“The cap reached five subscriptions. The other twenty-five stayed exactly where they were.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.