Hiring a CFO is a decision founders tend to get wrong in one of two directions: hiring the title too early (a $300K executive managing a bookkeeper's workload) or hiring the capability too late (walking into a Series B raise with a model nobody senior has pressure-tested). The fix for both is the same — treat this as two separate decisions made in order. First: what CFO-level work does the company actually have, and does it fill a seat or a slice? Then, and only then: who? This guide covers both, including the interview questions that separate real startup CFOs from big-company finance executives wearing the same title.
Inventory the actual work before inventorying candidates. CFO-level work is strategy, not processing: owning the financial model and forecast, running fundraising preparation and investor relations, managing burn and runway decisions, pricing analysis, board reporting. If that list fills one or two days a week — true for nearly every startup before Series B — the economics point at a fractional engagement: senior judgment at a monthly retainer instead of $250,000–$400,000+ of compensation for a partially utilized seat. The full-time hire earns its cost when the work genuinely fills the calendar (active M&A, a finance team to build and manage, IPO runway) or when investors require a dedicated finance executive as a condition of the round. If the work you listed is mostly transactions, categorization, and closing the books — stop; you're hiring for the wrong layer, and this breakdown of bookkeeper vs. CPA vs. CFO will save you the mis-hire.
The quality of a CFO engagement is set partly before it starts. Three preparations from the merged wisdom of watching these succeed and fail: know your objectives specifically enough to scope against ("get diligence-ready by Q3," not "help with finance"); commit to transparency — a CFO working from partial information produces partial-information advice, and founders who withhold the ugly numbers get exactly the strategy those sanitized numbers deserve; and decide in advance that you'll act on recommendations or at least engage with them, because paying for judgment you routinely overrule is the most expensive way to feel validated. Add a defined communication cadence and success metrics for the first two quarters, and you've eliminated the most common failure modes before day one.
Résumés converge; answers don't. The questions that expose the difference between a startup CFO and a corporate finance executive in a startup costume:
Signals we'd treat as disqualifying, having seen the aftermath: pitching strategy services while your books are visibly broken (the honest move is fixing the foundation first — strategy on bad data is fiction with a retainer); no questions about your business model in the first conversation; fee structures untethered to defined scope; inability to name a client at your stage; and — for individual hires — a career of managing large finance teams with no evidence of ever having been the entire finance function alone. The startup CFO job is hands-in-the-spreadsheet work with executive judgment attached; candidates who've only ever delegated the hands are mis-fits regardless of pedigree.
The pattern that works, stage by stage: founder-run finances on clean bookkeeping through pre-seed; fractional CFO engaged around the first priced round or 9–12 months before a planned raise (the model and data room take that long to make diligence-grade without panic); and the full-time hire when the work fills the seat, usually Series B or beyond — at which point a good fractional relationship often converts into the search committee's best advisor. The mistake to avoid at every stage is the same one: hiring the title as a signal rather than the work as a need. If you're trying to figure out which stage you're actually at, that's the first conversation we have with every CFO client.