Будьте внимательны! Это приведет к удалению страницы «Interim CFO defining a successful exit: mandate questions».
Most owners preparing for a sale treat the interim CFO as a hired hand for the numbers, and that mistake costs them at the worst possible moment. In practice, interim CFO defining a successful exit work is really about deciding who holds which decisions before buyers start asking. Skip that step and you get clean financials attached to a business that still can't explain itself under pressure.
Treating the mandate as a job title instead of a set of decisions
The first mistake is hiring for a label. An owner decides they need "a CFO" and starts comparing résumés, when the real question is which decisions are currently stuck. If you can't name three decisions that keep landing on your desk and shouldn't, no title will fix that.
Think about what actually stalls in a business heading toward a sale. Pricing exceptions that only you approve. A bank covenant question nobody owns. A customer contract renewal that needs a financial read before you sign. Those are decisions, not job descriptions, and they tell you what the mandate has to cover.
Write them down before you talk to anyone. A simple list works: the decision, who makes it today, who should make it, and what information that person needs. If the list is short, you may not need interim leadership at all. A bookkeeping cleanup or a controller might be enough.
The consequence of skipping this step is predictable. You bring in someone senior, they spend the first month figuring out where they're allowed to act, and the transaction clock keeps running. Buyers don't pause while you sort out internal authority.
There's a second layer here that owners often miss. The mandate has to survive contact with your existing team. If your controller has been making the calls for years, an interim CFO who overrides them without a clear handoff creates friction that shows up in the data room as inconsistency.
One more thing worth doing before you write the mandate: separate the decisions that are urgent from the ones that are merely important. A covenant question with a deadline next month is urgent. Rethinking your pricing architecture is important and can wait until after the transaction. Mixing the two produces a mandate that tries to do everything and finishes nothing.
Confusing decision rights with decision influence
Decision rights and decision influence are different things, and interim chief financial officer mixing them up is where most mandates go soft. Rights mean the interim CFO can commit the company: sign off on a forecast, approve a payment run, agree to a covenant waiver. Influence means they shape the answer but you still decide.
Both are legitimate. The problem is when nobody says which is which. An interim CFO who assumes rights they don't have will make commitments your team then has to unwind. One who only has influence will produce recommendations that sit in a folder.
Sort it by category rather than by person. Some areas usually belong with the interim CFO during a transaction: the forecast model, the working capital schedule, the quality-of-earnings preparation, the investor reporting calendar. Others usually stay with you: pricing strategy, key hires, anything that changes the shape of the business.
Put it in writing, even if it's a page. Something like this:
Forecast and cash model: interim CFO owns the numbers, you own the assumptions. Bank and lender conversations: interim CFO leads, you attend the ones that matter. Customer contract terms: interim CFO advises, you decide. Spending above an agreed threshold: interim CFO approves within the plan, you approve outside it. Hiring in finance: interim CFO recommends, you decide.
That list does more for a successful exit than any org chart. When a buyer's diligence team asks who approved a given transaction, you want a clean answer, not a shrug.
There's a practical test for whether the split is working. Ask yourself how often you've had to reverse a decision the interim CFO made. If the answer is never, you may have given them too little authority and they're just producing analysis. If it's often, the boundaries weren't clear enough. A healthy mandate produces reversals rarely, and when they happen, everyone understands why.
Authority also has a time dimension. Some rights should be temporary and tied to the transaction, like approving adjustments to the earnings presentation. Others should outlast the engagement, like the reporting calendar that your permanent team will keep using. Deciding which is which at the start saves an awkward conversation later.
Setting the first 30 to 90 days around deliverables, not activity
The first weeks should produce things a buyer will eventually read, not a flurry of meetings. Owners often judge this period by how busy the interim CFO seems. Judge it by what exists at the end that didn't exist before.
A reasonable first month produces a cash forecast you actually trust, a list of the accounting questions that need answers before diligence, and a clear view of which months are tight. That's it. Not a strategy deck.
The second month usually turns to the story. How does revenue actually behave, which customers carry the margin, what does a normal month look like versus a good one. This is where an interim CFO earns their keep, because buyers pay for predictability, and predictability comes from understanding the drivers.
By the third month you should have a working quality-of-earnings view, a documented set of adjustments, and a reporting package that doesn't require three people to assemble. If you're past day ninety and still explaining basic numbers, the mandate is behind.
One caution: don't let the deliverables list become a wish list. Five items done well beats fifteen started. The point is to reach the point where an outside party can look at your numbers and reach the same conclusions you do.
It helps to write the deliverables as sentences a stranger could check. "A thirteen-week cash forecast updated weekly, with the top ten customers modeled individually" is checkable. "Better cash visibility" is not. The same discipline applies to the accounting questions: list them as questions with owners and target dates, not as a topic called "cleanup."
Watch for the moment the work shifts from building to maintaining. Once the forecast is reliable and the reporting package runs on its own, the interim CFO's time should move toward the transaction and the handoff. If they're still rebuilding the same spreadsheet in month four, something upstream is broken.
Leaving the connection to operating routines until later
Strategic finance work that never touches the operating routine is decoration. The forecast has to connect to how you actually buy inventory, bill customers, and pay people. If it doesn't, it will be wrong within a month and nobody will notice until it matters.
In practice, this means the interim CFO sits inside a few recurring meetings rather than reporting from the outside. The weekly cash review, the monthly close, the sales pipeline conversation. Not to run them, but to make sure the financial read is present when decisions get made.
There's a real tension here. Owners sometimes want the interim CFO kept away from operations so the team isn't disrupted. That instinct is understandable and usually wrong. A forecast built in isolation from the people who generate the numbers is a guess with a spreadsheet around it.
The fix is narrow. Pick two or three routines where financial information changes a decision, and put the interim CFO in those. Leave the rest alone. You're not reorganizing the company; you're making sure the money view shows up where it's needed.
This is also where you find out whether the mandate is working. If the operating team starts asking the interim CFO questions without being prompted, the connection is real. If they route around them, it isn't.
Consider what happens when the connection is missing. A large order gets accepted on terms that stretch working capital, and nobody flags it until the cash forecast breaks. The sale doesn't fail because of the order. It fails because the business couldn't see the consequence coming, and a buyer will notice that gap during diligence.
Assuming the buyer will accept your reporting as-is
Buyers and lenders read financial information through their own standards, and those standards are not yours. A reporting package that satisfies you may raise questions the moment someone else opens it. Preparing for that is part of the mandate, not an afterthought.
Revenue recognition is the classic example. Under ASC 606, the timing of when you record revenue depends on performance obligations and how contracts are structured. If your current practice has drifted from that, diligence will find it, and the conversation shifts from price to credibility.
The same applies to how you present one-time items, how you treat owner compensation, and how you describe customer concentration. None of these are dishonest by default. They're just presented in a way that made sense internally and doesn't travel well.
An interim CFO's job here is to build the bridge before anyone asks. That means a version of the numbers that follows recognized conventions, plus a clear reconciliation back to what you've been reporting. Two views, one story.
If your business operates in regulated areas, quality standards like ISO 9001 can also come up, not because a buyer cares about certification itself, but because it signals whether processes are documented and repeatable. The financial equivalent is having your close process written down.
Owner compensation deserves its own pass. Many small businesses pay the owner through a mix of salary, distributions, and expenses that blur together. A buyer will normalize all of it, and if you haven't done that work first, the adjustment lands as a surprise. Better to present the normalized figure yourself, with the reasoning attached.
Customer concentration is the other one that catches owners off guard. If a handful of customers drive most of the revenue, that's a fact, not a flaw. What matters is whether you can show the history, the contract terms, and the retention pattern. An interim CFO who prepares that view turns a difficult question into a routine one.
Letting the handoff to permanent leadership stay vague
Interim means it ends, and the ending is part of the mandate. Owners often leave the handoff undefined, which means knowledge walks out the door with the person who built it. That's a real loss, and it's avoidable.
Start by deciding what permanent looks like. A full-time CFO, a controller stepping up, a fractional arrangement that continues. Each answer changes what the interim period should produce. If a controller is taking over, the systems and documentation matter more than the strategy work.
Then decide what gets transferred and how. Not "everything in their head," but specific things: the forecast model and its assumptions, the diligence file, the list of open accounting questions, the relationships with your bank and your accountant.
A simple transfer plan looks like this:
Name the person who takes over each workstream. Have them run it alongside the interim CFO for a full cycle. Document the assumptions behind the forecast, not just the output. Introduce them to the outside parties who matter. Set a date when the interim CFO stops being the default answer.
The last item is the one people skip. Without it, the interim CFO stays on speed dial and the permanent person never fully owns the work. That's comfortable and it's a problem.
Documentation is where handoffs usually fail. A forecast model with hardcoded numbers and no notes is not transferable, even if it works. The test is simple: can the person taking over change an assumption and explain what happened to the output? If not, the model belongs to one person, and that person is leaving.
Relationships transfer the same way. An introduction from the interim CFO to your bank contact, with a short note on what's been discussed, does more than a list of names. The goal is that your permanent finance lead walks into those conversations already known, not starting from zero.
Measuring progress without pretending you know the outcome
You can't measure an interim CFO by whether the business sells, because too much of that sits outside anyone's control. What you can measure is whether the finance function is more useful than it was. That's a fair test and it's observable.
Look at how long it takes to answer a basic question about the business. If a lender asks about your cash position in a bad month and the answer takes a week, that's a signal. If it takes an hour, something changed.
Look at whether the forecast has been wrong in ways you understand. A forecast that misses because a big customer paid late is fine if you saw it coming. One that misses because nobody was watching is not.
Look at whether decisions are getting made faster. Not recklessly, but without the usual circling. When the financial read is available and trusted, conversations shorten.
And look at whether your team can explain the numbers without the interim CFO in the room. That's the real test of transfer, and it's the one that predicts how the next phase goes.
It also helps to check the mandate itself at a fixed point, say every month. Are the decisions you listed at the start actually moving? Has anything new landed on your desk that shouldn't have? Is the interim CFO spending time on the transaction or on maintenance? Those three questions take ten minutes and tell you whether to adjust course.
What you shouldn't do is grade the engagement on the sale price or the closing date. Those depend on the market, the buyer, and timing you don't control. Grading on them turns a useful mandate into a scapegoat when things move slowly.
Deciding what stays with you no matter what
Some decisions should never leave the owner's hands during a transaction, and knowing which ones keeps the mandate healthy. The interim CFO can inform all of them. They should own none of them outright.
Anything that changes the shape of the business belongs to you. Selling a product line, exiting a customer, hiring a senior leader, agreeing to an earnout structure. These are judgment calls about your future, and delegating them to someone who will be gone in six months is a mistake.
Relationships with your key people are the same. An Interim Chief Financial Officer CFO can help you think through a compensation question, but the conversation with your long-time operations lead is yours. Handing that off signals something to the team that you probably don't intend.
What you can hand over freely is the machinery: the models, the reporting, the diligence preparation, the lender conversations, the accounting questions. That's where the interim CFO adds the most and where the handoff matters most.
The line isn't always obvious, and it shifts as the engagement progresses. Early on, you may want to keep more. As trust builds and the numbers prove reliable, you can let go of more of the machinery and focus on the decisions only you can make.
A worked example: a distributor preparing for a sale
Picture a hypothetical distribution business with steady revenue and a founder who has run the finances personally for years. A buyer has expressed interest, and the founder decides to bring in interim CFO support. Here's how the mandate questions play out.
First, the decisions. The founder lists what keeps landing on their desk: approving customer credit terms, deciding when to draw on the line of credit, and signing off on the monthly numbers. Those three become the core of the mandate, with credit terms staying with the founder and the other two moving.
Next, the first ninety days. Month one produces a cash forecast tied to the actual payment behavior of the top customers. Month two maps the margin by product line, which nobody had done. Month three builds a quality-of-earnings view and a reporting package a buyer could read without a guided tour.
Then the operating connection. The interim CFO joins the weekly cash meeting and interim chief financial officer the monthly close review, and nothing else. Within a few weeks, the operations lead starts asking about the cash impact of a large order before committing to it. That's the signal the connection took.
Finally, the handoff. The controller, who has been there for years, takes over the forecast and the reporting package, running both alongside the interim CFO for two full cycles. The bank relationship transfers with an introduction. A date gets set for when the interim CFO stops being the default call.
None of this guarantees a sale, and it isn't meant to. What it produces is a business that can answer questions quickly, explain its own numbers, and hand the finance function to whoever comes next. That's what a well-defined interim mandate is for, and it's the part you control.
Будьте внимательны! Это приведет к удалению страницы «Interim CFO defining a successful exit: mandate questions».