Resources

There’s a particular kind of investor meeting where a founder presents a revenue forecast and the room goes quiet in the wrong way. The numbers are ambitious but not unreasonable. The growth curve looks compelling. And then someone asks a question, “walk me through how you got to that Q3 number,” and the answer reveals that the model was built backward from a desired outcome rather than forward from the actual mechanics of the business.

Most venture-backed startups have something that functions as a financial model. A budget, a burn tracker, maybe a pitch deck with a revenue forecast that was built during the last fundraise and has not been meaningfully updated since. The founders know the burn rate. They have a sense of runway. They can pull up last month’s P&L.

There is a moment in nearly every fundraise where a founder realizes, too late, that the conversation has gone sideways. The metrics are there. The growth is real. But something in the room has shifted…a follow-up question that is a little too pointed, a pause before a response, a request to revisit an assumption that felt settled. The numbers looked good. The story they told was something else entirely.

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.”