Learning how to extend startup runway starts with a plain question: how many months of cash you have left at your current net burn. Cutting costs can buy time, but only the right ones. Collections, payment terms and software waste usually come before layoffs. How far those moves get you depends on a forecast you trust, and the rest of this article shows how to build one.
How do you calculate runway without fooling yourself?
Runway is the number of months your current cash lasts at the rate you spend it. The usual formula is simple: divide cash on hand by net burn, which is the cash you lose each month after money comes in. In a hypothetical case, a company holds 600,000 dollars and loses 50,000 a month on net, so its runway is twelve months. The arithmetic is easy. The inputs are where teams go wrong.
Here's the catch: many founders start with gross burn, meaning total monthly spending, and forget when revenue actually arrives. If a large customer pays late, your cash does not improve just because the invoice went out. Net burn should reflect when money lands in the bank, not when it is earned on paper. That is why a monthly close matters. Bookkeeping that trails the bank by several weeks gives you a runway number built on old facts.
A second trap is treating one-time items as recurring, or the reverse. A legal bill for a financing, an annual insurance premium or a deposit on office space can make one month look far worse than the business really is. A one-time payment from a partner can make the runway look longer than it is. Good runway math separates recurring costs from lumpy ones and says which is which.
Then build the runway in scenarios instead of a single line. Use a base case that matches current trends, a downside case where collections slip or a new hire takes longer to pay off, and an upside case you would not bet payroll on. The goal is not to predict the future. It is to know which assumption breaks the plan first.
Finally, agree internally on what counts as cash, and write the formula down. A revolving credit line belongs in the number only if the terms let you draw on it in a crisis, and it should be shown separately. Recalculate the runway every month. A number nobody updates turns into a feeling, and feelings about cash tend to be optimistic in good months and panicked in bad ones. A spreadsheet works for a small company. As the company grows, planning tools such as Adaptive Insights, or the reports inside QuickBooks, NetSuite or Sage Intacct, can do the same job, provided someone checks the inputs.
Which costs are safe to cut, and which ones quietly kill growth?
The wrong cut is the one that saves cash this quarter and costs revenue next year. Before you touch a line item, ask what it does for customers, the product or the people who bring in money. A cost that feeds revenue is not waste just because it is large. Cutting it can make runway look longer on paper and shorter in practice, part-time CFO cost in Massachusetts because the business shrinks to match a smaller income.
Waste is easier to find. Most companies carry software seats nobody uses, duplicate tools that do the same job, annual contracts for products the team dropped and subscriptions tied to people who left. Reviewing these is low risk because the work does not change. A useful habit is to list every recurring vendor with its owner, its renewal date and its last real use. Anything without an owner is the first candidate for review.
Growth costs deserve a harder look. A quota-carrying sales hire, the one engineer who owns the release process and the customer support that keeps accounts from leaving are expensive. Cutting them usually hurts the next several months of revenue. Marketing spend works the same way. A channel that brings in paying customers at a known cost should not be treated like a brand experiment. Mark these costs clearly in your forecast so the cut list does not reach them by accident.
Hiring freezes need the same care. A freeze protects cash, but it can also stop the company from filling a role it already needs. Sort open positions into essential, nice to have and only feels urgent. A freeze on nice-to-have roles is easy to defend. A freeze on the only person who can ship the product is a decision whose consequences may not show up for a while. Compensation changes deserve caution too. Cutting salaries can break trust with the people you most need to keep, and on a small team one resignation can cost more than the savings.
If you do reduce pay or benefits, state the duration and the conditions for restoring them, and put both in writing. Vague promises tend to turn into resentment. It also helps to label each cut as structural or temporary before you make it. Dropping an unused product line is structural. Pausing a conference budget is temporary. Labeling them this way lets the team understand the plan and makes it easier to restart spending when the cash position improves.
Where can cash come back before you cut anything?
Before you decide what to cut, look at what you can collect, time and reorganize. These moves do not change what the company does, so they usually carry less risk than a hiring freeze. They also have limits, and some of them pull cash forward at the expense of later months. The main levers are these:
Collections: invoice on the day work is delivered, follow up on overdue balances and name one owner for each late account. Payment terms: shorter terms with customers and longer terms with vendors, where the vendor agrees, change when cash moves without changing the price. Deposits and prepayments: some customers will pay upfront for a discount or a set period of service. Vendor prepayment discounts: paying a year in advance can lower the unit price, but it uses cash now, so it only helps if enough runway remains after the payment. Payroll timing: align pay cycles with incoming receipts where your payroll setup allows it and a lawyer or payroll provider confirms it is permitted.
Agencies and service firms have a version of this problem that catches people off guard. Client retainers billed in advance help cash, but they create deferred revenue on the books. Under ASC 606, revenue is recognized as the work is performed, so a large prepayment can look like money in the bank without appearing as income on the statement of operations. Cash and profit tell different stories. When you decide what you can spend, your forecast should follow the bank balance, not the income statement.
Hardware and product companies have inventory to manage. Buying stock early ties up cash that could cover payroll for months. Ordering in smaller batches, or negotiating supplier deposits that match the delivery schedule, can create room. The trade-off is that smaller orders often cost more per unit and risk stockouts if demand rises faster than expected.
The table below compares the levers by cash effect, speed and main risk. The point is not to pick one. It is to see which moves are fast, which take time and which can strain a customer or supplier relationship.
Lever Cash effect Speed Main risk
Faster collections Brings existing receivables forward Usually fast Strained customer relationships
Shorter customer terms Moves cash earlier on future invoices Slow to build up Lost deals with customers who want longer terms
Vendor payment extensions Delays outflows Depends on the vendor Late fees and damaged supplier trust
Annual prepay discount Lowers unit cost but uses cash now Immediate outflow Shortens runway in the months after payment
Cutting unused software Reduces recurring outflow Usually fast Low risk once an owner confirms the seat is unused
Here's the catch with stretching vendor payments: it feels free until a critical supplier stops shipping or pauses a service you depend on. Negotiate extensions in writing, keep the relationship honest and never stretch payments to the point where operations are interrupted. A supplier who trusts you will help in a bad month. A supplier who is being paid late will not.
How does a fractional CFO differ from a controller, accountant or bookkeeper?
These titles overlap in small companies, and that confusion causes many bad hiring decisions. A bookkeeper records transactions and keeps the ledger accurate. An accountant prepares financial statements and tax filings. A controller runs the monthly close and the accounting team. A CFO decides how money should be used and what the company should do with it. A fractional CFO is a senior financial leader who works part time or on a defined scope, often across several clients on a flexible schedule.
Role Main job Typical outputs Usually does not do
Bookkeeper Records daily transactions Reconciled accounts, categorized expenses Forecasting, strategy or investor reporting
Accountant Prepares statements and tax filings Annual statements, tax returns, audit support Designing the cash plan or leading a raise
Controller Runs the close and internal controls Monthly close, accruals, reporting package Long-term capital strategy or lender negotiations
Fractional CFO Leads finance decisions part time Cash forecast, KPI pack, board materials, financing plans Daily bookkeeping, payroll processing or replacing a controller
The overlap is real. A fractional CFO may review the bookkeeper's work, and a controller may build a forecast. The useful question is who is accountable for what. If the company has no controller and no clean monthly close, a fractional CFO will spend early time on basics before reaching strategy. That is not a failure. It is the job when the foundation is missing, and you should expect it and plan for it.
In practice, a company with a bookkeeper and an outside accountant may need a fractional CFO only for the forecast, the lender package and the board deck. A company with an in-house controller may need one only for financing strategy. The right mix depends on what is missing, not on headcount alone.
Here's the catch: a fractional CFO cannot replace accurate source data. If bank transactions are misclassified, invoices sit unrecorded or revenue is booked before it is earned, the forecast will look polished and still be wrong. Ask who owns the close before you ask who owns the strategy.
Also check whether the person's background fits the stage you are at. Someone who has run finance at a large public company may not be comfortable working with a founder who is still watching every expense. That says nothing about either person's skill. It is a mismatch in working style, and it usually shows up within the first few weekly meetings.
What does a fractional CFO actually do week to week?
Most of the work is repeated routine, with occasional projects that take over several weeks. The routines are the forecast update, the review of the monthly close, a look at receivables and payables and a short conversation with the CEO about decisions coming up. The projects are usually a financing round, a lender package, the next annual budget or preparation for a sale.
The rolling forecast sits at the center of the work. It is updated on a regular cadence, usually weekly for cash and monthly for the full plan, and it shows the expected bank balance across the coming months. Each assumption is written down: when a customer pays, when payroll goes out, what the sales team expects to close. When actual results differ from the forecast, the gap is explained rather than buried.
Other recurring work covers the KPIs the business actually uses. For a software company, that might mean bookings, gross margin, net retention and cash burn. For an agency, it might mean utilization, realization and client concentration. For a nonprofit, it might mean restricted fund balances against budget. The useful KPIs are the few that trigger a decision, and each needs a definition that does not change from month to month.
The working relationship with the CEO and the accountant is steady, not dramatic. The CEO brings priorities and questions. The accountant owns the books and the tax work. The fractional CFO connects the two by explaining what the numbers mean for the choices in front of the company. If there is a board, it receives a standard pack each period, so updates do not depend on who happened to ask last.
The first few weeks usually look less strategic than people expect. Expect time spent on bank reconciliations, a review of the chart of accounts, a list of open invoices and an inventory of tools and contracts. That groundwork is what makes the forecast credible. Ask for a written list of deliverables for the first month and check it against what actually gets done. The time commitment varies, and vague agreements about availability cause friction. Put the expected meeting schedule, the response time for urgent questions and the deliverables into the engagement letter. Also write down what the role does not do, such as signing tax filings, managing staff directly or making payroll decisions. A clear boundary protects both sides.
How do you tell whether a candidate fits your stage, size and industry?
Start with the stage the company is at, not the stage it hopes to reach. A candidate who has built forecasts for a company of your size may not know how to handle a business with irregular income and a few months of runway left. Ask for specific examples: what they built, what the company decided because of it and what they would do differently now. Specific answers are more useful than general claims about experience, and you should check any claim you cannot verify.
Industry fit matters, but it is easy to overvalue. A candidate from life sciences will understand milestone-based funding and long development timelines. A candidate from retail will understand inventory and seasonality. Neither is automatically better for your business. Ask how they would handle the specific risks you face, such as trial costs, grant reporting or dependence on a few large clients, and listen for practical detail rather than industry vocabulary.
Ask how they work day to day. Some fractional CFOs stay hands-on with the close and the books. Others focus on strategy and expect the internal team to run the systems. Neither style is wrong, but each requires different staffing. Ask what they would do in a month when the bookkeeper is late, a key customer pays slowly and the board wants an update on the same week.
Check references, and ask about the hard parts. Good references describe what the candidate did when the numbers were bad, when the CEO disagreed or when a financing fell through. Be careful with any testimonial that promises results. Outcomes depend on the business, the market and the timing, and no candidate can guarantee that a round will close or that a sale will happen.
Read the proposal with the same skepticism. A clear scope lists deliverables, meeting cadence, what is included and what costs extra. A vague one reads like a general offer of help. If the proposal mentions prices or timelines, ask how they were set. Pricing with no stated method is a warning sign, because you cannot compare options or judge whether the work matches the cost. Finally, ask what the candidate will actually own. Before you hire anyone to help with a raise, know which deliverables they are accountable for, which ones you will hand over and which stay with your team. A good candidate will say plainly that no one can promise the round closes, and will show you how they would prepare the company for either outcome.
How do the trade-offs change for startups, life sciences, nonprofits and agencies?
The general method is the same across segments, but the cash patterns are not. A startup, a life sciences company, a nonprofit and an agency each have different sources of money and different reasons the balance can drop. Treating them as the same kind of company produces forecasts that look tidy and miss the real pressure points.
Startups
Early-stage startups usually depend on equity and need to plan around the next round. The forecast should show the cash balance at the point where the company would have to raise, along with the milestones investors will expect to see. Here's the catch: a runway that ends before the next milestone is a problem even when the bank balance is positive. Investors and lenders often want to see a plan that reaches the next proof point with some room to spare.
Life sciences
Life sciences companies often face long development timelines and funding linked to milestones, grants or partner payments. Those payments may arrive in lumps, and some depend on reports or results. The forecast should separate committed funding from expected funding. Regulatory work, lab costs and study expenses should be modeled as uneven rather than smooth. In a hypothetical case, one delayed milestone can move the whole runway calculation, so scenario planning matters more here than in most businesses.
Nonprofits
Nonprofits work with restricted money. A grant for one program cannot quietly cover payroll for another, and funders often require reports that tie spending to the purpose of the grant. The runway question becomes two questions: how much unrestricted cash is left, and when each restricted fund must be spent or reported. Combining them into one figure hides the real constraint. Tracking each fund separately, with a monthly review of grant deadlines, is usually more useful than a single headline number.
Agencies
Agencies sell time, so their cash depends on billing, collections and staffing. A large client that pays late can leave payroll exposed. Retainers billed in advance help cash but create deferred revenue, which can make profit look different from the bank balance. The forecast should track each major client's payment pattern, the share of revenue from the largest accounts and the timing of contractor payments. When an agency adds staff to win a big account, its runway can shrink before the new revenue arrives.
The common thread is that the forecast has to match how cash actually arrives, not how the business describes itself. If your company runs on grants, milestones, retainers or equity rounds, build the forecast around those specifics. Otherwise the runway will look cleaner than it really is.
When does it make sense to move from a fractional CFO to a full-time one?
A fractional model is not a stepping stone for everyone. Many companies keep it for years because the work fits their size and budget. The signal to move to a full-time executive is usually the workload, not the calendar. When finance questions start needing someone on site every day, a part-time CFO cost in Massachusetts arrangement may be stretched too thin.
Look for specific signals. The company manages several legal entities or complex debt. Board meetings and investor updates happen often enough that a part-time person cannot prepare them well. A financing or sale is coming up that needs a leader accountable for the process from start to finish. The team has grown enough that the controller needs a senior peer for decisions about hiring and budgets. The most common signals are these:
Board or investor reporting has become a weekly or near-weekly demand. Debt, equity or lender covenants need regular attention rather than occasional review. A sale, merger or acquisition is in active preparation or due diligence. The company runs several entities, currencies or complex revenue streams. Operating decisions take up most of the fractional CFO's time, and the CEO wants that role full time.
Here's the catch with moving too early: a full-time executive costs much more than a fractional one, and the company carries that salary whether or not the work is ready for it. Hiring too soon can shorten runway at the moment you need it longer. Moving too late means a senior person arrives into a messy close and spends months fixing basics instead of leading strategy.
A middle path is common. Some companies hire a controller first and keep a fractional CFO for strategy until the workload justifies a full-time CFO. Others convert the fractional role into a full-time one after a trial period with clear terms. Neither path is automatically right. The choice depends on whether the coming year needs hands-on execution or outside judgment. Whatever you choose, part-time CFO cost in Massachusetts write down the criteria before you talk to candidates: what the role must own, what it must not own and how success will be judged. A search without that list tends to produce someone who fits the title but not the company.
A worked example: how a hypothetical team extends runway without cutting its sales hires
This example is hypothetical. The company, the numbers and the situation are invented to show the method. They do not describe any real business or a typical result. Suppose a software team holds 900,000 dollars in cash and loses 90,000 dollars a month on net. Its runway is ten months. The founder wants to reach the next milestone, which would take about fourteen months at the current pace, so the team needs roughly four more months of cash without weakening the business.
The first step is to fix the forecast. The initial pass shows two large invoices due next quarter, but both customers have paid late before, so the forecast moves each payment back by one month. The team also finds three unused software seats, a duplicate analytics tool and an annual contract for a product line that was shut down. In this example, those items add up to about 4,000 dollars a month. They are waste, and cutting them does not touch the sales team. Each one gets a named owner who confirms the cut.
The second step is collections. The company starts invoicing on delivery instead of at the end of the month, and it calls its two slowest accounts directly. It also asks one customer whether a partial prepayment would work in exchange for a small discount. In this hypothetical, the customer agrees. The forecast records the effect in the months the cash lands, not in the month the deal is signed.
The third step is the hard decision. The team could cut the sales hire planned for next quarter, and that would extend runway on paper. The example rejects that cut. The new hire is the person expected to bring in the revenue that makes the next milestone reachable. Cutting them would weaken the case for the raise. Instead, the team pauses a marketing experiment with no measurable return and delays a planned office expansion by one quarter.
The fourth step is scenarios. The base case now shows about thirteen months of runway. The downside case, where one large customer pays two months later and the sales hire takes longer to ramp up, shows about eleven. The team decides in advance that if the downside happens, it will pause the next hire and cut discretionary spending. That rule is written into the plan before anything goes wrong.
What the example does not show matters too. It does not guarantee that the milestone will be reached, that the raise will close or that the customer will prepay. It only shows that each decision was tied to cash timing, and that the rejected cut would have damaged the revenue the company needs. In a real business, the same method might produce a larger runway gain, a smaller one or none at all. The forecast should be updated as facts arrive, and the plan should change when they do.