Advocacy

For a long time, looking after a customer after the contract was signed meant two things: answer them when something breaks, and ask for a renewal when the term runs out. Nothing in that split had a place to record what a happy customer was doing outside the company.

So the same scene kept repeating. A demo request arrives at Pagedeck with nothing in the "how did you hear about us" field except "a friend told me." Sofia asks on the first call and hears, "the team lead who used this at my last company moved over and said we should use it here too." That last company has been paying for two years. The person who owns that account never finds out the request came from her customer, because the only things the account record tracks are logins and support tickets.

Advocacy is the name given to that blank field. It treats what a customer says on our behalf as a stage of its own, separate from what they pay. It sits at the end of the lifecycle for a reason: it only comes out of accounts where the earlier stages actually produced results, so the number of accounts in it is a late report card on how well those stages were run.

Customers in this stage bring up the product before anyone asks them to. What separates it from earlier stages is that the action points outward, and it shows up in a few recognizable forms.

1. They offer to have their results written up. A case study documents what problem a customer solved and what it was worth in numbers, and normally the vendor has to beg for one.
2. They take a call from a stranger who is evaluating the product. A reference call is a half-hour conversation where a prospect asks an existing customer what using it is actually like.
3. They name the product in industry meetups and community threads where nobody from the company is present.
4. They bring it with them when they change jobs.

Accounts that get this far have something in common. Usage genuinely spread during adoption, a second team picked it up during expansion, and at renewal the first question was about adding seats rather than cutting the price. You cannot skip the order and manufacture advocacy on its own.

The other feature of this stage is how few accounts are in it. Of Pagedeck's 180 paying customers, 12 look like advocates. That is under 7 percent, and yet 4 of last quarter's 18 new demo requests came from those 12. Requests that arrive this way also close faster. A company that comes in from an ad spends about six weeks getting to a contract; a company that comes in on a recommendation takes three. It doesn't have to re-verify a story someone it trusts has already verified.

The stage after advocacy doesn't belong to this customer — it belongs to a different one. This is the last box in the lifecycle, so there is nowhere further to go, and what happens here instead opens the first box for somebody new. That makes the condition a matter of plumbing rather than feeling: does anything connect the goodwill to actual demand? Three pieces are needed.

1. Something that tells you advocacy is happening. Put one line on the demo form asking how they heard about the product, and when the answer is a company name, mark that account. Without it, the 4 requests those 12 accounts generated stay four lines reading "a friend told me."
2. Something that turns goodwill into a request you can make. A customer willing to say good things still does nothing if nobody asks for anything specific. An hour-long interview, a 30-minute call, five lines of testimonial — naming the cost up front gets a yes far more often than an open-ended favor.
3. Something that gives back. Not money, but visibility. Put the customer's name and photo on the case study, put them on stage at an event, give them early access to new features. What advocates get out of this is usually professional reputation, so that currency works better than a gift card.

The volume of asks needs its own limit. With only twelve accounts in this stage, every request lands on the same people. Ask one contact for five calls a quarter and within six months they stop picking up. A cap of roughly one ask per account per quarter holds up longer.

"Four of last quarter's eighteen demo requests came in through existing customers."

Accounts in this stage are absorbing part of the sales cost.

"I think this account is at advocacy. They offered to do the write-up before we brought it up."

A proposal to move the account up one box in the lifecycle.

"Our job right now isn't to create advocacy, it's to fix adoption."

Advocacy can't be demanded, so the earlier stage is where the work is.

Pagedeck re-sorts the customer list by stage every quarter. Sofia reads out the accounts she has placed in the advocacy box, and Grace picks two or three to contact herself about speaking at the next event. The question that comes up most in that meeting is why a particular account isn't in the box yet. When an account is large and renews smoothly but says nothing outside, it usually turns out that only one person inside is pushing the product, and one person is in no position to speak for the company.

The reverse gets attention too. When an account that was in the advocacy box goes quiet, someone asks why. Talk drying up outside often means the number of people using it inside has dropped, and that signal arrives three or four months earlier than a renewal conversation would.

The most common mistake is believing advocacy can be manufactured as a campaign. Referral programs visibly work, so it looks like the same mechanism should produce advocates. But an incentive only clears the path for someone who is already satisfied; it cannot produce the satisfaction. Attach rewards to a product that isn't earning its keep yet and you get accounts that collect the reward and leave, plus customers who arrive on an oversold pitch and churn within three months. The machinery built to create advocacy ends up creating churn instead.