You paid for the software. Nobody uses it
TL;DR
Your team did not reject the software. They quietly stopped opening it, and the work moved back to WhatsApp.
Zylo's 2026 index, built on 40 million licences, puts 36% of paid licences unused, at a median spend of $9,455 per employee a year.
The tool failed for one of three reasons: it did not match how the team actually works, nobody owned it after launch, or it asked for more effort than the chat it replaced.
Before you buy another tool, run the four-week check in this article. If the team is not living in it by week four, cancel it.
The fix is rarely a better tool. It is one system built around the work your team already does.
You bought the CRM on a good day. The demo looked clean. The sales call promised your follow-ups would never slip again. You paid for five seats, sent the team the login link, and moved on.
Three months later, open the tool. When was the last lead logged? When was the last task closed inside it? Now open WhatsApp. That is where the work actually lives. The customer photos, the price quotes, the "call him tomorrow" messages, all of it sits in chats, not in the software you pay for every month.
Nobody told you the tool failed. Nobody quit it in a meeting. It just faded. That quiet fade is the most common software failure in a small business, and it costs more than the subscription. It costs you the one thing the tool was meant to give you: a place where the work lives when nobody is watching it.
How common is software nobody uses?
Very common, and the people who measure it sell the tools that fix it, so read the numbers as direction, not gospel.
Zylo's 2026 SaaS Management Index, built on more than 40 million licences and $75 billion in tracked spend, puts 36% of paid licences unused, against a median spend of $9,455 per employee per year. The same index puts the average portfolio at 305 applications, with large enterprises adding around 21 new ones a month. Vertice's Q2 2026 data goes further: 65% of licences are unused or underused, with 14% fully unused and 51% used at less than half their capacity. BetterCloud's 2026 survey, which leans toward smaller companies, puts the average at 118 apps per company, up from 106 the year before.
The numbers disagree with each other because the datasets are different. The direction does not change. A large share of what companies pay for sits unopened, and the count keeps growing while the usage does not. Your business is smaller than the companies in those indexes. Your version of the same problem is one CRM, one project tool, one invoicing app, paid monthly, opened by nobody.
Why did your team stop using it?
Because the tool asked them to change how they work, and WhatsApp did not.
Think about the day the CRM arrived. Your salesperson was already doing the job in WhatsApp. A customer messaged, they replied, they quoted a price, they set a reminder in their head. The CRM asked them to leave that flow, open a second app, type the same details into a form, and set a status. That is extra work, every single time, for a benefit they never felt. The benefit went to you, the founder. The cost went to them.
So they did what anyone would do. They kept the customer in WhatsApp and filled in the CRM later, when they remembered. Then they filled it in at the end of the week. Then they stopped. The tool did not fail in a dramatic way. It lost a small contest, repeated daily, against the chat app that was already open.
There are three usual reasons, and most dead tools have at least two of them.
First, the tool did not match the real work. It was built for a sales team with stages and pipelines. Your team has conversations and follow-ups. The fields did not fit, so the team worked around them, and the workaround became the system.
Second, nobody owned it after launch. You bought it, announced it, and moved on to the next fire. Nobody checked the usage in week two. Nobody asked why the logins stopped. A tool with no owner dies in about a month, quietly.
Third, it solved your problem, not theirs. You wanted a dashboard. They wanted fewer steps between a customer message and a closed job. A tool that gives the founder visibility and the team extra typing will always lose to the chat.
How do you know if your software is already dead?
Run this check. It takes ten minutes and it tells you the truth faster than any renewal reminder.
Open the tool and look at the last ten entries. When were they made? If the newest one is more than a week old while the business ran all week, the tool is dead. It is a museum, not a system.
Now count the seats. How many did you pay for, and how many people opened it in the last 30 days? If you paid for five and two open it, you are paying for three ghosts. That is the same maths as every new hire raising your software bill, except here the seats were never real in the first place.
Then ask your team one question, in person, not in a form: "Where do you actually track this work?" If the answer is a chat, a notebook, or "in my head", the tool has already been replaced. The replacement just does not send you an invoice.
Last entry is over a week old: The team stopped logging: You pay for a museum
Fewer logins than seats: You pay for ghosts: Per-seat fees for nobody
Work lives in WhatsApp: The chat won the contest: No record when someone leaves
Same data typed twice: The tool adds work: Double entry, half the accuracy
Nobody can say who owns it: No owner, no adoption: It dies again next month
What should you do before you buy another tool?
Stop buying tools for a month. That sounds extreme, and it is the point. The last tool did not fail because it was the wrong brand. It failed because the work had no home. Buying a second tool into the same gap repeats the failure with a new logo.
Instead, do this. Pick the one job the dead tool was meant to do. For most small businesses it is one of three: follow up with leads, track jobs from quote to payment, or know who owes what. Write down, in plain words, how that job actually happens today, step by step, starting from the customer's first message. Not how it should happen. How it happens.
Then ask the team what the smallest change would be that makes their day easier, not your dashboard better. If they say "I want the quote and the follow-up in the same place", that is the requirement. If they say "I want to stop retyping the customer's name", that is the requirement. Build or buy to that requirement, and nothing else.
That is also why a generic tool keeps losing to WhatsApp. WhatsApp already does the thing your team cares about: the conversation is right there, the reply is one tap, and nothing needs typing twice. Any system that replaces it has to be at least that easy, or it will lose the same contest. This is the same lesson as your lead going cold in seven days: the follow-up did not fail for lack of a tool. It failed because the reminder lived nowhere the team actually looks.
What does a system that actually gets used look like?
It looks like the work, not like software.
It starts where the customer starts. If customers come through WhatsApp, the system takes the conversation from WhatsApp instead of asking the team to retype it. If quotes go out as photos, the system keeps the photo next to the job, not in a separate folder. The team does the same steps they already do, and the record builds itself behind them.
It has one owner. Not a committee, not "everyone". One person whose job includes checking that the work is in the system, and who is allowed to change the system when it gets in the way. You hired help to save time and ended up managing them for the same reason: a job with no owner drifts back onto the founder's desk.
And it has a finish line. A tool earns its keep in four weeks or it goes. That is a rule you set before you buy, not a feeling you check at renewal time. Four weeks, one owner, one job, real usage. If the team is not living in it by week four, cancel it and keep the money. That is cheaper than paying for a year of good intentions, and it is the same discipline as refusing a retainer that bills whether anything ships or not.
The bigger point is about ownership. A tool you rent per seat is a tax that grows with your team, and you own nothing when you stop paying. A system built around your work, that you own, does not charge you again for the next hire. That is the shape we build at BaseEngine: your operations, in one place you own, instead of a stack of subscriptions your team quietly abandons. And if you are comparing shapes before you commit, read what one monthly fee hides about your value and what happens when a retainer ends and nobody tells you, because the same questions apply to software: what do you own, what do you pay for, and who notices when it stops working.
The four-week check, in short
Week one, name the one job and the one owner. Week two, watch where the work actually happens, not where you hoped it would. Week three, fix the one friction the team names, not the one the demo showed. Week four, count the logins and the entries. If the work lives in the system, keep it. If it lives in WhatsApp, cancel the subscription and admit the chat won. Then build the system around the work instead of buying another tool to fight it.
Your team was never lazy about software. They were rational. They picked the tool that cost them the least effort. Make your system the easiest option, and they will use it without being chased.
Frequently Asked Questions
How much money do companies waste on software nobody uses?
Zylo's 2026 index puts 36% of paid licences unused, at a median spend of $9,455 per employee per year. Vertice's Q2 2026 data puts 65% of licences unused or underused. Both datasets come from vendors who sell licence management, so treat the figures as direction, not precision. Your own invoice is the honest number.
Why do teams go back to WhatsApp after a CRM is bought?
Because WhatsApp is already open, the customer is already there, and replying costs one tap. The CRM asks the team to leave that flow, retype the same details, and update a status, which is extra work for a benefit only the founder feels. The chat wins that contest every day unless the system removes steps instead of adding them.
How do I check if my team actually uses our software?
Open the tool and check the last ten entries. If the newest is more than a week old while the business ran all week, it is dead. Then compare seats paid for against people who logged in during the last 30 days. Then ask the team where they really track the work. The answer is usually a chat, a notebook, or memory.
Should I buy a cheaper tool instead?
A cheaper tool fails the same way if the work has no home. Price was not the problem. The problem is that the tool did not match how the team works, nobody owned it after launch, and it solved the founder's problem instead of the team's. Fix the home first, then pick the tool, at any price.
When should I cancel a tool nobody uses?
Set the rule before you buy: four weeks, one owner, one job, real usage. If the team is not living in it by week four, cancel it. Waiting for the renewal date buys more months of intentions. The money saved is the smallest part. The bigger win is admitting the system must fit the work, not the other way round.