ROI and Break-Even Builder

Big spending decisions get made on gut or on a vendor's optimistic slide. This skill builds an honest ROI and break-even analysis: what the investment costs fully, what it returns, when it pays back, and how sensitive that is to the assumptions, so a decision rests on the real return rather than hope or a sales pitch.

1. The investment being evaluated and its full cost (upfront and ongoing).
2. The expected benefits (revenue gained, cost saved, time reclaimed) and their basis.
3. The time horizon for the decision.
4. What alternative the money or time would otherwise go to.

1. Capture the full cost, not just the sticker

Include upfront cost, ongoing cost, and the hidden costs (implementation, training, time). Understated cost is the most common way ROI cases mislead.

2. Quantify benefits honestly with their basis

Translate benefits into money where possible (revenue, cost savings, or hours reclaimed valued at a rate), and state where each estimate comes from. Label optimistic assumptions as such rather than baking them in.

3. Compute ROI and payback

Net benefit over cost for ROI, and the point in time where cumulative benefit covers cost for break-even. Payback period is often the more decision-useful number for a business watching cash.

4. Compare to the alternative

An investment should beat what the money or time would otherwise do, including doing nothing. Frame the return against the real alternative.

5. Stress-test the case

Show ROI and payback under conservative assumptions, not just the base case. A decision that only works in the optimistic case is a risky one, and saying so is the honest thing to do.

ALWAYS use:

# ROI and Break-Even: [Investment]
## Full cost (upfront | ongoing | hidden)
## Benefits (quantified, with basis; optimism flagged)
## ROI (net benefit / cost) and payback period
## Comparison to the alternative (including doing nothing)
## Conservative case (ROI and payback under downside assumptions)
## Recommendation and assumptions

• Counting the sticker price and ignoring implementation and time.
• Baking optimistic benefit assumptions in without flagging them.
• Reporting only the rosy case with no downside.
• Ignoring the alternative use of the money or time.

This analyzes figures and estimates the user provides; it is not financial or investment advice. Never invent costs or benefits; use placeholders and flag assumptions. The estimate is only as good as its inputs.

An ROI case for an automation tool counts license plus implementation plus training, values reclaimed hours at a loaded rate, shows a 5-month payback in the base case and 9 months conservatively, and beats the do-nothing alternative.