Customer Advisory Board

Purpose: Gather strategic input from trusted customers to shape product direction and positioning

How to run this meeting

A customer advisory board (CAB) is one of the most high-leverage forums you have — but it requires discipline to not turn it into a product demo or a roadmap reveal. Your customers are here because they have context and experience that you don't. Structure the meeting so they spend more time talking than you do. A good target is 30% product team presenting, 70% customer discussion.

Share roadmap themes and directions, not specific features or timelines. Specifics invite negotiation ("but we need X by March") and create implicit commitments. Themes invite strategic input ("we're thinking about helping teams stay aligned across time zones — what does that challenge look like for you?"). You'll get better signal, and you won't box yourself in. When you do share something directional, frame it as a question: "We're considering investing in this area — does that match what you're experiencing?"

Compose your CAB deliberately. Mix company sizes, industries, and maturity levels — a startup and an enterprise will give you very different signal on the same question, and both are useful. Aim for 8-15 members; larger than that and the conversation becomes a presentation. Rotate members periodically to refresh perspective. Follow up with every member within 48 hours — even a short personal note — to reinforce that their time was valuable and their input was heard.

Before the meeting

• Set and share the agenda at least one week in advance
• Prepare 2-3 specific discussion questions — not yes/no, but open and directional
• Brief all internal attendees on listening objectives and rules of engagement (no pitching, no defending)
• Prepare a short product update covering only what has shipped and why — no future promises
• Assign a dedicated note-taker separate from the facilitator
• Prepare a brief summary of how previous CAB feedback influenced recent decisions (close the loop)
• Confirm attendance and logistics at least 48 hours before

Meeting Details

• Date:
• Facilitator:
• Attendees:
• Duration: 90–120 minutes (quarterly cadence recommended)

---

Product Updates

What has shipped since the last CAB? Keep this brief and connect it to feedback you received from this group. Customers feel invested when they see their input reflected in the product.

• Shipped: Audit log export (CSV) — directly driven by the compliance feedback from Q4's CAB. Available to all plans.
• Shipped: Webhook support — enables teams to route notifications to Slack, PagerDuty, and custom tools. Several members asked for this at the last session.
• In progress: SSO / SAML — responding to enterprise adoption blockers that came up in our Q4 discussion. Expected Q2.

---

Industry Trends

What is happening in your members' industries that is shaping how they think about tooling, process, and priorities? Let members lead this discussion — your job is to listen and probe.

• AI-assisted workflows: Three members mentioned pressure from leadership to evaluate AI tooling across the stack. Primary concern is AI reliability for compliance-sensitive decisions.
• Distributed team coordination: Members with teams across multiple time zones are struggling with async decision-making. "We make decisions in Slack threads and they disappear" (Foxridge Health).
• Headcount constraints: Two members noted they're managing the same scope with fewer people in 2025 — they need tools that reduce coordination overhead, not add to it.

---

Customer Priorities

What are the most important things members are trying to accomplish in the next 6-12 months? These are their goals, not their feature requests.

• Foxridge Health: Reduce time-to-deploy by 30%; cross-team dependency visibility is the biggest blocker
• Meridian Corp: Pass SOC2 Type II audit in Q3; needs reliable audit trails across all tooling
• Crestline Partners: Expand product team from 8 to 15 people without losing coordination quality
• Avex Technologies: Consolidate from 4 tools to 2; looking for a platform that can absorb their current Notion + Jira workflow

---

Feedback

Specific reactions to product updates, demos, or discussion questions raised today. Attribute to company, not individual names in shared notes.

• On audit log export: Meridian Corp confirmed it's directionally right but needs field-level filtering to be useful for their compliance team. Current export is "a start."
• On webhook support: Three members said they'd use it but want Slack as a first-class native integration, not a workaround. "Zapier is fine for developers, not for my team."
• On the async decision-making discussion question: Strong resonance across the group. Foxridge and Avex both described informal workarounds (pinned Slack messages, Notion decision logs) that are fragile.

---

Strategic Insights

Step back from individual feedback items. What are the bigger themes? What do you now believe to be true that you didn't before this meeting?

• The compliance requirement (SSO, audit logs) is becoming table stakes for enterprise deals, not a differentiator. Shipping SSO is a trust signal, not just a feature.
• Native integrations are increasingly a buying criterion. Webhook-as-workaround is not landing as a substitute.
• There is an emerging "async decision record" use case that none of our current flows address well. Multiple members have built their own workarounds — this is a strong signal of an unmet need.
• Customers are consolidating tools. Positioning as a platform (not a point solution) is increasingly relevant, but only if the breadth is real.

---

Action Items

Follow-up

Send a personal thank-you to each member within 48 hours — not a mass email. Reference something specific they said. Share a brief written summary of what you heard and what you plan to do with it; this is the most important thing you can do to sustain trust and keep members engaged for future sessions. At the next CAB, open by closing the loop on what changed as a result of this one.