Why the percentage question is the wrong question
Founders often ask what percentage of revenue they should spend on technology, hoping for a number they can budget against. It is an understandable question with an unhelpful answer, because no single percentage fits every business.
Two companies with identical revenue can have completely different technology needs. One might run on a handful of cheap tools; another might depend on software for the thing that makes it competitive. A benchmark percentage tells you what other businesses spend, not what your business should spend.
The better question is not "what is the right number" but "what is each investment worth to me." Answer that for each decision, and the total budget emerges from real reasoning instead of a guess borrowed from someone else's business.
Spend on outcomes, not on tools
Technology spending goes wrong when it is organized around tools rather than outcomes. It is easy to accumulate subscriptions, each individually cheap, that collectively drain money without moving the business.
Start from the outcome instead. What costly, recurring problem are you trying to remove. How much does that problem cost you now in time, errors, or lost revenue. A system that removes a genuine, expensive problem earns its budget many times over. A tool that solves a problem you do not really have is pure cost.
This reframing also stops you spending on technology for its own sake. New software is not automatically progress. Spending is justified by the outcome it produces, and if you cannot name the outcome, you are not ready to spend.
Count the total cost of ownership
Every technology decision has a headline price and a real price, and they are rarely the same. The monthly subscription or the quoted build cost is only the start.
The real cost over three years includes setup and configuration, migrating your existing data, training your team, building integrations to your other systems, per-user fees as you grow, and the cost of switching if it does not work out. A tool that looks cheap can be expensive once all of this is counted.
Comparing options on their headline prices leads you to the wrong answer confidently. Compare them on total cost of ownership over the horizon you actually care about, and the cheapest option often turns out to be the most expensive one.
- Include setup, migration, and training, not just licenses.
- Model per-user pricing at the size you expect to be, not today's size.
- Count the cost of integrating the tool with your other systems.
- Factor in the cost of leaving if the tool does not keep up.
Weigh spend against return, in money
The cleanest way to decide how much to spend on any given piece of technology is to put both sides in the same units: money, over the same period.
On one side, estimate the return: hours saved and what they are worth, errors avoided, revenue captured, cost removed, all over three years. On the other side, the total cost of ownership over the same three years. If the return clearly beats the cost, the spend is justified, regardless of what percentage of revenue it represents.
This discipline does two things. It gives you a real basis for saying yes to spends that look expensive but pay back, and it gives you the confidence to say no to cheap tools that produce no measurable return. Return, not price, is what makes a technology purchase good or bad.
Concentrate spend where you compete
Not all technology deserves equal investment. The systems that are core to how you win are worth more of your budget than the commodity tools everyone uses the same way.
For commodity work, such as email or basic bookkeeping, buy something reasonable and cheap and stop thinking about it. Reserve your real investment for the processes that are your advantage, where fit and control genuinely matter. Overspending on commodities and underspending on your core is a common and costly imbalance.
There is a second reason to concentrate spend deliberately: connection. Money spread across disconnected tools produces silos, and silos force manual re-keying that eats the savings you were chasing. Spending that keeps your core systems talking to each other returns far more than the same money scattered across tools that ignore one another.
Protect the value of what you spend
A technology spend is only as good as its durability. Money spent on a tool that traps your data or cannot connect to anything is money at risk, because the day you outgrow that tool, you pay again to escape it.
Protect every purchase with two commitments from the vendor: you can export all your data cleanly at any time, and the system can integrate with your others through a real interface. Those two things keep today's spend from becoming tomorrow's trap. They mean you can change your mind, add new tools, and grow without starting over.
Think of it as spending for optionality. The best technology investments not only return value now but leave you free to make new choices later. Lock-in quietly destroys the value of a spend by removing your ability to change course.
How to set your number
Put it together and the budget builds itself. List the processes that cost you the most in waste and the ones most central to how you compete. For each, estimate the return of fixing it and the total cost of ownership of the fix over three years. Fund the ones where the return clearly beats the cost, starting with the biggest gaps, and keep those systems connected so data flows instead of being re-typed.
What you will not have is a tidy percentage of revenue, and that is fine. You will have something better: a spend justified by outcomes, sized to your business rather than someone else's benchmark, and protected against lock-in.
At Upeosoft we both build custom software and implement platforms like ERPNext, so we help founders decide not just what to spend but whether to spend at all on a given problem. If you want an honest read on where technology will actually pay back for your business, and where it will not, talk to us before you commit the budget.
