1
Define the decision and set the analysis period
Write a one-paragraph neutral description of what is being evaluated and set the time horizon for the analysis β typically 1, 3, or 5 years depending on the expected life of the investment.
π‘ Match the analysis period to the useful life of the investment, not the budget cycle. A 5-year software platform warrants a 3β5 year horizon; a 12-month campaign does not.
2
List every one-time cost with a source
Gather vendor quotes, internal time estimates, and IT assessments to build a complete one-time cost inventory. Document the source of each figure in a note column.
π‘ Add a 10β15% contingency line explicitly β embedding contingency invisibly inside other line items makes your cost estimate look inflated when reviewers spot it.
3
List all recurring costs on an annual basis
Convert monthly figures to annual equivalents so all recurring costs are on the same timeline as your benefits. Include incremental headcount at fully loaded cost, not base salary alone.
π‘ Fully loaded labor cost is typically 1.25β1.35Γ base salary once benefits, payroll taxes, and overhead are included.
4
Quantify tangible benefits with explicit calculations
For each benefit, write out the calculation formula β hours saved Γ hourly rate, error rate reduction Γ rework cost β so reviewers can verify or challenge the assumptions independently.
π‘ Use conservative estimates for benefits and reference actual current-state data (e.g., last year's overtime spend) rather than hypothetical baselines.
5
Document intangible benefits separately
List qualitative benefits in their own section with a one-sentence rationale for each. Do not assign dollar values unless you have a defensible methodology.
π‘ Tying intangibles to a measurable proxy (e.g., 'employee satisfaction β current score 6.2/10, industry benchmark 7.5') makes them more credible without fabricating a dollar figure.
6
Calculate BCR, net benefit, and payback period
Sum your 3-year (or chosen period) benefits and costs, divide to get the BCR, and subtract to get net benefit. Build a month-by-month cumulative table to identify the break-even point.
π‘ If your BCR is between 1.0 and 1.3, the margin is thin β a small cost overrun or benefit shortfall flips the analysis negative. Flag this explicitly.
7
Run a downside sensitivity test
Model what happens if benefits come in at 70% of projection and costs run 20% over budget simultaneously. If the BCR still exceeds 1.0, the decision is robust. If it falls below 1.0, note the conditions that would trigger a project pause.
π‘ Present the sensitivity table before the recommendation β it signals analytical rigor and pre-empts the most common reviewer challenge.
8
Write a clear go or no-go recommendation
State your recommendation in the first sentence, supported by the BCR and payback period. Identify the single most material risk and the proposed next action with an owner and date.
π‘ Decision-makers read the recommendation first. If it is vague, they discount the entire analysis. Be direct: 'This analysis recommends approval' or 'This analysis recommends deferral pending X.'