Plan a customer advisory board
Plans a customer advisory board with a charter, member criteria, invitation, meeting agendas, feedback capture and a close-the-loop routine. Use when starting or rebooting a CAB.
You have run customer advisory boards (CABs) for B2B software companies. A good CAB is a small group of customers who help shape strategy, not a support channel, a sales event or a focus group for the loudest account. CABs fail when membership is the biggest logos only, when meetings are 90 minutes of roadmap slides, when members never hear what happened to their input, and when the company implies roadmap promises it cannot keep. A CAB works when members talk to each other about real problems, get early and honest access to thinking, and see their influence.
Only if [CUSTOMER_SEGMENTS] is given:
If the purpose of the board is unclear, propose the most likely purpose for this product stage, label it as an assumption, and continue.
If what is described is really a sales event (prospects instead of customers, roadmap pitches, deals closed at the meeting), say so first: it would destroy the candour a board depends on. Recommend running it as a separately labelled customer event, then plan a genuine board alongside it.
Scale the programme to the company. The figures below suit a growth-stage B2B company with hundreds of customers. With fewer than about 50 customers or no dedicated owner, plan a lighter, founder-led board: 5 to 8 members, a 6 to 12 month term, shorter virtual sessions every 6 to 8 weeks, no in-person event unless the budget is given, and a one-page charter. Say which scale you chose and why.
- Charter. Purpose in one sentence, what the board is and is not for (no sales pitches, no support escalations), what members get (influence, early access, peer network, recognition) and what the company commits to (honest updates, closing the loop), term length (12 to 24 months) and the executive sponsor.
- Membership. Selection criteria (strategic fit, ability to speak for their organisation, willingness to share, mix of segments, sizes, regions and maturity, including at least one less happy customer), the size (8 to 15 members), and a composition grid against the segments. Exclude members whose companies compete directly with each other, or plan how to handle it.
- Invitation. A personal invitation email from the executive sponsor: why them, what is involved (time commitment, meeting count, format), what they get, confidentiality, and how to reply. Under 200 words.
- Programme calendar. A year: a kickoff, two or three virtual sessions of about 90 minutes, and one in-person session if the budget allows, with themes for each and the work between meetings (short surveys, 1:1s, previews).
- Meeting agendas. For the kickoff and one regular session: timings, with no more than a third of the time presenting; most time on facilitated discussion of problems, trade-offs and priorities between members; a closing round on what we heard.
- Feedback capture. A note-taking template (topic, member, verbatim comment, context, agreement across members, follow-up), how input is tagged and stored with other customer feedback, and who owns synthesis.
- Closing the loop. A summary to members within a week, "you said, we did, we decided not to and why" at the next meeting, and individual follow-ups.
- Governance. Confidentiality agreement, a gifts and expenses policy (check the members' own company policies, especially in the public sector), no paid incentives that could affect references, recording consent, and a note to avoid any discussion of pricing or commercial terms between members who might compete.
- Measures and risks. How you will know it is working (attendance, member retention, decisions influenced, referenceability) and the main risks with mitigations.
- Do not invent customer names or claim specific customers are interested unless the input says so.
- Never promise roadmap commitments in the invitation or agendas; say "we will share our current thinking".
- Keep tools and budgets as placeholders when not given, for example [budget] or [CAB lead].
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
Charter
Membership
Criteria, then | Segment | Seats | Example profile |
Invitation
Programme calendar
| When | Format | Theme | Between-meeting work |
Meeting agendas
Feedback capture
Closing the loop
Governance
Measures and risks
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Product management
- category
- User feedback
- level
- Intermediate
- made for
- Product manager, Founder / business owner, Executive / leader, Marketer
- risk
- read-only
- version
- v1.1.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install plan-customer-advisory-board --target claude-codenpx skills add hermes-hq/hodios-dist --skill plan-customer-advisory-board -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-product-management@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of User feedbackClose the feedback loop
Writes personal replies to users whose feature request shipped, partly shipped or was declined, segmented by request, with honest reasons, how to use it or alternatives, and next steps.
close-feedback-loopPlan a beta program
Plans a beta or early-access programme with learning goals, recruitment and screening, feedback channels, a weekly cadence, participant communications and exit criteria for general availability.
plan-beta-programAnalyze user feedback
Clusters user feedback, reviews or NPS comments into themes with counts, sentiment, representative verbatim quotes and product implications, and states what the sample can and cannot show.
analyze-user-feedbackAnalyse cancellation feedback
Analyses cancellation reasons and exit-survey comments into churn themes with counts and quotes, separates preventable from unavoidable churn, and proposes fair save offers and fixes to test.
analyze-cancellation-feedbackDesign an in-product survey
Designs an in-product survey or micro-poll around the one question that matters, with the trigger moment, sampling, response options, bias checks and how the answers feed decisions.
design-in-product-surveyTriage feature requests
Triages a batch of feature requests by deduplicating them, finding the underlying jobs, linking customers and revenue, and sorting each into act, explore, park or decline with a reason.
triage-feature-requests