Technology budgets are usually argued in two registers. The first is efficiency: this will save time. The second is fear: if we do not do this, something bad may happen.
Both are weak arguments, for the same reason. Neither connects to a number the owner, the board or the buyer of the business actually cares about.
There are four that do.
Revenue
Technology affects revenue in more direct ways than most companies credit.
It decides whether you can serve a client segment at all. A firm that cannot pass an institutional client's security review does not lose on price; it never gets to the price conversation. A contractor without the required insurance and controls is not on the bid list.
It decides cycle time on the commercial path. How long from enquiry to proposal, from proposal to contract, from contract to delivery. Every handoff that runs through a spreadsheet and an email adds days, and days compound into a win rate.
And it decides whether you can grow without proportionally growing headcount, which is the difference between a business that scales and one that adds people to add revenue.
The measurable version: win rate by segment, cycle time by stage, revenue per employee.
Margin
The obvious part is cost: licences nobody uses, duplicate tooling, contracts renewed at list price, support arrangements bought twice. Real money, and usually the first thing found.
The less obvious and larger part is rework. Data entered twice. Numbers reconciled by hand every month. Reports rebuilt from exports. This work is invisible in the accounts because it is done by people who are already on the payroll, and it is frequently several times larger than the software spend it exists to compensate for.
The measurable version: total technology cost as a percentage of revenue, benchmarked against peers, and hours of manual reconciliation per month.
Risk
Not risk in the abstract. Risk as a distribution of outcomes with money attached.
The question is not whether you might have an incident. It is what the range of outcomes looks like if you do, and whether that range is one the business can absorb. A company that can restore operations in a day has a different distribution from one that cannot restore at all, and the difference is worth pricing.
The same applies to concentration: single points of failure in systems, in vendors and in individual people who are the only ones who understand something.
The measurable version: recovery time actually demonstrated by a test, coverage of the small number of controls that matter, and a register of accepted risks with named owners.
Valuation
This one is specific and it is the one most often missed by owner-managed businesses.
A buyer or a lender pays for predictability. Financial reporting that is timely and consistent, systems that a new owner can operate without the founder, contracts that are documented and transferable, and an absence of unpleasant surprises in diligence.
Technology affects all four. It is also where diligence findings most reliably produce either a price adjustment or an escrow, and where remediation costs get deducted from the number on the offer.
The measurable version: days to close the month, key-person dependencies, diligence findings raised and closed.
What this is for
The point is not to produce a scorecard. It is to change the conversation about a technology decision from "is this worth doing" to "which of these four does it move, by how much, and how would we know."
A proposal that cannot answer that is usually a proposal that should wait.