Expansion

For a long time the selling job ended on the day the contract was signed. Performance was counted in new logos closed this quarter, and everything after signature was handled only when a ticket came in. For a business that sells a product once, that arithmetic works.

For a subscription business it doesn't. What a customer is worth isn't the first contract; it's the total that accumulates over the years they stay. Sofia can close five new accounts in a quarter while three existing accounts cut seats, and quarterly revenue lands exactly where it started. Looking only at what came in, the quarter was a success. Looking at the whole book, nothing happened.

A cost difference sits on top of that. Reaching a company that has never heard of the product, getting through evaluation, and arriving at a signature costs advertising budget plus months of a salesperson's time. Opening twenty more seats for a customer who already uses the product costs one email and a billing update. When the same amount of revenue costs several times more to add one way than the other, the thing that happens after signature gets its own name and its own owner.

Expansion is that name. It comes after customer onboarding has gotten the customer up and running and after adoption has made the product part of daily work. What follows it is renewal, where the contract gets signed again.

Customers in this stage already use the product, and growth arrives in three directions.

1. Headcount — more accounts under the same contract. This is seat expansion: a twenty-seat contract becomes a sixty-seat one.
2. Reach — the product crosses from one team to another. Thirty engineers joining an account that twelve marketers were using adds headcount, but it also changes the kinds of work the product is doing.
3. Depth — a higher plan or additional features. Usually this shows up when the customer needs finer permission controls or connections to outside tools. Nudging a customer onto a higher plan is called an upsell.

All three start with a signal from the customer's side. Eighteen of twenty seats are filled with five people waiting on invitations. Documents shared outside the account jump. The usage ceiling gets touched every month. So the work in this stage is less about building a proposal and more about noticing the signal first. The account owner reads the customer list grouped by stage rather than alphabetically, and counts how many accounts lit up this week.

Skipping the order is expensive. Sell more seats to a customer who hasn't settled in yet and that account arrives at its next renewal holding a list of seats nobody used. If sixty seats were opened and twenty-two people log in weekly, the number the customer's decision-maker brings to the renewal conversation is twenty-two.

Getting to renewal means the added capacity is actually being used. Three conditions decide it.

1. The new seats filled up. Check whether the people who just joined crossed the first value milestone, the moment a customer sees the payoff of the purchase for the first time. Thirty engineers added and eight logging in weekly means the expansion happened on paper only.
2. The results are written in the decision-maker's language. The person who signs the contract usually isn't using the product every day. Without a quarterly summary of how much meeting time went away, or what changed about hunting for documents, the only thing visible at renewal is a larger invoice.
3. It doesn't hang on one person. Some accounts stop expanding the day the person who drove it leaves. When three or more departments use the product and each has someone who knows it well, the account survives that departure.

Checking these two weeks before renewal is too late. Almost nothing can be turned around at that point, so in practice teams start the check two or three months out and spend that time filling whichever condition is short.

"This account is in expansion. Eighteen of twenty seats are full and five people are waiting on invites."

The signal fired, so open the seat conversation now rather than later.

"They haven't even adopted it yet. Don't lead with expansion — it comes straight back off at renewal."

Seats added now won't get used, and unused seats become an argument for a smaller contract.

"New business missed the number this quarter, but expansion covered it."

Fewer new customers came in, and existing customers using more held total revenue flat.

At Pagedeck the stage got its own name because of one account. The contract started with twelve marketers, and over six months in which Sofia did nothing at all, the engineering team wandered in and the account grew to thirty-five seats. Nobody on the selling side had done anything. When Sofia went looking for the same pattern elsewhere she found fourteen accounts shaped like it, and what they had in common was that the first team settled in and then a neighboring team arrived through shared documents. Since then the count of documents shared outside the account sits on her weekly list.

The most common mistake is reading expansion as something the selling side produces. Revenue goes up, so it looks like a sales result. But the decision to put a neighboring team on the product is made inside the customer's company, not by the vendor. The work here is closer to recognizing a movement already under way and turning it into a contract. Get the order backward and proposals go out to accounts with no signal at all, where the contact has nothing to take upstairs and lets the email sit.

Reading a customer with no expansion as a quiet customer is nearly as common. No complaints, so no problem. But an account whose user count hasn't moved in six months is usually one where the product is attached to a single task on a single team, and that attachment disappears the moment the task changes or the person handling it leaves. That's why a stalled account gets flagged as an early churn signal rather than a calm one.