The First 90 Days of a SaaS CFO — What to Build in What Order

Walking into a new SaaS CFO role is simultaneously exciting and overwhelming. The problems are usually more complex than the job description suggested. The financial infrastructure is often more fragile than the previous reports indicated. The board has higher expectations than anyone communicated during the interview process. And the CEO is watching to see whether the new hire was worth the cost.

The first 90 days define whether a CFO becomes a strategic partner or gets stuck firefighting operational problems for the next two years. This post provides a concrete framework for those first 90 days.

The Mindset: Diagnose Before You Prescribe

The most damaging mistake a new SaaS CFO can make is starting with solutions before finishing the diagnosis. Coming in with a pre-built playbook and executing it regardless of what you find is a fast path to destroying credibility and fixing the wrong problems.

The first 30 days should be almost entirely diagnostic. The goal is a complete picture of:

• Financial infrastructure quality (accounting system, close process, controls)
• Data accuracy (do the reported numbers match the underlying reality?)
• Reporting gaps (what metrics are missing, wrong, or misleading?)
• Team capability (who can do what, and where are the gaps?)
• Investor and board expectations (what do they need that they are not currently getting?)

Only after that audit is complete should you prioritize what to build first.

Days 1–30: The Diagnostic Phase

Week 1: Meet Everyone

In the first week, have an introductory meeting with every person who touches finance in any way: the bookkeeper, the Controller if there is one, the CEO, every department head, and every member of the board. The agenda for each meeting is the same:

• What are you responsible for?
• What financial information do you rely on to make decisions?
• What do you currently not get from finance that you wish you had?
• What worries you most about the financial state of the company?

These conversations surface problems that no document review will reveal. The Head of Sales will tell you the CRM pipeline data does not match the bookings numbers finance reports. The Head of Engineering will tell you AWS costs are growing faster than anyone realizes. The bookkeeper will tell you there are 45 transactions from three months ago that are still uncategorized.

Also in Week 1: meet individually with every board member and investor representative. Ask what their biggest financial questions are, what they find most useful about current reporting, and what they wish were different. These conversations set your agenda for the next 90 days.

Weeks 2–3: Audit the Financial Infrastructure

Work through a systematic audit of the financial infrastructure:

Accounting system audit: Pull the chart of accounts. Does it follow standard SaaS accounting conventions? Are COGS and operating expenses properly separated? Is deferred revenue tracked as a liability?

Close process audit: When did the last three monthly closes complete? Who owns each step? What are the documented procedures? Are there steps that only one person knows how to do?

Revenue recognition audit: Reconstruct the MRR from your billing system (Stripe, Chargebee, Recurly) independently of what accounting shows. Reconcile the two. Identify every discrepancy and its cause. Common issues to look for:

• Annual contracts recognized entirely in month of signing (should be spread over 12 months)
• Stripe fees netted against revenue (should be separate COGS line)
• Trials counted as MRR before payment confirmed
• Grace period accounts counted as active subscribers

Deferred revenue audit: Pull your billing system's list of active annual contracts. Calculate what the deferred revenue balance should be. Compare to the balance sheet. If they differ by more than a rounding error, there are accounting errors to correct.

Gross margin audit: Calculate gross margin from first principles — pull all COGS line items and verify each belongs in COGS. Recalculate gross margin. If it differs materially from what has been reported, identify the cause. Most commonly: some COGS items have been classified as G&A or R&D.

For benchmarks on what SaaS gross margins should look like by stage and segment, see the analysis on SaaS gross margin benchmarks.

MRR waterfall audit: Verify the last 6 months of MRR waterfalls from first principles. Build them yourself from billing data. Compare to whatever was previously reported. Identify every discrepancy. This audit frequently reveals churn underreporting (customers on grace periods counted as active) or expansion overreporting (platform fees miscounted as MRR).

Week 4: Synthesize and Prioritize

By the end of Week 4, you should have a written diagnostic report covering:

• The state of financial infrastructure (rating: solid / needs work / broken)
• Revenue recognition accuracy (quantify any restatements needed)
• Key metrics gaps (what is missing or inaccurate)
• Close process gaps (timeline, ownership, automation opportunities)
• Reporting gaps (what does the board or investors not currently receive?)
• Team gaps (skills or capacity the finance function is missing)

From this list, identify the top three to five problems that most need fixing in the next 60 days. These become your Days 31–60 agenda.

Share this diagnostic with the CEO, but frame it carefully. The goal is not to criticize the previous approach — it is to define a path forward. Lead with what is working, acknowledge what needs to improve, and propose specific solutions.

Days 31–60: Stabilize the Foundation

The middle 30 days focus on fixing the most critical infrastructure gaps and establishing a consistent operating cadence.

Fix Revenue Recognition

If the revenue recognition audit revealed systematic errors, this is the first thing to fix. A revenue recognition error affects every financial statement and every metric derived from revenue. You cannot have accurate reporting until revenue is correct.

Depending on the severity of errors, this may require:

• Restating prior periods (complex, but necessary if planning a fundraise)
• Correcting the ongoing process without restating (acceptable for small errors in very early companies)
• Implementing a proper revenue recognition schedule going forward

For the detailed mechanics of revenue recognition in SaaS, see SaaS revenue recognition and MRR calculations.

Establish the Monthly Close Cadence

Implement the five-day close process if it does not exist. Create the checklist, assign owners to each step, and schedule the Day 5 review as a recurring calendar event.

The close process produces everything downstream: the MRR waterfall, the P&L for variance analysis, and the data for the board package. Until the close runs consistently in five days, everything else is built on sand.

Build the Core Metrics Dashboard

Identify the eight to ten metrics that most accurately describe the health of the business and build a dashboard to track them consistently month over month. For most SaaS companies at the growth stage, these are:

• MRR / ARR
• Net Revenue Retention
• Gross Revenue Retention
• Gross Margin
• CAC by channel
• CAC Payback Period
• Burn Rate and Runway
• Pipeline Coverage

The dashboard does not need to be sophisticated — a well-maintained Google Sheet updated during the monthly close is better than a partially-built analytics tool that requires someone to manually run queries.

For a guide to structuring a SaaS metrics dashboard, see SaaS metrics dashboard guide.

Begin the Financial Model

Start building the three-statement financial model if one does not exist:

• Income statement (P&L) with 18-month quarterly projection
• Balance sheet with quarterly projection
• Cash flow statement (derived from P&L and balance sheet)
• Revenue model: MRR waterfall with cohort assumptions feeding ARR projection
• Expense model: headcount plan + non-headcount operating expenses

The model should have clearly stated assumptions, three scenarios (base / conservative / optimistic), and a summary dashboard showing key metrics from each scenario.

This model will be the centerpiece of every investor conversation for the next 12–18 months.

Meet with Key Investors Again

After the diagnostic phase, meet again with each board member and lead investor. Share:

• What you found in the audit (framed constructively)
• The three to five most important problems you are fixing
• What the updated financial picture looks like once corrections are made
• What they can expect from financial reporting going forward (format, cadence, content)

This proactive communication prevents surprises and builds credibility. Investors who discover problems through channels other than the CFO — even problems that predated the CFO's tenure — interpret the silence as a red flag.

Days 61–90: Produce Investor-Grade Output

The final 30 days are about demonstrating that the diagnostic and stabilization work has paid off in the form of investor-grade financial output.

Deliver the First Board Package

The first board package produced under the new CFO is a defining moment. It should reflect:

• Accurate, reconciled financials with proper revenue recognition
• The complete metrics package (ARR bridge, NRR, CAC, burn, pipeline)
• Honest variance analysis comparing actuals to prior forecasts
• Clear scenario forecasts for the next two quarters
• Three to five strategic questions you want board input on

For a detailed guide to board package design, see designing a board metrics package that investors actually read.

A board package delivered accurately and on time builds more trust with investors than any amount of explanation. The absence of errors, the presence of clear variance analysis, and the proactive framing of forward scenarios communicate: this CFO knows what they are doing.

Establish the Forecast Cadence

By Day 90, the rolling 13-week cash forecast should be running weekly. The monthly MRR model should be updated as part of the close. The quarterly scenario model should be updated for the most recent board meeting.

Document the forecast process: who builds it, when it is built, what assumptions are used, and how it is reviewed. This documentation is essential for when the process needs to be handed off or scaled.

Plan the Finance Team

By Day 90, you should have a clear view of what finance talent the company needs over the next 12 months. Common build-out patterns:

• $3–8M ARR: CFO + bookkeeper/Controller (full or fractional)
• $8–20M ARR: CFO + Controller + FP&A analyst
• $20–50M ARR: CFO + VP Finance + Controller + FP&A team (2–3 people)

Hire the Controller before the FP&A analyst if the close process is still fragile. You need operational financial accuracy before you need modeling sophistication.

Define Success Metrics for Year 1

Work with the CEO and board to define what "success" looks like for the finance function after 12 months. Typical Year 1 success criteria for a first SaaS CFO:

• Close process running in five business days or fewer (from whatever it was at hire)
• Revenue recognition on accrual basis with deferred revenue properly tracked
• Monthly investor update sent by Day 10 of each month
• Quarterly board package delivered 72 hours before each meeting
• Financial model updated and used for quarterly planning
• No material restatements needed for due diligence purposes

These criteria make the CFO role legible to the CEO and board, which reduces the vague anxiety that often surrounds a finance leader who is making fundamental improvements but whose impact is not yet visible in revenue growth.

The Capital Efficiency Lens

An effective SaaS CFO does not just track spend — they continuously evaluate capital efficiency. The key efficiency metrics to establish in the first 90 days:

Burn Multiple (Net Burn ÷ Net New ARR): Measures how much capital you consume per dollar of ARR growth. According to Bessemer Venture Partners, below 1.5x is strong; above 2.0x at scale is a flag.

Revenue per Employee: Total ARR divided by full-time headcount. For growth-stage SaaS, $150K–$250K ARR per employee is typical. Best-in-class companies with strong self-serve or PLG motions can reach $300K+.

Magic Number (Net New ARR ÷ Prior Quarter S&M Spend): Measures sales and marketing efficiency. Above 1.0 means $1 of S&M spending generates $1 of ARR — a green signal for increasing S&M investment. Below 0.5 signals poor efficiency.

Tracking these from day one sets the benchmark for measuring improvement over your tenure.

What Good Looks Like at Day 90

By the end of the first 90 days, the finance function should have:

• A five-day monthly close process with documented owners
• Accurate revenue recognition and deferred revenue tracking
• A complete metrics dashboard updated monthly
• A three-statement financial model with three scenarios
• The first board package delivered under your ownership
• A weekly cash forecast running
• Individual relationships with every board member

These are not glamorous. They are not the strategic capital allocation decisions or the fundraise process or the M&A analysis that make the CFO role look interesting from the outside. But without this foundation, all of the strategic work is built on unstable ground.

The fastest path to strategic impact as a SaaS CFO is establishing operational credibility first — then the door opens to the more strategic work that justifies the role's cost.

For the ongoing FP&A process that runs on top of this foundation, see building an FP&A process when you do not have a finance team.

Conclusion

The first 90 days of a SaaS CFO role are a foundation-building exercise. The diagnostic phase reveals what exists. The stabilization phase fixes what is broken. The output phase demonstrates the results.

Resist the temptation to start building complex models or recommending major strategic decisions before the foundation is solid. The sequence matters. A CFO who fixes the close process in month one, delivers an accurate board package in month two, and presents a clear financial model in month three will have more organizational trust and board credibility by month four than one who immediately jumps to strategic recommendations built on inaccurate financial data.

The first 90 days define the next three years. Spend them well.