What I Learned Running 50 Meetings

I started using Board of One eight months ago (I'm on the Pro plan) for a specific reason: I was stuck on a pricing decision and didn't want to spend $400 on a consultant to tell me what I probably already knew. That first meeting cost me fifteen minutes and actually changed my mind. So I ran another one. And another.

Fifty meetings later, I've learned things about the product — and about my own decision-making — that I wouldn't have predicted from that first session. Here's what I know now.

The First Ten Meetings Were the Worst

Not because the advice was bad. Because my problem statements were terrible.

My first meeting was about pricing, and I asked something like: "How should I price my B2B SaaS product?" The expert panel gave me a perfectly reasonable overview of value-based pricing, competitor benchmarking, and willingness-to-pay research. Accurate. Useless. I already knew all of that conceptually — what I needed was someone to look at my numbers and tell me whether $29 or $39 was the right call for my situation.

By meeting ten, my problem statements had transformed. I was including specific metrics, naming the options I was considering, and stating my constraints upfront. The advice got dramatically more actionable. Not because the AI got smarter — because I got better at asking.

If you're in your first ten meetings, be patient with yourself. The skill of framing a decision clearly is the skill. The product is just the forcing function.

Context Compounds

Around meeting fifteen, something shifted. I'd been running meetings on related topics — pricing, then positioning, then a feature prioritization that was informed by the pricing decision, then a hiring question that depended on the feature roadmap. Each meeting built on the last.

I started providing business context at the beginning of each meeting: "Here's where the company stands — $28K MRR, 180 customers, 3-person team, targeting SMB project managers." The expert panels began giving advice that fit my actual situation rather than a generic company at my stage.

This is the compound effect. A solo founder who runs a one-off meeting gets decent advice. A solo founder who runs monthly meetings with consistent business context gets advice that accumulates — each recommendation informed by the trajectory of previous decisions.

I think of it like a doctor visit. The first visit, they take your history. The tenth visit, they know your history. The quality of care is fundamentally different.

Meeting Sequences Beat One-Offs

My biggest unlock came when I stopped treating each meeting as independent and started running sequences.

The pattern that works best: Explore, then Decide, then Validate.

Explore: "I'm seeing three possible directions for Q3. Here they are with rough pros and cons. What am I missing? What questions should I be asking?"

The panel pokes holes, surfaces risks I hadn't considered, and sometimes suggests a fourth option. I don't make a decision in this meeting. I collect perspectives.

Decide: A week later, with the exploration insights digested: "Based on the analysis from last week, I've narrowed to two options. Here's my updated thinking and the new data I've gathered. Which option, and what does the implementation plan look like?"

Now the panel is working with richer context. They've already debated the landscape. The advice is sharper because it's building on prior reasoning.

Validate: A month later: "I chose Option A. Here are the results so far. Am I on track? What should I adjust?"

This is where the real learning happens. The panel can compare the prediction to the outcome and help me calibrate my decision-making for next time.

I ran this sequence for a market expansion decision and it was worth more than any single meeting I'd done. The explore phase kept me from committing too early. The decide phase gave me confidence. The validate phase caught a distribution assumption that was wrong and saved me a quarter of wasted effort.

Dissent Is the Feature

Around meeting twenty, I started paying close attention to something I'd initially skimmed past: the dissenting opinions.

In most meetings, the expert panel converges on a recommendation. But there's almost always one expert who disagrees, or at least adds a significant caveat. Early on, I'd read the synthesis, see the recommendation, and move on. The dissent felt like noise.

It's not noise. It's the most valuable part.

Meeting twenty-three was about whether to hire a marketer or a second engineer. Three experts said hire the marketer — the product was good enough, distribution was the bottleneck. One expert — a technical advisor persona — disagreed. The argument: my product's onboarding flow had a 40% drop-off rate, and no amount of marketing would fix a leaky bucket. Pouring more traffic into a broken funnel was the wrong move.

That dissenting view was right. I fixed the onboarding first, then hired the marketer two months later. If I'd gone with the majority recommendation immediately, I'd have burned the marketing budget on users who churned in week one.

Now I read the dissenting opinions first. They're where the non-obvious insight lives.

Constraints Make Advice Actionable

One of my early mistakes was presenting decisions without constraints. "Should I expand to Europe?" is a strategy question with infinite possible answers. "Should I expand to Europe given that I have $15K to spend, no local presence, and need to see revenue impact within 6 months?" is a constrained problem with a finite solution space.

The more constraints I include, the more actionable the advice gets. This feels counterintuitive — shouldn't more constraints limit the panel's thinking? In practice, constraints do the opposite. They force the experts to get creative within realistic boundaries instead of giving you the theoretically optimal answer that you can't actually execute.

A middle manager I know started using Board of One for team decisions and told me the same thing. When she framed problems as "how should I reorganize my team," the advice was generic. When she framed them as "how should I reorganize my 8-person team to absorb a new product line without backfilling the two people who just left, while keeping response times under our SLA," the advice was surgical.

Constraints aren't limitations. They're specifications.

The Prep Chat Changed Everything

Around meeting thirty, I discovered the meeting prep chat — and immediately regretted not using it from meeting one.

Instead of jumping straight to creating a meeting, you start a conversation with the Advisor in prepare mode. You talk through what you're thinking about. As you chat, a readiness panel shows a score — breaking down how clear your problem is, whether you've provided enough context, whether you've defined constraints, and whether the board could actually produce a concrete recommendation.

My first time, I typed what I thought was a pretty good problem statement. The readiness score came back at 35. Missing: budget constraints, timeline, and a clear decision point. Three more messages later, the score was 82, and the extracted problem statement was sharper than anything I'd written on my own.

Now I start every meeting in prep mode. The conversation helps me think through what I'm actually deciding before I commit a meeting credit to it. Half the time, the prep conversation alone clarifies my thinking enough that I realize the meeting I was going to run isn't the one I need. The readiness score is a forcing function — it won't let you convene the board until your thinking is actually board-ready.

If you take one thing from this post: use the prep chat. Your meeting readiness score is the best predictor of whether you'll get generic advice or something genuinely useful.

The Surprise: It Changed How I Think, Not Just What I Decided

This is the thing I didn't expect. Fifty meetings in, the biggest impact isn't any single decision the panel helped me make. It's that I now think in structured tradeoffs automatically.

When I face a decision, I instinctively frame it the way I would for a Board of One meeting: What are the options? What are the constraints? What does success look like? What would the dissenting view be?

I run about half as many meetings as I used to — not because the product is less useful, but because the mental model it trained me on now runs in the background. When I do run a meeting, it's for the genuinely hard problems where I need external perspectives, not for decisions I can now frame and resolve myself.

A growth-stage team I've spoken with had the same experience. Their head of product said the team started pre-structuring decisions in a "Board of One format" before bringing them to the actual human leadership team. The AI advisory board made their human meetings better.

That might be the most honest endorsement I can give: the product is so useful that it eventually makes you need it less for the easy stuff, and makes you use it more deliberately for the hard stuff. That's a tool doing its job.

What I'd Tell Someone Starting Today

Run your first meeting on a decision you've already been agonizing about. Don't pick something trivial as a test — pick something real. The value is most obvious when the stakes are actual.

Then run two more meetings in the next two weeks. Not because three is a magic number, but because you need enough reps to feel the difference between a vague problem statement and a specific one.

After that, try a sequence: explore a big upcoming decision, then come back to decide once you've processed the exploration, then validate after you've acted. That's when the compound effect kicks in.

Fifty meetings later, I can't imagine going back to deciding alone.

---

Learn more: Read our help center guide on building an effective meeting cadence for templates, sequencing strategies, and tips on maintaining business context across meetings.