🧩 Overview
This guide shows you how to use FCF conversion in valuation as a practical lens for comparing scenarios in a performance model. It’s built for CFOs, finance teams, advisors, and valuers who need to move beyond ‘revenue vs EBITDA’ comparisons and answer a tougher question: which scenario actually produces cash-and when? You’ll learn how to set up a scenario structure, define a consistent FCF construct, build a driver-based bridge, and compare outcomes with decision-ready outputs. The result is faster scenario analysis, clearer trade-offs, and fewer surprises when valuations meet real-world cash constraints.
🧰 Pre-Check: What You Need Before You Start
Before you begin, make sure you have four things in place. First, clarity on your FCF definition: unlevered vs levered, capex treatment, lease treatment, and what counts as ‘recurring.’ Without this, scenario comparisons become misleading. Second, access to the right inputs: recent financials, working capital detail, capex history/plans, and tax assumptions. Third, a modelling toolset that supports clean scenario separation-whether that’s a disciplined spreadsheet process or a platform with explicit scenario controls. Fourth, agreement on the scenario purpose: are you comparing investment cases, budgeting outcomes, covenant headroom, or valuation ranges?
You should also decide your primary comparison metrics and time horizon. For example, if liquidity risk matters, you may need monthly periods. If valuation is the priority, annual periods can work-provided you stress timing. If you’re structuring the work in a free cash flow financial model, ensure the model’s logic is stable before you duplicate scenarios.
🛠️ Step-by-Step Instructions
Define the Scenario Set and Lock the Base Logic
Start by writing down scenario definitions in plain language: base, downside, upside, plus any ‘special case’ scenario (e.g., delayed product launch). Each scenario should reflect a coherent operational story, not just a different growth rate. Next, lock the model logic: revenue recognition, cost drivers, working capital calculations, capex schedules, and tax treatment must be identical across scenarios. Only the inputs change. This prevents false differences caused by inconsistent formulas. Establish a naming convention and a single place where scenario inputs live. If you’re using a platform like Model Reef, set each scenario as a branch/toggle so the structure is preserved and comparisons are clean. Driver-based model structure is especially helpful here because it reduces manual rework as you iterate.
Build Driver Inputs That Control Cash Conversion
Now set the driver inputs that govern conversion: gross margin, operating expense scaling, capex (timing and magnitude), and working capital days (DSO/DPO/inventory). These are the levers that change cash outcomes even when headline revenue looks similar. Keep drivers measurable and auditable: you want inputs that connect to real operating initiatives (collections improvement, procurement terms, inventory turns). Add scenario-specific assumptions only when the scenario narrative demands it. A common misstep is to change too many inputs at once; you lose line-of-sight on what mattered. Instead, keep scenario deltas focused and then use sensitivities to explore additional uncertainty. If your workflow depends on frequent iteration,scenario analysis features and structured toggles reduce errors and help keep comparisons consistent.
Create a Bridge to Compare Scenario Mechanics
Don’t compare scenarios using a single free cash flow line. Build a bridge: EBITDA/EBIT → cash taxes → working capital change → operating cash flow → capex → free cash flow. This turns scenario comparison into diagnosis: you can see whether the downside fails due to margin pressure, working capital timing, capex pulls, or tax friction. This bridge is also the fastest way to explain results to non-modellers. As you build it, align the bridge to the same driver definitions used in your operating lines to avoid disconnects. This is the backbone of financial modeling cash flow work that can stand up in reviews. If you need a deeper walkthrough on translating operating assumptions into cash outputs,use the cash projection guide as your reference point.
Convert Cash Outcomes into Valuation and Performance Views
Once scenario cash mechanics are clear, translate them into the views stakeholders care about: valuation impact, funding need, and performance resilience. For valuation, keep assumptions consistent and run discounted cash flow analysis across scenarios to produce a clear range, not a single point. For performance, compare conversion KPIs (cash EBIT margin, conversion %, capex intensity, working capital days) so you can describe ‘why scenario A is better than scenario B.’ This is where business valuation metrics become operational: they explain trade-offs, not just results. In Model Reef, you can keep valuation outputs tied to the same driver set used for performance scenarios, reducing the risk of ‘two models that don’t match.’ If you want more context on where conversion affects DCF outcomes,connect this step to the DCF and conversion deep dive.
Finalise Comparisons and Write Decision-Ready Conclusions
Wrap the work by producing a one-page scenario comparison summary: key assumptions, key bridge movements, headline free cash flow, and value range (if applicable). Include ‘decision triggers’-what must be true for the upside to hold, and what would indicate drift toward the downside. Add two to three monitoring KPIs tied to conversion drivers (e.g., DSO trend, capex variance, gross margin by segment). Finally, validate internal consistency: if revenue drops but working capital improves dramatically without a reason, you likely have a modelling error. The goal is not just analysis; it’s action. Present outcomes using simple charts and consistent tables so stakeholders can absorb differences quickly. Dashboards and scenario comparison views can make this far easier,especially when teams need to review multiple runs.
- If your business is seasonal, annual models can hide cash crunches; consider monthly/quarterly periods for working capital-heavy businesses.
- Watch for ‘growth consumes cash’ dynamics: high-growth scenarios often look great on profit but require more working capital and capex.
- Separate one-offs from recurring conversion. If restructuring costs or unusual capex distort the story, isolate them so scenarios remain comparable.
- Be careful with capex timing: a single period shift can change near-term liquidity and materially change valuation ranges.
- Don’t let scenario inputs drift. Lock baseline assumptions and document what changed and why-especially when multiple people are iterating.
- If you’re comparing scenarios across versions, you need traceability. Change logs, notes,and version history reduce rework and improve trust in the outputs.
🧪 Short Example or Illustration
Example input → action → output:
Input: Two scenarios for a distribution business. Scenario A: 12% revenue growth, stable margins, inventory days +8. Scenario B: 9% revenue growth, stable margins, inventory days flat, capex delayed one quarter.
Action: Build the bridge and compare conversion. Scenario A shows higher EBITDA but larger working capital investment and higher capex timing pressure; Scenario B shows slightly lower EBITDA but stronger near-term cash generation.
Output: Scenario B produces higher year-1 free cash flow and lower funding need, while Scenario A produces better year-3 cash if inventory turns are improved. The team chooses Scenario B for budgeting, while keeping Scenario A as an ‘execution upside’ contingent on operational inventory improvements. This comparison becomes a cash flow projection for valuation input when preparing a valuation range discussion.
FAQ TITLE: ❓ FAQs
Use all three, but prioritise conversion when you need to understand 'cash quality.' Absolute FCF can be skewed by scale, and FCF margin can be skewed by pricing or cost structure changes. Conversion helps you see how efficiently earnings translate into cash, which is often what drives confidence in the story. The best approach is: use absolute FCF for liquidity, margin for efficiency, and conversion for quality and resilience. A good next step is to standardise a small set of metrics so every scenario pack uses the same lens.
Build a bridge and compare the movements line by line. The bridge forces differences into categories: margin, tax, working capital, capex. Without it, teams end up debating inputs rather than diagnosing outcomes. If you keep your drivers consistent, you can usually identify the dominant driver in minutes. Once you know the dominant driver, run a quick sensitivity to test whether the conclusion holds under plausible ranges. If you want to formalise the metrics lens, align comparisons to valuation cash flow metrics so results are consistent across stakeholders.
Make uncertainty explicit with sensitivity ranges and 'trigger-based' monitoring. Instead of pretending assumptions are certain, show what happens when key drivers move (DSO, margin, capex timing). This creates a decision-ready view: what must be true for the plan to work, and what signals early risk. Credibility comes from transparency and repeatability, not perfect prediction. As a next step, document scenario definitions and lock them so future updates don't silently change the logic.
Keep performance scenarios and valuation outputs connected to the same driver base. If you run a separate valuation model with different assumptions, you create inconsistency and lose trust. Instead, use scenario outputs as direct valuation inputs, then run a valuation range that corresponds to each operational story. This is especially important for FCF in DCF model work, where small differences in timing and conversion can create large value swings. As a next step, pick one scenario and trace the path from drivers → bridge → valuation output to validate consistency end-to-end.
🚀 CTA & Related Articles
Apply this workflow to your next board pack or investment memo: define scenarios, lock logic, compare conversion via the bridge, then translate outcomes into decision triggers. If you want to accelerate iteration and reduce spreadsheet version chaos, Model Reef can help you manage scenario branches, keep driver assumptions consistent,and produce comparable outputs without rebuilding your model each time.
Back