Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
9
9600634
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Issues 3
    • Issues 3
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
  • Kristy McClean
  • 9600634
  • Issues
  • #2

Closed
Open
Opened Oct 22, 2026 by Kristy McClean@kristymcclean
  • Report abuse
  • New issue
Report abuse New issue

Interim CFO first month transition planning: set the mandate


An interim cfo interim's first month works best when the mandate is written down before the work starts. In practice, interim CFO first month transition planning means deciding, in the first days, which decisions the interim leader owns, which ones they only advise on, and which ones stay with the founder or the board. Get that wrong and the rest of the engagement drifts.


Most founders I talk to bring in an interim CFO because something is pressing: a financing conversation, a cash squeeze, a leadership gap after a departure, or a transaction that needs a clean set of numbers. The temptation is to hand over "finance" as a whole and hope the person figures out the priorities. That usually produces a month of activity without a clear result.


The fix is unglamorous. Before the first week ends, you want a short document that says what the Interim CFO for strategic Finance CFO is accountable for, what they can decide alone, what needs your sign-off, and what the first ninety days should produce. Everything else in this guide builds on that.

Why the mandate comes before the work plan


A mandate is the boundary around the job. It answers a question most founders skip: when the interim CFO makes a call, is that call final, or is it a recommendation? Without an answer, every decision becomes a negotiation, and the finance function slows down exactly when you need it to speed up.


I have watched engagements stall because the interim CFO assumed authority over vendor payments while the founder still wanted to approve anything above a threshold. Neither person was wrong. Nobody had written the rule down, so each payment turned into a small argument.


The mandate also protects the interim CFO. If they are accountable for cash forecasting but cannot see the sales pipeline, the forecast will be weak and they will get blamed for it. Naming the inputs they need is part of the same conversation.


Think of it as the difference between hiring a contractor to renovate a kitchen and hiring one to redesign the house. Both are useful. Only one of them should be knocking down walls without asking. The mandate tells everyone which job this is.


The next question is what actually belongs in that document. It is shorter than most people expect, and it should fit on a page or two.

What belongs in a written mandate


A useful mandate covers five things: scope, decision rights, near-term priorities, reporting lines, and the definition of done. If any of those is missing, you will end up improvising it later, usually in the middle of a disagreement.


Scope is the list of work the interim CFO owns. It might be cash flow forecasting, the monthly close, investor reporting, and preparation for a financing round. It should also say what is out of scope, because the out-of-scope list is what stops the role from expanding into every operational problem in the company.


Decision rights are the part founders most often leave vague. A simple three-column split works well:

Decides alone: the interim CFO can act without asking, within a stated limit. Decides with you: joint call, usually on spending, hiring, or commitments to lenders. Recommends only: the interim CFO prepares the analysis, you or the board decide.


Near-term priorities should be three to five items, ranked. Not a wish list. If everything is a priority, the interim CFO will default to whatever is loudest that week, which is rarely what matters most.


Reporting lines matter more than they look. Does the interim CFO manage the controller and the bookkeeper, or just advise them? Does the role report to the founder, the board, or both? Ambiguity here creates two chains of command and a lot of quiet frustration.


Finally, define what done looks like. For some engagements it is a clean forecast model and a set of investor-ready reports. For others it is a completed transaction or a permanent CFO hired and onboarded. Write it down, because it shapes every priority decision in between.

Separating preparation from negotiation and closing


Funding work has three phases, and they need different things from an interim CFO. Preparation is analytical. Negotiation is about trade-offs and terms. Closing is about diligence, documentation, and follow-through. Mixing them is a common source of wasted effort.


In preparation, the interim CFO builds the forecast, cleans up the historicals, and assembles the story behind the numbers. This is where most of the value sits, because a lender or investor will probe the assumptions long before they discuss price.


Negotiation is where the founder usually leads and the interim CFO supports. The interim CFO's job is to keep the numbers straight, model the scenarios, and flag when a term quietly changes the economics. They should not be the one making the emotional case for the business.


Closing is operational. Diligence requests arrive in waves, documents need versions, and someone has to track what was sent and what is still outstanding. An interim CFO who has run this before will have a checklist ready rather than building one under pressure.


The mistake is treating these as one long blur. A founder who starts negotiating terms before the forecast is defensible will end up renegotiating later, and that costs credibility with the other side.

Common mistake: treating debt and equity as interchangeable


They are not, and the difference shows up in the mandate. A loan has a repayment schedule, covenants, and a lender who cares about coverage ratios. Equity has dilution, governance, and investors who care about growth and exit. The interim CFO's priorities shift depending on which one you are pursuing.


When the path is debt, the interim CFO spends early time on cash flow forecasting, working capital, and the metrics a lender will test. They need to know how much cushion exists if revenue slips, and they need the numbers to hold up under scrutiny.


When the path is equity, the emphasis moves toward the story, the growth model, and the reporting package investors expect. The forecast still matters, but the questions are different: how the business scales, what the unit economics look like, and where the next dollar of revenue comes from.


Some companies run both tracks at once, which is legitimate but demanding. It requires the interim CFO to keep two sets of assumptions and to be honest about which one is more likely to close. Blurring them produces a pitch that satisfies neither audience.


The correction is simple: name the path in the mandate, and revisit it if the path changes. If you start with debt and pivot to equity, that is a mandate change, not a detail.

Common mistake: letting the role expand without limits


Interim finance leaders are often competent generalists, which makes them easy to overload. A founder who is short on operational help will start routing HR questions, vendor disputes, and pricing decisions to the interim CFO. It feels efficient. It is not.


Every hour spent on something outside the mandate is an hour not spent on the forecast, the close, or the investor package. The role quietly becomes a catch-all, and the original priorities slip without anyone noticing until a deadline is close.


The correction is to keep a visible list of what is in scope and to route everything else somewhere explicit. That might mean deferring it, assigning it to an operations lead, or accepting that it will not get done this quarter. All three are better than silent scope creep.


There is a version of this that is legitimate: a founder may deliberately expand the mandate after the first month, once the core work is stable. That is a decision, made on purpose, with the trade-off understood. It is different from drift.


If you are unsure whether something belongs, ask whether it serves the definition of done you wrote down. If it does not, it is probably a separate conversation.

Setting priorities for the first thirty days


The first month should produce a small number of concrete things, not a broad assessment. Founders often expect a diagnostic report. What they usually need more is a working forecast, a clear view of cash, and a short list of risks.


A reasonable first-month output looks like this:

A cash flow forecast with named assumptions and a clear update cadence. A review of the monthly close: how long it takes, what is manual, where errors creep in. A short list of the biggest financial risks, ranked by likelihood and impact. A first draft of the reporting package for investors or lenders. A written mandate, signed off by whoever owns the decision.


Notice that none of these is a strategy document. Strategy matters, but it is hard to discuss credibly before the numbers are trustworthy. The first month is about establishing a baseline everyone can agree on.


The interim CFO should also be meeting people: the controller, the sales lead, the operations manager, whoever holds the information the forecast depends on. A forecast built in isolation will miss the pipeline reality and get discounted by everyone who knows better.


By the end of the month, you should be able to answer a simple question: if revenue came in lower than planned next quarter, what would we do? If nobody can answer that, the first month did not finish its job.

How decision rights work in practice


Decision rights sound abstract until a real choice lands on the desk. A vendor wants a deposit. A customer asks for extended terms. A lender requests a covenant waiver. Who decides, and how fast?


A practical split assigns thresholds. Below a certain amount, the interim CFO decides and informs. Above it, the founder decides with the interim CFO's analysis in hand. For anything touching lenders, investors, or long-term commitments, the board is usually involved.


The thresholds themselves matter less than having them. A company that decides case by case will be slower and will produce inconsistent outcomes, which is confusing for everyone downstream.


One nuance: the interim CFO should have clear authority over the finance function's own operations, including how the close runs, what tools are used, and how reports are formatted. Micromanaging that from the founder's seat defeats the purpose of bringing someone in.


Review the split after the first month. Some thresholds will turn out to be too low, creating bottlenecks. Others will be too high, creating surprises. Adjusting them is normal and should not be treated as a failure of the original plan.

Connecting finance work to operating routines


A forecast that lives in a spreadsheet and never touches the operating rhythm is decoration. The interim CFO's work has to plug into how the company already runs: the weekly leadership meeting, the sales pipeline review, the hiring plan.


The simplest connection is a recurring cash review. Once a week or once a month, the interim CFO walks through actual cash against forecast, explains the variance, and updates the outlook. It takes thirty minutes and prevents most surprises.


The second connection is the reporting calendar. If investors expect a monthly package, the close has to finish early enough to produce it. That constraint shapes how the finance team works and often exposes manual steps worth fixing.


The third is the budget or plan itself. If the company sets targets, the interim CFO should own the financial model behind them and be able to explain how the targets translate into spending and hiring.


Where these connections are missing, finance becomes a separate world that reports history while the business makes decisions on gut feel. That gap is usually what prompted the interim hire in the first place.

Knowledge transfer and the handoff to permanent leadership


An interim role has an end, and the mandate should say what gets handed over. The goal is that a permanent CFO, or the founder, can pick up the work without rebuilding it from scratch.


What to transfer:

The forecast model, with assumptions documented and a short guide to updating it. The reporting package and the calendar that produces it. The list of open risks and where each one stands. Relationships with lenders, auditors, and key vendors, introduced rather than dropped. A written summary of what was fixed, what was deferred, and why.


Transfer should start before the last week. Waiting until the end produces a rushed handover and a permanent hire who spends their first month reverse-engineering decisions.


If the interim CFO is helping hire their replacement, they should be clear about the trade-off: they can help define the role and screen candidates, but they should not be the only voice, since they have an interest in the shape of the job.


A clean handoff is also the best evidence that the engagement worked. If nothing can be transferred, the work was probably too dependent on one person.

Assessing progress without assuming results


You cannot promise a financing round will close or that cash will improve on a schedule. What you can assess is whether the work is on track: are the deliverables appearing, are the assumptions documented, are decisions getting made faster?


Useful signals to watch:

The forecast updates on the agreed cadence, and variances are explained rather than ignored. The close finishes closer to the target date than it did before. Decisions that used to stall now have a clear owner and a recorded outcome. Investors or lenders stop asking for information the company should already have. The founder spends less time assembling numbers and more time on the business.


These are process signals, not outcome guarantees. A company can do all of this and still face a difficult market. The point is to know whether the finance function is getting stronger, independent of how any single negotiation turns out.


Review progress at the end of the first month and again at ninety days. If the signals are weak, the mandate is the first place to look, because a vague mandate usually produces vague work.

The most costly mistake: leaving the mandate unwritten


The single most expensive error in an interim CFO engagement is starting without a written mandate. It does not feel expensive at the time. Everyone is aligned in the first meeting, the priorities seem obvious, and writing it down feels like bureaucracy.


Then the first real disagreement arrives. A payment the interim CFO approved gets questioned. A forecast assumption gets overridden without the model being updated. A priority shifts because a board member raised something else. None of these is dramatic on its own, and together they erode the engagement.


The cost shows up as wasted weeks. The interim CFO rebuilds work that was redirected, the founder loses confidence, and the finance function ends up roughly where it started, minus the fee.


Avoiding it takes an hour. Write the scope, the decision rights, the three to five priorities, the reporting line, and the definition of done. Have the person who owns the decision sign off, whether that is the founder or the board.


Then revisit it at thirty days. Mandates change as companies learn, and a revision made deliberately is a sign the engagement is working, not that the original plan failed. The document is the point of reference that keeps the first month, and every month after it, aimed at something specific.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: kristymcclean/9600634#2