Back to customer stories

Customer Story

Bridgecroft Capital

How Marcus Webb turned ten years of Treasury data into a rate-regime LBO framework with Energent.ai

We had always known rates move, but the template had no mechanism to show by how much. Now the regime tables are a standing IC deliverable.
Marcus Webb, VP of Acquisitions at Bridgecroft Capital
Industry
Private equity
Market
North America — mid-market buyout
Use case
Rate-regime LBO scenario analysis
Bridgecroft Capital

Bridgecroft Capital is a mid-market buyout firm evaluating several new platform investments per year. Marcus Webb, VP of Acquisitions, owns the financing assumptions section of each LBO model — debt sizing, coupon projections, and debt-service coverage. Every IC submission requires regime-specific scenario tables that hold up under cross-examination by senior partners and debt arrangers.

Static LBO templates absorbed a 500-bps rate swing without surfacing it

Standard LBO model templates encode a single financing rate and project it unchanged through the hold period. The 2-year Treasury — the benchmark driving most leveraged-loan pricing — moved from 0.09% to 5.19% within a single decade, a range of more than 500 basis points. On 21.8% of trading days over that period, the 10s-2s yield curve was inverted, compressing refinancing flexibility in ways a flat-rate model cannot represent.

At 450 bps credit spread, all-in cash interest ranges from approximately 4.86% in a low-rate regime to 8.74% in a high front-end regime. Under a 6.0x leverage / 40% EBITDA-to-FCF structure, interest burden moves from 0.29x to 0.52x EBITDA — a 23-percentage-point gap large enough to stall deleveraging before any operational miss.

Producing regime tables manually meant pulling raw Treasury CSVs, defining thresholds, computing cost-of-debt by bucket, and reconciling outputs to the LBO template — a multi-hour rebuild per deal, with threshold choices buried in spreadsheet cells no reviewer ever questioned.

Energent.ai replaced the multi-tool rebuild with a single-session deliverable

Marcus uploaded the daily Treasury CSV directly. The agent handled the full stack:

No raw-data wrangling. No thresholds buried in Excel. No separate reviewer to catch comparison errors.

Rate regime threshold table

Regime cutoffs the investment committee could challenge, not just accept

How Marcus runs it deal-to-deal

  1. Upload the daily Treasury rate CSV for the benchmark period.
  2. Agent defines regime thresholds, computes bucket frequencies, and derives all-in rates by regime at the deal's credit spread.
  3. Agent models interest burden and paydown sensitivities; packages the dashboard, CSVs, and written narrative.
  4. CSV outputs feed into the existing LBO model template; the written analysis drops directly into the IC memo.

A 388-bps cost-of-debt range quantified before the IC, not after

Interest burden sensitivity dashboard

"The agent treated the regime definitions as the thing that had to be defended first, before any output number. The IC can push back on the assumption rather than just the result." — Marcus Webb, VP of Acquisitions at Bridgecroft Capital

Back to customer storiesBook a Demo