पाठशाला Pathshala · ग्राहक Grāhak, The customer · Lesson 22 · Build
A customer advisory board that earns its dinner
Most advisory boards are a pleasant evening with friendly customers. Recruit eight who will disagree with you, give each session one decision to make, and write back within a fortnight with what changed.
Pathshala, The Founder Library · 11 October 2026 · 7 min read

A customer advisory board is usually set up after a good quarter, filled with the customers who like the founders most, and quietly abandoned after the third dinner. It was never an advisory board. It was a thank-you.
This lesson sets out how to build one that earns its cost: what it is for, whom to recruit and how, how to run a session around a single decision, how to turn what members say into roadmap changes, what the dinner and the travel mean for tax in India, and when to retire a member or the whole board.
What a customer advisory board is for
A board is not a focus group, a sales event or a feature vote. It is a standing group of customers who represent the segment you want to grow and who meet often enough to see whether their advice worked. Its job is to pressure-test the decisions that are expensive to reverse: which segment to serve next, how to package and price, which large bet goes on the roadmap, what to stop doing.
The limits of group conversation apply to it. Jakob Nielsen’s essay on the use and misuse of focus groups says groups are useful for discovering what users want and for spontaneous reactions, and a poor way to evaluate usability or learn what people actually do. His first rule of usability is blunter: watch what people do, do not believe what they say they do, and do not believe what they predict they will do. A board works when it is given evidence to react to and decisions to argue about, and fails when it is asked which features it would like.
Recruit eight who will tell you the truth
Eight is a number, not a rule, but it holds for a reason: in a two-hour session every member can speak at length on the main question and the founders can still listen. Fewer and one strong personality decides the evening; more and it becomes a conference.
Recruit from usage data, not from the founders’ phone contacts. Each member should use the product seriously, in the top third of activity for their segment; be able to decide, or be one step from the person who does, in their organisation; and come from the segment you want more of, not the one you happen to have most of. Then add disagreement on purpose. Two members should be customers who nearly left in the past year, or who complain often and specifically. Leave out friends, investors’ portfolio companies and anyone whose praise you can predict. In B2B, one person per company, and never two direct competitors at the same table.
In owner-led Indian businesses the person who decides and the person who uses the product every day are often different people, and the board needs to hear both. One approach is to invite the owner as the member and ask them to bring the staff member who runs the product to one session a year, for a working hour on the prototype before dinner. Another is to keep two of the eight seats for daily users from different customers. Either way, run the session in the language the members are most comfortable arguing in, which in Mumbai or Bengaluru may well not be English.
Make the invitation exact: four sessions a year, two hours each plus dinner, twenty minutes of reading before each, a one-year term renewable once. Say what they get: early access to what is coming, a direct line to the founders, and a say in decisions before they are made. Do not pay them in discounts; a member whose price depends on their goodwill will give you goodwill. Agree confidentiality both ways in a short letter, which the [lesson on NDAs](/library/ndas-when-they-are-worth-the-paper) can help you size.
Design each session around one decision
Pick the one decision this quarter turns on and write it as a question with options: “Should we build the GST reconciliation module or the purchase-order module first?” Send a two-page pre-read two weeks ahead with the data behind each option, and wherever possible a prototype members can use before they arrive, so they react to something they tried rather than something they imagine.

A two-hour session might run like this. Fifteen minutes on what changed since the last session because of them. Seventy-five minutes on the decision: members work through the prototype or the data in pairs, then each states a view and the reason, in turn, before any open debate. Thirty minutes round the table on one question asked of every member in every session: what would make you leave us this year? Then dinner, where the most useful sentences of the evening are usually said.
Someone other than the founder should moderate. Nielsen’s essay warns that a moderator must keep one participant’s opinions from dominating while making sure everyone contributes; a founder defending the roadmap cannot do that. The founders listen, ask for examples and write down verbatim quotes. They do not pitch.
Turn sessions into roadmap changes
After each session, log every claim members made against the evidence you have. If three members say the mobile app is unusable on the shop floor, check the usage data and the support tickets before building anything. Members are a source of hypotheses with unusual depth, not a substitute for the [voice of customer system](/library/voice-of-customer-system) that counts what thousands of customers do.
Within two weeks send every member a letter: what you heard, what you decided, what you will not do and why. The refusals matter as much as the changes; a member who sees their view weighed and declined with a reason stays honest. Six to ten weeks later, when the change ships or is dropped, ask the members who argued for it whether it did what they expected. Over a year, count the decisions the board changed. If the answer is none, the board is a dinner.
A board earns its dinner when it changes a decision, and keeps its members when they can see which one.
The rupee side: travel, gifts and tax
Hold sessions in person where members can reach them, in Mumbai, Bengaluru or Delhi NCR for most B2B boards, and pay travel and a hotel night for members from other cities. A video session works between in-person ones, not instead of all of them.
Track what each member receives. Under section 194R of the Income-tax Act, 1961, in force from 1 July 2022, a business that provides a benefit or perquisite arising from business to a resident must deduct tax at 10 per cent of its value once the aggregate given to that person exceeds ₹20,000 in a financial year. Flights, hotel nights, a dinner and a gift across four sessions can cross that line for a business owner on your board. Confirm the current provision, including any renumbering under the Income-tax Act, 2025, and how it applies to your board with your accountant before the first session. Checked October 2026. Separately, ask members from large companies and government bodies what their own gift and hospitality rules allow.
When to retire a member, or the board
Three signals say a member has stopped advising. They miss two sessions in a row. Their contributions have become praise. Or they have become a friend of the founders, which is pleasant and fatal to the job. Thank them, give them a place in a wider beta group and fill the seat from the segment you now want most. Plan to rotate two of the eight every year in any case.
Retire the board itself when it no longer represents the business: when the segment it was built for is no longer where growth comes from, or when two quarters pass without a decision it changed. Starting again with new members is cheaper than keeping a board that agrees with you.
Watch the board’s effect on the rest of the customer base too. Members talk to their peers, and a board that is seen to change the product becomes a reason to stay for customers who never attend. A board that is seen as a dinner for favourites does the opposite. Publish, with members’ permission, a short note to all customers each year on what the board changed.
The quarterly board ritual
Each quarter: four weeks out, choose the decision and write it as a question with options. Two weeks out, send the pre-read and the prototype. Week zero, run the session with a moderator, ask every member what would make them leave, and record verbatim quotes. Two weeks after, send the letter with what changed and what did not. Six to ten weeks after, check the shipped change with the members who argued for it. Once a year, count the decisions the board changed, rotate two members and total what each member received for tax.
Nothing here is legal, tax or investment advice. The section 194R threshold was checked in October 2026; confirm the current rule under the Income-tax Act, 2025 before relying on it.
Sources
- Jakob Nielsen, The Use and Misuse of Focus Groups, Nielsen Norman Group, 1 January 1997 — Good for discovering what users want; poor for usability and for what people actually do; keep one voice from dominating.
- Jakob Nielsen, First Rule of Usability? Don’t Listen to Users, Nielsen Norman Group, 4 August 2001 — Watch what people do; do not believe what they say they do or predict they will do.
- TaxGuru, Section 194R: TDS on benefit or perquisite of a business or profession (Finance Act 2022) — 10% of the value; no deduction if the aggregate to a resident is ₹20,000 or less in the financial year; from 1 July 2022. Checked October 2026.