The Board Meeting

San Francisco · February 5, 2026

The board meeting is at 10 a.m. At 9:47, the CEO is in her office with the door closed, practicing her opening. I know this because I can see her through the glass wall, standing in front of her desk, gesturing at nothing. She does this before every board meeting. She'll deny it if you ask.

I'm in the hallway, holding a coffee I won't drink, waiting to be called in for the growth section. My slides are done. Fourteen of them, which is seven too many, but the board likes data and I like giving people what they want. The problem is that the data, this quarter, tells a story that requires some narrative finesse.

Here's the story: MRR grew 6.2% quarter over quarter, from $2.92 million to $3.1 million. That sounds fine. It is fine, technically. But the plan was 11%, and 6.2 is not 11, and the board knows the plan because they approved it nine months ago.

"How are we going to frame the miss?" the CEO asked me yesterday, and I told her the truth: "We're going to say what happened and what we're doing about it."

She looked at me like I'd suggested we hold the board meeting in clown costumes. "That's refreshingly naive," she said.

There are five people on our board. Two VCs — one from the Series A, one from the Series B. One independent director who used to be the CRO of a public SaaS company. The CEO. And our co-founder, who's been CTO since the beginning and attends board meetings the way some people attend funerals: with a sense of duty and visible discomfort.

The Series A partner, a man I'll call David, is the one everyone watches. He's been on forty-something boards. He speaks in questions that are really statements. He has a habit of leaning back in his chair and looking at the ceiling when he's about to say something that ruins your afternoon.

The CEO opens with the product update. New features shipped, customer feedback, roadmap. This part goes well because the product is genuinely good. The CTO answers technical questions with the precision of someone who has spent twenty years writing code and has no patience for ambiguity.

Then it's my turn.

I walk them through the growth dashboard. New customers: 312 in Q4, versus a target of 410. Net revenue retention: 94%, down from 98% in the prior quarter. CAC payback period: 14 months, up from 11. Gross margin: 71%, holding steady.

"Walk me through the new customer shortfall," David says. He's leaning back.

"Walk me through the new customer shortfall," David says. He's leaning back. This is how it starts.

"Three factors," I say. "First, our primary paid acquisition channel — SEM — saw CPCs increase 23% quarter over quarter due to competitive pressure. Second, our outbound pipeline slowed in December due to holiday timing. Third, and this is the one I want to spend time on, our freemium conversion rate declined from 1.1% to 0.7%."

"Why?" David says.

"A competitor launched a free tier that covers most of our basic functionality. We lost differentiation at the entry level."

The independent director, a woman I'll call Maria, leans forward. "What's your response?"

This is the slide I've been dreading and preparing for in equal measure. I click to a page titled "Q1 Growth Plan: Three Scenarios."

Scenario A: Invest $180,000 in product-led growth improvements — better onboarding, activation campaigns, in-app upgrade prompts. Expected impact: freemium conversion rate back to 1.1% within two quarters. Confidence level: medium.

Scenario B: Kill the free tier (I use the word "sunset"), shift budget to outbound and content marketing. Expected impact: fewer total signups, higher quality, net neutral on new MRR within one quarter. Confidence level: medium-high.

Scenario C: Do both. Rebuild the free tier as a time-limited trial while investing in outbound. Expected impact: short-term MRR dip of 5-8%, recovery in Q3, growth acceleration in Q4. Confidence level: honestly, I don't know.

I said that last part out loud. "Confidence level: honestly, I don't know." The CEO, from the corner of my vision, closes her eyes for exactly one second.

David has questions. David always has questions.

"What does the LTV look like for freemium-converted customers versus direct signups?"

"Twelve-month LTV for freemium converts: $1,890. Direct signups: $3,240. Enterprise inbound: $14,700."

"So your cheapest customers are the ones you're spending the most to acquire."

"That's correct."

"And you've known this for how long?"

This is the question I was hoping he wouldn't ask. "The data has been available for about six months. We started analyzing it seriously about six weeks ago."

He nods slowly. He doesn't say "that's too late." He doesn't have to. Maria writes something on her notepad. The Series B partner, who has been silent until now, asks a question about our competitors' funding and I feel the pressure in the room shift slightly.

The CTO, god bless him, jumps in. "We've already started rebuilding the onboarding. First version ships in three weeks. The data pipeline for activation tracking is live."

This is the thing about board meetings that nobody tells you. They're not about the slides. They're about whether the board trusts that the team sees the problem and has the urgency to fix it. The data matters, but not as much as the energy in the room. Are these people on top of it? Do they know what they don't know? Are they moving fast enough?

Board meetings aren't about the slides. They're about whether the board trusts that the team sees the problem and has the urgency to fix it.

The meeting ends the way board meetings always end: with a list of follow-ups and a vague sense that something important happened but nobody's sure what.

David pulls the CEO aside afterward. I know because she tells me about it three hours later, standing in the kitchen while the rest of the office is in a team all-hands about the product roadmap.

"He wants to see a path to $5 million MRR by year-end," she says.

"That's 61% growth from where we are."

"I know."

"Is that realistic?"

"He doesn't care about realistic. He cares about the narrative for their LP meeting in September."

I think about this for a moment. The gap between what a board wants and what a growth team can deliver is the space where most growth leaders burn out. You can hit the number or you can build sustainably, and sometimes those are the same thing and sometimes they absolutely are not.

"I'll model it out," I say. "But I'm going to need cover on the short-term MRR dip if we go with Scenario C."

"You'll have it," she says. "I'll handle David."

She walks back to her office. I stand in the kitchen for another minute, looking at the San Francisco fog through the window, thinking about the difference between a plan and a promise. A plan is what you do when you have enough information to make a bet. A promise is what you make when someone with power needs to hear a number.

I make plans. The board wants promises. The CEO translates between the two. It's an imperfect system, but it's the system.

Three weeks later, we shipped the new onboarding. Four weeks after that, we killed the free tier. The number on my slide that said "confidence level: honestly, I don't know" turned out to be the most honest thing I said all quarter.

We're still finding out.