Interim CFO during rapid growth: define the mandate first

Hiring an interim CFO during rapid growth works only when the mandate is written down before the person starts. In a hypothetical example, a software company doubling revenue loses its finance head mid-quarter: the founder signs a six-month engagement, and the first week is spent arguing over who approves spending. That argument belongs in the contract negotiation, not in week one.

A hypothetical company to follow from start to finish

Picture a company we will call Northlane, and treat everything about it as an illustration, not a case. Northlane sells inventory software to mid-size distributors. Revenue has roughly doubled each year for two years, headcount went from twenty to fifty-five, and the permanent CFO resigned to join a larger firm. The board expects a funding conversation within nine months.

The founder, like most founders at this stage, is still approving invoices herself. The accounting close slips to the twentieth of each month, nobody owns the cash forecast, and the two people in finance spend most of their time on bookkeeping. Investors receive a spreadsheet the founder assembles the night before each call. Nothing is broken in an obvious way, but everything finance-related depends on one person: her.

Northlane decides to bring in an interim finance lead for nine months. The engagement has three phases that mirror the sections below: defining the mandate and decision rights, doing the work in the first ninety days, and handing off to a permanent hire. The trade-offs Northlane faces, between speed and control, between cost and coverage, are the same ones any growing company faces when a finance seat opens up at exactly the wrong moment.

One caution before the story starts. An interim arrangement solves a gap in leadership and process; it does not guarantee a financing outcome, a cleaner audit, or a sale. Northlane’s results in this example are plausible, not promised. The value of the structure is that it forces the company to decide, in writing, what it wants from the role while it searches for someone permanent.

The scenario also keeps debt and equity separate, because they are. A bridge loan from a bank, a venture round, and a credit line all put different demands on the finance function. The interim mandate should name which of those conversations is actually on the table, because that choice shapes what gets built first.

Define the mandate before the first day

The mandate is a short written document, ideally one page, that says what the interim finance lead is responsible for, what they explicitly are not, and what decisions they can make alone. Northlane drafts this before interviewing anyone. The draft changes after conversations with candidates, but the founder writes the first version, because outsourcing the definition of the role means outsourcing the company’s own priorities.

Northlane’s mandate lists four deliverables: a reliable monthly close by the tenth business day, a rolling thirteen-week cash forecast, investor-ready reporting the founder does not assemble herself, and preparation for the funding conversation. It also lists what the role will not do: no permanent hiring authority, no signing authority on bank accounts, no changes to the external accountant without the founder’s approval. Boundaries make the role usable.

Decision rights deserve their own paragraph in the document. The common failure is vagueness: the interim lead “manages cash” until the founder discovers that meant moving money between accounts without a call. Northlane sets a simple rule, and any company can copy the structure even with different thresholds. The interim lead approves routine operating spending within a budget line; anything outside a budget line, any new debt, any contract longer than a year, goes to the founder.

The next question is how long the mandate runs and what “done” looks like. Nine months suits Northlane because a permanent search takes time and the funding conversation needs preparation. The document names the exit condition: a permanent CFO signed, or the mandate renewed once with a revised scope. Open-ended interim arrangements drift into expensive permanent crutches, so an end date, even a soft one, keeps everyone honest.

Scope also depends on company stage, sector, and need. A company with heavy inventory carries working-capital pressure that a services business does not; a business approaching a transaction needs diligence readiness that a stable one does not. Northlane is pre-transaction and inventory-adjacent only through its customers, so its mandate weights process and reporting over deal support. A company copying this structure should re-weight it, not copy the priorities.

Finally, the mandate decides how the interim lead relates to the existing team. Northlane’s two finance staff report to the interim lead for the duration, which the founder communicates before day one. Skipping that conversation creates a shadow structure where the team keeps routing questions to the founder, and the interim arrangement becomes an expensive observer.

What the first thirty days should actually produce

The first month is for diagnosis and quick repairs, not transformation. Northlane’s interim lead spends the first two weeks on three things: running one monthly close personally to see where it breaks, reading the last three investor updates, and sitting in on the weekly leadership meeting without saying much. You learn about venture growth Partners interim cfo engagements more from watching a process fail than from reading a description of it.

By the end of week two, the interim lead writes a one-page findings memo. It lists what is urgent, what is important but not urgent, and what is noise. For Northlane, urgent turns out to be the close calendar and revenue recognition, because the company signed several multi-year contracts and the current method for recognizing that revenue is informal. That last point matters: with contracts in play, the memo flags that revenue recognition should follow a defined standard, and ASC 606 is the one that applies to US companies.

Days fifteen through thirty go to two repairs. First, the close gets a calendar: each task has an owner and a due day, and the accounting staff stop improvising the order of work. Second, the cash forecast gets rebuilt as a thirteen-week view, updated weekly, because that horizon is long enough to see trouble coming and short enough to stay accurate. Neither repair requires new software; both require someone with the authority to set a routine and the discipline to keep it.

The founder’s role in month one is to answer questions fast and protect the interim lead’s access. When the interim lead asks for the bank login, the customer contracts, and the last board deck in the same week, the founder provides all three. An interim engagement where information arrives slowly burns its own calendar, and the calendar is what the company is paying for.

One thing month one should not produce: a reorganization. New org charts, new titles, and new hires in the first thirty days are usually a sign the mandate was vague and the interim lead is filling the vacuum with structure. Northlane’s mandate prevents this by limiting hiring authority, and that limit is a feature, not an insult.

Building the cash forecast the board will actually read

A forecast is useful when you can explain what sits behind it, and See What Matters that is the standard Northlane applies from month two onward. The thirteen-week cash forecast becomes the single most-discussed document in the company. It is updated every Friday, and the founder reviews it Monday morning with the interim lead, in a meeting that takes twenty minutes once the format settles.

The forecast has three layers. The top layer is cash in and cash out by week, which is arithmetic. The middle layer is the assumptions: when customers actually pay, when the payroll hits, when the annual insurance invoice lands. The bottom layer is the triggers: what the company does if cash falls below a threshold the founder sets, and what it does if cash runs above another. The middle layer is where forecasts earn or lose credibility.

Northlane’s first version is wrong in a predictable way: it assumes customers pay on contract terms, and customers pay late. The interim lead fixes this by building the assumption from actual payment history rather than invoice dates. Within two months, the forecast is not perfect, but its errors are explainable, and an explainable error is something a board can work with. A precise forecast nobody can explain is worse than a rough one with visible assumptions.

The forecast also changes the founder’s behavior, which is the real point. When the forecast shows a tight week coming after a planned hire, Northlane delays the hire by three weeks instead of discovering the squeeze afterward. That is the forecast paying for itself: not through accuracy as a virtue, but through decisions made earlier than they would otherwise have been.

The next question is what the forecast should connect to, and the answer is working capital. Receivables, payables, and deferred revenue move together, and the interim lead adds a simple view of each alongside the weekly cash numbers. For a company selling annual contracts, deferred revenue is the item founders most often misread, because cash arrives before it can be counted as revenue, and the gap between those two events is where planning mistakes live.

Connecting finance work to the operating routine

Strategic finance that lives in its own spreadsheet dies quietly. The interim lead’s job is to wire finance into the meetings the company already holds, and Northlane does this in month two. The weekly leadership meeting gets a standing five-minute slot for cash and pipeline. The monthly close feeds a one-page summary the whole team can read. Nothing new is invented; existing routines get fed.

The monthly close moves to a fixed calendar, and this matters more than it sounds. When the close lands on the tenth business day every month, everyone downstream can plan: the founder writes the investor update the same week, the board packet follows a rhythm, and the finance team stops living in a state of perpetual catch-up. Predictability, not sophistication, is what makes a close trustworthy.

Budgeting gets lighter, not heavier. Northlane had no real budget; the interim lead introduces a simple one built from the cash forecast’s assumptions, so the two documents agree with each other. A budget that contradicts the cash forecast forces the founder to decide which number is real, and that decision, repeated monthly, corrodes confidence in both. One set of assumptions, used in both places, is the discipline.

Internal controls are the least glamorous part and the one that prevents the worst outcomes. Northlane’s interim lead separates three things that had been combined: who initiates a payment, who approves it, and who reconciles the bank account. In a fifty-person company this does not require software; it requires two people following a rule. The founder keeps signing authority, and the rule is that anything above the threshold she set in the mandate gets a second look by definition.

The routine also has to survive contact with growth. New hires, new customers, and new tools all create small process changes, and the interim lead’s test for each is whether it can be documented in a page and run by someone else. If a process only works when the interim lead runs it, that process is not finished. This test becomes important in the handoff, and it is the reason documentation is treated as a deliverable rather than an afterthought.

Investor reporting that answers questions before they are asked

Northlane’s investor updates had been a habit rather than a format: a spreadsheet, some commentary, and the founder’s apology for the lateness. The interim lead replaces this with a fixed template, sent the same week each month, with the same sections every time. Investors do not need more information; they need information in a shape they can compare across months.

The template has four parts. Cash and runway, stated against the forecast. Revenue and pipeline, with the recognition method named so nobody argues about definitions later. Headcount against plan. One paragraph on what went wrong, written plainly. Founders under-include the last part; a report that never contains bad news trains investors to stop believing it.

The reporting also has to be honest about what it cannot claim. Metrics that reflect this one company’s situation are just that: this company’s situation. They do not establish typical outcomes, and the interim lead resists the temptation to frame them as evidence of a trajectory. A board can handle a bad month; what erodes trust is a presentation that treats one quarter as a trend.

Preparation for the funding conversation runs alongside the monthly reporting rather than instead of it. The interim lead builds a data room in month four: contracts, cap table, financial statements, the forecast and its assumptions, each named consistently with the monthly updates. The discipline pays off at the moment of diligence, because the documents investors request are the documents the company has been maintaining all along.

The next question is what the founder should be able to say without notes, and the interim lead rehearses her on three: the cash position and what moves it, the revenue model and its recognition logic, and the plan if the round takes longer than hoped. Investors ask about assumptions, not just headlines, and a founder who can walk through her own forecast’s middle layer is doing the work the interim engagement was designed to enable.

The handoff to permanent leadership

A handoff planned in the last two weeks is a handoff that will fail. Northlane’s mandate names knowledge transfer as a deliverable from the start, and the interim lead keeps a running document of processes, assumptions, and open issues from month one. By month seven, that document is a manual, not a farewell memo.

The transfer has three concrete pieces. First, process documentation: the close calendar, the forecast’s assumption log, the controls, each written so a new hire can follow them. Second, relationship introductions: the bank contact, the external accountant, the investors who prefer a call before a board meeting, each handed over with context, not just an email address. Third, a judgment file: the decisions made during the engagement, why they were made, and what the alternatives were. New leaders inherit decisions without reasons often enough; the file exists to prevent that.

The permanent hire should overlap with the interim lead for a few weeks if the calendar allows. Northlane’s search lands a permanent CFO in month eight, and the interim lead’s final weeks are spent walking the new hire through the forecast history and sitting beside her in the first close under the new calendar. The overlap is short and structured: a schedule of what gets covered each week, ending with the interim lead genuinely gone.

Some engagements end without a permanent hire, and that outcome should be named in advance. If the search stalls, the mandate renews once with a revised scope, and the founder decides then whether the interim arrangement is still solving a gap or quietly becoming the company’s plan. The difference between the two is whether decision rights and documentation have kept improving or frozen in place.

The handoff is also the moment to judge whether the engagement worked, and the honest measure is capability, not outcomes. Can the team run the close without the interim lead? Does the forecast survive a month without intervention? Does the founder spend less time as the approver of everything? If yes, the structure delivered. Whether the funding conversation succeeds depends on factors no interim role controls, and a mandate that promised otherwise would have been written badly.

What to verify while the engagement runs

Progress checks work better than a single verdict at the end, and the founder can run them monthly against a short list. For Northlane, the checks are:

• The close lands on the calendar date, or the slip is explained in writing with a cause.
• The cash forecast is updated weekly, and its assumptions have not drifted from the budget’s.
• Investor updates go out on schedule with the same structure each month, including the paragraph on what went wrong.
• Decision rights have not expanded quietly; anything new the interim lead approves alone is either in the mandate or was added consciously.
• Process documentation grows with the work, so a permanent hire could pick it up at any point.

If several checks fail in the same month, the problem is usually the mandate, not the person. A vague mandate produces drift, and drift produces exactly these failures together. The founder’s response is to rewrite the one-pager with the interim lead, out loud, in one sitting, rather than to police individual symptoms.

The last check is about the founder herself, and it is the one nobody else can do. Is she approving less, delegating with clear limits, and spending her time on the business rather than as its bottleneck? An interim finance lead who does the work but leaves the founder exactly where she was has fixed the gap and not the habit, and the habit is what created the gap. The mandate, the calendar, the forecast, and the handoff all exist so that when the engagement ends, the company runs on structures rather than on whoever happened to be sitting in the seat.