Getting Answers Out of a CFO Without Wasting Everyone's Time
A CFO review meeting doesn't go well when you show up with a generic list of questions pulled from a LinkedIn article. It falls apart even faster when you bury the lead under polite small talk. The people who get useful answers have a system, and it's not particularly glamorous. I put together what I call the Questions For A Cfo framework after watching about thirty due diligence sessions go sideways because someone asked about revenue growth before understanding unit economics. The framework is essentially a categorized question bank organized by priority tiers, decision context, and time pressure. You don't use all of it. You pick the section that matches your actual situation and drill down from there.
Questions For A Cfo: How the Framework Actually Works
At its core, the framework splits questions into four buckets. Revenue and cash flow sit at the top because they answer whether the business survives. Margin structure comes next because it explains sustainability. Capital allocation and debt matter when you're evaluating growth strategy or restructuring. The fourth bucket covers risk and compliance, which people skip until something breaks. I built the first version in a Google Sheet with conditional branching logic. If the CFO mentions negative operating cash flow, the next recommended question automatically shifts from growth metrics to working capital cycles. That part alone saved me from wasting time on topics that were already irrelevant. Here's a concrete example from a project last year. We were evaluating a Series B startup for potential investment. The founder kept talking about market size and customer acquisition. I pulled the framework and went straight to bucket one, question seven: "What is the cash conversion cycle and how has it changed over the last four quarters?" The CFO hesitated for three seconds, which told us everything we needed to know. We asked about the receivables aging schedule next. It turned out they had ninety-day terms with no collection process, and the numbers didn't lie. We walked away from the deal. That happened because the framework forced us to ask the uncomfortable question early instead of getting swept up in the pitch.
How to Use This When You Actually Need It
Most people treat the framework as a script. That's wrong. It's a checklist you customize based on three variables: the company's stage, your relationship to the CFO, and what decision you're actually trying to make. A venture capitalist evaluating an early-stage company needs different questions than a department head asking for budget approval. The overlap is smaller than you'd think. When you're the one asking questions, lead with the hardest one first. CFOs are trained to deflect. If you start with easy questions like "How is the quarter tracking?" you get the polished answer everyone prepared. Lead with something specific and slightly uncomfortable like "Walk me through the difference between GAAP revenue and cash collected in the most recent quarter." You'll either get a direct answer or a reaction that tells you something useful either way. I've seen people spend twenty minutes prepping questions from the framework and still miss the point because they didn't research the company's last two earnings calls. The framework assumes you've done the homework. It won't compensate for ignorance. Read the SEC filings. Look at the balance sheet. Know the company's actual numbers before you open your mouth. Otherwise you're just asking a CFO to do your due diligence for free.
Get the Full Details
There's a specific edge case that trips people up constantly. When the CFO is also the founder, the questions change dramatically. Founders answer emotionally. They'll volunteer information you didn't ask for and bury the actual answer somewhere in a ten-minute story about their childhood. I learned this the hard way during a merger discussion where the CFO-founder spent twenty minutes explaining the company's origin mission before I got a single sentence about debt covenants. I had to stop him and say "I need the covenant details before we talk about anything else." He was annoyed but he gave me what I needed. The lesson was simple: with founder-CFOs, be more aggressive about steering the conversation back to specifics.
Common Mistakes That Make This Framework Fail
Asking too many questions in a single session is the biggest one. A CFO can handle about twelve substantive questions before the answers start degrading in quality. After that, you're getting rehearsed talking points instead of honest information. I cap my sessions at ten questions and leave the rest for follow-up emails or a second meeting. The extra answers you get from pacing yourself are worth more than the volume. Another mistake is asking questions that have yes-or-no answers. "Is cash flow positive?" is a terrible question. "Describe the components of cash flow from operations for the last eight quarters and what drove the variance in Q3?" is a workable one. The difference matters because CFOs will pivot on yes-no questions but have to actually think on open-ended ones. That thinking creates the gap where useful information leaks out. The framework also doesn't work well when you're dealing with a public company's IR team instead of the actual CFO. Those conversations follow a script. The questions-for-cfo structure assumes you have access to someone who controls the numbers, not someone who communicates them. If you can't get a real CFO on the phone, adjust your approach entirely and focus on publicly available filings rather than live Q&A.
What This Framework Can't Do
It won't help if the CFO is actively lying to you. No question bank compensates for deliberate fraud. I encountered this once with a company that was capitalizing expenses that should have been written off. The framework got me to ask about R&D spend trends and depreciation schedules, but the actual misreporting was hidden in the notes to the financial statements where no standard question template reaches. You need forensic accounting skills for that level of problem. The framework gets you to the door. It doesn't open it. It also struggles with extremely early-stage companies that don't have structured financial data. If a startup has three months of bank statements and a pizza receipt for "team dinner," none of the framework's questions are meaningful. In those cases, you pivot to personal references and founder track record instead. The framework has a boundary condition built into it: it requires a minimum of twelve months of financial history to function properly. If you want to use this right now, the framework is organized as a spreadsheet with dropdown menus for company stage, meeting type, and desired outcome. Each combination generates a filtered question set tailored to your situation. You can find it at questionsforcfo.com and it updates quarterly as I add new scenarios based on recent deals and board meetings.
The real value isn't the questions themselves. It's the structure that forces you to think about what you actually need to know before you walk into the room. Most people skip that step and hope the right questions come up organically. They don't.
