OEE Business Case Template: A One-Page Plan That Survives the CFO

Key takeaways

• A CFO-survivable OEE business case fits on one page and answers five questions: baseline, target, conversion to euros, total cost, payback period.
• Three cases (base, upside, downside) are non-negotiable. Single-case projections get rejected by default.
• Use measured baselines wherever possible. Estimated baselines must be conservative and revised after deployment.
• Use contribution margin, not selling price, when converting OEE points to financial value.
• Include a section on non-financial benefits (data quality, audit readiness, safety), they matter even when not quantified.

Short answer: An OEE business case that survives the CFO is one page, three cases, with measured baselines and contribution-margin math. Pad it with vague benefits or single-case projections and it dies in finance review. Lead with the math, defend the assumptions, present three scenarios. The CFO is not the enemy, vague assumptions are. See also OEE vs Utilization.

The five questions your business case must answer

1. What is the current OEE? Measured if possible, conservatively estimated otherwise.
2. What is the target OEE and by when? Realistic year-one improvement.
3. How many euros is each OEE point worth? Extra units x contribution margin per unit.
4. What is the total cost of the platform? License + implementation + internal labor.
5. What is the payback period? In months. Under 12 is approvable; under 6 is easy.

If your business case does not answer all five with specific numbers, it is not ready.

The one-page template

Header (3 lines): Plant name. Current state. Proposed investment.

Section 1. Baseline (4 lines):

• Current OEE: __% (measured / estimated based on __).
• Lines included in scope: __.
• Annual planned production hours per line: __.
• Ideal cycle rate per line: __ units/hour.

Section 2. Target (3 lines):

• Year-one target OEE: __% (improvement of __ points).
• Year-three target OEE: __% (sustained improvement of __ points).
• Confidence rationale (1 sentence per case).

Section 3. Financial conversion (4 lines):

• Extra units per year (base case): __.
• Contribution margin per unit: €__ (selling price €__ minus variable cost €__).
• Annual recovery (base case): €__.
• Year-three cumulative recovery: €__.

Section 4. Cost (4 lines):

• Platform license year 1: €__ (year 2+: €__).
• Implementation: €__ (one-time).
• Internal labor (rollout): __ FTE-months.
• Year-one total: €__.

Section 5. Cases (3 lines):

• Base case payback: __ months. Year-three NPV: €__.
• Upside case payback: __ months. Year-three NPV: €__.
• Downside case (50% of base improvement): __ months. Year-three NPV: €__.

Section 6. Non-financial (3 lines):

• Improved data quality for production planning.
• Audit-ready KPI definitions (ISO 22400 alignment).
• Faster root-cause response on safety-related stops.

How to fill in the numbers conservatively

Baseline OEE. If measured, use the last 90 days, not the best month. If estimated, use 55% for first-time discrete plants, 50% for batch.

Target OEE. Year-one realistic: +5 to +8 points. Anything above +10 needs case-study evidence and CFO will discount it anyway.

Contribution margin. Selling price minus raw material, direct labor variance, and variable energy per unit. Not gross margin (which includes fixed costs already covered).

Platform cost. Use the high end of the vendor's range. Add 20% for internal labor.

Cases. Base = +5 points. Upside = +8 points. Downside = +3 points (half the base).

What kills business cases in CFO review

1. Optimistic baselines. "Industry average is 60%" is not your number. Use measured or admit it is conservatively estimated.

2. Selling-price math. Treating each recovered unit as full revenue ignores variable cost. CFOs catch this in 30 seconds.

3. Single-case projection. If the model has no downside, the CFO assumes you are hiding one. Three cases are mandatory.

4. Vague benefits. "Better data" without quantification is fluff. Either quantify or list as non-financial benefit.

5. Ignored implementation cost. Internal labor for rollout is real. Include it.

What gets business cases approved

• One page (printable).
• Three cases.
• Measured or conservatively estimated baselines.
• Contribution-margin math.
• Specific cost (high end of vendor range plus 20%).
• Payback in months, NPV over three years.
• Honest non-financial section.

Fabrico's OEE module includes a 30-day baseline-lock workflow so the actual baseline replaces the estimate within the first month, letting you upgrade the business case from conservatively estimated to measured.

See how Fabrico captures this automatically, explore OEE for manufacturing or book a demo.

Related reading

• OEE vs Utilization
• OEE and ISO 22400
• OEE for Batch Manufacturing
• OEE vs Availability

Frequently asked questions

Does the business case need a discount rate?

For year-one payback math, no. For year-three NPV, yes. Use the company's standard WACC; if you do not know it, ask finance for the rate they use for similar investments.

What if my baseline OEE is unknown?

Use 55% for discrete, 50% for batch as conservative defaults. Commit to a measured baseline within 30-60 days of deployment and revise the case.

Should I include training cost?

Yes, under implementation or internal labor. Two-day operator training across 4 shifts is typically 80-160 FTE-hours per line.

How do I size the downside case?

Half the base case improvement. If base is +5 points, downside is +3 points. If the downside still pays back inside 12 months, the case is robust.

What if the CFO wants a 24-month payback proof?

Most OEE cases pay back in months, not years. If the CFO is asking for 24 months, the financial case is borderline, re-check baseline and target assumptions for over-conservatism.