Most founders build their customer advisory board after they have a product to show. They wait until there's something tangible, figuring that's when it becomes worthwhile to ask for people's time. This gets the sequence exactly backwards.
The customer advisory board's most valuable job is shaping the product before it's built — not validating a product that already exists. The feedback you get from five industry peers in month two costs you one Zoom call per month. The feedback you would have gotten, but didn't collect because you were waiting until you had something to demo, costs you in misdirected development and features that miss the actual workflow.
Operator founders have a structural advantage here that most founder advice ignores. You don't need to find a customer advisory board — you already know who belongs on it. The question is whether you're going to formalize those relationships before you start building or after.
Who belongs on a pre-product customer advisory board
The right CAB members are not your most enthusiastic supporters. They're the most operationally sophisticated people in your target market who are close enough to the problem to give you real feedback — and trusted enough in their networks to eventually introduce you to your first paying customers.
For a typical vertical SaaS company, five to eight people is the right size. You want some variation: different company sizes within your target segment, different geographies if the industry has regional variation, and at least one person who has tried and rejected the alternatives you're going to compete with. That last profile is the most useful — they've already done your competitive analysis and can tell you exactly where the alternatives fall short.
What you don't want: people who will be nice to you because you have a relationship with them. The most dangerous CAB member is the one who agrees with everything you say because they don't want to hurt your feelings. You need the person who ran the workflow for ten years and has strong opinions about what doesn't work. That person will tell you things your best friend won't.
The ask: how to recruit CAB members before you have a product
The instinct is to pitch the product — but you don't have one yet, and fabricating one sends the wrong signal. The honest ask is more effective anyway.
"I'm building software for [your industry] and I'm in the early stages of figuring out what to build first. You're one of the people I trust most to tell me what's actually broken and what actually matters. I'd like to spend 30 minutes a month getting your honest read on what I'm working on — in exchange, you'll have early access and a real say in what gets built."
That's the ask. It works because it's true, it's specific, and it respects the person's expertise without overpromising. Operators who've watched their industry tolerate bad software for years are often genuinely interested in helping build the right solution — if they trust the person doing the building. You're the person they trust.
What to do in the first 90 days
The first three months are about listening, not pitching. Your CAB conversations should follow a consistent format: what's broken this month, what have you tried, what did you wish existed. You're building a map of the real workflow — not the idealized version, but the actual one, with all its workarounds and failure modes.
At the 60-day mark, bring something to react to: a workflow diagram, a rough wireframe, a plain-English description of what you're thinking of building first. Not a polished demo — a sketch that they can push back on. The goal is to hear "that's not right, here's what's actually happening" as many times as possible before you've committed development time to the wrong thing.
At 90 days, you should have a strong signal about which part of the workflow to address first, which segment of the market is most ready to adopt, and what the first version of the product needs to do to be worth paying for. That's the foundation of your MVP scope — not a user story document written by a product manager who's never run the business, but a problem statement written in the words of the people who have.
How the CAB transitions when you have a product
Once you have something in market, the CAB's role shifts from problem validation to product accountability. They become the people who tell you when a feature is solving the wrong problem, when the UX is creating new friction, and when a competitor has shipped something that's going to matter to buyers.
Some CAB members will convert to early customers. Some will stay as advisors who aren't paying customers but are actively referring customers they know. Some will fade out as their priorities change. All of that is fine — the cadence changes as the company matures. What doesn't change is the value of having a small number of industry insiders who are invested in your success and willing to tell you the truth.
Operators who have been in their verticals for a decade tend to underestimate how many people in their network would say yes to this kind of relationship. You've built trust over years by being good at your job. That trust is transferable. You don't have to earn it again — you just have to ask for it.
If you're at the stage where you're building your first customer relationships and want to think through the structure, pitch us the idea. The CAB conversation is often the most valuable one we have with founders in the earliest stages.