Waterfall BridgePlan-to-actual variance bridgeCorporate & BusinessManagement ConsultingIT & Professional Services

Plan-to-actual variance bridge

Cloud overspend is EUR 6.5M due to inference growth and delayed decommissioning

Try in Playground
Plan-to-actual variance bridge slide template rendered with SlideForge
Cost
$0.05/slide
Engine
Deterministic
Pattern
Waterfall Bridge
Output
.pptx + PDF + PNG

Example brief

The planned operational expenditure was EUR 42.0M, but actual opex reached EUR 48.5M. Key factors contributing to the overspend include a EUR 5.8M increase in inference volume and a EUR 2.4M impact from delayed decommissioning. However, there were also cost savings from reserved-instance savings of EUR 3.2M, storage optimization of EUR 1.4M, and a vendor credit of EUR 0.9M. Other factors such as security logging and FinOps leakage added to the overspend. To address the overspend, it's essential to focus on reducing inference run-rate and tackling the decommissioning backlog.

Render it

Structured intent — create_slide payload

Copy-paste-ready. Renders deterministically (verbatim, no LLM). Add a theme_id for any of the built-in themes — the layout stays identical.

{
  "form": "waterfall_bridge",
  "variant": "plan_actual_variance_bridge",
  "headline": "Inference growth and delayed decommissioning explain most of the EUR 6.5M cloud overspend",
  "context": "FY26 cloud run-rate: plan to actual (EUR M)",
  "caution": "Tone is business impact: cost reductions are favourable even when negative.",
  "source_note": "FinOps actuals, FY26",
  "data": {
    "unit": "",
    "steps": [
      {
        "kind": "start",
        "label": "Plan opex",
        "value": 42,
        "display": "42.0"
      },
      {
        "kind": "delta",
        "label": "Reserved-instance savings",
        "value": -3.2,
        "impact": "good"
      },
      {
        "kind": "delta",
        "label": "Inference volume",
        "value": 5.8,
        "impact": "bad",
        "emphasis": "primary"
      },
      {
        "kind": "delta",
        "label": "Storage optimization",
        "value": -1.4,
        "impact": "good"
      },
      {
        "kind": "delta",
        "label": "Security logging",
        "value": 2.1,
        "impact": "bad"
      },
      {
        "kind": "delta",
        "label": "FinOps leakage",
        "value": 1.7,
        "impact": "bad"
      },
      {
        "kind": "delta",
        "label": "Vendor credit",
        "value": -0.9,
        "impact": "good"
      },
      {
        "kind": "delta",
        "label": "Delayed decommissioning",
        "value": 2.4,
        "impact": "bad"
      },
      {
        "kind": "total",
        "label": "Actual opex",
        "value": 48.5,
        "display": "48.5"
      }
    ],
    "takeaways": [
      "Overspend concentrates in just two drivers",
      "Most of the gap is structural, not one-off",
      "Delayed decommissioning compounded the variance",
      "Tighten forecasting on the top two drivers"
    ]
  }
}

cURL (REST)

curl -X POST https://dev-api.slideforge.dev/v1/render/intent \
  -H "Authorization: Bearer sf_live_..." \
  -H "Content-Type: application/json" \
  -d '{"form":"waterfall_bridge","variant":"plan_actual_variance_bridge","headline":"Inference growth and delayed decommissioning explain most of the EUR 6.5M cloud overspend","context":"FY26 cloud run-rate: plan to actual (EUR M)","caution":"Tone is business impact: cost reductions are favourable even when negative.","source_note":"FinOps actuals, FY26","data":{"unit":"","steps":[{"kind":"start","label":"Plan opex","value":42,"display":"42.0"},{"kind":"delta","label":"Reserved-instance savings","value":-3.2,"impact":"good"},{"kind":"delta","label":"Inference volume","value":5.8,"impact":"bad","emphasis":"primary"},{"kind":"delta","label":"Storage optimization","value":-1.4,"impact":"good"},{"kind":"delta","label":"Security logging","value":2.1,"impact":"bad"},{"kind":"delta","label":"FinOps leakage","value":1.7,"impact":"bad"},{"kind":"delta","label":"Vendor credit","value":-0.9,"impact":"good"},{"kind":"delta","label":"Delayed decommissioning","value":2.4,"impact":"bad"},{"kind":"total","label":"Actual opex","value":48.5,"display":"48.5"}],"takeaways":["Overspend concentrates in just two drivers","Most of the gap is structural, not one-off","Delayed decommissioning compounded the variance","Tighten forecasting on the top two drivers"]}}'

Related templates

Frequently asked questions

How do I render the Plan-to-actual variance bridge template?

Send a POST to /v1/render/auto with a brief, or call create_slide via MCP with the structured intent shown below. The response includes an editable .pptx, a PDF, and a PNG. $0.05 per slide.

Does an AI write the slide?

No. SlideForge renders deterministically from a structured intent — no LLM draws the slide, so text is never mangled or fabricated. The optional brief path uses a router to pick the pattern, then renders deterministically.

Can I customize the colors and fonts?

Yes. Pass a theme_id to apply a built-in or custom brand theme; the layout stays the same.

Try this template

Render Plan-to-actual variance bridge deterministically — editable PowerPoint in under a second.

Plan-to-actual variance bridge Slide Template | SlideForge | SlideForge (slideforge.dev)