Renewal

When software was bought once and kept, there was very little to do after the sale. The money arrived on day one, and whether the customer used the thing well after that had no bearing on revenue. Selling by subscription inverted the arrangement. Day one now brings in a fraction of the total, and the rest has to be earned again every year.

For a long time nobody owned that moment. Sales comp was written against new contracts, so there was no reason to look at a customer already signed. Support answered what came in. The expiry date lived in a spreadsheet on the finance team's drive. Which produced a familiar scene: an automated payment-failure notice goes out three days before the term ends, and the customer calls to ask when their contract actually expires. They didn't know, and neither side had prepared anything.

Renewal exists because that moment needed to be treated as a stage with a name. Not a single date but a window two or three months wide. Seen that way, there is work inside it: assemble what the customer got out of the past year, put it in front of whoever holds the budget, and settle the terms of the next period. A window can be staffed and scheduled, which a single date cannot.

The window opens 90 days before expiry. Pagedeck meets the budget owner at 60 days, sends next-term terms at 30, and aims to have a signature at 14. If the contract carries an auto-renewal clause — a provision that continues the agreement unless one side gives notice — the notice deadline in that clause sets the start instead. A 60-day notice requirement means the window opens at 120 days, not 90.

The defining feature of the stage is that almost nothing new can be built inside it. The material for the decision accumulated over the preceding ten months. A call two weeks out can realistically change nothing; the only available move is to present accurately what is already there. You cannot cram for an exam the night before and change what you learned.

The subject matter shifts too. During adoption — the stage where a product settles into daily work — conversations were about features and how to use them. Here they are about outcomes and budget. The people in the room change as well: instead of the day-to-day contact you've been talking to all year, the person who controls spend shows up, and often that person has never opened the product.

There are three endings. The contract continues on the same terms, continues with fewer seats or a lower tier, or ends. At Pagedeck the middle outcome is the most common one — an 80-seat contract carrying forward as 50 seats. This is where a company ends up with a cancellation count that looks clean while revenue quietly drains. Recording renewals as simply won or lost hides that middle case, so the seat and tier changes get tracked on their own.

The stage after renewal is advocacy — where a customer recommends the product to people who never asked. A signature by itself doesn't get you there. Three conditions do.

1. The outcome is confirmed in numbers. Something like document review dropping from 3.5 days to 2. A contract that leaves behind only an impression that things went well is the first line cut in next year's budget review. Pagedeck writes that figure down at signing so there is something to compare against a year later.
2. The budget owner knows about that outcome. An outcome only the daily user can describe disappears the day that person changes jobs. Pagedeck insists on one meeting with the budget owner inside the window, and shows them the numbers directly.
3. There is room left to grow. If someone mentioned that a neighboring team wants in, or that they'd like to make this workflow a company standard, the next cycle runs into expansion — the stage where usage spreads to more people or more scope.

Miss any one of the three and the contract continues while the stage stays put. An agreement signed without those conditions met means having the same conversation from scratch at the next renewal.

"This account hit 90 days out. Let's get the budget owner meeting on the calendar first."

Teams move off the day the window opened, not off the expiry date.

"Finding out two weeks before renewal is too late. Let's play this one to protect the terms."

Giving up on reversing the outcome and aiming instead to prevent a reduction.

"We got the signature, but seats went from 80 to 50. That isn't a save."

A renewal by count, a loss by revenue.

At Pagedeck, Sofia pulls the list of next quarter's expirations in the first week of the quarter. When the list runs past twenty accounts, equal effort everywhere isn't possible, so the first job is ordering it. That ordering work is renewal forecasting, and the actual work of the renewal stage starts after it.

The artifact she spends the most time on is a single page of outcomes: the goal the customer stated at signing on the left, what actually happened over the year on the right. When the numbers are poor, they go on the page anyway with an explanation. Hiding them means a larger version of the same conversation twelve months later. For accounts Grace joins, that page gets read before the meeting.

The most common misreading treats renewal as a sales activity. A signature is involved, so it looks like selling. But what happens in the room is confirmation, not persuasion. The customer already owns a year of experience, and if that experience was bad, no deck changes the decision. Organizations that treat renewal as sales respond by assigning someone a month before expiry, and the only lever that person has left is a discount — which amounts to cutting next year's revenue in advance. It also resets what the customer believes the product is worth, and the following negotiation starts from the lower number.

Assuming an auto-renewal setting means the stage needs no management is the other frequent mistake. The contract continues unless someone objects, so doing nothing looks like the safer play. But a contract that continued automatically is not a contract the customer decided on. Inside that group are customers who forgot, noticed the charge on a statement, and started looking into how to cancel — and they tend to demand a refund or leave mid-term. Pagedeck sends its one-page outcome summary to auto-renewing accounts too, 60 days out.