Customer Lifecycle

When software was sold once and installed forever, the signature was the end of the job. You handed over a license key and an install disk, and whether the company actually used the product or left it in a drawer was something you found out two or three years later, when you showed up to sell the next version. There was no word for the period after the contract because there was no work in it.

Subscriptions turned that around. Payment arrives every month or every year, so the contract is a starting line rather than a finish line, and the customer decides all over again at the end of each term whether to keep going. The money still to come is far larger than the money already collected, which means the months after the signature determine most of the revenue. The seller suddenly had work to do after closing, and the team that owns that work is customer success.

Even after that team existed, one problem stuck around: everyone past the signature sat in a single bucket. Pagedeck's monthly review looked like this for a long time. Sofia would read down the account list, saying that one company was doing well and another one worried her, and Grace would ask how many accounts were still in setup and how many were coming up for renewal. Nobody ever had the answer in the room. An account two weeks old and an account eleven months old lived in the same list, and both of them were just customers.

Put those two in the same bucket and the work lands in the wrong place. The two-week-old account needs seats configured and old documents imported, and instead gets a deck about next quarter's usage plan. The eleven-month-old account needs a renewal conversation started, and instead gets a training email about basic features. Both were contacted, so it looks like work happened, and neither one was helped. With ten accounts the owner keeps the difference in her head and nothing breaks. At three hundred accounts the difference disappears.

The customer lifecycle draws a time axis across that list and cuts it into sections. The stretch after signing is divided into onboarding, adoption, expansion and renewal, and each section has its own set of things to do. That's where the reason comes from for a rep to say different things to a three-month-old account and an eleven-month-old one. There's a second reason to cut it up: you need a line to judge whether an account has crossed. Define the end of onboarding as ten active users and fifty documents within thirty days of signing, and an account that misses it gets caught right there instead of drifting quietly into the next section.

Dividing the time also makes the handoffs visible. If sales owns everything up to the signature and a customer success owner takes over at onboarding, each section has a named owner and the dead weeks right after signing stop happening. Without section names, the handoff happens at a different moment for every rep, so one customer meets their new owner the day after signing and another gets no contact at all for three weeks.

Six terms sit under this one, and they split into two kinds. Five are names for the sections themselves, and one is a line drawn between two sections. The five run in a fixed order, so an account can't skip ahead.

The stages follow the clock.

1. Customer onboarding — the stretch from signing until the customer is in a state where they can actually use the product. Accounts get created, permissions get sorted, existing material gets imported, and the first training session happens. Teams usually cap this at a few weeks, because the enthusiasm that existed at signing cools the longer it runs. A customer who never gets settled here spends the remaining ten months struggling.
2. Adoption — the stretch where the product becomes part of the company's daily work. Being able to use something and actually using it are different states. If fifty accounts exist and six people log in each week, onboarding finished but adoption never started. The work here splits two ways: raising the number of people and raising the depth at which they use the product.
3. Expansion — the stretch where the scope or the headcount grows. What the marketing team used moves to engineering, a twenty-seat contract becomes sixty seats, or the account moves up a plan. For the seller this is where revenue grows without acquiring anyone new, which makes it the cheapest revenue available. Sell more seats to a customer who hasn't adopted yet, though, and that account cuts the contract at the next renewal, citing seats nobody used.
4. Renewal — the stretch where the term ends and the next one gets signed. The decision lands here, but the material for the decision piled up over the preceding ten months. Almost nothing can be reversed by calling two weeks out, so in practice the work starts two or three months ahead, assembling what this customer actually got out of the year and putting it in front of whoever signs.
5. Advocacy — the stretch where the customer recommends the product to people who didn't ask. They sit for a case study interview, mention the name at an industry meetup, or bring the same product into the company they move to. Unlike the first four, this one can't be produced on request. It only comes from customers where adoption and expansion actually paid off. These accounts also cut the seller's costs: when a prospect hears that a company in their own industry already runs on it, the evaluation gets shorter.

There is one threshold term. First value milestone marks the moment the customer sees the benefit of the purchase with their own eyes for the first time. At Pagedeck it's pinned to the first time a team finishes a jointly edited document during a meeting. This moment gets its own name because you need grounds for saying onboarding is over. Finishing account setup is the seller's definition of done; the customer feels the rollout is over at the moment they first see something for the money they spent. Accounts that cross this line within thirty days and accounts that don't diverge sharply in renewal rate a year later, so some teams measure the onboarding owner on that date alone. That makes this term different in kind from the other five. It isn't a stretch anyone sits in — it's a single line drawn between two of them.

Put all six together and the daily work changes shape. Owners stop reading the account list alphabetically and read it by section instead: eight accounts in onboarding this week, forty in adoption, twelve with a renewal inside two months. Laid out that way, it becomes obvious where the staffing is short. If twenty accounts are piled into onboarding and one person owns onboarding, all twenty cross the first value milestone late, and that delay comes back as a renewal number ten months later. This is why cutting the list into sections is a staffing input rather than a reporting category.

"That account is still in onboarding. Let's hold the expansion conversation until they clear the first value milestone."

Going in to sell more seats now means talking money with someone who can't use what they already bought.

"Four months in and weekly logins are at six people. The record says adoption, but they're really still in onboarding."

The section was assigned by elapsed time, so the label no longer matches the actual state.

"We start renewal prep two months out. Ask for the meeting at the deadline and they've already finished evaluating something else."

The work has to start well ahead of the moment the decision lands.

At Pagedeck the account list gets reviewed together every Wednesday. Sofia puts it up split by section and flags two groups separately: accounts that crossed into a new section that week, and accounts that should have crossed and didn't. The second group takes up most of the meeting. Last month nine accounts had been sitting in onboarding for more than sixty days, and going through them one at a time showed that six were stuck at the same place. Importing existing documents was a manual job, so the contact on the customer side kept putting it off. No amount of chasing the contact would have cleared it.

Mia sits in on that meeting too, because when accounts keep getting stuck at the same point in a section, it's a product problem rather than a staffing problem. What she took away from the nine accounts was an import feature, and after it shipped the following quarter the average stay in onboarding dropped from forty-one days to twenty-four. The number Grace watches in that meeting isn't the count per section but the rate of crossing between them: what share of accounts entering onboarding reach adoption within thirty days, and what share of accounts approaching renewal actually renew, quarter over quarter. Counts tell her how much sales brought in; crossing rates tell her whether the company is holding on to what sales brought in. Onboarding crossing rate going from 58 percent to 74 percent last quarter is what justified hiring two more customer success people.

The most common mistake is assuming an account moves to the next section as time passes. The word lifecycle suggests the growth of something alive, so the assumption comes naturally, and plenty of companies do record a three-month-old account as adoption and a ten-month-old account as renewal prep. But sections are separated by whether a threshold was cleared, not by the calendar. An account four months in with six weekly users is still in onboarding, and adoption-stage work aimed at them lands nowhere. Leave the mistake alone and the record shows forty adopted customers until renewal season arrives and half of them turn out to barely use the product. By then there is no time left to do anything about it.

The second mistake is assuming the sections only run one direction. The order is fixed from front to back, which makes it easy to read a crossing as permanent. Accounts move backward often. When the person who championed the rollout leaves, the people left behind no longer know why the company uses this product, and an account marked adopted effectively returns to the state before onboarding. A reorganization that splits the team or a change in who controls the budget does the same thing. If a section is assigned once and never revisited, that backward move never shows up in the record, and the account stays green until a month before renewal. So in practice sections get reassigned every quarter. An account promoted to adoption last quarter is judged again on this quarter's usage, and one that falls back picks up the onboarding tasks from the beginning. In organizations that never move a label back down, the counts pile up toward the later sections over time, and the list stops telling anyone where to put people.