Add Startup board finance materials: the questions to answer early

2026-10-21 01:39:33 +00:00
commit e278836b23
@@ -0,0 +1,174 @@
<br>Startup board finance materials exist to answer a small set of questions before a board meeting turns into a debate about direction. The condition is simple: the pack has to show what happened, what it cost, and what the next quarter needs. Without that, every other discussion stalls.<br>
<br>Boards rarely argue with a number they can trace. They argue with a number they cannot place, and a founder who has to reconstruct the story mid-meeting loses the room. The materials should carry the story so the founder does not have to.<br>
What startup board finance materials have to answer before anyone debates strategy
<br>A board pack answers three things: what the business earned and spent, what it expects over the next few quarters, and what it needs from the board. Everything else in the document supports those three. When a pack leaves one of them out, the meeting fills the gap with opinion, and [cfo services](https://Venturegrowthpartners.com/) opinion is harder to resolve than a number.<br>
<br>The gap between plan and actual comes first. A board wants to know whether the company hit what it said it would hit, and if not, which line moved. Revenue below plan with costs on plan is a different conversation from revenue on plan with costs above it. Materials that show only totals force the board to guess which one happened.<br>
<br>Cash comes second, and it outranks profit in most early-stage rooms. Profit is an accounting result. Cash is what pays salaries next month. A pack that leads with net loss and buries the bank balance invites a question the founder did not prepare for, so put the cash position and the runway on the first page where nobody has to hunt for them.<br>
<br>The ask comes third. Boards approve things: cfo services a budget, a hiring plan, a financing decision. If the pack has no clear ask, the meeting drifts into commentary. Even "no decision is needed this quarter" counts as an ask, because it tells the board what you want from them.<br>
<br>A short checklist covers most of what a board expects to see, and the list rarely grows much from one company to the next.<br>
Cash on hand, runway in months, and the assumption behind the runway
Revenue against plan, split the way the board already tracks it
Gross margin and the one or two costs that moved it
Headcount against plan, including open roles and start dates
The ask, stated once, in one sentence
<br>None of this requires a large finance team. It requires deciding in advance which questions the board will ask and answering them before they are asked. The rest of the pack is supporting material, and supporting material can be short. What cannot be short is the answer to why the numbers look the way they do.<br>
The questions a board asks about revenue and margin
<br>Revenue questions start with the split, not the total. A board wants to know which product line, region or customer group moved. One revenue number hides whether growth came from new customers or from an existing account ordering more, and those two stories lead to different decisions about the next quarter.<br>
<br>Margin questions arrive right after. Gross margin tells the board whether growth is getting cheaper or more expensive to produce. If the company added customers and margin fell, someone will ask which costs scaled with them. Materials that separate cost of delivery from operating costs answer that in one line instead of five minutes of discussion.<br>
<br>Then come efficiency questions, and these change with stage. An early board may ask how much cash each new dollar of recurring revenue consumed. A later board may compare this quarter's spending with the same quarter a year earlier. The question underneath is the same in both cases: is the company getting better or worse at turning money into growth?<br>
<br>A table helps when several audiences read the same numbers, because board members, prospective investors and lenders look at the same revenue line and want different supporting detail attached to it.<br>
AudienceChecks firstNeeds attached
BoardVariance to planCommentary on causes and next steps
Prospective investorGrowth rate and margin trendCohort detail and contract terms
LenderCash flow and coverageCollateral, covenants, payment history
<br>Contract terms shape how revenue appears. Under ASC 606, revenue is recognized as performance obligations are met, so a large annual contract may spread across months rather than land in the month it was signed. That is a standard rather than a preference, and it matters when a board compares a bookings figure with a revenue figure and finds that they do not match.<br>
<br>Where this breaks down is a company with irregular, project-based revenue. Monthly comparisons say less in that business than a rolling quarter, and a pack that insists on a rigid monthly rhythm can make a normal quarter look like a swing it is not. Match the reporting period to the way the business actually earns.<br>
Building a monthly reporting pack that survives follow-up questions
<br>A monthly pack that survives follow-up questions is built backwards from those questions. Instead of starting with the statements, start with the five or six things a board member would ask if they had two minutes, and make each of them visible on the first page without anyone turning a page.<br>
<br>The first page carries the summary: cash, revenue, gross margin, headcount and the runway assumption. One line each, with the plan number beside the actual. If a metric is off plan beyond the tolerance the company set for itself, a short comment explains why and what changes as a result. Tolerance matters, because a pack that comments on every small movement trains the board to ignore the comments.<br>
<br>Commentary is where most packs fail. A line that says "revenue below plan" restates the table directly above it. A useful line says which deals slipped, whether they closed later or fell out, and what that does to the quarter. Write commentary as cause and effect, not as a label attached to a number.<br>
<br>Consistency matters more than polish. If the pack splits revenue by product in January, it should split it the same way in July, even when the product list changes underneath. Boards notice when a category quietly disappears, and the first question will be about the category rather than about the quarter.<br>
<br>A short checklist keeps the pack honest from month to month.<br>
Same definitions for every metric, every month
Actual, plan and variance in the same row
A written reason for each variance beyond tolerance
A one-line status on every commitment made at the last meeting
A note on anything that changed in how a number is calculated
<br>Timing decides whether the pack is management or history. A document delivered three weeks after month end describes a period the company has already moved past. Decide which numbers must be final for the meeting and which can arrive two days later, then hold that line rather than waiting for a complete set.<br>
Cash forecasting questions the model has to answer
<br>A cash forecast answers one question above all: how many months until the balance reaches the point where the company has to act. Everything else in the model exists to make that answer trustworthy, and every assumption that touches it deserves a second look before the board sees it.<br>
<br>The first thing a board tests is the assumption behind collections. If customers pay later than the invoice terms suggest, a model built on the terms will show a comfortable runway that does not exist. Use the observed collection pattern, calculated from what actually landed in the bank, and say so on the page.<br>
<br>The second is the timing of the largest outflows. Payroll, annual software renewals, insurance and tax payments land in specific months and can move a forecast more than a change in revenue. A model that spreads those costs evenly across the year hides the month that decides whether the company is comfortable or tight.<br>
<br>Third, structure the scenarios. A board usually wants three versions: the plan, a slower case and a faster case. The value is not the number at the end of each case. It is which cost the company would cut first in the slower one. If no cutting is described, the scenario is arithmetic rather than a plan.<br>
<br>A checklist of questions the model should be able to answer on demand:<br>
What does the runway look like if collections slip by two weeks?
Which hires are committed and which are still optional?
What is the largest single outflow in the next six months?
What has to happen to reach the next milestone without new money?
<br>Working capital sits behind all of it. Growing revenue consumes cash when customers pay late and the company pays contractors or suppliers early. A forecast that shows revenue rising and cash rising at the same rate deserves a check, because the two usually move apart during a growth push.<br>
<br>A forecast is a range, not a promise. Some businesses with long sales cycles cannot forecast monthly with any confidence, and a quarterly view with an honest note about uncertainty serves a board better than false precision dressed up as a monthly number.<br>
Investor reporting and board reporting cover different ground
<br>Investor reporting and board reporting draw on the same ledger but answer different needs. An investor update describes progress against the thesis someone invested in. A board pack supports decisions the directors are accountable for. Treating one as a copy of the other leaves both short.<br>
<br>An investor update tends to be shorter and more narrative: what changed, what is working, what help is needed. Investors outside the board do not vote on the budget and do not carry the same duties. They want to know whether the company is on the path they funded and whether anything has changed about the risks they accepted.<br>
<br>A board pack carries what a director has to stand behind. That includes the budget, the cash position, compliance matters and compensation decisions. Directors hold duties, so the materials need enough detail to support a decision they may be asked to defend later. A summary that reads well but supports nothing is not enough for that audience.<br>
<br>The two documents differ in predictable ways.<br>
ElementInvestor updateBoard pack
FrequencyMonthly or [Cfo services](https://Venturegrowthpartners.com/) quarterlySet by the board calendar
DepthHeadline numbers with narrativeVariance detail and supporting schedules
Decision contentNone, though input is welcomeApprovals and formal resolutions
DistributionBroader investor listDirectors and named attendees only
<br>One practical rule: build the board pack first, then write the investor update from it. The update becomes a selection from material that has already been checked, which keeps the two versions from drifting apart in ways someone will eventually notice.<br>
<br>Confidentiality shapes what goes where. Board materials may contain detail that should not reach every investor, such as individual compensation, litigation, or a financing discussion at an early stage. Decide what is board-only before the pack is distributed, not after someone forwards it.<br>
<br>The limit here is that a small company with a single investor and no formal board may not need two documents at all. One well-built pack, distributed with the right notes, can serve both purposes until the cap table and the board grow enough to require a split.<br>
Keeping the data room honest before diligence begins
<br>A data room is only useful if it matches the numbers in the board pack. Diligence teams compare documents across years, and the fastest way to lose time is to hand over a schedule that disagrees with the management accounts they already received. Every mismatch costs an explanation, and enough of them cost credibility.<br>
<br>Assemble the core documents early, before anyone asks.<br>
Financial statements for the periods a buyer will request, tied back to the management accounts
The monthly reporting pack and any board minutes that reference it
Customer agreements, renewals and any unusual terms that affect revenue
Debt and lease agreements, including covenants and security
Equity records: cap table, option grants and the documents behind them
Payroll records, tax filings and correspondence with a taxing authority
<br>Reconciliation is where diligence slows down. Revenue recognition choices, deferred revenue balances and any adjustments made during the year all need a clear trail. A buyer will rebuild revenue from contracts and compare the result with what the statements show. If the two do not meet, the gap will be treated as a problem until it is explained.<br>
<br>The story the numbers support matters as much as the numbers. A schedule that presents a picture the underlying records cannot back up creates work during diligence and a harder negotiation afterward. It is better to disclose a weak spot with context than to have it discovered in a document request.<br>
<br>Preparation is not the same as selling. The materials should let a question be answered, not steer the answer. A data room that omits an unfavorable contract invites the assumption that there are more of them, which is a worse position than documenting the one.<br>
<br>Some businesses need a longer runway before diligence than others. A company with clean monthly closes, consistent revenue recognition and organized contracts can open a room quickly. One that has been running on spreadsheets and a shoebox of receipts needs months to reach the same starting line, and that timeline should shape when a process begins.<br>
Where outsourced accounting and internal controls fit
<br>Outsourced accounting changes who prepares the numbers, not what a board asks of them. The pack still has to arrive on time and agree with the bank. What changes is where the work sits and how quickly an unusual question can be answered when it comes up in a meeting.<br>
<br>The split that tends to work: the internal team owns the business context, because people close to sales understand why a deal shifted, and an outside bookkeeping team owns the ledger, the reconciliations and the monthly close. Someone still has to own the review, and that role should be named rather than left to whoever notices first.<br>
<br>Internal controls matter even when the finance team is one person and a contractor. Separation of duties is not always possible in a small company, but visibility is. Approval limits, a second review of the bank reconciliation and a clear rule about who can add a vendor all reduce the chance that an error goes unnoticed for a quarter.<br>
<br>Decide what stays in-house. Forecast assumptions depend on sales knowledge and hiring plans, so they usually belong to the internal team, even when an outside group builds the model. Transaction processing, reconciliation and preparation of the standard pack are easier to hand over, because the rules are stable and the output is checkable.<br>
<br>Keep the documentation current. When the person who ran the close leaves, undocumented steps leave with them. A short written calendar, a list of the accounts that need judgment, and a note on where each source file lives make a transition boring instead of disruptive.<br>
<br>Outsourcing does not fix a weak process. If invoices reach the accounting inbox weeks after the work is done, the close stays late no matter who performs it. The constraint is usually upstream of finance, and moving the work without addressing that constraint only relocates the delay.<br>
A worked example: board materials for a company weighing a raise
<br>Consider a hypothetical software company with recurring revenue, a dozen employees and a board meeting three weeks before the first investor conversation. The figures below are illustrative for one imaginary case, not benchmarks, and the sequence is what matters rather than the amounts.<br>
<br>In this example, collections had been landing later than the invoice terms suggested, while the forecast assumed payment close to the terms. The first page of the pack put the two runways side by side: the one under the observed collection pattern and the one under the plan assumption. That single comparison set the agenda, because it changed how many months the company had before a raise became urgent rather than optional.<br>
<br>The materials assembled for that meeting would include three years of statements tied back to the ledger, a revenue schedule organized by contract with the recognition treatment noted, a hiring plan split into committed and optional roles, and a customer concentration table showing how much of the revenue came from the largest accounts. Each of those items answers a question the board or a later diligence team would ask.<br>
<br>What the company in this example would leave out is projections built on conversations that never advanced past a first call. Including them invites a question the founder cannot answer in the room, and a pipeline number that gets discounted once is discounted every time afterward. Keep the base case to what the records support and label everything else as a scenario.<br>
<br>Then run the check a careful director would run: in the slower case, does the runway still reach the next milestone, and if not, what would change first? Cutting marketing, delaying two optional hires or renegotiating a payment schedule each move the answer. The value of the exercise is naming those levers before the board asks, so the slower case arrives as a plan rather than a surprise.<br>
<br>The same structure holds when the event is a sale rather than a raise, though the audience changes and the data room carries more weight than the pack. Preparation does not promise an outcome, and it does not remove the questions. It moves them earlier, when there is still time to answer them with evidence instead of recollection.<br>