What Fractional FP&A Actually Buys You: Inside a Real Engagement, Week One to Delivery

Inside a Real Engagement, Week One to Delivery

Last week a founder asked me the positioning question. "Do I need FP&A or just better bookkeeping?" Her monthly variance had been running above twelve percent for two quarters. She was making hiring decisions without cash models. Both early signals, not crisis yet.

She expected cleaner reports. What she got was forward infrastructure.

This is the final part of the FP&A positioning stack, and it's the one that shows what actually happens when you hire fractional FP&A before the crisis hits. Not the pitch, not the theory, the week-by-week reality of an engagement from first call to delivery. The founder in that opening moment had read the prior three weeks: she understood the structural question (week one), she could name the deliverable (week two), and she'd spotted the early signals (week three). What she didn't know was what the work itself looked like once it started.

That's the gap this post closes. What fractional FP&A actually does in the first month, what gets built, what changes, and why most founders hire it too late because they mistake the engagement for something else entirely.

A shorter version of this post appears on LinkedIn: [LINKEDIN_POST_URL]

The Engagement Trap Nobody Names

The founder in that opening moment had done everything right up to the point of hiring. She'd recognized the positioning question as structural, not philosophical. She'd identified the deliverable as forward-looking finance infrastructure, not backward-looking cleanup. She'd spotted the early signals in her variance pattern and her decision-making gaps before they became cash problems.

But she still asked the wrong question when we started. "How long until I have clean books?"

That's the engagement trap. Founders hire FP&A thinking they're buying a better version of what they already have, cleaner reports, tighter reconciliation, variance analysis that makes sense. What they're actually buying is a finance function that didn't exist before, one that looks forward instead of backward, one that catches problems while they're still signals instead of documenting them after they've become crises.

The trap compounds all three prior weeks. Founders hire FP&A too late because they mistake the positioning question for a philosophical debate instead of a structural one (week one), they don't know what the deliverable actually is so they can't recognize when they need it (week two), and they wait for crisis instead of watching for early signals (week three). The result is hiring FP&A to fix a cash crunch when they should've hired it to prevent one.

That's not FP&A work. That's crisis management dressed up as financial planning.

Week One: The Rolling Cash Model

The first week of a fractional FP&A engagement doesn't touch the P&L. It builds a rolling thirteen-week cash flow model.

Not a static forecast. A live model that updates as actuals come in, that shows cash position under three scenarios (base, upside, downside), that flags the week runway drops below the threshold that matters for the business. The model isn't there to predict the future with precision. It's there to show how much room exists between the current trajectory and the constraints that matter.

For the founder in that opening moment, the constraints were hiring decisions. She was considering two roles, a senior engineer and a sales lead, and she was making the decision based on revenue growth and gut feel about timing. Not wrong inputs, but incomplete ones. Revenue growth tells you whether you can afford to hire in theory. Cash runway tells you whether you can afford to hire in practice, and whether the timing of one hire changes the viability of the other.

The rolling cash model answered that question in week one. Under the base case, both hires were viable with eighteen weeks of runway remaining after onboarding. Under the downside case (revenue growth slows by fifteen percent, a modest assumption given the variance pattern she'd been running), the second hire pushed runway below twelve weeks. Not a crisis, but a signal that the decision wasn't as clean as it looked from the P&L alone.

The model structure itself is straightforward but not simple. It tracks three categories of cash movement: operating inflows (revenue collected, not revenue recognized), operating outflows (expenses paid, not expenses accrued), and non-operating flows (financing, one-time events). Each category rolls forward week by week, and the model updates the forward projection every time actuals come in for a completed week.

The formula for weekly cash position is:

Simple in structure, hard in practice. The difficulty isn't the arithmetic. It's the discipline of separating cash timing from accounting timing, of recognizing that a sale in week three might not convert to cash until week seven, and that an expense accrued in March might not hit the bank account until April. Founders who don't have this model make decisions based on P&L timing, and P&L timing lies about cash.

Week Two: The Management Pack Nobody Built

The second week builds the first monthly management pack. Not a prettier version of the bookkeeper's output. A structured set of reports that answer the questions a board member or investor would ask if they were looking at the business for the first time.

Revenue by product line. Gross margin decomposition. Variance commentary with root causes, not just the delta. Operating expense breakdown by category, with headcount and non-headcount spend separated. Cash burn rate and runway, updated from the rolling model built in week one.

The founder in that opening moment had been running her business on QuickBooks reports and a mental model of what was happening underneath. QuickBooks told her revenue was growing. It didn't tell her which product line was driving the growth, or whether the growth was coming from new customers or expanded contracts with existing ones. It didn't tell her that gross margin had dropped three points over the prior quarter because the product line driving growth had lower margin than the legacy product.

The management pack answered those questions in week two, and it answered them in a format that could be repeated every month without rebuilding from scratch. That's the part most founders miss when they think about FP&A deliverables. The value isn't in the first report. It's in the infrastructure that makes the second report take an hour instead of a day, and the third report take thirty minutes instead of an hour.

The variance commentary is where the real work lives. A line that says "Revenue up 12% vs. prior month" is a fact, not insight. A line that says "Revenue up 12% vs. prior month, driven by Product A expansion with three existing customers, partially offset by Product B churn in the SMB segment" is insight, and it's the kind of insight that changes decisions.

For the founder in that opening moment, the variance commentary in week two caught something she hadn't seen in the QuickBooks roll-up. Her customer acquisition cost had risen twenty-three percent over two quarters, buried under a marketing spend line that looked flat because she'd shifted budget from paid channels to a contract recruiter running outbound. The cost hadn't gone away. It had moved categories, and the P&L structure she was using didn't show it.

Week Three: Scenario Planning for the Hires

The third week took the rolling cash model from week one and the management pack structure from week two and used both to model the two hiring decisions she was considering.

Three scenarios for each hire. Base case: revenue growth continues at the trailing three-month average, gross margin holds steady, the new hire reaches full productivity in twelve weeks. Upside case: revenue growth accelerates by ten percent, margin expands by one point as the product mix shifts toward the higher-margin line, productivity ramps in eight weeks. Downside case: revenue growth slows by fifteen percent, margin contracts by one point, productivity ramps in sixteen weeks.

The scenarios weren't guesses. They were bounded by the actual variance the business had been running over the prior two quarters, and by the productivity ramp data she had from the last two hires in similar roles. Not perfect data, but real data, and real data beats gut feel every time when the decision has a six-figure cost attached to it.

The model structure for each scenario tracked the same components:

The hiring cost included signing bonus, recruiter fees, and onboarding expense. The monthly burn included the new salary, the allocated overhead (benefits, software, workspace), and the trailing three-month average burn for the rest of the business. The formula gave a single number: how many months of runway remain after the hire, under each scenario.

For the senior engineer role, the base case showed eighteen weeks of runway post-hire. The upside case showed twenty-two weeks. The downside case showed fourteen weeks. Viable under all three scenarios, though the downside case left less room than she would've liked.

For the sales lead role, the base case showed sixteen weeks of runway if hired immediately after the engineer, fourteen weeks if hired simultaneously. The upside case showed nineteen weeks. The downside case showed nine weeks.

Nine weeks is where the decision changed. Not a crisis, but not enough room to recover if the downside case materialized. The model didn't tell her not to hire the sales lead. It told her that hiring the sales lead in the downside case required either faster revenue growth than the trailing average, or a smaller burn rate than the business was currently running, or a financing conversation she wasn't planning to have yet.

She hired the engineer in week four. She delayed the sales lead by two months, enough time to see whether the base case was holding or whether the business was trending toward the downside. That's what scenario planning buys you. Not certainty, but clarity about which assumptions have to hold for the decision to stay viable.

Week Four: The Deliverable Nobody Shows You

By week four, the founder in that opening moment had three things she didn't have in week zero.

A rolling thirteen-week cash model that updated every week and showed runway under three scenarios. A monthly management pack that broke down revenue, margin, and burn in a format that could be repeated without rebuilding. A decision framework for the two hires she was considering, with scenario analysis that showed which assumptions mattered and how much room existed if those assumptions didn't hold.

Not better backward-looking books. A forward-looking finance function that caught problems while they were still signals.

That's the deliverable nobody shows you when they pitch fractional FP&A. The pitch talks about CFO-level insight without the full-time cost. The reality is infrastructure, the kind of infrastructure that takes four weeks to build the first time and then runs every month without starting from scratch.

The founder in that opening moment expected cleaner reports. What she got was the ability to make hiring decisions with cash models instead of gut feel, to see variance patterns before they became cash problems, to know how much room existed between her current trajectory and the constraints that mattered for her business.

That's not bookkeeping. That's FP&A.

Why Most Founders Hire Too Late

The engagement trap compounds because founders don't see the work until it's done, and by the time they see it, they're usually hiring to fix a crisis instead of prevent one.

They wait until variance is above fifteen percent for three quarters instead of two. They wait until they've made a hiring decision that pushed runway below eight weeks instead of modeling it before the offer went out. They wait until the cash crunch is visible in the bank balance instead of visible in the rolling model.

That's not a failure of judgment. It's a failure of positioning. Founders can't hire for something they can't see, and they can't see forward infrastructure until someone builds it and shows them what it does.

The founder in that opening moment hired early because she'd read the prior three weeks and recognized the signals before they became problems. Most founders don't have that context, so they hire late, and hiring late means the first month of the engagement is spent fixing problems that could've been prevented instead of building infrastructure that prevents the next ones.

The work is the same either way. The outcome isn't.

What Changes After Week Four

After week four, the engagement shifts from building to running. The rolling cash model updates every week with five minutes of data entry instead of four days of construction. The monthly management pack runs in under an hour instead of being rebuilt from scratch. The scenario planning framework exists, so the next hiring decision or pricing change or product launch gets modeled in a day instead of being made on gut feel.

The founder in that opening moment didn't need me in week eight the way she needed me in week one. She needed the model updated, the management pack reviewed, the occasional scenario run when a new decision came up. That's what fractional means in practice. Full build in the first month, maintenance and decision support after that.

The infrastructure doesn't disappear when the engagement scales back. It stays, and it keeps working, and it keeps catching signals before they become problems.

That's what fractional FP&A actually buys you. Not a better version of what you already have. A finance function that didn't exist before, one that looks forward instead of backward, one that catches problems while they're still signals instead of documenting them after they've become crises.

This closes the FP&A positioning stack. Next week, we start the implementation series: what correct FP&A setup looks like when you're building it from scratch.

If you're seeing the early signals and you'd rather build the infrastructure before the cash crunch forces it, the E3 Fractional FP&A Retainer gives you CFO-level finance infrastructure without the full-time hire: calendly.com/muhammed-adediran/30min