Present Worth Analysis for Technology Infrastructure Build-vs-Lease Decisions

Understanding the Build-vs-Lease Alternatives

When a company needs computing power, storage, or networking capabilities, it faces a fundamental choice that has significant financial implications. The decision boils down to two primary models:

1. Build (or Buy): This is the traditional On-Premise model. The company purchases physical servers, racks, networking equipment, and other hardware. This involves a significant upfront Capital Expenditure (CapEx). The company then owns these assets and is responsible for all ongoing Operating Expenses (OpEx), such as power, cooling, maintenance, security, and the salaries of the IT staff who manage it all.

2. Lease: This is the model behind Cloud Computing (e.g., Amazon Web Services, Microsoft Azure). Instead of buying hardware, the company rents capacity from a cloud provider. This model avoids the large initial CapEx and instead involves predictable (or usage-based) operating expenses in the form of monthly or annual subscription fees.

To better understand the strategic trade-offs before we dive into the numbers, it's helpful to review the general pros and cons of leasing versus buying capital assets.

As you've just read, the decision is a trade-off. Buying offers control and potential long-term cost savings, but requires a large initial investment and carries the risk of technological obsolescence. Leasing offers flexibility, scalability, and lower upfront costs, but can be more expensive over the long term and leads to vendor dependency.

Our job with PW analysis is to quantify this financial trade-off.

Applying Present Worth Analysis: A Case Study

The PW analysis for a build-vs-lease decision follows the exact same steps we used for make-vs-buy: define a study period, identify all cash flows for each alternative, and discount them to time zero using the Minimum Acceptable Rate of Return (MARR).

Let's ground this in a realistic case study. The following paper from MIT presents a detailed cost comparison of Cloud vs. On-Premise computing. We'll use the data from this paper to perform our own PW analysis.

The paper's analysis in Table 2 calculates a simple "cross-over" point where the cumulative undiscounted cost of one option becomes cheaper than the other. However, this ignores the time value of money. Let's apply a proper PW analysis to their data.

Scenario:
From the paper's simplified example (Table 2), let's analyze the costs over a 5-year study period with a MARR of 12%.

• Alternative 1: Lease (Cloud)

  • Annual Subscription Cost: $3,000 (assumed to be paid at the end of years 1-5).

• Alternative 2: Build (On-Premise)

  • Initial Purchase Cost: $6,000 (at year 0).
  • Annual Maintenance Cost: $1,080 (at the end of years 1-5).
  • Let's assume a salvage value of $500 for the hardware at the end of year 5.

PW Calculation:
We need the following factors for i=12%, n=5:

• (P/A, 12%, 5) = 3.6048
• (P/F, 12%, 5) = 0.5674

1. Present Worth of Lease (Cloud)
$P{W}_{Lease}=-(\text{Annual Cost})(P/A,12\%,5)$
$P{W}_{Lease}=-3,000(3.6048)$
$P{W}_{Lease}=-\$10,814$

2. Present Worth of Build (On-Premise)
$P{W}_{Build}=-(\text{Initial Cost})-(\text{Annual Cost})(P/A,12\%,5)+(\text{Salvage Value})(P/F,12\%,5)$
$P{W}_{Build}=-6,000-1,080(3.6048)+500(0.5674)$
$P{W}_{Build}=-6,000-3,893+284$
$P{W}_{Build}=-\$9,609$

Decision:
The Present Worth of the cost to build is -$9,609, while the PW of the cost to lease is -$10,814. Since -$9,609 is "less negative" than -$10,814, the Build (On-Premise) option is the more economical choice under these assumptions.

This shows how PW analysis provides a more definitive answer than a simple crossover point calculation, as it correctly accounts for the timing of the cash flows.

Beyond the Simplified Example

Real-world scenarios are often more complex. The "Cloud versus On-Premise Computing" paper goes on to model a more realistic situation with gradual user adoption.

When cash flows are not a uniform series, as in the gradual ramp-up scenario, we can't use the P/A factor directly. Instead, we would calculate the Present Worth by treating each year's cost as a single future amount (F) and discounting it back to the present using the P/F factor, then summing them all up. This is tedious by hand but trivial with a spreadsheet.

The key takeaway is that the underlying method remains the same, regardless of the complexity of the cash flow pattern.

Conclusion

You have now successfully extended your knowledge of Present Worth analysis to evaluate build-vs-lease decisions for technology infrastructure. This is a vital skill for making sound capital investment decisions in any technology-driven company.

• Key Takeaways:
  • The build-vs-lease decision is a comparison between a high-CapEx, lower-OpEx alternative (On-Premise) and a no-CapEx, higher-OpEx alternative (Cloud/Lease).
  • Present Worth analysis provides the financial framework to compare these different cost structures on an equal footing.
  • The alternative with the lower Present Worth of cost (the less negative value) is the financially preferred option.
  • The quantitative result must always be balanced with strategic factors like scalability, control, security, and vendor risk.

Preview of the Next Lesson

In our next module, we will introduce a new but closely related method of analysis. The next lesson's goal is to convert project cash flows to an equivalent uniform annual worth (AW). Annual Worth analysis is another way to compare projects, and it is especially useful when you need to compare alternatives that have different useful lives. You'll see how it directly relates to the PW calculations we've been mastering.