b2b-customer-advisory-board-coach

Coach a B2B founder, CEO, CRO, CCO, or product leader through designing, recruiting, and running a Customer Advisory Board (CAB) — a 6-12 person body of senior customer executives that meets 2-4x/year to provide strategic input on roadmap, market direction, and product priorities. Covers when a CAB is worth doing (product-market-fit confirmed, $5M+ ARR, you have 50+ paying customers, you're entering enterprise tier), the difference between CAB / customer council / user group / advisory board (these are not interchangeable; mixing them confuses customers), member-selection criteria (champion strength, segment representation, deal-size mix, executive-level not user-level, willingness to commit), the recruiting pitch (what you offer them, what you ask of them, term length 12-18 months, compensation expectations — usually no cash, sometimes equity at very late stage), the meeting structure (8-hour day or 2x4-hour halves; pre-read 2 weeks ahead; CAB chair role; agenda format), the do's-and-don'ts of CAB content (it's not a sales pitch, not a steering committee with binding decisions, not a feature-prioritization vote), the CAB chair role (often an exec from the customer side, sometimes an outside facilitator), the post-meeting follow-up cycle (action items, commitment loops, prep for next meeting), the special challenges of running a CAB (one dominant member who hijacks discussions, customer-confidentiality across competing members, what to do when CAB feedback contradicts your roadmap), and the natural CAB lifecycle (typically 18-36 months before refresh / dissolve / restructure). Use when founder/CRO/CCO says "we should start a CAB", "customer advisory board first meeting", "CAB charter", "who should be on our CAB", "CAB chair", "CAB meeting agenda", "CAB member churn", "sunset CAB". Triggers on phrases like "Customer Advisory Board", "CAB", "advisory council", "customer council", "user group", "exec-level customer feedback", "strategic customer input", "CAB charter", "CAB chair", "CAB pre-read", "CAB rotation", "advisory board NDAs".

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "b2b-customer-advisory-board-coach" with this command: npx skills add charlie-morrison/b2b-customer-advisory-board-coach

b2b-customer-advisory-board-coach

Coach a B2B leader through designing, recruiting, running, and eventually evolving a Customer Advisory Board (CAB). A well-run CAB compounds in value over 18-36 months and becomes a strategic moat: deeper roadmap insights, peer-introduction power, executive-level reference accounts, and a community of customers who feel ownership in your direction.

A poorly-run CAB is worse than not having one — it consumes exec time, frustrates senior customers, and creates expectation gaps that damage relationships.

When to engage

Trigger when:

  • "We're thinking about starting a Customer Advisory Board"
  • "How do I structure our first CAB meeting?"
  • "Who should we invite — top customers, biggest customers, or strategic ones?"
  • "Our CAB has stalled / one member is dominating / engagement is dropping"
  • "We need to dissolve / refresh / sunset the CAB"
  • "How do we handle a CAB member whose company became a competitor?"
  • "How do we balance CAB feedback against our own roadmap?"
  • "What do we offer CAB members in exchange for their time?"

Do not engage for: VC advisory boards, board-of-directors design, technical advisory boards (different stakeholder logic), or user-group / community programs (different audience, different mechanics).

Step 0: Is a CAB the right tool?

Many founders confuse different customer-engagement structures. They are not interchangeable.

  • Customer Advisory Board (CAB): 6-12 senior executives from customer companies. Meets 2-4x/year. Provides strategic input on direction. Decision-influential, not decision-making. Confidential discussions among members.
  • Customer Council: broader, often 20-40 customers, mixed levels. Meets virtually 4-6x/year. Tactical product feedback. Less confidential.
  • User Group: end-user-level meetups (sometimes regional). Tactical, peer-to-peer. Not strategic.
  • Beta Council: customers who get early-access features. Feedback-focused. Time-bound to releases.
  • Reference / Customer-Marketing Program: external-facing; case studies, references, conference speakers.

CAB ≠ User Group ≠ Beta Council. Mixing them in one body confuses customers and dilutes the conversation.

A CAB is the right tool if you want:

  • Senior-executive perspective (VPs and C-suite from customer companies).
  • Strategic, not tactical, input.
  • A confidential / off-the-record forum.
  • A long-term, high-trust relationship with key customers.
  • An asset for executive references / market signaling.

A CAB is the wrong tool if you want:

  • Broad product feedback (use Council).
  • Beta-feature testing (use Beta).
  • Customer-marketing leverage (use Reference Program).
  • A "voice of the customer" funnel (CAB is too small a sample).

Step 1: Pre-conditions before starting a CAB

Don't start one too early. The signals that you're ready:

  • Product-market fit confirmed; not searching for it anymore.
  • $5M+ ARR (rough threshold; some companies start earlier).
  • 50+ paying customers across at least 2 segments.
  • You're entering or expanding into enterprise tier (CAB is most valuable for enterprise-tier strategic decisions).
  • You have an exec-level "champion" who can drive the program (founder/CEO directly, or CRO/CCO with founder commitment to attend).

If you're missing any of these — focus on the gap first. A CAB requires customer-side seniority that you can't conjure if you're still doing $50K-deal SMB sales.

Step 2: Define the charter

Before recruiting, write a 1-2 page charter. This is your contract with members.

Charter components:

  • Purpose: what the CAB exists to do (e.g., "Provide strategic input on product direction, market positioning, and competitive landscape, with the goal of shaping a 2-3 year roadmap.")
  • Membership: size (8-12), composition (segments, deal sizes, geo), eligibility (named exec from customer company, can include founder + decision-maker, term length).
  • Term: 12-18 months default. Renewable.
  • Cadence: in-person 1-2x/year + virtual 1-2x/year. Half-day virtual; full-day in-person.
  • Confidentiality: mutual NDA. Discussion is "Chatham House" — anyone can take ideas; no attribution.
  • What members get: roadmap influence, peer network, executive-level access, occasional pre-release access, possibly stock-warrant pool (advanced; legal counsel required).
  • What we ask of members: attend 2 of 3 meetings/year, do pre-reads, participate in 1-2 short surveys/year, occasional 1:1 calls with our team between meetings.
  • CAB Chair: typically a senior member elected by peers; outside facilitator optional.
  • Decision rights: advisory only; no binding votes.
  • Confidentiality of competitors: policy on members from competing customer companies.

Get the charter approved by your CEO, CRO, CCO before reaching out to potential members.

Step 3: Member selection

The single biggest determinant of CAB quality. Get this wrong and the CAB never recovers.

Selection criteria

  • Champion strength: member already advocates for you internally; uses your product strategically.
  • Senior-level: VP and above. C-suite preferred. Director-level only as a 2nd seat from a major customer.
  • Decision-maker / decision-influencer: they can actually buy more, expand, evangelize.
  • Articulate / opinionated: quiet members add no value to the discussion.
  • Diversity: segment, geo, deal-size, industry, gender / background. Echo-chamber CABs are useless.
  • Time commitment willingness: ask explicitly upfront. People who can't commit will damage the meetings.
  • Customer health: they should be a strong customer; not currently churning, not in renewal-fight mode.

What to avoid

  • All your biggest customers (they dominate, and small customers' perspectives are lost).
  • All from one segment / industry / geography.
  • Multiple competing customers without conflict-of-interest plan.
  • Members who are vendors or partners, not pure customers (different motivations).
  • Anyone whose primary motivation is selling you something.

Composition templates

  • Pure-play SaaS, $5-50M ARR: 8-10 members. 2-3 marquee customers, 2-3 mid-market growers, 2-3 strategic-deal customers in your target tier, 1-2 international.
  • Vertical SaaS: 6-8 members representing the dominant sub-segments of your vertical.
  • Platform / API: 6-10 members representing different use cases (e.g., for an analytics platform: product analytics user, marketing analytics user, finance analytics user, executive-dashboard user).

Recruiting outreach

  1. Identify candidates via CRM data, sales-team input, exec-relationships.
  2. CEO or CRO does the personal ask (not a CSM, not via email blast).
  3. Pitch:
    • Brief (10 min): "We're building a Customer Advisory Board. We'd love your perspective."
    • Charter share + commitment ask + term length.
    • Honest about cost: "It's about 4-6 days of your time over the year, including travel."
    • Honest about value: "You'll get peer access, roadmap influence, advance access. You won't get cash."
  4. Confirm acceptance in writing; send NDA.

Compensation

  • Standard: no cash compensation. Token "thank you" gifts (high-quality dinners, occasional small luxury).
  • Travel: company pays travel + lodging + per-diem.
  • Equity: rare and complex. Late-stage companies sometimes grant warrants to advisor-track CAB members; legal counsel required; can complicate customer-relationship cleanliness.
  • In-kind: premium support tier, early-access features, named-account engineer access.

Step 4: Meeting design

CAB meetings are unlike normal meetings. The whole purpose is generating senior-customer dialogue — not pushing your roadmap.

Cadence

  • 2-4 meetings per year. Most established programs: 2 in-person + 2 virtual.
  • In-person typically 6-8 hours, often a full day with social dinner.
  • Virtual 3-4 hours with breaks; never 8 hours.

Pre-read (2-week lead time)

  • 4-8 page document.
  • Covers: agenda, 2-3 core questions for the meeting, current company state (key metrics, recent product changes, current strategy), competitor / market context, specific decision points where input is sought.
  • Sent 14 days ahead. Members are expected to read.
  • "Did you read the pre-read?" is a question you'll need to ask in early meetings; expect 60-70% of members to engage with pre-read in year 1.

Agenda (8-hour in-person template)

  • 09:00-09:15 Welcome + intros (especially first meeting)
  • 09:15-09:30 State of the company / market (15 min, not 60)
  • 09:30-10:30 Topic 1: roadmap framing question
  • 10:30-10:45 Break
  • 10:45-11:45 Topic 2: market / competitive landscape question
  • 11:45-12:45 Lunch (working / informal)
  • 12:45-14:00 Topic 3: deeper dive on a strategic decision
  • 14:00-14:15 Break
  • 14:15-15:00 Open Q&A / member-raised topics
  • 15:00-15:30 Action items + next-meeting setup
  • 15:30 Adjourn (dinner optional same evening)

Topic types that work

  • "We're considering [strategic option A vs B]; what would each mean for you?"
  • "What's changing in [your industry / market] that we should know about?"
  • "Where are we under-investing vs. over-investing on the product?"
  • "What would make our product 10x more valuable to your business?"
  • "What competitors are you evaluating, and why?"
  • "What's the biggest blocker to expansion within your company?"

Topic types to avoid

  • "Should we build feature X?" (too tactical; use Council or surveys)
  • "Vote on these 5 priorities" (CAB is advisory, not decision-making)
  • "How can we sell more to you?" (too transactional)
  • "Pitch deck of next 12 months of features" (one-way, kills dialogue)

Facilitation

  • A CAB Chair (often a member) opens, sets tone, occasionally redirects.
  • Internal team: founder/CEO + CRO/CCO + product lead. Avoid filling the room with internal staff; signal-to-noise drops.
  • Note-taker: dedicated. Often an outside CAB facilitator or chief-of-staff.
  • One-dominant-voice management: the CAB Chair / facilitator must redirect, e.g., "Sarah, that's a great point. Mark, what's your take from the [segment] perspective?"

What members say after a great meeting

  • "I learned more from the other CAB members than from the company team."
  • "This is the most candid forum I'm in for [our category]."
  • "I felt my input shaped the conversation."

If members are saying "I learned about your roadmap" — the meeting was 1-way and not a real CAB.

Step 5: Follow-up cycle

The 4 weeks after a meeting determine whether the next meeting will be valuable.

Within 1 week

  • Send synthesized notes + action items to all members.
  • Clearly mark which CAB inputs are being adopted, which are being explored, which are being deferred — and the reasons.
  • Don't pretend to adopt every input; CAB members can smell that and lose trust.

Within 2-4 weeks

  • 1:1 follow-up calls with each member: thank-you, deeper dive on their specific topic, ask for next-meeting topics they want.

Between meetings

  • Periodic updates (1-2/quarter): short note of "what's changed since we met, what's coming, what we'd love your input on at next meeting."
  • Surveys 1-2x/year on focused topics.
  • Occasional 1:1 calls between exec team and members on specific topics.

Pre-next-meeting

  • 4 weeks before, share planned themes for the next meeting; ask members for suggestions.
  • 2 weeks before, send the pre-read.

Special challenges

One dominant member

Member who hijacks discussions, drives off topic, or steamrolls quieter members. Address:

  • CAB Chair (or facilitator) actively redirects in-meeting.
  • 1:1 between CEO and dominant member: "We deeply value your input; in the meetings we want to draw out the others — can you help us with that?"
  • If continued, term-end exit conversation: "We're rotating the seat at end of term."

Competing customers

Two members from companies that compete with each other. Common in vertical SaaS. Solutions:

  • Stagger membership to avoid overlap.
  • Explicit "Chatham House" rule: anyone may take ideas, no attribution.
  • Strategic-topic carve-outs: avoid topics that are competitive moats for either company.

CAB feedback contradicts your roadmap

The CAB strongly recommends [X]; you've already decided [Y]. Be honest:

  • Acknowledge the input, explain the trade-off, share your reasoning.
  • Don't pretend to take the input then ignore it.
  • Members will respect "We considered this carefully and chose Y because [specific reasons]"; they will not respect being ignored.

Member becomes a competitor

A CAB member's company pivots into your market or a competing market. Address immediately:

  • 1:1 with the member: discuss the conflict honestly.
  • Often the right outcome is they step down from the CAB; sometimes they remain in a modified capacity.
  • Update the charter if needed for future cases.

Meeting attendance erosion

Member skipping meetings. Address by month 6:

  • 1:1 to understand: bandwidth issue? value issue? scheduling?
  • Re-engagement plan or graceful exit at term-end.

CAB lifecycle

Phase 1 (months 0-12): Establishment

  • Recruit, run first 2 meetings, establish the rhythm.
  • Members are still figuring out "what is this thing?"
  • High exec-team time investment.

Phase 2 (months 12-24): Productive plateau

  • Meetings produce consistent, useful input.
  • Some natural attrition (job changes, company changes).
  • Refresh 1-2 seats per year.

Phase 3 (months 24-36): Refresh / evolve

  • Either: refresh half the membership for renewed energy; or
  • Expand: add a second CAB for a new segment / region; or
  • Evolve: shift purpose (e.g., from roadmap-focus to peer-network-focus).

Phase 4 (eventually): Sunset or restructure

  • Sometimes the right move is to dissolve and replace with a different structure.
  • Signals: meeting energy declining, exec-team stops attending, members rotate without replacements.
  • Sunset gracefully; thank members publicly; convert relationships to alumni network.

Anti-patterns to flag

  • Starting too early. $1M ARR, 10 customers — you don't need a CAB; you need product-market-fit work.
  • Recruiting based on relationship rather than fit. Friends-of-the-founder make worse CAB members than strategically-relevant customers.
  • Letting Sales / CS run the CAB. This becomes an upsell engine; trust dissolves.
  • Asking the CAB to vote on features. Wrong tool; CAB is for strategic input, not tactical decisions.
  • No follow-through on action items. Single biggest reason CABs decay.
  • Mixing levels. A VP and an analyst in the same room — neither will be candid.
  • Over-presenting / under-listening. Pre-read should carry the briefing; meeting should be 80% dialogue.

Integration with other coaches

  • saas-acquisition-prep-coach: strong CAB members are valuable references in M&A diligence.
  • saas-pricing-auditor: CAB can stress-test major pricing changes pre-rollout.
  • nrr-recovery-coach: CAB feedback is a leading signal for NRR direction.
  • chief-of-staff-onboarding-coach: CoS often becomes CAB program manager.
  • enterprise-sales-coach: CAB members often become reference accounts, peer-introducers.

A CAB is a 2-3 year commitment. Don't start one if you can't sustain it.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Obsidian Cleaner

Automatically clean up loose images and attachments in Obsidian vault root, moving them to the Attachments folder. Trigger when user says "clean obsidian", "clean attachments", or "整理附件".

Registry SourceRecently Updated
General

tradealpha实时新闻

获取 TradeAlpha 实时新闻和语义检索结果。适用于用户提到 TradeAlpha 新闻、今日新闻、路透、彭博、Truth、国内资讯、研报快讯,或要求按主题、事件、公司、叙事检索相关新闻的场景。通过聊天向用户索取 token,并在当前会话中复用,不读取环境变量,不写入本地文件。

Registry SourceRecently Updated
General

Everclaw — Inference You Own

Open-source first AI inference — GLM-5 as default, Claude as fallback only. Own your inference forever via the Morpheus decentralized network. Stake MOR toke...

Registry SourceRecently Updated
General

Identitygram Signin

Sign in to IdentityGram by calling the /auth/signin endpoint.

Registry SourceRecently Updated