Work World
14,264 views
25 min · 2 min read
7 steps
Advanced

How to conduct a basic cost-benefit analysis for a small project

A basic cost-benefit analysis helps you decide whether a small project is worth doing by comparing expected costs and benefits in simple numeric terms. This guide walks you through a straightforward, practical process you can complete in a few hours using a spreadsheet or notebook. Keep it focused and conservative so your result is useful for a real decision.

Verified by pleasexplain editors
  1. Step 1: Define the project clearly

    Write a one-sentence objective and list the main deliverables. Limiting scope to 2–5 tangible outcomes reduces ambiguity and makes cost and benefit estimates more reliable.

    [Illustration: notebook page with one-sentence project goal and 3 bullet deliverables]

  2. Step 2: Set the time horizon

    Choose a realistic period to evaluate, usually 3–12 months for small projects; this keeps estimates manageable and avoids long-term forecasting noise. Note the start and end dates and any phased milestones.

    [Illustration: calendar showing a 6-month span with milestones marked]

  3. Step 3: List all costs

    Enumerate direct and indirect costs: materials, labor hours, contractor fees, equipment rental, and overhead. Quantify each as a number and currency, for example 40 hours at $30/hour = $1,200, plus $200 for materials.

    [Illustration: spreadsheet rows with cost items, quantities, unit prices, and totals]

  4. Step 4: Estimate benefits in value

    Identify quantifiable benefits such as increased revenue, saved time, or reduced expenses; convert them to currency using conservative assumptions. For example, saving 10 hours/month at $25/hour equals $250/month or $1,500 over 6 months.

    [Illustration: chart converting time savings and revenue increases into dollar amounts]

  5. Step 5: Assign probabilities and adjust

    For uncertain benefits or costs, apply a probability factor (e.g., 50–80%) to avoid overoptimism. Multiply the base estimate by the probability to get an expected value; this makes the comparison more realistic.

    [Illustration: calculator and probability percentages being applied to dollar figures]

  6. Step 6: Calculate net present values

    Sum expected benefits and subtract total costs to get net benefit. For horizons over 6 months, discount future values by a modest rate (e.g., 3–5% per year) to compare apples-to-apples. Present results as total net value and benefit-to-cost ratio.

    [Illustration: simple equation on paper showing benefits minus costs equals net benefit and a ratio]

  7. Step 7: Review sensitivity and decide

    Run 2–3 scenarios (pessimistic, realistic, optimistic) changing key numbers by ±25%. If net benefit is positive in realistic and pessimistic cases, proceed; if not, revise scope or reject the project.

    [Illustration: three-columns table labeled pessimistic, realistic, optimistic with different net values]


  • Keep the list of costs to under 20 line items to stay practical.
  • Use 1–2 trusted colleagues to sanity-check key assumptions in about 30 minutes.
  • Document assumptions next to each number so you can revisit them later.
  • When estimating labor, include a 10–20% buffer for unexpected hours.
  • Round estimates to reasonable precision, e.g., nearest $10 or nearest hour.
  • If benefits are non-monetary (morale, brand), assign a small proxy dollar value and label it qualitative for transparency.
  • Use a simple spreadsheet template with formulas to avoid manual arithmetic errors.

  • Avoid inflating benefits to justify the project — overoptimistic inputs give misleading results.
  • Do not ignore recurring costs; small monthly fees add up and can flip the analysis.
  • Be wary of double-counting benefits, such as measuring the same time savings in two different places.
  • If a benefit depends on another uncertain event, treat it as conditional and reduce its expected value accordingly.
  • Do not use more than three decimal places or overly complex discounting for small, short projects — it creates false precision.

Was this guide helpful?