How to Judge Whether Borrowing for a Technology Project Is Worth It

Ad Blocker Detected

Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker.

A technology or software proposal can promise faster work, lower costs or happier customers. The difficult part is deciding which benefits are plausible, which can be measured, what the project will really cost—and, if you plan to borrow, whether the loan still makes sense once interest, fees and repayment are included.

This is a structured way to examine those questions. It is a method for making assumptions visible, not a device that guarantees an accurate forecast. It is general information, not financial, legal or tax advice.

Six steps for reviewing the case

  1. Determine the purpose. What decision does the analysis need to support? For example: should we buy this tool, delay it, or not proceed? If a loan is involved, the question also includes whether the expected benefits can support the repayments.
  2. Choose the area of investigation. Decide the scope, whose perspective counts (the business, a department, customers) and what you will leave out. A narrow scope can hide costs that fall on another team.
  3. Describe the situation and choose a comparison. Identify the people and processes the project would affect. Choose a comparison, such as doing nothing, improving the current process, or choosing a smaller option. Benefits only have meaning relative to that comparison.
  4. Identify benefits. Explore the consequences and how a benefit might create value—saved time, avoided cost, extra sales, fewer errors or better service. Ask whether a “saving” can actually be turned into lower spending or into work that would not otherwise get done.
  5. Quantify what can be measured. Choose suitable measures and formulas where a reasonable estimate is possible. Some effects are too uncertain to express reliably as a number. Those should be discussed and evidenced, not dressed up as precise cash.
  6. Calculate the value and the full cost. Translate quantified effects into money and set them against implementation, licenses, integration, training, support, security, exit costs—and, if you borrow, interest, fees and the repayment schedule. Watch for counting the same benefit twice under different headings.

Why borrowing changes the test

A project funded from cash and the same project funded with a loan are not the same case. Loan interest and fees are additional cash outflows. Repayments usually continue even if the promised savings arrive late or not at all. If the loan is secured, a shortfall can put other assets at risk.

Include those terms in the cost side from the start. A case that looks acceptable before financing can fail once the cost of borrowing is added. Test an optimistic and a pessimistic scenario, and be explicit about the evidence behind adoption, prices and timing.

The quality of the result depends on the assumptions you use. A low headline price, or a vendor’s estimate of hours saved, is useful information. It is not a decision on its own.

Leave a Reply