Cela supprimera la page "Financial model review checklist for founders: cash first". Soyez-en sûr.
A financial model review checklist for founders is a short list of questions you answer before anyone else sees your numbers: where the cash actually is, what drives it, and which assumptions would embarrass you in a room with a buyer. Cash comes first because every other line in the model eventually turns into cash or fails to. It matters most when a sale, a financing round, or a budget cycle is close enough that weak assumptions have a price.
Start with cash, not the income statement
Cash is the first thing to review because it is the last thing a model can hide. Revenue can be recognized, margins can be adjusted, but a bank balance either covers payroll next month or it does not. When I review a model, I start at the cash line and work backward, and I would encourage any founder to do the same before a buyer or lender does it for you.
Open the model and find the ending cash balance for each month of the forecast. Then ask one question per month: what has to happen for that number to be true? If the answer involves collecting from customers faster than you ever have, or a supplier extending terms you have not negotiated yet, the model is describing hope, not operations. That distinction is exactly what a reviewer is looking for.
The income statement can wait because it is built on matching and accruals, which are easy to get subtly wrong. A sale booked in the model in March might not produce cash until June, and if your cash forecast assumes March, the gap shows up as a shortfall you did not plan for. Reviewing profit first tends to create optimism; reviewing cash first tends to create accuracy.
There is a practical order to this part of the review:
Monthly ending cash for the full forecast period, with no negative months unexplained. The gap between revenue recognized and cash collected, month by month. Debt service and fixed obligations, placed in the months they actually clear the bank. The minimum cash cushion the model assumes, and whether it survives one bad month.
Look at both sides here. A cash-first review is not an argument that profit does not matter; it is an argument about sequence. Profit tells you whether the business works over time, and cash tells you whether it survives long enough to get there. A founder who can explain both, and show where they diverge in the forecast, is prepared for the harder questions that come later in any negotiation.
Trace every assumption to a source you can defend
Every model is a stack of assumptions wearing the costume of arithmetic. The review is where you find out which assumptions you can defend out loud, to a skeptical person, without notes. A buyer's analyst will not ask what the growth rate is; they will ask why it is that number and not a lower one.
Pick the three assumptions with the largest effect on ending cash. Usually these are revenue growth, customer churn or retention, and the collection period. For each one, write down where it came from. If the source is your own history, note the period it covers and whether that period was typical. If the source is a plan, say so plainly: "we assume two new accounts per quarter because that is the hiring plan," is defensible; "we assume strong momentum," is not.
Then stress the assumption in the direction that hurts. If collections slip by two weeks, which month goes negative first? If the new accounts arrive one quarter late, does the cushion survive? You are not trying to make the model pessimistic; you are trying to know, before someone else tells you, where the model is fragile. A founder who has already found the weak spot negotiates differently than one who is discovering it in real time.
Watch for assumptions that quietly agree with each other. Growth that assumes new hires, hires that assume revenue, and revenue that assumes growth form a loop that looks solid on a spreadsheet and collapses under one question. Break the loop by anchoring at least one of the three to something outside the model: a signed contract, a hiring budget already approved, a pipeline with dates.
One habit worth borrowing from formal reporting: when in doubt about revenue timing, look at how ASC 606 treats performance obligations, because the logic of "when have you actually earned it" is a good discipline even for a private company forecast. You are not filing with the SEC, but a buyer's accountants will read your model with that lens, and matching yours to theirs removes an easy line of attack.
Reconcile the model to books that a stranger could follow
A forecast that does not tie to the general ledger is a story, and reviewers can tell. The reconciliation step is unglamorous and it is where most models fail a first review: the historical baseline in the model does not match the financial statements, and nobody can say which one is right. Fix this before anything else, because every downstream number inherits the error.
Start with three ties: the last full month in the model should match the balance sheet from the books; the revenue and expense totals for the historical period should match the income statement; and the cash balance should match the bank. When these do not agree, the usual causes are timing differences, entries booked after the model was built, or revenue recognized differently in each place. Document which explanation applies, because "we will fix it later" is the sentence that ends a diligence process early.
Bookkeeping quality shows up here more than anywhere else. If the books have unreconciled accounts, miscategorized expenses, or revenue sitting in undeposited funds, the model built on top of them inherits all of it. This is one place where strategic finance and record-keeping connect directly: the quality of the forecast is capped by the quality of the records underneath it. A fractional finance arrangement that includes bookkeeping oversight can close this gap, but the review itself is something a founder can do with the books in front of them.
Continuity matters too. If the model was built by a person who has since left, or updated by several people with different habits, check that the structure is consistent: same chart of accounts, same treatment of one-time items, same definition of revenue. A reviewer who finds three definitions of "revenue" in one workbook stops trusting the rest of it, and rebuilding trust costs more time than the reconciliation would have.
The test I would use is simple: could a competent stranger pick up the model and the books and trace any number in the forecast back to a source within a few minutes? If yes, the model is reviewable. If no, the model is not ready for a buyer, a lender, or even a serious board conversation, regardless of how attractive the outputs look.
Test working capital the way a buyer will
Working capital is where purchase price adjustments live, and founders often meet the concept for the first time after the letter of intent is signed. The review checklist should treat it as a first-class item, not an accounting footnote, because in a sale the buyer will typically propose a target based on your history and adjust the price against it at closing.
Walk the cash conversion cycle in the model: how many days inventory sits before it sells, how many days receivables sit before they collect, and how many days payables sit before you pay. Multiply those against the forecast volumes and see whether the model funds the working capital the growth requires. A growing business with tight terms can be profitable every month and still run out of cash, which is the single most common surprise in founder-built models.
Then look at the seasonality. If your business collects heavily in some months and pays evenly in all of them, the annual working capital average hides the months that hurt. A buyer modeling your business will see the monthly pattern, and if your model smooths it, the discrepancy reads as either error or flattery. Neither helps you in negotiation.
A few questions that surface most working capital problems:
Does the model hold inventory or prepaid expenses that grow with revenue, or does it assume they stay flat? Are receivables modeled with the actual collection pattern, or a single average? Do payables stretch when cash gets tight, in a way you have not negotiated with suppliers? Is there debt or deferred revenue whose treatment changes at a change of control?
Look at both sides of the working capital question. Lean working capital is efficient and it flatters cash flow, but it can also mean you have been under-investing in inventory or squeezing suppliers in ways that will reverse under new ownership, and buyers price that reversal in. Heavy working capital is safer operationally but ties up cash that a buyer has to fund. The review is not about picking a winner; it is about knowing which side you are on and being able to explain why.
Separate the operating forecast from the deal math
Founders often blend two models into one workbook: the operating forecast that runs the business, and the transaction math that prices it. Keep them separate. The operating forecast should stand on its own, built to be useful whether or not a sale happens, because a model that only makes sense inside a deal is a model you cannot defend on its merits.
The deal layer, when it exists, answers different questions: what EBITDA or revenue base the price references, what normalizations apply, and what the pro forma looks like after adjustments. Normalizations are where founders get tripped up. Adding back your own salary above market, one-time legal costs, or personal expenses run through the business is standard practice, but each add-back needs documentation, and the aggressive ones are the first thing a buyer challenges. A normalization you cannot paper is a price reduction waiting to happen.
The operating forecast deserves its own scrutiny regardless. Check that the budget inside it reflects decisions actually made, that the headcount plan matches the hiring plan, and that capital expenditures appear in the years they will be paid for, not smoothed for presentation. This is ordinary financial planning and analysis work, and it is worth doing even if no transaction ever materializes, which is the honest framing: most exploratory sale processes do not end in a closing, and the model should be useful in all of those outcomes.
When the deal layer does exist, watch the capital structure assumptions. If the model assumes refinancing at terms you have not quoted, or an earnout you have not stress-tested, mark those clearly as assumptions rather than facts. Buyers and lenders will run their own versions, and the founder who knows which parts of the model are load-bearing survives the comparison.
The practical rule: the operating forecast is the business telling the truth about itself, and the deal math is an argument about what that truth is worth. When they share cells and tabs, a challenge to the argument looks like a challenge to the business, and the founder ends up defending both at once. Separated, each can be discussed on its own terms.
Prepare the model for someone else's accountant
A model under review will be examined by people whose job is to find problems, and the review should simulate that before it happens. Internal controls sound like big-company language, but at the level of a founder's checklist it means something plain: the numbers in the model come from a process, the process leaves a trail, and the trail can be followed by someone who was not there.
Check who can change what. If anyone with the file can edit the historical actuals, the model has no fixed baseline, and a version that drifts silently is worse than one that is wrong in a known way. Keep actuals locked, keep assumptions in a visible tab rather than buried in formulas, and keep a version history so you can say what changed and when. These are habits, not software purchases.
If an audit or a quality-of-earnings review is likely, the preparation overlaps heavily with this checklist. Reviewers will compare the model to the books, test the revenue recognition logic, and sample the assumptions against evidence. FASB guidance and standard audit practice shape what they expect to find; a founder does not need to master the technical standards, but knowing that the review will be evidence-based changes what a defensible assumption looks like. "We believe" loses to "here is the file" every time.
Documentation can be light and still sufficient:
A one-page map of the model: tabs, what each does, where inputs live. A source note on each major assumption, even just a sentence. The date of the last reconciliation to the books. A change log for anything edited after the baseline was set.
None of this guarantees a smooth diligence process, and it should not be presented as if it does. What it does is remove the failures that come from disorder rather than substance, which are the cheapest failures to prevent and the most embarrassing to explain. A buyer can accept a business with real risks; disorder makes them unable to tell which risks are real.
When a review like this is worth the time, and when it is not
The checklist earns its cost in specific situations: a sale process you are seriously considering, a financing round with a live counterparty, a budget season where the forecast will drive hiring, or a stretch of months where cash is genuinely tight. In those moments, the review is cheap insurance against expensive surprises, because the alternative is discovering the model's weaknesses while someone across the table is discovering them too.
It is not worth the same effort in every situation. A very early business with one revenue stream, a handful of customers, and a few months of runway does not need a formal review; the founder can hold the whole model in their head, and a checklist would mostly produce paperwork. A stable business with no transaction, no financing, and a forecast that has tracked reality for several quarters needs a lighter touch: a periodic reconciliation and a look at the cash line, not a full teardown.
The middle case is where judgment matters. A growing business with expanding headcount, new customer contracts, or uneven collections is accumulating complexity faster than most founders notice, and that is when the review starts paying for itself even with no deal in sight. The trigger is not the intention to sell; it is the moment the model's assumptions start affecting decisions, like hiring or inventory purchases, that are hard to reverse.
Capacity is hire part time cfo of the honest answer too. A full review takes focused time, and a founder running the business may reasonably choose a partial version: cash line, top three assumptions, and reconciliation, with the deeper work deferred until a transaction makes it necessary. Fractional financial leadership exists partly for this shape of problem, but whether you use outside help or do it yourself, the sequence is the same. What matters is that the choice is deliberate rather than a default of doing nothing.
Look at both sides and set the bar honestly. A review that finds nothing is not a wasted review; it is evidence, and evidence has value in negotiation. A review that finds serious problems before a process starts has saved the founder from the worst timing, which is finding out mid-negotiation, when every discovery costs leverage.
The costliest mistake: presenting the model before it survives contact
The most expensive failure mode in this whole topic is not a wrong number; it is showing the model to a counterparty before it has been reviewed, and losing credibility on something fixable. Once a buyer's analyst finds a broken tie or an indefensible assumption, every other number in the workbook inherits the doubt, including the ones that were right. Credibility in a transaction is not won back with corrections; it is won back with time, and time is what processes run out of.
The mistake usually looks innocent. The founder has a strong quarter, a credible growth story, and a model that looks good on screen, so it goes out with the teaser or the data room ahead of schedule. The fix is almost embarrassingly simple: run the checklist first, in the order it exists for a reason. Cash, assumptions, reconciliation, working capital, separation of deal math, documentation. Each step exists because it catches the failure the previous steps cannot see.
There is a discipline worth naming here, which is to have someone else do the review if you can. The founder who built the model reads it with the assumptions already believed, and belief is exactly what a review is supposed to test. A colleague, an outside finance professional, or even a deliberately hostile self-review, where you argue the buyer's side out loud, will find things the builder cannot. If the business has a board or advisory relationships, a dry-run question session is the cheapest simulation of diligence available.
And keep the timing honest. A review is not a promise that a sale closes, a round funds, or a forecast proves true; none of those outcomes is assured, and a model that implies certainty is making a claim the review itself should reject. What the review buys is narrower and more useful: the confidence that the numbers you present are the numbers you can defend, and the knowledge of where they are fragile before anyone else does. In a negotiation, that knowledge is most of the advantage a founder can reasonably hold.
Cela supprimera la page "Financial model review checklist for founders: cash first". Soyez-en sûr.