Buying Is Not the Decision
Buying software feels like the decision. The real one comes afterwards, and it usually never gets made. Industry data shows it plainly: more than half of all licences are either unused or used too rarely to justify the cost.
Money went out, the system got installed, the work stayed the same. A step went missing in between, and that step rarely appears in anyone’s plan.
Why Is the Question Being Asked Now?
BU BÖLÜMÜN ÖZETİ
- Buying got easy
- The invoice became visible
- Application counts are falling
- AI tools repeat the same pattern
Four developments made it visible.
Buying got easy
A card and five minutes cover it. No approval process, no implementation team, no long contract. What gets easier multiplies; the threshold for deciding dropped, and what is bought easily is forgotten just as easily.
The invoice became visible
Waste now gets calculated per employee. It stopped being an abstract budget line. Something visible has to be defended, and a per-person figure is hard to argue with.
Application counts are falling
Numbers that climbed for years reversed. Companies stopped accumulating and started selecting. The shift is deliberate and widespread; the hoarding era is closing.
AI tools repeat the same pattern
A new wave of tools arrived and the same mistake is being made. Bought, barely tried, forgotten. The pattern is familiar and only the category is new; the lesson has clearly not landed yet.
What Is Wrong?
BU BÖLÜMÜN ÖZETİ
- “The right tool will fix this”
- “Installation done, job done”
- “The team will get used to it”
- “We might need it later”
Four assumptions keep the cycle going.
“The right tool will fix this”
The search never ends because the problem is not the tool. Buying new software is a comfortable way of postponing a decision. It feels like action while the picture stays exactly where it was, and three months later you are at the same point with one more line on the invoice.
“Installation done, job done”
Accounts opened, data migrated. The work looks finished. Yet the habit has not changed and the real work begins here, which is generally where nobody begins.
“The team will get used to it”
Getting used to something does not happen by itself. While two methods stay open, the familiar one wins. That is not resistance but a natural preference, and nobody was given a reason to choose the harder path.
“We might need it later”
That sentence pays the same invoice every year. A tool unused this year will go unused next year too. Postponement is not a decision. It is indecision, and the cost gets paid quietly.
The Real Mechanism
BU BÖLÜMÜN ÖZETİ
- Stage 1: the purchase
- Stage 2: the installation
- Stage 3: the switch
- Stage 4: settling
A tool enters the work through four stages.
Stage 1: the purchase
The easiest and most visible stage. Budget approved, payment made. In most businesses the process ends here and gets treated as complete, though nothing about the work has changed yet.
Stage 2: the installation
Accounts, data migration, settings. A technical task with a definite end. But once installation finishes, the tool does not start being used; it only becomes usable. The gap between those two is wide.
Stage 3: the switch
Leaving the old method and settling into the new one. This stage takes weeks and needs an owner. The switch method covers exactly this ground, and this is the stage that gets skipped — not because it is hard, but because it was never planned.
Stage 4: settling
The tool becomes a normal part of the work. People use it without thinking. Far fewer tools reach this stage than get bought, and that difference is the waste itself.
Who Is Affected, and How?
BU BÖLÜMÜN ÖZETİ
- The one-person business
- The small team
- The business with separate teams
- The fast-growing business
Four profiles.
The one-person business
The buyer and the user are the same person, which is an advantage: no persuasion is needed for the switch. But there is a risk too. With nobody to remind you, a stalled setup goes unnoticed. A calendar reminder three months out closes that gap.
The small team
The easiest environment for a switch. Everyone sees everyone, so blockages surface immediately. The usual omission here is failing to name an owner; whoever installed it does not run the switch and the tool ends up in limbo.
The business with separate teams
Each team buys its own tool. The same job gets paid for two or three times over and nobody knows about the others. A central list is the only remedy; an inventory exposes those duplicates immediately.
The fast-growing business
Every new need brings a new tool and nobody stops to look during growth. Two years later the list holds items nobody recognises. An annual inventory prevents that accumulation, though a six-month rhythm suits this profile better.
Decision Order
BU BÖLÜMÜN ÖZETİ
- One: build the inventory
- Two: decide on each item
- Three: plan a switch for what you keep
- Four: set a rule for new purchases
Four steps.
One: build the inventory
What are you paying for? Bank statements suffice. The list takes an hour and usually surprises; forgotten items surface.
Two: decide on each item
Use it or close it. Leaving it in the middle is not a third option and costs the most; you pay for it and get nothing.
Three: plan a switch for what you keep
One job, one owner, one date. Without a planned switch the tool stays idle and the decision comes to nothing.
Four: set a rule for new purchases
Two questions before buying anything: do we already have a tool that does this, and who will run the switch? If neither has an answer, the purchase is premature.
Where to Start?
BU BÖLÜMÜN ÖZETİ
- Draw up the list
- Mark the idle ones
- Settle one of them
- Set the renewal calendar
Four jobs, the first week.
Draw up the list
Twelve months of recurring payments. It takes an hour and catches the annual items too.
Mark the idle ones
Anything untouched for three months. A few items usually turn up, some of them forgotten.
Settle one of them
Either put it to work or close it. Starting with one is enough; everything need not be solved at once.
Set the renewal calendar
Write each date and set a reminder a month ahead. The decision gets made then.
What Not to Do?
BU BÖLÜMÜN ÖZETİ
- Trying to fix it by buying
- Moving everything at once
- Leaving the old route open
- Postponing the decision
Four traps.
Trying to fix it by buying
If the existing tool goes unused, a new one will too. The problem sits in the switch rather than the tool. A new purchase only lengthens the list and makes the same problem bigger.
Moving everything at once
Migrating every process simultaneously overwhelms the team. Errors rise and within weeks everyone reverts. Diagnosing the cause prevents that from the start.
Leaving the old route open
Out of politeness the old method stays available. But with two doors open the familiar one wins, and the switch never finishes. Setting a date breaks that loop.
Postponing the decision
“We might need it” repeats annually. Three years on, the total is a serious figure. A decision can be reversed; indecision cannot, and it recurs every year.
A Solid Digital Foundation
BU BÖLÜMÜN ÖZETİ
- The software inventory
- The renewal calendar
- The switch owner
- Two questions before buying
Four stones.
The software inventory
Tool, cost, owner, last use. Four columns, updated annually.
The renewal calendar
Which tool renews when? A reminder sits a month ahead of each date.
The switch owner
A name for every new tool. Half an hour a week is enough.
Two questions before buying
Do we have a tool for this? Who runs the switch? No purchase happens without both answers.
Frequently Asked Questions
Sık Sorulan Sorular
The money already left and not using it does not bring any back. The real question is what you will pay from here. Keeping an unused tool does not rescue the past spend; it enlarges the future one. Decide by looking at the next twelve months rather than the last three years. If you will use it, plan the switch. If you will not, close it.
Find the cause first. Why is the current tool unused: is it unknown, unsuitable, or was the switch simply never made? Buying something new without knowing produces the same outcome. If the current tool genuinely does not fit, replacing it is right. But if it goes unused because no switch happened, the new one lands in exactly the same place.
The structure is one table and two questions. An hour to set up, an hour a year to maintain. In a small business it is also easier: the person deciding does the implementing and no approval chain waits. The same work circulates for months in a large organisation. So the smaller the scale, the lighter this gets rather than the more redundant.
It happens and it is spreading fast. When a new wave arrives everyone tries something and most of it gets forgotten. One difference stands out: these tools are usually cheap, so the invoice does not draw attention and they never enter the inventory. The confusion cost is identical though. The same rule applies here: close what goes unused, and plan the switch for what you keep.