First Value Milestone

For a long time the vendor decided when a rollout was done, using a checklist the vendor wrote. Create the accounts, sort out the permissions, migrate the old files, run one training session, and the owner ticked the completed box. Every item on that list describes work the vendor did. On the customer's side, nothing about that day was different from the day before.

Pagedeck ran into this directly. Sofia reported that all eight accounts from the previous month were fully set up, and Grace asked what those eight accounts were getting out of the product right now. Nobody could answer. That renewal season the numbers made the gap explicit: the accounts marked as fully set up and the accounts still around a year later were largely not the same accounts.

The first value milestone moves the test from the seller's side to the buyer's side. Done is no longer the day preparation ended but the day the customer first saw what the money bought. Completion gets defined by what the other party received rather than by how much work went in. Moving into a new apartment, it's not the day the boxes arrive — it's the first night you cook a meal there.

You define one specific moment in advance, then record the date each account crosses it. There are three steps.

1. Decide what counts as first value. Pick the single effect the product promises that a customer can confirm soonest. Pagedeck chose the moment a team edits one document together during a meeting and finishes it right there, because a shared document is what the product actually sells.
2. Turn that moment into something the product can observe. "Finished it during the meeting" leaves no trace, so it becomes: three or more different members of one account edited the same document in the same week.
3. Stamp the date each account first meets that condition, and count the days from the contract date. Pagedeck flags any account that passes 30 days without crossing it.

Three conditions constrain the choice. The customer has to be able to recognize it, the product has to be able to observe it, and it has to be reachable early in the contract. "All 50 seats have accounts created" satisfies only the second. For the people doing the work at the customer, that day is nothing, which is why that date predicts nothing about renewal.

A useful test when choosing: could a customer describe the moment to a colleague without mentioning your company? "We ran a whole meeting off one shared doc" passes. "Our tenant was provisioned" does not.

Once set, the milestone stays put for a while. Adjust the definition every quarter and a pass rate of 62 percent against last quarter's 71 percent becomes unreadable — you can't tell whether onboarding got worse or the bar got higher.

The first use is deciding when customer onboarding ends. Customer onboarding is the stretch from signature to the point where the customer can actually use the product, and until this milestone existed there was no evidence for calling that stretch over. The crossing date supplies it, and it also settles handoffs — the account moves off the onboarding owner's list on that date rather than on a date somebody negotiated.

It also measures the work of the onboarding specialist, the person who handles early setup and training. Score that role on sessions delivered or response time and you get numbers unrelated to anything the customer gained. Score it on how many assigned accounts crossed the milestone within 30 days and the incentive points the right way.

It surfaces accounts at risk. An account 45 days into its contract that still hasn't crossed is already in trouble, well before its health score — the blended usage-and-responsiveness rating — starts to slide. Pagedeck puts a person back on those accounts to hear directly what got stuck.

The last place is sales. When a prospect asks how soon they'll see results, "22 days on average over the last six months" carries weight a promise doesn't, because it's a record. What a hesitant buyer actually fears isn't the price — it's ending up six months later with a tool nobody opens — and this number answers that fear directly.

"This account is 38 days in and still hasn't hit first value."

Past the normal 30-day range, so someone needs to step in personally.

"Let's not define first value as seat activation. That's our work, not theirs."

Pushing back as the definition drifts back toward the vendor's task list.

"Our 30-day pass rate this quarter is 62 percent."

Reporting in one number whether onboarding improved over last quarter.

Pagedeck opens its Monday customer success meeting with this list. Sofia pulls up the accounts that haven't crossed yet, ordered by contract date, and the team works through anything past day 20 one at a time. The causes sort into a few piles: file migration never finished, only the approver logged in while the actual team never did, or the person who championed the purchase left the company. Each cause calls for a different move, so that sorting sets the following week's work. Accounts stuck on migration get a person assigned; accounts where the team never showed up get another conversation with the approver.

The most common mistake is setting the milestone at the end of product training. Once the customer knows the product, the thinking goes, value is the next thing to arrive. But knowing and getting are different. Accounts that sat through all twelve features and never applied one to their own work are ordinary. Define it this way and the pass rate climbs past 90 percent while renewal stays flat — and that reassuring number is exactly what keeps anyone from intervening in time.

The second mistake is treating the crossing as the finish line. This is a line, not a stretch, so crossing it doesn't keep anyone there. A team that finished one document together often reverts to the old way the following month. What comes after belongs to adoption, the stretch where the product settles into daily work. Let go there and the same account arrives at renewal a year later, pointing at unused seats as grounds for cutting the contract.