Advisory Board or Informal Advocates: Picking the Right Fit
A formal customer advisory board sounds more impressive than a loose group of enthusiastic customers you call on occasionally, but it's also a lot more overhead, and it's the wrong choice for plenty of companies that would get more value from a lighter structure.
Here's a comparison of the two approaches, what each actually demands of you, and how to tell which one fits your current customer base.
What a formal advisory board actually requires
A real advisory board means recurring meetings, prepared materials, a clear charter about what the board influences, and enough executive attention that members feel their time is respected. Members expect roadmap visibility and a genuine voice in decisions, not a marketing photo opportunity dressed up as strategic input.
This model fits best when you have a stable base of sophisticated, high-value customers with a genuine stake in your product direction, and when you have executive bandwidth to actually run the program well rather than let it fade into occasional, poorly attended calls.
What a looser advocate network actually requires
An informal advocate network runs on lighter-weight, ad hoc asks: a reference call here, a quote for a case study there, an early look at a new feature for someone who's genuinely enthusiastic about your product. It needs a way to track who's already been asked for what recently, so the same handful of eager customers aren't tapped constantly while everyone else is ignored.
This model fits well for a broader, more varied customer base, or for a company not yet ready to commit the executive time a formal board needs to run properly.
Match the model to what you can actually sustain
A poorly run advisory board, with sporadic meetings and no clear influence on decisions, does more damage to your relationship with those customers than never having formed one at all, since members feel like their time was wasted on something that was never going to matter. Be honest about your actual bandwidth before committing to the formal version.
If you're not sure you can sustain quarterly meetings with real preparation for a full year, start with the lighter advocate network and consider a formal board later once you've proven you can run the lighter version consistently.
Choose the formal advisory board only if you can answer yes to each of these questions:
- Do you have a stable base of sophisticated, high-value customers with a real stake in your product direction?
- Can you sustain recurring meetings with real preparation for at least a full year?
- Will executives give the board genuine attention and roadmap visibility?
- Is there a clear charter stating what the board can and cannot influence?
Track the ask, not just the relationship
Whichever model you choose, keep a simple record of every ask made of each advocate: which reference calls, quotes, or reviews they've contributed, and when. Without that record, it's easy to unintentionally overuse your most generous customers while more reluctant advocates never get approached at all.
Rotate asks deliberately based on that record, and set a rough limit on how often any single advocate gets tapped in a given period, so goodwill doesn't quietly get exhausted by the same small group of people saying yes to everything.
For example, keep a shared sheet with one row per advocate and columns for the type of ask, the date and the outcome, such as a reference call completed or a quote approved. Before requesting a favor, check the sheet and pick the advocate who has been asked least recently. Add a note when someone declines, so you don't ask again for the same thing. A common mistake is letting each team keep its own private list, which guarantees that the same enthusiastic customer is contacted by marketing, sales and customer success in the same month.
Give something back that isn't just recognition
A public thank you or a small gift is nice but doesn't sustain a relationship on its own. The advocates who stay engaged longest tend to get something functionally useful in return: real influence on roadmap decisions, early access to features before general release, or direct access to your product team when they have a real problem.
Ask your advocates what they'd actually value instead of assuming recognition alone is the currency that matters to them. What motivates a technical buyer to keep saying yes is often different from what motivates an executive buyer, even within the same program.
Check in on that preference periodically rather than assuming it's fixed once you've asked. An advocate's own priorities shift as their role or company changes, and what felt valuable to offer a year ago may no longer be the thing that keeps them engaged today, so a short annual check-in conversation is worth the small amount of time it actually takes to run properly.
What Good Looks Like
A working advocacy program matches its structure, formal board or informal network, to actual available bandwidth and customer base, tracks every ask made of each advocate to avoid overuse, and offers something functionally valuable back rather than relying on recognition alone.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
Do we need a formal advisory board, or is an informal network enough?
It depends on your bandwidth and customer base. A formal board needs recurring meetings and real executive attention to be worth the overhead. If you can't sustain that consistently, a lighter advocate network usually serves a broader customer base better with far less commitment.
How often should we ask the same advocate for a favor?
Track every ask made of each advocate and set a rough limit within a given period. Without that record, the same generous, easy-to-reach customers tend to get overused while more reluctant advocates never get approached, which wastes a lot of untapped goodwill.
What do advocates actually want in return for helping?
Ask them directly rather than assuming. Recognition matters less over time than something functionally useful, like real influence on the roadmap or early access to new features. What motivates one type of buyer often differs from what motivates another, even in the same program.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
Ranking for High-Intent Queries When an AI Overview Sits Above You
How to structure pages for high-intent, commercial search terms so both traditional rankings and AI answer overviews can actually extract and cite them.
Running a Case Study Pipeline Instead of a One-Time Push
How to pick customers worth asking, get a usable quote without an interrogation, and place proof where it actually changes a visitor's decision.
Why AI-Referred Visitors Convert Differently (and What to Track)
AI-referred visitors arrive mid-decision, not mid-search. Here's how to compare their conversion rate fairly against organic and paid traffic.
Getting NPS Responses That Are Actually Worth Reading
Why most post-purchase surveys get ignored, when to actually send one, and how to turn a single number into feedback specific enough to act on.
Content Syndication Without Duplicating Your Own Rankings
Compare guest republishing, licensed syndication networks and self-syndication, and learn how to protect your canonical rankings when others repost your work.
Why AI Citations Show Up as 'Direct Traffic' and How to Fix It
Most AI assistants strip referrer data, so traffic from a citation shows up as direct in your analytics. Here are three practical ways to recover the signal.