Customer advocacy programs fail when they are built around rewards instead of relationships. Customer advocacy is not a referral program with a gift card. It is identifying your happiest customers and making it easy for them to tell their peers. The ask should be specific and the timing should be right. Ask your happiest customers for one specific introduction at the moment they are happiest with you.
Health scores should be simple and actionable
A customer health score has one job: tell you which customers need attention this week. If your health score requires a data scientist to calculate, it is too complex. If it does not lead to a specific action, it is too abstract. The best health score is three signals combined into red, yellow, green.
The three signals that matter for most B2B products: usage frequency, breadth of feature adoption, and relationship strength. Usage frequency is how often they log in. Breadth is how many of your core features they use. Relationship is whether your champion is engaged and responsive. Weight them equally, review weekly, and act on every red account within forty-eight hours.
QBRs are for the customer, not for you
The quarterly business review is not a report on your product's usage statistics. It is a strategic conversation about the customer's business and how you are helping them achieve their goals. If your QBR is a slide deck of login counts and feature adoption rates, you are doing it wrong.
The QBR that works: thirty minutes, three topics. Topic one is the customer's goals for the quarter and how you contributed. Topic two is what is not working and what you are doing about it. Topic three is what is next on your roadmap that maps to their needs. The customer should talk more than you do. If they are not engaged in the conversation, the QBR is a waste of both your time and theirs.
Support is a product feedback channel
Every support ticket is a product decision waiting to be made. A bug report is a quality issue. A how-to question is a UX issue. A feature request is a roadmap signal. If you are only resolving tickets without categorizing and analyzing them, you are throwing away your cheapest source of product intelligence.
Categorize every ticket: bug, UX confusion, feature request, or account issue. Review the categories weekly. If twenty percent of tickets are the same UX confusion, fix the UX. If ten customers request the same feature, consider building it. Support volume is a product health metric. Rising volume means your product is getting harder to use, not that your customers are getting needier.
Customer feedback should change your roadmap
If your roadmap looks the same after three months of customer feedback, you are not listening. Customer feedback should be the primary input to your product prioritization. Not the only input, but the primary one. The customers who use your product every day know things about it that you do not.
The system: collect feedback from support tickets, sales calls, customer success conversations, and NPS surveys. Categorize it by theme. Count the mentions. When a theme reaches ten mentions from different customers, it goes on the roadmap. This is not scientific, but it is better than building what the loudest customer asked for last week.
Renewals start ninety days before the contract ends
The renewal conversation does not start when the contract is up. It starts ninety days before. That is when you should be assessing health, identifying risks, and planning the expansion conversation. By the time the renewal date arrives, the outcome should already be determined by the value you have delivered.
The ninety-day renewal plan: day ninety, review the health score and usage data. Day sixty, have a value conversation with the champion: what have we accomplished together, what is next? Day thirty, address any concerns and present the renewal proposal. Day zero is a formality, not a negotiation. If you are negotiating on day zero, you started too late.
Frequently asked questions
What is a customer advocacy program?
A system for identifying your happiest customers and making it easy for them to tell their peers: introductions, references, reviews, and case studies. It is built on relationships and timing, not gift cards and points.
How is customer advocacy different from a referral program?
A referral program pays for leads. Advocacy asks happy customers to vouch for you because they want to. Referral incentives can fill the top of funnel; advocacy produces the references and proof that actually close deals.
When is the right time to ask a customer for advocacy?
Right after a visible win: a renewal, a successful rollout, a support save, a strong quarter in your product. The ask should be specific and small, like one introduction or thirty minutes for a reference call.
How do I find my happiest customers?
Your health score already knows. Look for green accounts with high usage, broad feature adoption, and an engaged champion. NPS promoters and customers who renew without negotiating are your first advocacy list.
How many advocates does an early-stage company need?
Three to five who will take a call, join a case study, or make an introduction. That covers most early sales cycles. Depth beats size: one champion who tells a specific story is worth twenty names in a spreadsheet.