Sorenson News
Many software CEOs don’t look forward to board meetings. Not because their business is struggling, but because the meeting itself, in most cases, is structurally broken. The board materials take a lot of time and effort to assemble and arrive late, the board spends the first 90 minutes getting up to speed on the data, function owners take too long covering their respective departments, and the last 30 minutes collapse into a scramble of action items no one follows up on.
But board meetings don’t have to be this way. We’ve built a downloadable template of exactly how to structure a board meeting that creates alignment, surfaces real issues, and gets the board working with you to maximize time spent in the board room.
The Six-Section Framework for an Optimal Board Meeting
Structure the deck and the meeting in this order, every time:
- CEO Priorities: Set the table before diving into data. What matters most right now, what’s stuck, and where does the leadership team needs to be strengthened.
- Financials: A deliberate sequence of six data layers that builds shared understanding across the room with a consistent format.
Product and Engineering: The strategic anchor of the deck. Is the product vision clear, the roadmap deliberate, and the pricing/packaging built for expansion? - Go-To-Market: Two distinct functions – lead generation and lead closing – each with their own metrics, owners, and definitions of success.
- Customer Success: Gross retention is a lagging indicator. Track what precedes it.
- People: The health of the business starts with the health of the team. Headcount gaps, unplanned turnover, and satisfaction scores tell you where the next problem is forming before it surfaces anywhere else.
The sequence is deliberate. You’re building a shared picture of the business – top-down, layer by layer – with each discussion leading to logical conclusions. Don’t skip sections. Don’t reorder them. Consistency and appropriate context is the point.
Section 1: CEO Priorities
Open with the CEO’s top four priorities – not a company overview, not a market update. Four priorities. What’s new, what’s ongoing, what’s been completed, and what’s stuck.
There are two things to include on this slide that most CEOs skip. First, bottlenecks. For each priority, name the specific blocker slowing progress. This immediately focuses the board on where it can help rather than on just the positive spots. Second, a leadership team scorecard. Grade each department – a simple A through D is fine. Which teams are executing? Which ones need support? This isn’t about calling people out. It’s about making sure the board understands where the gaps are before the business feels the impact of them.
What’s not on the CEO’s priority list is just as telling as what is. If the board thinks something is critical and it doesn’t appear here, that tension is worth addressing head-on at the start of the meeting.
Section 2: Financials
Present financial data in six sequential layers. Don’t mix them – they build upon one another and each one provides context for the next.
Layer 1 – Top-line trends
Show monthly ARR as a waterfall: new logo ARR in, expansion ARR in, churn and contraction out, and net movement. Show ending ARR versus budget. Show year-over-year growth rate. Always show at least 24 months of history – a single quarter without context tells you almost nothing.
Layer 2 – New logo and retention
Break ARR growth into its components. How much is coming from new logos versus expansion? What is gross revenue retention – the percentage of existing ARR that renewed without any expansion? What is net revenue retention, accounting for expansion, contraction, and churn? If you had to pick one metric to protect at all costs, gross retention is it.
Layer 3 – System efficiency
CAC payback – all-in, including customer success – is the primary metric here. What does it cost to acquire a customer? And how long does it take to earn that back in gross margin dollars? Pair this with a Rule of 40 calculation. Together, they answer the most important question about any growing software business: are we spending efficiently?
Layer 4 – P&L by department
Show actuals versus budget for sales and marketing, R&D, and G&A separately. The goal isn’t just to track spend – it’s to make sure each category is demonstrating operating leverage over time. If revenue is growing 80% and G&A is growing 80%, something is wrong.
Layer 5 – Cash flow and runway
Show monthly EBITDA and free cash flow. Show cash balance trends and current runway. If runway is tightening, the board needs to see it clearly – not buried in a footnote.
Layer 6 – Share price
Estimate enterprise value based on ARR, growth rate, and a reasonable revenue multiple. Calculate an implied share price. This won’t be precise, and it doesn’t need to be. It simply gives everyone in the room a shared, integrated answer to the question that underlies every other conversation: are we building value?
Section 3: Product and Engineering
Start this section with a product strategy one-pager. Not a roadmap. A single page that shows the core problems the product will solve, the module architecture being built to address them, and the phased plan for getting there. This should anchor every product discussion, board meeting after board meeting. If it shifts dramatically from one quarter to the next without explanation, that’s a flag worth addressing.
Then introduce pricing and packaging – current state on one page, future state on the next. The question to answer is “Does the current product structure facilitate module-based upsells in a natural way?” If not, that’s a net revenue retention problem waiting to happen.
On the engineering side, two core metrics tell you whether the organization is healthy and producing.
The first is how engineering time is allocated across three categories: bug fixes, sustaining work (improvements to existing features), and new module development. The right balance will vary by stage and strategy, but the direction of travel matters. If bug fixes consume a growing share of engineering capacity, product velocity slows and technical debt compounds. If new module development is crowding out sustaining work, existing customers start to feel neglected. Showing this split as a simple stacked bar over time makes the trend immediately visible.
The second metric is the ratio of individual contributors to managers. If that ratio is skewing toward managers over time, the organization is accumulating overhead faster than output and needs to be rebalanced to ensure the organization is operating efficiently.
Section 4: Go-to-Market
Split this into two distinct parts: lead generation and lead closing. They have different owners, different metrics, and different definitions of success.
Lead Generation
The single most important discipline here is working backward from revenue targets to activity requirements.
Here’s the math every GTM leader should know: if the average sales cycle is 45 days, the average contract value is $X, and the close rate is Y%, then hitting the quarterly ARR target requires Z stage-one opportunities created every week. That number should be on the slide as a horizontal line – the definition of success – alongside actual weekly performance. If the team is consistently below that line, you will miss the new ARR number within a few months. Move quickly to get lead-gen fixed in a few days so that future new ARR is not impacted.
We always encourage GTM executives to track pipeline in two ways: first, as a balance sheet (the current dollar value of open opportunities by stage), and second, as an income statement (how much new pipeline was created this week or month). The balance sheet without the income statement is dangerously incomplete. A pipeline full of stale opportunities will lie to you every time.
Lead Closing
Once you have a good sense of your lead generation, focus on lead closing across four key metrics:
- Quota capacity – the total quota assigned across all AEs, including ramping reps at partial quota. If quota capacity is below your ARR target, you already know the quarter is at risk before it starts.
- Attainment distribution – a dot chart with one dot per rep, showing each rep’s attainment against quota. Run an average line across the team. If average attainment is below 70%, you have either a lead gen problem, a training problem, or a quota-setting problem. The distribution will tell you which.
- OTE return – same dot chart format, one dot per rep, showing new ARR generated divided by OTE. Target is roughly 3x at 80% gross margin (build in a buffer). Below 2.5x consistently is a capital efficiency problem that will show up in CAC payback, just as it will show up in the ARR line.
- Ramp time and success rate – across your last 10 to 15 hires, what’s the average time to first deal, time to 50% of quota, and time to full quota? What percentage of hires made it? These two numbers are the inputs to every capacity planning decision you’ll make for the next 12 months. If you don’t know them, you’re guessing on headcount.
Section 5: Customer Success
Gross retention is the metric that matters most in customer success, but it’s a lagging indicator. By the time gross retention moves, the damage is done. Build the section around the leading indicators instead. These include:
Implementation lag – show the ARR that has been contracted but not yet fully implemented, and the average days to value realization. A growing pile of unimplemented ARR is a churn risk that doesn’t show up anywhere else in the deck.
Usage by module – not just which modules customers have purchased, but which ones they’re actively receiving value from. A customer with low ROI on a core module is a renewal risk regardless of what their NPS score says.
At-risk ARR – aggregate all yellow and red accounts into a single ARR figure. Show it trending over time. If at-risk ARR is growing faster than total ARR, that’s the conversation to have quickly.
Upcoming renewals – list the significant pending renewals by name. Discuss the likelihood and dynamics of each renewal. Use the board to help build support within the client base wherever possible.
Section 6: People
Close here every time.
Start with headcount by department: a simple table showing current headcount versus plan. Don’t just show the gap; name the reason for it. A department that’s significantly under plan because of a failed search is a different problem than one that’s under plan because hiring was intentionally paused.
Turnover deserves more attention than most board decks give it. Separate planned turnover from unplanned, and show both trending over time. A spike in unplanned departures in a particular department is almost always a management or culture signal – and it compounds quickly if it isn’t addressed. By the time it shows up in productivity metrics, you’ve already lost ground that’s hard to recover.
Satisfaction scores by department – eNPS or an equivalent measure – round out the picture. The aggregate company score is useful, but the department-level breakdown is where the real signal lives. Which teams are energized and executing? Which ones are quietly disengaged? The gap between those two answers is often where your next retention problem is hiding.
Finally, show open roles alongside average time-to-fill. If a VP-level seat has been open for four months, that’s not a recruiting update – that’s a priority for board network activation. Name it explicitly, state what you’ve tried, and ask for help. The board’s collective network is one of the most underutilized resources a CEO has access to, and the people section is where that resource should get put to work.
The Underlying Principle
Every section of this framework answers the same question from a different angle: do we understand our business well enough to make the right decisions at the right time?
Board meetings aren’t just a reporting exercise. They’re the highest-leverage operating rhythm a software CEO has access to. When the deck is consistent, the data is deliberate, and the board arrives prepared, the conversation shifts from catching up to moving forward.
That shift, compounded across years of consistent board meetings, is one of the clearest separators between companies that scale predictably and companies that don’t.
Reach out to us or anyone at Sorenson Capital if you’d like to talk through how this framework applies to your business.
Download Article
