Resources

At the earliest stages of a company, finance is one job held by one person. A bookkeeper, or sometimes a founder with a spreadsheet and a Gusto account, handles payroll, tracks expenses, files taxes, and produces something resembling financial statements at the end of each month. The work is varied and the lines between functions are deliberately blurred because there are not enough hours or budget to draw them.

Picture a board meeting six months into your Series A. You have good revenue numbers: ARR is up, the sales team is executing, and the quarter looked solid in the summary slide. Then your lead investor asks: “If enterprise sales slip 15% in Q3, what does that do to your runway, and how does it change your hiring plan for the back half of the year?” You open a spreadsheet. You scroll. You say you’ll follow up.

Early-stage companies make tooling decisions under pressure. There is a month-end close to get through, an investor asking for a report, a new hire who needs system access on day one. In that environment, the question is almost never “what is the best long-term infrastructure decision here” — it is “what works well enough right now.”

For a long stretch, the phrase “path to profitability” did a lot of heavy lifting in startup circles. It became shorthand for seriousness — a signal that a company understood the difference between growth and sustainability. Investors asked about it. Boards tracked it. Founders built their narratives around it.

The traditional image of a CFO — guardian of the balance sheet, approver of spend, preparer of financials — reflects a version of the role that has been functionally obsolete for some time. In modern operating environments, especially at venture-backed companies scaling through early growth stages, the CFO’s value is determined far less by technical accounting competence than by organizational influence.

Most companies reach a point where waiting on financials becomes routine. “We’ll have numbers soon” stops being a temporary explanation and starts being an operating assumption. Teams plan around it, leadership works around it, and everyone quietly adjusts to running decisions on information that is days or weeks old.