SaaS Customer Renewal Desk: Renewals Closed or Held for a Reason That Is Still True

Renewals that look settled in HubSpot and are not

A quarter's renewals look simple from the pipeline view. Each deal either renews or holds, and the close policy says why. Four hold rules are checked in a fixed order: an unpaid prior invoice, an open billing dispute, a purchase order the customer requires but has not sent, and a discount above the cap. The first rule that applies becomes the hold reason. A deal with none renews.

The evidence is scattered. Deals and company records sit in HubSpot, invoices and payment status in Stripe, POs and objections in the shared renewals mailbox on Outlook and in the controller's Gmail, and every finance notice in a run folder on Google Drive. When a PO finally arrives, the tempting move is to flip that deal to renew. Often a rule further down the list still holds it.

Who works in the room

The desk runs one Kylon room per quarter. Ryan is the room's default agent, so a question about any deal's status goes to it without a mention. Questions about the order file go to Ada, which owns that review, and anything that needs a customer reply goes to Fin. When Ryan re-checks a deal and the result changes what a customer should hear, it opens a thread for Fin whose first message carries the deal, the rule and the amount.

How the quarter closes

The close policy lives in the run folder, and its rule order is copied into the room guidelines so every agent applies the same precedence. Each stage ends with a person.

When a reason clears, start again from the top

Most changes arrive as mail. A billing contact sends a PO number, a customer accepts a credit, finance posts the close FX rate, the deal desk approves one discount above the cap. Each of these clears a reason on some deals. Ryan records the new fact, then re-checks those deals against all four rules in order, because clearing the recorded reason only means the next rule gets its turn.

That is how a PO can land and a deal still hold. Brighton's PO clears the missing-PO rule on both of its deals, but one carries a discount above the cap, so it stays on hold under the discount rule with a note that says so. When finance revises the cap or converts a euro deal at the close rate, the same re-check runs on every held deal, not only those named in the notice.

What the checks catch

• A deal whose recorded hold reason has cleared but which still fails a rule lower on the list, most often the discount cap
• An order file line for a held deal, which is removed rather than corrected
• An in-scope renewal that never made it into the order file, listed as missing
• A PO reply that quotes one deal's amount when the PO covers two, so the reply states the combined net amount
• A carried deal whose close date was never moved into the next quarter

What stays with people

• Approving every dealstage and hold reason before Ryan writes it to HubSpot
• Approving the dunning action on each invoice before anything reaches a customer
• Sending every customer reply, which Fin prepares as a draft in Gmail or Outlook
• Deciding discounts above the cap, and signing the quarter closeout

Integrations in this workflow

Kylon is not a CRM or a billing system, and it does not replace either one. It sits across HubSpot, Stripe and the two mailboxes the desk already works in, and holds the coordination between them.

• Gmail
• Google Drive
• HubSpot
• Outlook
• Slack
• Stripe

• HubSpot holds the renewal deals, company records, dunning actions and the closeout notes
• Stripe holds the invoices and customers each deal links to, read for payment status and disputes
• Outlook carries the shared renewals mailbox where POs and customer objections arrive
• Gmail carries the controller's own customer threads, with replies drafted for the controller to send
• Google Drive keeps the run folder: the close policy, finance notices and the draft order file
• Slack is where renewal managers flag customer news that has not reached a mailbox yet

Where to start

Start with one quarter and one connection. Connect HubSpot through a lasting grant the controller approves for this room, point Ryan at the run folder, and put one rule in the room guidelines: when any hold reason clears, the deal is re-checked from the first rule, and nothing is written until the controller approves.

“A cleared reason is a reason to check again, not a reason to renew.”

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.