Due diligence

What IT problems could cost a business buyer

Before buying a business, find out what it would cost to keep its systems running and connect them to yours. Those costs can change the price worth paying.

A buyer may base an acquisition price on growing sales and lower operating costs. But those plans depend on the acquired business continuing to take orders, deliver goods and collect payment. Before agreeing the deal, the buyer needs to know what could interrupt that work and what it will cost to keep it running. These checks are part of due diligence: examining the business's claims, records and commitments before buying it.

Checking security and recovery arrangements can reveal costs missing from the business plan. It does not, by itself, prove the business deserves a higher price or cheaper borrowing. A reassuring report is less useful than a clear account of which services the business relies on, what staff can recover after a failure and what the buyer will need to pay for.

Follow an order through to payment

Take an important piece of work, such as receiving an order and delivering it, and trace the systems, suppliers and people it needs. Ask what happens if one is unavailable. Can staff still see what the customer ordered? Can the warehouse dispatch it? Can accounts issue an accurate invoice? Several teams may depend on the same sign-in service or the same specialist, so one failure could stop more than one part of the business.

A list of software and suppliers is a starting point, not proof that work can continue. Talk to the people doing the work and examine exercises that show what happens when something fails. Separate what those exercises demonstrated from management's estimates. If the buyer cannot inspect an important service or supplier arrangement, say which question remains unanswered and how it could affect the purchase decision.

Check whether staff could resume work after a failure

Ask what a recovery exercise actually demonstrated. Which systems and records were restored, who did the work and what help did they have? Restarting a system may not be enough. Staff may need to check which orders were entered by hand during the interruption so they do not miss or duplicate them. Also check whether the people, sign-in access and equipment used in the exercise would be available during the failure being considered.

No recorded security incidents does not prove there were none or that future risk is low. The business may not have monitored all its systems, and its use of them may have changed. Age alone is also a poor guide to a system's reliability. Older software with continuing support differs from software nobody will repair and only one employee understands. The buyer needs to know what will keep working and what recovery would require.

Separate existing repair costs from the buyer's changes

Some work will be needed even if the buyer changes nothing. Software without supplier support may need replacing. Unresolved faults may need repair. Work understood by only one specialist may need documenting and teaching to others. Estimate the cost, staff time and interruption with the people who will do the work. Show a range where the extent of the problem is still uncertain, rather than presenting an unsupported fixed amount.

The buyer's plans can create additional work. Connecting the two companies' networks or combining staff sign-in systems may give people access they did not have before. Existing safeguards may need changing so that staff see only the information they should. Include those costs in the plan for combining the businesses. An assessment of today's arrangements does not establish that the proposed arrangements will work safely.

Show how each finding changes the purchase assumptions

Work with finance to distinguish repairs paid for once from costs the business will face every year. Examine what an interruption would do to sales and payments. An order delivered late may delay cash coming in without losing the sale. A cancelled order loses income, but may also avoid some material or delivery costs. The lost income minus those avoided costs is called lost contribution: the money the order would have left to cover other costs and profit. This is why the full selling price is not always the business's loss.

Check when money would be needed as well as how much. Recovery bills may arrive before customers pay, requiring cash or borrowing to bridge the gap. Ask how slower system changes or more maintenance would affect the business plan and the price the buyer is willing to pay. Where future amounts are discounted in a valuation, finance adjusts them to today's value: money expected later is not equivalent to money available now. Findings need to change the relevant cost, timing or uncertainty in that calculation, rather than sit in a separate technical report.

Trace each proposed adjustment to the problem it addresses. If the forecast already includes a repair cost, adding a reserve for the same repair and then seeking a further price reduction for it could count the cost repeatedly. Finance, commercial and legal teams must decide how findings affect the forecast and deal terms. The people checking systems provide evidence for that decision; their report cannot determine the price alone.

Give the people taking over the unresolved questions

After the deal, the managers responsible for the business need the findings, not just the conclusion that checks were completed. Hand over the services and suppliers on which work depends, unanswered questions, agreed actions and the people responsible for them. State what must be done before systems are connected and what can wait. Restrict sensitive details to the people who need them; a public announcement is not the place for information that could help someone attack the business.

In the hypothetical distributor, the manager combining the systems needs evidence that records can be moved, the service recovered and access restricted correctly before committing to the timetable. Until that evidence exists, keep the uncertainty and the cost of resolving it in the plan. Completing the purchase does not make those operating assumptions true.

Where this applies in our work: estimating cyber loss and disruption.