Client Advisory Council: How to Conduct a Customer Advisory Board

A practical guide to the Customer Advisory Board: boundaries of the format, charter, membership, agenda, confidentiality, signals for the roadmap and follow-up.

A customer advisory board is needed by a company when occasional interviews with customers are no longer enough, and holding another presentation for VIP guests is pointless. The Customer Advisory Board, or CAB, creates a recurring loop: the same group of representatives from several clients discusses strategy, workflows and development directions, while the company analyses the signals and returns with a clear follow-up.

At Aventura, we view the CAB as a management process that requires an event format. First, the business defines the decisions and hypotheses to be tested. Then the team assembles the membership, discussion rules, agenda, confidentiality, protocol and feedback loop. The venue, technology and guest services support this work but do not replace it.

If the board is already in the plan, request a quote and discuss the format. In your request, specify the product or direction, roles of future participants, proposed city, connection format and the questions the business wants to explore.

What is a Customer Advisory Board?

A Customer Advisory Board is a standing or recurring group of representatives from several clients. A company engages it to validate strategic directions, understand real-world usage scenarios and discuss development priorities. Participants provide context and recommendations, while the right to make product and commercial decisions remains with the company.

In English-language practice the name Customer Advisory Board is used. Oracle links such a board to validating and shaping strategy, while Microsoft describes it as a direct feedback channel for discussing development directions. In both cases, it is about a selected group of clients and recurring interaction, not an open event for the entire customer base.

A working CAB rests on four characteristics:

• there is a permanent core of participants from several client organisations;
• meetings are part of a cycle rather than ending with a single event;
• the agenda covers strategy, product and clients' real processes;
• after each meeting, signals get owners, statuses and a response to participants.

The board advises. It does not vote on a finished product development plan, or roadmap, and does not make decisions in place of the product, leadership or legal team. A participant can highlight a problem, explain the consequences and assess a trade-off. The company validates that signal against other data, economics, risks and strategy.

Distinction from executive briefing, round table, and client day

CAB differs from neighboring formats in composition, frequency, and outcome. Executive briefing is assembled for one client company and its specific task. A round table can be a one-off discussion. Client day informs a broader audience. The CAB maintains a permanent group of several clients and closes the feedback loop after each meeting.

The distinction is needed before choosing a venue and guest list. If a company needs to thoroughly analyze the tasks of one client organization, an executive briefing for a key client is more useful. If the task is an open exchange of positions around one topic, a round table for clients is closer.

The name CAB will not fix a weak architecture. The meeting will remain a presentation if the company talks most of the time, shows a ready-made roadmap, and leaves questions for the last minutes. A closed dinner with executives also does not become a council without a recurring composition, a research agenda, and follow-up.

When Does a Company Need a CAB?

A CAB is worth launching when the business is ready to regularly validate decisions together with customers and is able to process feedback within the company. You need an internal sponsor, owners of product or strategic issues, access to participants, and a process for reviewing signals. If the team cannot explain what will happen after the meeting, the format is not ready yet.

Check your readiness with several questions:

1. Which decisions does the company want to improve with customer context?
2. Which hypotheses cannot be tested with analytics, sales, or support alone?
3. Who within the business will receive the meeting materials and assign owners?
4. Which topics are acceptable to discuss in a customer group?
5. How will participants learn what happened with their feedback?
6. Can the company honestly say that some suggestions will not be taken forward?

If there is no answer to the last two questions, the advisory board will quickly lose trust. Customers spend time, share their work context, and expect at least a clear status. Silence after the meeting looks like collecting ideas without accountability.

A CAB does not replace interviews, analytics, support, and user research. The board adds another layer: participants hear different contexts, compare constraints, and help the company see trade-offs between segments. The board's signal needs to be validated with other data, especially when one experience dominates the room.

If you need to bring the charter, participant list, agenda, venue, and follow-up together into one brief, submit a request for a quote. We will review the inputs and show which decisions are needed before inviting participants.

You need a working meeting, not a ceremony around a list of VIP guests. For such a project, we combine a research objective with organizing a business event: participant list, agenda, private venue, equipment, moderation, and subsequent work with the materials.

Charter of the council and internal customer

Charter is a short working document that defines the council's purpose, allowed topics, composition, roles, confidentiality rules, meeting rhythm, and feedback path. It protects the CAB from agenda creep and random promises. The document is approved by the internal customer, who can bring signals to decision makers.

Start the charter with one sentence: “The council helps the company better solve...” The continuation should name a product, service, or strategic area. The wording “strengthen relationships with key clients” is too broad. For relationships, you can hold a client event; the council needs a working decision area.

The charter should include:

The internal customer connects the CAB with management decisions. The program owner collects topics and coordinates teams. The facilitator leads the conversation, and the note-taker records formulations and context.

A lawyer or data protection officer checks the confidentiality regime, data handling, and recording where required.

At Aventura, we ask to separate the content customer and the meeting producer. The former is responsible for the questions and the fate of the feedback. The latter gathers invitations, venue, connection, timing, service, equipment, and materials. If these areas are mixed, the team can easily polish the guest journey and miss the decision for which the CAB was created.

How to select participants?

The CAB is composed based on the task, not on client ratings. A participant must personally know the process under study, influence decisions, or be responsible for implementation. The council benefits from managed heterogeneity: executives and practitioners, different segments and maturity levels, supporters and constructive critics. A random VIP without the necessary experience weakens the conversation.

First, describe the profile of the seat on the council: role and context, for example, the economic buyer of a large company, the head of implementation, an active user of a complex process, or a representative of a less mature segment. After that, customer success teams propose candidates, and the program owner checks compliance with the agenda.

Evaluate the candidate along five axes:

• real experience in the area under discussion;
• role in selection, implementation, or daily work;
• segment, scale, maturity, and constraints;
• willingness to speak to the point and respect group rules;
• absence of a situation that would completely pull the conversation into one acute conflict.

Atlassian separately advises caution when working with clients in active escalation. Their problem may be important, but the current conflict can take up the entire agenda. It is better to first address such a signal in a separate setting, and evaluate participation in the council after the situation stabilizes.

Don't assemble the council only from loyal supporters. A comfortable conversation rarely reveals the weaknesses of a hypothesis. At the same time, don't turn the group into a debate of segments that have nothing to discuss together. The composition and permitted topics of a closed meeting are checked in advance by the legal team.

GOV.UK provides a guideline of three to eight participants for small working groups. This is not a universal norm for the size of the entire council, but a useful limit for work in a small group: everyone has time to speak, and the facilitator can see the dynamics. A larger group needs additional facilitators and separate working tables.

The invitation should explain the role without flattering promises. Indicate the purpose of the council, the expected contribution, the approximate scope of participation, confidentiality rules, the recording policy, accessibility, and how to decline. It is convenient to collect registration and statuses according to the principles from the guide on event participant registration, but with special attention to closed materials and the authority of the client's representative.

Agenda: From Client Context to Trade-offs

The working CAB agenda moves from the client's real context to testing hypotheses and trade-offs. The company says just enough to set the frame. Most of the time goes to processes, constraints, workarounds, and consequences. Concepts are shown in small blocks, and roadmap discussions are held without promising a specific feature or timeline.

A poor agenda starts with company history, quarterly results, and a long demo. By the time questions begin, participants already know what answer is expected. Research value drops: clients comment on the presentation, not their own work.

The working logic looks like this:

1. Confirm the purpose of the meeting, the boundaries of the topic, and the rules for using the materials.
2. Give participants the opportunity to describe changes in their business and priorities.
3. Review the latest real case, the process, and the current workaround.
4. Clarify the consequences of the problem for time, quality, risk, or manageability.
5. Show one hypothesis, scenario, or prototype without a long explanation.
6. Collect individual reactions before the group discussion.
7. Discuss the value, implementation risk, required elements, and acceptable trade-offs.
8. Record the questions the team will answer after validation.
9. Summarize: what you heard and when the next contact will be.

Misunderstanding a concept is also a result. Don’t rush to explain to the participant what they “should have seen.” First, clarify the expectation, where the gap lies, and the words the person uses to describe their process. After that, the team can separate the problem of the interface, terminology, and the hypothesis itself.

If the agenda has a large general part and several tracks, the mechanics of organizing conferences resonate with us: a single timeline, track moderators, transitions, equipment, and collection of results. The difference is that CAB remains a closed research loop, not a public conference.

How to facilitate a closed-door conversation?

The facilitator keeps the goal, time, and equal participation, while the note-taker captures exact wording and context. These roles are best not combined. It is useful to collect individual responses first, then open the discussion. This order reduces the influence of status, a loud voice, and the first position voiced on the group's conclusion.

At the beginning, show the agenda and keep it visible. Confirm the confidentiality rules, recording, use of quotes, and the participant's right not to answer a particular question. If the rules differ for different blocks, state the transition before disclosing information.

Questions should lead to the most recent real case:

• what happened in a specific process;
• who was involved and at which step the problem arose;
• what the person did instead of the expected scenario;
• what consequences emerged;
• why the question matters now;
• what needs to change for the new approach to be adopted.

The question "Do you like the feature?" provides almost no context. A positive answer may mean politeness, interest in the idea, or genuine readiness to implement. Ask them to describe the action, the dependency, and the cost of changing the process.

Strong personalities and senior-ranking individuals can set the frame for the entire group. Use written input, round-robin responses, pair work, and small groups. Do not put a quiet participant in the spotlight with a pointed question. Give time to write down a thought, then invite them to share the part they are ready to discuss.

We rehearse complex transitions in advance: opening the closed part, presenting the material, collecting individual responses, changing groups, the roadmap question, and ending the recording. The general method of such a rehearsal is discussed in the article about the technical rehearsal of an event.

Signal Card for the Product Team

The main unit of CAB feedback is a combination of role, segment, process, problem, consequences, and current workaround. A separate feature request does not show why the idea is important and who needs it. The signal card preserves context, links the meeting material to the review owner, and helps validate the conclusion against other data.

During the session, do not try to immediately decide what will go into the roadmap. First, capture the signal so that an employee who was not in the room can understand it without guessing.

A single strong request does not become a commitment. SAP's participation terms explicitly separate submitted feedback from a promise to use it, and the disclosure of plans from a promise of delivery. The facilitator can honestly say that the direction is under consideration. No decision has been made yet; no timeline can be given.

After the meeting, the team groups the cards by topic and looks for repetitions, contradictions, and differences between segments. GitLab describes a practice in which recordings and notes are passed to the responsible teams, feedback is linked to product tasks, and special labels help track the impact of CAB. A company's specific system may be different, but the signal still needs an owner and a status.

Confidentiality, data, and accessibility

Confidentiality, recording, personal data, and accessibility rules are agreed before invitations and materials are disclosed. The CAB may contain sensitive information from both parties. The team must define permissible purposes of use, access scope, retention period, citation rules, and deletion procedures. The legal form is reviewed by a specialist in the applicable law.

An NDA should not be sent after the first presentation. WIPO recommends formalizing obligations before exchanging confidential information and clearly describing protected information, permitted purposes, access, disclosure, exceptions, and duration. For the advisory board, a two-way logic is needed: clients may also share information about processes, limitations, and plans.

Before the meeting, the lawyer needs to check:

• what is considered confidential information, including oral communications;
• whether audio or video recording is allowed;
• who will receive the recording, transcript, notes, and photos of boards;
• whether anonymized quotes may be used;
• how ideas, feedback, and jointly created materials are regulated;
• how files are labeled and who has access on a need-to-know basis;
• when materials are deleted or returned;
• what information is excluded from confidentiality.

Separately, create a data map: name, position, company, contacts, screening responses, accessibility requests, dietary requirements, image and voice, transcript, quotes, and linkage of the signal to the client account. For each field, the purpose, access, storage location, and deletion period are needed. The ICO principles provide a useful management framework for minimization and storage limitation, but do not replace a review of Russian legislation.

Recording should not be enabled by default just because it is convenient. Sometimes a note-taker and structured cards are sufficient. If recording is needed, the participant must understand the purpose, access scope, and further use in advance. The team separates raw materials from an anonymized internal summary.

Accessibility begins with the invitation. W3C recommends asking about needs in advance, checking the in-person and remote venue, sending materials before the meeting, using microphones, and describing significant visual information. Responses about health and special needs should not be transferred to the general CRM comment.

For an in-person CAB, we check the route from the entrance to the workspace, acoustics, privacy, seating, restroom, and space for an accompanying person. For a hybrid format, an accessible platform, subtitles or interpretation if needed, an alternative connection method, and board work rules are added. A preliminary search can begin in the venue catalog, but privacy, accessibility, and acoustics are confirmed by a site visit.

If the meeting is recorded for internal debriefing, determine the composition of materials in advance. The full recording, individual interviews, and the final video have different purposes and access. If necessary, we engage photo and video production with a clear list of permitted shots and files.

What to do after the meeting?

Follow-up starts with an internal debrief while the context is still fresh. The team separates facts from interpretations, groups signals into themes, and assigns owners and statuses. Then participants receive a brief summary: what was heard, what has been taken into analysis, what is not being promised yet, and when the next checkpoint will be.

First, hold an internal debrief with the core team. The facilitator, note-taker, product owner, customer-facing team and internal stakeholder compare notes. A participant's wording should not immediately be turned into a general conclusion for the entire segment. Note where there is an observation, where there is the team's interpretation, and where there is a hypothesis for further verification.

Then proceed in order:

1. Close access to raw materials according to the approved rules.
2. Consolidate the signal cards and remove duplicates.
3. Separate confirmed problems from solution ideas.
4. Record contradictions between roles and segments.
5. Assign an owner and status to each significant signal.
6. Pass the themes to the product, strategy or service track.
7. Prepare a safe summary for participants without any third-party confidential information.
8. Name the next checkpoint and the channel for clarifications.

Follow-up does not equal a promise to release a feature. Its purpose is to show that the company heard the signal, analysed it and came back with a clear status. Even a negative decision is better than silence if it can be explained without disclosing closed plans.

The CAB works in cycles. The agenda of the next meeting partly builds on previous signals and changes in the customer context. At the same time, the council should not spend years discussing the same list of promises. The charter, membership and working topics should be reviewed periodically, and outdated issues should be closed.

Production checklist and budget

CAB production is calculated based on a single brief: content preparation, work with participants, facilitation, venue or platform, equipment, recording, accessibility, material security, and follow-up. The budget should not hide substantive work within the venue rental. Proposals can only be compared when the scope of tasks and responsibilities is the same.

At Aventura, we build the production framework around the charter and the program. This way the team understands why each element is needed. A separate room for breakout sessions is tied to the method of collecting responses. Microphones are needed for audibility and accessibility. Closed registration supports access rules. The note-taker preserves context for subsequent debriefing.

What to include in the budget

Checklist before invitations

• goal, boundaries, and internal client are approved;
• roles and profiles of participants are described;
• legal counsel has checked confidentiality, recording, and use of materials;
• registration data, access, and retention period are defined;
• method of responding to participants after the meeting is chosen;
• first draft charter is prepared.

Checklist before the meeting

• agenda is linked to decisions and data types;
• participants received rules and materials in advance;
• facilitator and note-taker roles are separated;
• venue, platform, accessibility, and privacy are checked;
• equipment, recording, and backup scenario are agreed;
• team has run through opening, breakout, roadmap question, and closing;
• card and status templates are ready.

Checklist after the meeting

• access to raw materials is restricted;
• facts are separated from interpretations;
• signals are consolidated and assigned owners;
• promised materials are sent;
• participants received a safe summary;
• next checkpoint is named;
• data and recordings are deleted according to the approved deadline.

It is useful to design a customer advisory board right away as a cycle: task, composition, meeting, debrief, decision and response to participants. We can combine a substantive agenda and event production into one work plan. Request a quote for a CAB.

Sources

• Oracle PeopleSoft: Customer Advisory Boards
• Microsoft Learn: Engineering Direct Customer Advisory Board
• SAP: Participation Terms for Advisory Council
• GitLab Handbook: Customer Advisory Board
• Atlassian Team Playbook: Design Labs for User Research
• GOV.UK Service Manual: Researching in small group workshops
• WIPO: Trade Secret Management
• W3C WAI: Making Events Accessible
• ICO: Guide to the data protection principles