commit
4f296d7b96
1 changed files with 151 additions and 0 deletions
@ -0,0 +1,151 @@ |
|||||
|
<br>Knowing how to model cash runway under multiple scenarios means building three honest versions of the same bank account, not one hopeful number. A base case shows the plan, a downside case shows what happens when collections slow or sales miss, and a stress case shows how many months the company lasts if both go wrong. Lenders read these side by side.<br> |
||||
|
|
||||
|
The symptom: one runway number that nobody can defend |
||||
|
|
||||
|
<br>Most owners who bring a runway figure to a lender have one number in their head. It came from a spreadsheet, a quick estimate or the last board update, and it says the company has about eight months left. Ask how it was built and the answer is usually vague. The number may be roughly right, but nobody can trace it back to the bank account.<br> |
||||
|
|
||||
|
<br>This is the first symptom to watch for. The figure changes when someone asks a follow-up question, and the owner cannot say why. A lender asks what happens if the largest customer pays late, and the answer is a shrug or a new number that contradicts the old one. Read the scope of your own model the way you would read a proposal. What does it include, and what did someone leave out on purpose?<br> |
||||
|
|
||||
|
<br>A second symptom is the single line. One forecast, one growth rate, one month when cash turns negative. It looks tidy. It also hides the fact that cash does not move as neatly as revenue does. Customers pay late, payroll runs on fixed dates, a tax deposit lands in the wrong month, and a loan installment comes due while invoices sit unpaid in a folder.<br> |
||||
|
|
||||
|
<br>A third symptom is the panic version. The owner has a runway number but no idea what to do at each level of cash. If the balance falls below a certain point, who cuts what, who calls the bank, and when? Without those answers, even an accurate model is only a warning light with no instructions attached.<br> |
||||
|
|
||||
|
<br>None of this means the owner is careless. Most founders build their first cash view while running the business, between sales calls and hiring decisions. The gap is rarely effort. It is a missing structure, and multiple scenarios are that structure. They turn one guess into a set of answers you can check, change and explain.<br> |
||||
|
|
||||
|
Why one forecast breaks when a lender starts asking questions |
||||
|
|
||||
|
<br>The main cause is that a single forecast tries to answer two questions at once: what do we expect, and how much room do we have if we are wrong? The first question is ordinary planning. The second one is what a lender cares about, because a loan is repaid from cash under bad conditions as well as good ones.<br> |
||||
|
|
||||
|
<br>Another cause is building runway from the profit and loss statement instead of the bank. Profit reports revenue when it is earned and expenses when they are incurred. Cash records money moving in and out of the account on the day it moves. Under the revenue recognition rules in ASC 606, revenue can be recorded before an invoice is paid, so a contract can look healthy on paper while the cash arrives months later.<br> |
||||
|
|
||||
|
<br>The third cause is stale inputs. Accounting platforms such as QuickBooks, NetSuite and Sage Intacct can produce an accounts receivable aging report, but only if the bookkeeping is current. When receipts are posted late and bills sit unrecorded, the model starts from a bank balance that is not the real one. The forecast is wrong before the first formula runs.<br> |
||||
|
|
||||
|
<br>The fourth cause is scenarios that are not tied to anything observable. A downside case that cuts sales by a figure picked at random tells a lender nothing. A downside case tied to a real signal, such as a large account asking for longer payment terms or a renewal still unsigned near its deadline, tells them what the company is watching and when it will react.<br> |
||||
|
|
||||
|
<br>Many owners also treat the model as a document for one meeting. It is a tool that needs updating every month. If the last update came before the last payment dispute, the model describes a company that no longer exists. Lenders notice this quickly, because an outdated model is often the first sign that management is not reviewing cash regularly.<br> |
||||
|
|
||||
|
Start from the bank balance and the timing of cash, not from revenue |
||||
|
|
||||
|
<br>A usable runway model begins with the cash balance on the most recent bank statement, reconciled to the books. Write that figure down as the starting point, then list the dated movements that will change it. This step sounds basic, and it is the one most often skipped, because the revenue line feels more interesting than a reconciliation.<br> |
||||
|
|
||||
|
<br>Next, map the money coming in. Use the accounts receivable aging report and ask a plain question about each large customer: when was the last payment, and when is the next one expected? Customers with a history of paying late should move later in the model, even if their invoices are current. New contracts need the same care. Billing in advance and billing in arrears produce very different cash timing, even when the work is identical.<br> |
||||
|
|
||||
|
<br>Then map the money going out. Payroll, rent, software subscriptions and loan installments are fixed and dated. Vendor payments follow the terms you negotiated, but many small businesses pay early to keep relationships easy, and that shortens the runway without anyone noticing. Include the irregular items too: quarterly tax deposits, annual insurance premiums, sales tax remittances and equipment purchases. A model that leaves them out makes the company look healthier than it is.<br> |
||||
|
|
||||
|
<br>Decide how many months to show and how often. Weekly views help during the first weeks of a cash squeeze, while monthly views work better for a conversation with a lender about the next year. Use the same structure for every scenario so the comparison is fair. If the base case uses monthly columns and the downside uses quarterly ones, the numbers cannot be read side by side, and a reader will assume the difference is hiding something.<br> |
||||
|
|
||||
|
<br>Ask who checked the bank reconciliation before the model was built. If nobody did, the first part of the work is cleaning the books, and that work is worth more than any scenario you add later. A provider who wants to start building scenarios before the starting balance is confirmed is asking you to trust numbers nobody has tested.<br> |
||||
|
|
||||
|
Set three scenarios with triggers you can actually observe |
||||
|
|
||||
|
<br>Most useful models have three cases: a base case, a downside case and a stress case. The base case is what you expect if the plan holds. The downside case assumes the business is weaker in one or two ways. The stress case combines bad news and tests whether the company can keep operating. Each case needs its own assumptions, and each assumption needs a reason you can point to.<br> |
||||
|
|
||||
|
<br>Start with the base case, because it sets the reference point for the others. It should match the operating plan, the hiring plan and the collection pattern you have seen in recent months. Do not raise sales in the base case just to make the runway look better. If the plan assumes growth, write down what has to happen for that growth to show up in cash, and when.<br> |
||||
|
|
||||
|
Downside case |
||||
|
|
||||
|
<br>The downside case changes a small number of inputs that have a real trigger. A large client moves from paying in 30 days to paying in 60, or a renewal expected in one quarter is still unsigned when the next quarter starts. Name the trigger. The trigger is what tells you when to switch from the plan to the contingency, and without it the downside case is just a worse guess.<br> |
||||
|
|
||||
|
Stress case |
||||
|
|
||||
|
<br>The stress case assumes several things go wrong together, but it should still be plausible. Revenue drops, collections slow, and a fixed cost rises, such as a lease renewal or an insurance premium. A stress case is not a disaster with every number set to zero. It shows how many months the company can keep operating if the business it has now stops delivering what the plan expects.<br> |
||||
|
|
||||
|
<br>The table below shows how the three cases can be laid out. Each row names the trigger you watch and the action you take when it appears, so the model is a set of decisions and not only a set of numbers.<br> |
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
Scenario |
||||
|
Trigger you watch |
||||
|
Cash coming in |
||||
|
Action when the trigger hits |
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
Base case |
||||
|
Renewals signed on schedule and receivables paid on current terms |
||||
|
Matches the plan |
||||
|
Keep the hiring plan and report cash monthly |
||||
|
|
||||
|
|
||||
|
Downside case |
||||
|
One large client pays late for two months in a row |
||||
|
Lower than plan, with later timing |
||||
|
Pause discretionary spending and contact the lender early |
||||
|
|
||||
|
|
||||
|
Stress case |
||||
|
Two major contracts lost or delayed at the same time |
||||
|
Well below plan |
||||
|
Freeze new hires, review fixed costs and check the minimum balance |
||||
|
|
||||
|
|
||||
|
|
||||
|
|
||||
|
<br>Keep the scenario list short. Five or six cases make the model harder to read and harder to defend in a meeting. Three cases, each with a named trigger and an action, are enough for most lender conversations. More cases do not make the forecast more accurate. They usually make the owner less able to explain what matters.<br> |
||||
|
|
||||
|
Which assumptions move the runway and which ones only look important |
||||
|
|
||||
|
<br>Once the scenarios exist, test which inputs change the answer. A sensitivity check changes one assumption at a time and records what happens to the months of runway. Most owners find that a few inputs move the result a lot, and many others barely matter. Spend the review time on the first group.<br> |
||||
|
|
||||
|
<br>Collection timing is usually the strongest lever in a service business. A payment that arrives two weeks later can matter more than a small change in monthly revenue, because the company still has to pay its bills on the due dates. Check the receivables aging and ask which few accounts drive most of the balance. Those accounts deserve a conversation, and sometimes a change in terms.<br> |
||||
|
|
||||
|
<br>Vendor payment terms are the second lever. If suppliers allow thirty days instead of fifteen, the company keeps cash longer. The trade-off may be a higher price or a strained relationship, so ask what the vendor would charge for faster payment before you assume the terms are free. A model that treats the longer terms as a permanent gift will break the first time a supplier changes its policy.<br> |
||||
|
|
||||
|
<br>Some inputs look important but rarely change the answer. Software subscriptions are visible line items, yet their total is often small next to payroll and rent. A model that spends an hour on each minor expense and ten minutes on receivables has its priorities reversed. Keep the detail where the risk is, and summarize the rest without apology.<br> |
||||
|
|
||||
|
<br>Keep a short list of the five assumptions that matter most and update them every month. Everything else can stay on a lighter review. This is also where you decide what a lender should see. A sensitivity table that shows which inputs drive the result builds more trust than a polished base case presented alone, because it shows you know where the model is fragile.<br> |
||||
|
|
||||
|
<br>Read the model's notes as carefully as its totals. If a cell says "estimated" with no explanation, that is the cell a lender will question first. Replace estimates with sources where you can, such as a signed contract, a payment history or a vendor invoice, and label the ones you cannot source yet.<br> |
||||
|
|
||||
|
What lenders look for in the downside and stress cases |
||||
|
|
||||
|
<br>A lender is less interested in your best month than in your worst reasonable one. They want to know whether the company can keep paying principal and interest when conditions slip, and whether management notices a problem early enough to act. A model with clear downside and stress cases answers both questions without a speech.<br> |
||||
|
|
||||
|
<br>Many loan agreements include covenants, which are conditions the borrower must keep meeting. A minimum liquidity covenant, for example, requires the company to hold a set amount of cash or available credit at all times. Read the loan terms and list each covenant next to the scenario results. If the downside case breaks a covenant, you need to know that before the lender does.<br> |
||||
|
|
||||
|
<br>Minimum cash is a concept many owners overlook. Runway measured to zero makes the company look more capable than it is, because no business can run with an empty account. Measure runway to a minimum operating balance instead, and show the lender what that balance is and why you chose it. The example near the end of this article shows how much the answer changes.<br> |
||||
|
|
||||
|
<br>Lenders also look for early warning. They like to see triggers, the dates when you review the model, and the actions you take at each level. A company that says it will contact the bank when cash falls below a set point, and then does so, earns more trust than a company that promises to be transparent without saying how or when.<br> |
||||
|
|
||||
|
<br>Be careful with the language you use in these conversations. Phrases such as "we expect to grow fast" or "the downside is unlikely" invite questions the model cannot answer. Write the assumption, its source and its trigger, then let the numbers speak. Do not promise an outcome. A lender will hold you to any promise you make, and the future rarely follows a model exactly.<br> |
||||
|
|
||||
|
<br>Ask your lender what format they prefer. Some want a monthly cash flow, some want a quarterly view and some want the scenarios in a single file with a short written summary. Asking shows you are planning for their review, not only for your own.<br> |
||||
|
|
||||
|
Questions to ask a fractional CFO before they build the model for you |
||||
|
|
||||
|
<br>If you hire an outsourced or fractional CFO to build the runway model, read the scope before the work starts. Ask who owns the assumptions, who has access to the bank and accounting systems, and who signs off on the numbers before a lender sees them. A good provider welcomes these questions because they show how the work will be done.<br> |
||||
|
|
||||
|
<br>The difference between roles matters here. A bookkeeper records transactions and keeps the books current. A controller oversees the monthly close, the reports and the internal controls. An outsourced accounting firm may handle bookkeeping and the close on a fixed schedule. An outsourced CFO sets the financial direction, builds the scenarios and joins the conversations with lenders or investors. Ask which of these the proposal actually includes, and which it leaves out.<br> |
||||
|
|
||||
|
<br>Before you sign, ask these questions:<br> |
||||
|
|
||||
|
|
||||
|
What exactly is included in the runway model, and how often is it updated? |
||||
|
Which inputs come from my books, and which come from your assumptions? |
||||
|
Who prepares the lender conversation, and who attends it? |
||||
|
Ask what's not included, such as bookkeeping cleanup, tax work or system setup. |
||||
|
How will you flag a trigger, and how fast after the bank balance changes? |
||||
|
What do I receive at the end: a file, a presentation, or access to a live model? |
||||
|
|
||||
|
|
||||
|
<br>Avoid any provider who promises a lender approval, a specific loan amount or a guaranteed extension of runway. Those outcomes depend on the lender, the market and your business, and no honest proposal can guarantee them. Ask instead how the model will be tested and what the provider will do if the downside case shows a problem. The answer tells you more than any headline figure.<br> |
||||
|
|
||||
|
<br>Ask about experience with companies at your stage and in your industry, but read the answer carefully. A biography full of large numbers does not prove those results apply to your company. Ask for a plain description of the work, and ask which parts the provider has done before and which would be new for your situation.<br> |
||||
|
|
||||
|
<br>Compare the fee to what you actually receive, not to a return someone has promised. A fee for a model you can update yourself is a different purchase from a fee for ongoing lender support. Ask what happens when the business changes and you need to rebuild the scenarios. The answer to that question is often where the real cost sits.<br> |
||||
|
|
||||
|
Worked example: a hypothetical New York services firm with three cases |
||||
|
|
||||
|
<br>Consider a hypothetical services firm in New York with a small team and mostly monthly billing. Assume it holds $300,000 in cash at the start of the month and wants to keep a minimum operating balance of $60,000. These figures are invented for the example and do not describe any real company.<br> |
||||
|
|
||||
|
<br>In the base case, [what is a outsourced CFO in New York City](https://Venturegrowthpartners.com/locations/new-york-new-york-city-outsourced-cfo-services/) cash coming in is $115,000 a month and cash going out is $150,000. The net burn is $35,000. Runway to zero is about 8.6 months ($300,000 divided by $35,000). Runway to the minimum balance is about 6.9 months, because usable cash is $240,000 and $240,000 divided by $35,000 is about 6.9.<br> |
||||
|
|
||||
|
<br>In the downside case, the largest client starts paying 30 days later, and cash coming in falls to $95,000 a month. Net burn rises to $55,000. Runway to zero drops to about 5.5 months, and runway to the minimum balance to about 4.4 months. The owner now knows the lender conversation should start well before the balance reaches the next quarter.<br> |
||||
|
|
||||
|
<br>In the stress case, the same collection slowdown happens, and a new equipment lease adds $20,000 a month to cash going out, so the total rises to $170,000. Net burn becomes $75,000. Runway to zero is 4.0 months, and runway to the minimum balance is about 3.2 months.<br> |
||||
|
|
||||
|
<br>The three numbers do not tell the owner [what is A outsourced CFO in New York City](https://Venturegrowthpartners.com/locations/new-york-new-york-city-outsourced-cfo-services/) to do on their own. The actions do. In the downside case, the owner pauses discretionary spending and sends the lender the three-case model with the trigger attached. In the stress case, the owner also reviews the lease before signing it, checks whether the payments can be deferred, and confirms the covenant level with the lender. Each step follows from a trigger agreed in advance, not from a decision made in a panic.<br> |
||||
|
|
||||
|
<br>Notice what the example avoids. It does not assume the client returns to its old payment pattern, that the lease is approved on the first request, or that the business wins new work in time. Each case changes one observable thing at a time, and the table shows what happens at each level. That is the kind of model a lender can test, and it is also the kind you can explain to your own team without a long meeting.<br> |
||||
Loading…
Reference in new issue