Twice a year, we fly eight customers to a nice hotel, feed them well, and spend a day and a half asking for their honest feedback on where the product should go next. This is called a Customer Advisory Board, and it is, in theory, the most democratic thing we do. In practice, we'd like to walk through what actually happens to the feedback once the hotel checks everyone out.
The invite list is not random
The eight customers invited are not a representative sample. They're the eight who are most likely to say something quotable, least likely to say something legally inconvenient, and — this part never appears in the invite email — most likely to renew a big contract within the next two quarters. An advisory board stacked this way isn't gathering customer opinion. It's gathering the opinions of the customers it would be most expensive to lose, which is a different and much smaller population than "our customers."
The feedback session has already been pre-answered
By the time the board sits down to discuss "where should we invest next year," the roadmap for next year has already cleared an internal planning cycle. The session isn't gathering input for a decision. It's gathering reactions to a decision, dressed in the open-ended language of a decision not yet made — "we'd love your thoughts on our direction" — when the direction was finalized six weeks earlier in a document none of the eight people in the room have seen.
When the board says no
This happens more than anyone admits publicly. A feature gets presented, the room pushes back — too complex, solves a problem nobody has, duplicates something a competitor already does better — and the feedback gets captured accurately, in good faith, by whoever's taking notes. Then the feature ships anyway, four months later, because the internal case for it was never really about this room. It was about a competitive pressure, or a single enterprise logo's renewal terms, that the board was never told about and wasn't in the room to weigh in on. The no gets logged. The no does not get honored.
The feedback that does get honored
Whatever the board says that confirms a decision already made internally. If the roadmap already included a particular integration and three board members independently mention wanting it, that becomes "validated by our Customer Advisory Board" in the next internal planning doc — a sentence that is technically true and also reverses the actual causality, since the integration was planned before anyone asked, and the board's enthusiasm is being cited as the reason rather than the coincidence.
The dinner is more honest than the session
The structured feedback session happens in a conference room, with a facilitator, an agenda, and a note-taker, and produces exactly the kind of polished, hedged input you'd expect from customers who know a vendor is listening and might remember who said what. The dinner, three glasses of wine later, produces the real complaint — "honestly your support team took two weeks to answer a P1 ticket last month, that's the actual thing that's going to make us churn" — which is both the most useful thing said all week and the thing least likely to appear in any summary deck, because nobody was taking formal notes at dinner.
What the board is actually for
Not primarily product input, however real some of it is. It's relationship insurance — eight key accounts who now feel heard, who have a direct line to leadership, who are measurably less likely to churn simply because they were flown somewhere and asked a question, regardless of what became of the answer. This is a legitimate function. It's just a different function than "where should the roadmap go," and conflating the two is how a board can be overruled on a real decision while still being reported upward as a resounding success.
What we're not saying
We're not saying advisory boards are theater end to end — real roadmap items do trace back to real sessions, and the relationship value alone can justify the hotel bill. We're saying the sessions that get publicized as "customer-informed decisions" are frequently decisions that were made first and validated second, and the board's actual power to say no is considerably smaller than the warmth of the invitation implies.
Our recommendation
Keep the board. Just be honest internally about what it's actually deciding versus what it's confirming, and when it says no to something that ships anyway, go back and tell them why, specifically, rather than letting the no quietly disappear into a notes doc nobody revisits.
If your last advisory board said no to something that's currently in this quarter's roadmap, email us at contact@b2bsaas.guru. We'll help you plan the next one. We'd also gently suggest inviting whoever said the thing at dinner.