Island Waters Insights
What Belongs in a Startup Board Reporting Package
The board meeting most founders dread is a reporting problem wearing a governance costume: the team reads the deck aloud, the clock runs out, and the two decisions that actually mattered never get made. The fix is the package, and the package is a pre-read, not a presentation. A startup board reporting package is a one-page dashboard of five or six core metrics, the three financial statements against plan, a short cash and runway view, and two or three decisions framed for debate, sent 48 to 72 hours before the meeting so the room can spend its time deciding instead of being briefed.
So the real question is not what to put in the deck, it is where the most expensive meeting on your calendar spends its ninety minutes. Fred Wilson, who has sat on tech boards for two decades, draws the line plainly. "Board meetings should not be operational reporting sessions with information flowing one way."4 A package built to be read aloud forces exactly the one-way meeting he warns against. A package built as a pre-read does the opposite: it clears the reporting out of the room in advance and hands the hour back to the founder for the one thing a board is actually for, helping with the calls that are hard.
The whole package, on one screen
Start with the shape of it, because the pieces only make sense together. If a founder asked me what belongs in a first real board package, in order, this is the list I would hand over, and it does not change much as the company grows. It gets deeper, not different, which is why a stable template you reuse every period beats a fresh build each time.17
- Cover and headline. One line on the state of the company, the period covered, and the two or three things you need help with.
- KPI dashboard. Five or six core metrics against plan and against last period, each with a defined formula that never moves.
- Financials. Income statement, balance sheet and cash flow, actuals against budget, with a short variance note on anything material.
- Cash and runway. Cash on hand, net burn, and months of runway, plus the date you would have to act if nothing changed.
- Functional updates. Short read on product, go to market, and hiring, written as progress against the plan, not activity for its own sake.
- Strategic discussion. Two or three real questions, each with the options you weighed and the call you are leaning toward.
- Housekeeping. Approvals, option grants and prior action items, parked at the end where they belong.
Elad Gil frames the purpose of the whole exercise in a single sentence that is worth taping to your monitor: "board meetings exist to (1) help the company and (2) provide proper corporate governance for all classes of stock."6 Every item on that list serves one of those two jobs. Anything that serves neither is padding, and padding is what turns a ninety minute meeting into a two hour one that decides nothing.
The package is not the meeting, and that is the whole point
The single most common mistake I see is treating the package as the presentation. It is the opposite. The package is what lets you skip the presentation. Mark Suster has a name for the failure mode, the filibuster board, where "the executive team spends 2 hours going through 100 slides and runs out the clock with no discussion."2 You walk out having informed everyone and decided nothing, and you did it with the most expensive room on your calendar. The fix is not a better presentation. It is sending the information early enough that the presentation is unnecessary.
That means cadence and timing are part of the package, not separate from it. Wilson likes eight touch points a year, a mix of formal meetings and shorter update calls,21 and Sequoia describes early board meetings as running four to six times a year at two to three hours each. Whatever rhythm you pick, the deck goes out ahead of it. Suster sends financials seventy two hours in advance and calls each board member beforehand, and Gil recommends the same forty eight to seventy two hour window. Visible, summarizing what a shelf of investors told them, lands in the same place: it comes down to "sharing relevant data and information so your meeting can be a discussion as opposed to an update session."10 The package that arrives the night before is not a package. It is an ambush that fails.
Suster also budgets the meeting itself, and the ratio is the tell. He wants roughly fifteen percent of the time on information and context, seventy percent on debate and decisions, and fifteen percent on admin.11 Your package is what buys you that seventy percent. If the numbers are already read and the context is already absorbed, the room can spend its time on the two or three questions that actually move the company. If the numbers are new to everyone, you spend the whole meeting on the fifteen percent and the seventy percent never happens.
The one page that goes first: five or six numbers, no more
Open the package with a dashboard, not a data dump. Pick the five or six metrics that actually run your business and show each one against plan and against the prior period. The discipline is in what you leave out. Andreessen Horowitz, in the piece every founder should read before their first board meeting, and its companion set of further metrics,12 warns that the danger is not missing numbers but wrong ones: "A common mistake is to use bookings and revenue interchangeably, but they aren't the same thing."3 A board that cannot tell your bookings from your revenue, or your gross churn from your net, cannot help you, and worse, it will start to distrust the rest of the pack.
So define every metric once and never move the definition. For most recurring-revenue startups the core set is some version of recurring revenue and its growth, net revenue retention, gross margin, customer acquisition cost and payback, burn, and runway. Bessemer argues the anchor should be committed monthly recurring revenue, because "CMRR is the single most important metric for a cloud business to monitor."526 Retention is the twin. Bessemer's Good, Better, Best framing has become the shared language of board decks, with net revenue retention of one hundred percent read as good, one hundred ten as better, and one hundred twenty or above as best,13 and its later benchmark reports track where the best cloud companies actually land.14 Put the number next to that scale and the board reads it in three seconds.
Churn deserves its own line because founders consistently underweight it, and the arithmetic is unforgiving. David Skok's rule of thumb is one every board should feel in their stomach: "At 2% monthly churn, you are losing about 22% of your revenue every year."9 That is the difference between a compounding machine and a bucket with a hole in it, and it hides completely if you only show new bookings. Show the gross and net churn, show the cohort behind it, and let the board see whether growth is real or just outrunning the leak. The point of the dashboard is not to look impressive. It is to be honest quickly.
The financials, and the number that flatters you
Behind the dashboard sit the three statements the SEC teaches every investor to read, income statement, balance sheet and cash flow,18 shown as actuals against budget with a short note on anything that moved materially, revenues and cost of revenue presented the way the accounting rules ask.19 The board does not need you to read these line by line, and if your package is doing its job they will have read them already. What they need is the variance story. Why did gross margin move, why did burn spike, what in the plan turned out to be wrong, and what you are doing about it. The statements are the evidence; the variance note is the argument.
Cash is the part that cannot be spun, and it belongs on the front page in plain terms: cash on hand, net burn, and the number of months of runway that implies. Bessemer's line on early companies has not aged a day: "In the early stages, a business lives or dies based on its cash management."5 A board that learns about a cash problem in the meeting where it becomes urgent is a board you have failed to use. Show them the runway clock every time, name the date you would have to act, and describe the ripcord plan you would pull if the plan slips, the kind of capital-efficiency discipline the best benchmark work treats as table stakes.23 That is not admitting weakness. It is the single most useful thing you can give people whose job is to help you survive.
One warning on the financials, because I have cleaned up the aftermath more than once. The blended number is the one that flatters you, and it is the one a diligence team will take apart. A single gross margin that averages a high-margin software line with a low-margin services line tells the board a story that is technically true and practically useless. Break it out. The same goes for blended customer acquisition cost, which quietly lets your organic customers subsidize your paid ones. Give the board the number that is honest rather than the one that is comfortable, because the honest one is the only one they can actually help you improve. Investors say the same thing back to founders: the data has to be relevant, accurate and mastered before a discussion is even worth starting,15 and intellectual honesty about the facts is what improves the odds.16
Narrative versus numbers: the board reads the story, not the spreadsheet
Here is a thing that surprises founders. The best board reporting is often not a slide deck at all. Sequoia, which has seen more first board meetings than almost anyone, says it plainly: "Board decks don't actually have to be decks."7 They point to companies that report to their boards in Amazon-style written memos instead, on the theory that prose forces clearer thinking than bullet points do. Whether you write a deck or a memo, the job is the same: pick the fewest correct charts that frame the real state of the company, and write the sentences that say what the charts mean. The numbers are the evidence. The narrative is what you are actually paid to provide.
This is also where formatting quietly lies, and where a board learns whether to trust you. Andreessen Horowitz calls out the most common offender: "Cumulative charts by definition always go up and to the right for any business that is showing any kind of activity."3 A cumulative signups chart looks like a rocket even when monthly signups are falling off a cliff. A savvy board member spots that in a heartbeat, and once they catch one chart dressed up, they reread the whole pack with a raised eyebrow. Show growth as periodic, label your axes, and never present a percentage without the absolute number underneath it. The credibility you are protecting is not this chart's. It is every chart you will ever show them.
The discussion section that earns the room
If the dashboard and financials are the pre-read, the discussion section is the reason to meet at all. This is where you put the two or three questions that are genuinely keeping you up, and you frame each one for a decision. Suster's structure is the one I use: lay out the issue, give a few real options, and say which one you are leaning toward, so the board can react to a recommendation instead of inventing an agenda.2224 Get this wrong and you get the other failure mode Suster warns about, because "Boards will comment on anything you put in front of them."2 Put a logo redesign in the deck and you will lose thirty minutes to it. Put your pricing model in the deck and you will get the debate you actually needed.
Which is the deeper discipline behind the whole package, and Suster states it as a rule I repeat constantly to my own clients: "Never put information in front of people if you don't want it discussed."1 Every page you include is an invitation to spend time there. So build the package as a set of choices about where the room's attention goes, not as a complete record of everything that happened. The record lives in your systems. The package is a filter, and the filter is the value.
I learned this on the other side of the table. Years ago I ran financial operations as an EVP for a fertility pharmacy that grew from a concept to about fifty million dollars in revenue across roughly forty state permits before it sold to private equity. I owned the reporting the board and eventually the buyers read from, and I learned fast that the pack was not there to defend the past quarter. It was there to tee up the two decisions that quarter actually turned on. When I got that right, the meeting felt like a working session. When I overloaded it, the meeting felt like a deposition, and nobody left with any help.
Investor-grade formatting, and the cautionary tale
Investor-grade does not mean glossy. It means consistent, defined, and trustworthy. Use the same metric definitions every period so the board can compare, keep the format stable so they know where to look, and above all follow the one rule that governs everything else: no surprises. A board can handle bad news that arrives on time. What corrodes trust is good news that turns out to be blended, or a cash problem that shows up already on fire. The package is a promise that the person running the company sees the business clearly, and it is a promise you make in the format as much as the content.
At the far end of getting this wrong sits the cautionary tale, and it is worth holding in mind precisely because it is extreme. When John Ray took over FTX after its collapse, a man who had steered Enron through bankruptcy, he wrote that "Never in my career have I seen such a complete failure of corporate controls."825 The company had essentially no trustworthy financial information to give anyone, let alone a board. Nobody reading this is FTX. But the lesson scales all the way down: a board can only be as good as the reporting it is fed, and a package built to impress rather than to inform is a control failure in miniature. Governance is not a slide at the back of the deck. It is whether the numbers are real.
None of this requires a full-time finance chief, which for most startups runs about two hundred fifty thousand to four hundred fifty thousand dollars or more all-in once bonus, benefits, payroll taxes, equity and recruiting are counted.20 What it requires is someone who owns the definitions, ties the numbers out, and builds the pack as a filter rather than a firehose. Do that, and the board meeting stops being the thing you dread and becomes the ninety minutes a quarter where your best advisers actually earn their seats. That is the whole return on a board reporting package, and it is decided long before anyone walks into the room.
Board reporting your investors can actually act on
We build the pack, own the metric definitions, and tie every number out, so your board meeting becomes a working session instead of a recital. Senior CFO judgment for founders in regulated, capital intensive industries, priced to the scope of the work, not sold by the clock. A full-time finance chief runs about $250,000 to $450,000 or more all-in; we give you that judgment for a fraction of it. If you want a second set of eyes on your next board package, see whether we are a fit at islandwaters.ai/get-started, learn how we work with technology founders, or look at where you would land on pricing.
Launch. Scale. Exit. Beach.
Sources
- Mark Suster, "How to Prepare for a Board Meeting to Make Sure you Crush It," Both Sides of the Table, February 28, 2019. medium.com↩
- Mark Suster, "Managing Your Startup Board (A Short Presentation)," Both Sides of the Table, May 22, 2019. medium.com↩
- Jeff Jordan, Anu Hariharan, Frank Chen and Preethi Kasireddy, "16 Startup Metrics," Andreessen Horowitz, August 21, 2015 (updated September 9, 2024). a16z.com↩
- Fred Wilson, "The Board Of Directors: Board Meetings," AVC, April 2, 2012. avc.com↩
- Byron Deeter, "The five accounting metrics for cloud companies," Bessemer Venture Partners, October 2, 2012. bvp.com↩
- Elad Gil, "The role of the CEO: Managing your board of directors," High Growth Handbook. growth.eladgil.com↩
- Bryan Schreier, "Preparing a Board Deck," Sequoia Capital, accessed September 21, 2026. sequoiacap.com↩
- John J. Ray III, Chapter 11 declaration, quoted in "New FTX CEO details 'complete failure of corporate controls' at crypto platform," NBC News, November 17, 2022. nbcnews.com↩
- David Skok, "SaaS Metrics 2.0 - A Guide to Measuring and Improving what Matters," For Entrepreneurs, January 16, 2013 (updated June 18, 2026). forentrepreneurs.com↩
- Matt Preuss, "What We've Learned From Investors About Running a Board Meeting," Visible.vc, September 11, 2018. visible.vc↩
- Mark Suster, "Why You're Not Getting the Most Out of Your Board," Both Sides of the Table, 2016 (15/70/15 time ratio, reproduced with attribution in the Visible.vc compilation above). bothsidesofthetable.com↩
- Jeff Jordan et al., "16 More Startup Metrics," Andreessen Horowitz, 2015. a16z.com↩
- Bessemer Venture Partners, "State of the Cloud 2023" (Good, Better, Best net revenue retention framework). bvp.com↩
- Bessemer Venture Partners, "The Cloud 100 Benchmarks Report 2025." bvp.com↩
- Jean de la Brochechard, "How To Run Your Board Meetings," Kima Ventures. medium.com↩
- John Vrionis, "Managing Series A Board Meetings," Lightspeed / Unusual Ventures. medium.com↩
- Standard Metrics, "Free Board Deck Templates for Startups," accessed September 21, 2026. standardmetrics.io↩
- U.S. Securities and Exchange Commission, "Beginners' Guide to Financial Statements," SEC.gov. sec.gov↩
- U.S. Securities and Exchange Commission, 17 CFR 210.5-03, "Statements of comprehensive income," Regulation S-X, eCFR, current 2026. ecfr.gov↩
- Robert Half, "Salary Guide" (CFO and finance leadership compensation), 2026. roberthalf.com↩
- Fred Wilson, "The Board Of Directors: Role and Responsibilities," AVC, March 5, 2012. avc.com↩
- Mark Suster, "What Do Boards Actually Do?" Both Sides of the Table. bothsidesofthetable.com↩
- Bessemer Venture Partners, "Scaling to $100 Million," Bessemer Atlas, 2021 (updated 2024). bvp.com↩
- Holloway, "The Holloway Syllabus on Startup Boards," accessed September 21, 2026. holloway.com↩
- "FTX's new CEO: 'Never in my career have I seen such a complete failure,'" CBS News, November 17, 2022 (corroborating the declaration quoted above). cbsnews.com↩
- Byron Deeter and Bessemer Venture Partners, "10 Laws of Cloud Computing," Bessemer Atlas. bvp.com↩