The criterion that separates an interim cfo supporting a permanent cfo from other finance hires is ownership of decisions. The arrangement works when the interim executive owns defined deliverables while the permanent CFO keeps decision rights. One needs hands to finish specific finance work; the other needs room to lead. If both claim the same decisions, it stalls.
In practice, the arrangements that survive are the ones where nobody has to guess who decides what. The permanent CFO owns the financial direction of the company: the annual plan, the capital structure, the hiring of the finance team, the story told to the board. The interim executive owns a bounded piece of work that would otherwise sit unfinished, such as rebuilding the cash forecast, cleaning up working capital, or getting reporting ready for a lender.
That split sounds obvious, and yet most friction in these setups comes from skipping it. A permanent CFO who has been in the seat for six months usually has a plan. An interim arrives with momentum and pattern recognition from other companies. Without a written line between them, both drift into the other’s lane, and the team ends up taking direction from two people on the same spreadsheet.
The cleanest version puts it in one sentence: the permanent CFO decides, the interim executive delivers. There are exceptions, and you should name them in advance rather than discover them mid-project. For example, if the interim CFO for Manufacturing companies is rebuilding the forecast, does she choose the forecasting tool, or does she recommend and the CFO approves? Either answer works. What fails is leaving it open.
A useful test before signing anything: list the ten decisions the engagement will touch. Budget revisions, vendor selection for finance software, collection policies, board reporting format. Next to each, write one name. If you can’t fill the column, the mandate isn’t ready.
This matters more in this pairing than in a straightforward interim placement, where the interim simply holds the seat. Here two senior people share a function, and senior people don’t naturally yield. The structure has to do the yielding for them.
A mandate is not a job description. It is a short document that answers four questions: what the interim executive delivers, what she decides on her own, what she recommends before someone else decides, and what stays entirely with the permanent CFO. One page is enough. In practice, the companies that skip this page spend the first month renegotiating scope in meetings that should have been about the work.
Start with deliverables, and make them concrete enough that done means done. ”Improve forecasting” is not a deliverable. ”A rolling 13-week cash forecast, refreshed weekly, reviewed with operations every Monday” is. The difference matters because the permanent CFO will be asked, by the board and by her own team, what the interim is actually producing.
Decision rights deserve their own section in the mandate, with three tiers. Tier one, the interim decides alone: the layout of a model, the agenda of a forecast review. Tier two, the interim recommends and the permanent CFO approves: changes to reporting that the board sees, policies affecting other departments. Tier three, the permanent CFO decides and the interim contributes: financing strategy, targets, anything that outlives the engagement.
Include an expiry date or a trigger. Interim mandates tied to a permanent CFO make sense for a defined period or a defined problem, and the document should say which. ”This mandate ends when the 13-week forecast has run for two full quarters and the controller owns the update” gives everyone a finish line.
Two practical details get skipped and cause trouble later. First, say how the two finance leaders communicate: a standing weekly meeting, not ad hoc hallway updates. Second, say what the interim says to the team and to the board, so nobody invents their own explanation of why there are two CFO-level people in the building.
The case that justifies adding a second senior finance person alongside permanent leadership is a spike in work that needs senior judgment, not just hours. Some situations fit that shape better than others, and it helps to be honest about which one you’re in.
It tends to be worth it when several of these are true at once:
Consider a hypothetical: a wholesale distributor with about four months of runway pressure during a seasonal inventory build. The permanent CFO is negotiating a credit line with the bank. In practice, that person cannot also rebuild the 13-week cash forecast, chase receivables aging, and renegotiate payment terms with the three largest suppliers. An interim executive who does exactly that, reporting to the CFO, keeps the bank conversation from being sabotaged by a missed payroll projection.
The pattern across these cases is the same: the permanent role keeps its full authority, and the interim absorbs a block of work whose output the permanent CFO would otherwise have to produce personally. Nobody’s job shrinks. The function’s throughput doubles for a period.
Notice what is not on the list: ”the finance team feels overwhelmed.” That feeling is often real, but it is a symptom. Before adding senior firepower, check whether the actual bottleneck is scope, tools, or a missing mid-level hire. Sometimes a controller and a better close checklist solve what looks like a CFO problem.
The same arrangement turns into an expensive standoff under conditions that are easy to spot in advance. The most common one is a permanent CFO who has not actually accepted the idea. If she sees the interim as an audit of her performance, every deliverable becomes a negotiation, and you pay senior rates for friction.
It is also not worth it when the problem is a vacancy, not a supplement. If the company has no permanent CFO and needs leadership, that is a straightforward interim placement with full authority, or an urgent permanent search. Interim cfo supporting a permanent cfo is a specific structure, and forcing it onto a different problem creates two deputies and no leader.
Scope mismatch is another disqualifier. If the real need is bookkeeping cleanup, a tighter close process, or sales tax filings, that is accounting work, and hiring a CFO-level person to do it wastes money and insults the actual problem. In practice, many small businesses that think they need finance leadership actually need a stronger controller and a disciplined monthly close. The lens test: if the work produces no decisions, it probably is not CFO work.
Be skeptical when the rationale is vague. ”Extra strategic firepower” is not a mandate. If nobody can name the three deliverables due in the first month, the engagement will drift into meetings, opinions, and invoices. Also be skeptical of arrangements where the interim reports around the permanent CFO, say directly to the CEO or board. That structure can work in a turnaround, but in a supplement scenario it tells the permanent CFO she has been sidelined, and the information flow through the finance function splits in two.
The economics also have to clear a low bar that people forget to check: the deliverables should be worth more than the cost, and ”worth more” means something you can point to, like a credit line secured on time or a collection process that shortens the cash cycle. If the value case rests on intangibles alone, wait.
Ninety days is a fair horizon to expect visible output, and it helps to know what good output looks like so you can tell progress from activity. The exact list varies with the mandate, but strong engagements tend to include a version of the following.
In the first month, expect a diagnosis written down: the state of the forecast, the close, working capital, and reporting, with the two or three problems that actually constrain the function. Expect the first version of the deliverable named in the mandate, rough but real. A 13-week cash forecast in week four, imperfect, beats a beautiful one in month six.

In the second month, expect the routines to form: the weekly forecast refresh, the Monday review with operations, the close calendar with owners. This is the part most often skipped, and it is the part that makes the work outlive the engagement. A model nobody updates is a document, not a capability.
By the third month, expect the permanent CFO to be using the output in real decisions: a hiring choice informed by the forecast, a supplier negotiation armed with the payables aging, a board pack that answers cash questions before they’re asked. The interim’s name should be appearing less in meetings, not more, as the routines take hold.
![]()
Watch for the reverse signal. If at ninety days the interim is still ”getting up to speed,” or the deliverables keep changing shape, or the team routes simple questions through the newcomer because the mandate is unclear, stop and fix the mandate before spending another quarter. In practice, a stalled engagement rarely recovers by adding time. It recovers by narrowing scope.
Strategic finance work that never touches operations is decoration. The forecast that matters is the one the operations lead checks before ordering inventory, and the investor report that matters is the one built from numbers the team already produces monthly. A big part of the interim executive’s value is wiring these connections, because she is not the one who will maintain them.
The connection usually happens through a small set of routines. A weekly cash review where the forecast is compared to what actually happened last week, and the gap gets a name and an owner. A monthly close that ends on a fixed day, so the numbers feeding any report are trustworthy. A short operating meeting where one finance number, collections or inventory days, is on the agenda until it stops being a problem.
Hypothetical example to make it concrete: a software company where receivables sit ninety days because invoices go out late and without purchase order numbers. A forecast alone doesn’t fix that. The fix is a rule, invoices only leave without a PO at the CFO’s explicit sign-off, plus a weekly list of the ten largest overdue accounts with the account owner’s name next to each. That is an operating routine wearing a finance hat, and it moves cash more than any model.
The same logic applies to investor reporting. When the permanent CFO reports to a board, the interim’s work should make that report easier and more credible: reconciled numbers, a cash bridge that explains the movement, an early warning section for the metrics that could break the plan. The board sees one voice, the permanent CFO’s, backed by machinery the interim built.
The test for whether the connection is real: pick a number in the latest investor report and ask the operations lead where it comes from. If the answer involves a spreadsheet only one person understands, the wiring isn’t done. If the answer is a routine with a name and a date, it is.
Handoffs fail when they are treated as an event instead of a thread through the whole engagement. The interim executive who saves documentation for her final fortnight leaves behind a folder nobody reads, and the permanent CFO inherits routines she never saw built. The better pattern makes transfer part of each deliverable from the start.
Practical version: every artifact the interim produces ships with an owner and a maintenance note. The forecast has a tab explaining the assumptions and who updates what, every week. The close checklist names the person who now runs each step. Investor report sections carry a comment on where the data comes from. None of this is glamorous, and all of it is the difference between renting expertise and buying capability.
Structure helps too. Having the interim run the Monday forecast review for the first month, then co-run it with the controller the second month, then attend silently the third, transfers judgment in a way a document never will. The team learns how a senior finance person thinks about a variance, not just what the model outputs.
The permanent CFO’s role in transfer is to be a real participant, not a spectator. She should review the diagnosis, argue with the assumptions, and redirect the work when it conflicts with where she wants the function to go. That friction is healthy. It means the permanent leader is taking ownership, which is the entire point of the arrangement.
One caution: transfer cuts both ways. The permanent CFO should also be explicit about context the interim can’t see, such as board dynamics, the history behind a policy, or which department will resist a collections push. Interim CFO support works best when the newcomer gets that context in week one rather than discovering it through failed attempts in month two.
Progress in this kind of engagement is observable, and you don’t need a dashboard full of vanity metrics to see it. What you need is the discipline to define, at the start, what the deliverables are and what evidence of progress looks like for each. Then check against that definition, not against how busy the calendar looks.
Sensible evidence looks like this: the forecast ran every week for a full quarter and the weekly variance got smaller as assumptions got calibrated. The close moved earlier and fewer adjustments appeared after the fact. Collections routines produced a payables and receivables aging that finance and sales both accept as accurate. None of these are guarantees of financial outcomes, and nobody honest will promise them. They are signs the machinery works.
Be direct with candidates during selection about this distinction. Ask how they measure their own progress on a similar mandate, and listen for answers about routines installed, owners named, and documentation left, rather than answers about results they delivered for other companies in other contexts. Contexts differ; a routine that fit a software company may not fit a manufacturer. The transferable asset is the method, not the outcome.
Inside the engagement, a simple monthly review with three questions beats any elaborate scorecard: did the deliverables due this month land, do the routines run without the interim pushing them, and does the permanent CFO consider the output usable in real decisions? When the answer to the third question is yes for two consecutive months, the engagement is approaching its finish line, and the mandate’s expiry trigger should be honored.
Resist extending by default. The most expensive version of this arrangement is the one that quietly becomes permanent, with the interim doing work the permanent CFO’s team should own, at senior rates, indefinitely. If the work still needs a second senior person after two quarters, the honest question is whether it’s time for a full-time director or VP of finance instead.
The most expensive failure in this setup is leaving decision ownership undefined, because it doesn’t fail loudly. Both leaders, being capable, keep making calls. The team learns to shop for the answer it prefers. Models multiply with conflicting assumptions, the close slips because nobody accepts the calendar, and by the time the friction surfaces in a board meeting, you have paid for months of senior time and gotten a finance function that trusts itself less than before.
You avoid it with unglamorous moves made early. Write the one-page mandate with the three tiers of decision rights before the engagement starts. Review the ten-decision list together and make both leaders say the split out loud, so disagreement surfaces while it is still cheap. Give the permanent CFO visible, unambiguous authority, including the right to end the engagement. Then hold the line yourself as the owner of the business: when two answers conflict, don’t absorb the decision, send it back to the mandate.
One closing checklist you can use before signing anything:
In practice, interim CFO support alongside a permanent CFO rewards companies that treat it as a defined project with an end, and punishes those that treat it as extra leadership by the month. Start with the decisions that need making, assign each one a single owner, and the rest of the arrangement tends to fall into place.
No listing found.