The Problem

Your LBO model has a sell-side case and an upside acquisition case, but the partner wants a downside scenario before the IC memo goes out. Adding a new case manually means duplicating assumption blocks, rewiring formula references across revenue, EBITDA, debt schedules, and returns outputs, then sense-checking every link. For a model with any complexity, that could be 20 minutes of error-prone work. Tracelight helps you do it in 5.

The Solution

You describe the new scenario to Tracelight in plain English: add a downside case with reduced revenue growth assumptions. Tracelight reads the existing model structure, identifies the assumption architecture and case toggle logic, and builds the new scenario directly into the workbook, wired to the same outputs as your existing cases.

Step 1: Define the New Scenario in Plain English

You open the existing LBO model containing the sell-side and upside acquisition cases and tell Tracelight what you need: a downside scenario with reduced revenue growth. No prompt engineering required. If an analyst sitting next to you would understand the instruction, Tracelight will too.

Step 2: Generate the Downside Case

Tracelight reads the existing case structure, mirrors the assumption layout, and populates the downside scenario with the reduced revenue growth parameters. The new case is wired into the model's existing architecture, so it flows through to EBITDA, free cash flow, debt paydown, and returns outputs without manual relinking.

Step 3: Summarise Insights

With the downside case built, you can toggle between sell-side, upside, and downside scenarios to compare returns profiles. You can then ask Tracelight to summarise specific insights from the downside case.

The Result

Adding a new sensitivity case to an existing LBO model, a task that typically takes 20 minutes of careful work and interpretation, can now be easily accomplished under 5 minutes.