Advocacy Ask

Advocacy Ask

Advocacy is the one thing in customer success where the customer does the work and your company gets the benefit. That asymmetry is the whole problem, and pretending it is not there is why the asks land badly.

The failure this exists to prevent: asking at renewal. The timing converts a favour into a trade. Even when the customer says yes, they now know that agreeing to be a reference is worth something at the negotiating table, and you have taught them that at your own expense.

What this needs

Shared context. If an account-context document exists, read it first for the segments and the value metric, which decides what a useful reference story even is here. Where it is absent, carry on and name the assumption.

Minimum: the account and what is being asked for. Enough to judge whether to ask, who to ask, and how to shape it.

Better with the account's recent history, any open escalations, and a record of what they have already been asked for. That last one prevents the most common damage.

Best with an outcome the customer has stated themselves, because an ask that starts from their own words is a different conversation from one that starts from your need.

Step 1: Decide whether to ask at all

Four disqualifiers. Any one of them and the answer is not yet.

• An open escalation or an unresolved commitment. Asking for advocacy while something of theirs is broken reads as tone-deaf and is remembered
• No realised value they would state themselves. If they cannot name what they got, the reference will be vague and it will not convert anyway
• A renewal or a negotiation inside the next quarter. Wait. The trade problem above
• Reference fatigue. They have been asked recently, or repeatedly, and nobody tracked it

The last one is the most common and the least visible. The same three cooperative accounts get asked by sales, marketing, product and support independently, none of whom can see the others, and the customer experiences one company asking eleven times. It is your job to see the whole picture, because nobody else can.

Step 2: Time it to realised value, not to your quarter

The best moment to ask is a specific one: shortly after the customer has said out loud that something worked.

Those moments are identifiable. The end of a successful rollout. A business review where they presented their own results. An escalation that was genuinely well handled, which is often the strongest of all. A milestone they hit and told you about.

Log the moment when it happens even if you do not need anything then, because the ask three months later starts with "you mentioned in March that..." and that is a far better opening than a request out of nowhere.

Step 3: Pick the person who benefited, not the person who signed

The economic buyer signs. Someone else got their evenings back, or hit their number, or stopped being the person who explains the spreadsheet.

That second person is the reference, because they have something to say and they mean it. Ask the signer and you get a paragraph of vendor-management language that convinces nobody.

Two constraints on top:

• Match the reference to the prospect. Same industry, similar size, similar problem. A generic enthusiastic reference is worth less than a specific lukewarm one from an identical company
• Check they can speak publicly at all. Regulated industries, listed companies before results, government, and anyone in an acquisition frequently cannot, and finding this out after they said yes wastes their goodwill and your time

Step 4: Make the ask specific and small

The size of the ask determines the answer more than the relationship does.

Bad: "Would you be willing to be a reference for us?" Open-ended, unbounded, and the honest answer to an unbounded commitment is no.

Good: "Would you take one 30-minute call with a company in your industry looking at the same problem, in the next two weeks?"

The ladder, roughly in order of how much you are asking:

• A G2 or peer-site review, which is short and they control it
• A quote for a page, which they approve
• One reference call, bounded in time and number
• A named case study, which is the big one because their marketing and legal get involved
• A speaking slot or a webinar, which is a genuine imposition and should be treated as one

Ask for the smallest thing that does the job. Sales frequently asks for the largest by default.

Step 5: Surface the approval path before you start

This is what kills case studies, usually after everyone has already spent hours on them.

Ask early and directly: does this need sign-off from marketing, communications, legal or a manager. Almost always yes at any size, and almost never surfaced until a draft exists.

Then work with it rather than around it. Ask who owns it, ask what they usually require, and give your contact something they can forward internally rather than making them explain it. A one-pager they can send to their comms team removes the reason most case studies quietly die.

Step 6: Say what they get, and mean it

An ask with nothing on the other side is a favour, and favours run out.

What actually has value to them, roughly in order:

• Peer access. An introduction to someone facing the same problem, or a seat in a customer group. The most reliably valued and the least often offered
• Their own visibility. A case study with their name on it is a career asset for the individual, if it is written to make them look good rather than to make your product look good
• Influence. Time with your product team, early access, a genuine say
• Something concrete you already owed them. A commitment pulled forward, a feature escalation, support given

Do not offer a discount for a reference. It prices the relationship and it makes every future ask a negotiation.

Then deliver whatever you promised. The second ask is decided entirely by what happened after the first.

Step 7: Track it, and treat consent as per-use

• One register of who has been asked, for what, by whom and when. Across sales, marketing and support, not only yours
• Never use someone as a reference without asking each time. A yes last quarter is not standing permission, and finding out they were used again from the prospect is how an advocate stops being one
• Record the expiry. People change roles and companies, and a case study quote from someone who left two years ago is a liability rather than an asset
• A no is data. Ask why, gently and once. "Not right now" from a happy customer usually has a reason attached, and it is frequently a health signal you did not have

Output

1. The disqualifier check: escalation, unstated value, renewal proximity, fatigue
2. The moment: what they said, when, in their words
3. The person, who benefited rather than who signed, and whether they can speak publicly
4. The ask, specific, small and bounded, with the ladder rung named
5. The approval path, asked about before anything is drafted
6. What they get, and who owes it
7. The register entry, including expiry
8. What you could not check

Failure modes

• Asking at renewal. Converts a favour into a trade, permanently
• Asking during an open escalation, which is remembered longer than the escalation
• Asking the signer, and getting vendor-management language nobody is convinced by
• The unbounded ask. "Would you be a reference" invites a no
• Asking for the largest rung by default, usually because sales asked for it that way
• Discovering the approval path after a draft exists. Where most case studies die
• No register. The same three accounts asked by four teams who cannot see each other
• Treating one yes as standing permission. Reusing someone without asking ends the relationship as an advocate
• Offering a discount for advocacy. Prices the relationship and makes every future ask commercial
• Not delivering what you promised in return. There is no second ask
• Letting a quote outlive the person, so the case study names someone who left two years ago

What good looks like

• The ask followed a moment where they said something worked, and quoted it back
• It went to the person who benefited, not the person who signed
• It was small, bounded and specific enough to answer in one line
• The approval path was known before anyone drafted anything
• Something real went back the other way, and it was delivered
• The register shows who has been asked by every team, not just yours
• A no was met with one gentle question, and the answer was informative

Related skills

• business-review for establishing the value that makes an ask reasonable
• escalation because a well-handled escalation is one of the strongest advocacy moments there is
• stakeholder-map for identifying who actually benefited
• one-pager for the document your contact forwards to their own comms or legal team
• renewal-negotiation for the case where advocacy is genuinely being traded, which should be a deliberate choice
• csql-motion for the other place customer success is asked to monetise trust, with the same asymmetry and the same failure mode

Supporting files

None. The output is a decision, an ask and a register line, and a template would be longer than all three.