You pay for software. Your team uses WhatsApp.
TL;DR
You bought the tool. The team quietly stopped opening it.
The bill did not notice. It renews every month, per seat.
Across firms, roughly a third of SaaS licences sit unused, and half of all licences go a full year without a login.
You are not paying for software. You are paying for adoption that never happened.
Audit the seats this week, kill the shelfware, and buy one system your team will actually open.
You bought the CRM because the demo was smooth. You bought 14 seats because that is how many people you had. Today six of them log in. The other eight live in the WhatsApp group, same as before.
Nobody told you they left the tool. They just stopped opening it. The renewal, on the other hand, tells you nothing. It arrives on time, every month, and charges for all 14 seats.
This is the quietest leak in a small business. Not fraud. Not a bad month. A bill for software that does not exist in your team's day.
Why do teams quietly abandon the tools you pay for?
Teams abandon tools because the tool asks for more effort than the work. Every update has to be entered twice. Once in the WhatsApp thread where the work actually happens. Once in the CRM, for the record that nobody reads.
That double entry lasts about two weeks. Then the busy week comes, and only the WhatsApp entry survives. After that, the CRM is a museum of your last good intention.
The tool was also bought for the wrong person. It was bought for the founder's idea of the company, not for the people who have to open it daily. It was designed for some other firm's process, so your team bends their work to fit the tool instead of the tool fitting the work.
And nobody teaches it. The onboarding was one video call. The people who joined later got a login and a "figure it out". Three months later, half your seats belong to people who never finished the setup.
I said a version of this in Your AI tools sit next to the work, not in it. A tool that lives beside the work instead of inside it gets skipped on a busy day. A CRM beside WhatsApp is a CRM waiting to be abandoned.
How big is this waste?
The numbers are measured on bigger firms, and the pattern survives the trip down to a 15-person team. Zylo's 2026 SaaS Management Index puts about 36 percent of SaaS licences unused against recommended use levels. Vertice's Q2 2026 data goes further: 65 percent of licences are either fully unused or underused. BetterCloud's State of SaaS 2026 reports that 53 percent of an organisation's licences go a full year without a single login. You can read the roll-up of these benchmarks on UseCarly and the waste data on ToolRelief.
Gartner expects organisations without a clear view of their SaaS stack to overspend by about 25 percent through 2028. That projection is for enterprises. In a 15-person firm the waste is not a percentage on a dashboard. It is five tools, three renewals you forgot about, and two seats held by people who left months ago.
Meanwhile the work still runs on the old rails. An industry read cited this year puts 67 percent of Indian SMEs on a mix of Excel, email folders, WhatsApp Business, and manual follow-ups for customer work. The bill and the work live in different places. You pay for one system and operate another.
Why does the bill keep coming after everyone left?
The bill keeps coming because nobody owns the seat count. Four quiet things keep it alive.
First, renewals are automatic. The card is on file, the invoice lands in your inbox, and it is small enough that you skim past it. The cost of noticing is higher than the cost of paying, until one day it is not.
Second, seats were bought for people, not for use. You bought 14 because headcount was 14. Two people left. One role was never filled. Those seats renew anyway, because offboarding only collects the laptop.
Third, the tier was chosen once, at purchase, by whoever needed the most features. Everyone else inherited it. You pay the expensive plan for a team that uses the tool like a phonebook.
Fourth, nobody can say the tool failed, so nobody can kill it. The founder announced it. Killing it means admitting the money was wasted. So it sits there, half used, fully billed, and the team learns that new tools are theatre.
What does this cost a 15-person firm?
Do the rough maths on a per-seat stack. A per-user ERP or CRM suite runs roughly two to three thousand rupees per user a month at current pricing. For 15 people that is thirty to forty five thousand a month in licences alone, before any setup, migration, or training cost lands. That is the advertised number. The real number is what you pay divided by the seats that actually get used. At half adoption, you are paying double for every seat that matters.
This is why per-seat pricing punishes growth. Every hire is a new bill. Every person who does not adopt is a bill you pay anyway.
The honest question is not what the software costs. It is what the software did last week that WhatsApp and Excel did not do. If the answer is nothing, you do not have a tool. You have a subscription.
How do you catch it in one hour this week?
Give it one hour, not a project. Open your card statement and list every software charge. For each one, write three things: who uses it, when they last used it, and what breaks if you cancel it.
Then apply one rule. If fewer than half the seats opened the tool in the last month, it is not a tool. It is a bill. Cancel it, or cut the seats to the people who actually log in.
Watch for the predictable ghosts: seats held by people who left, seats bought for hires that never happened, the premium tier nobody needed, the second tool that does what the first one was supposed to do. A good walkthrough of this first audit is set out by Bitrix24.
Do the same for the tools nobody talks about. The survey tool from one event. The design seat from one festival post. Small bills are the hardest to notice and the easiest to kill.
This hour pays for itself every month after. Keep the list. Revisit it every quarter. Put one name next to the review date, because a review with no owner dies like a CRM with no user.
What should you buy instead of seats?
Buy adoption, not software. Before any new tool, ask for the adoption proof, not the feature list. Who opens it daily in a firm like yours? What does week three look like, after the demo excitement wears off?
Prefer the tool that goes to where the work already is. Your team opens WhatsApp a hundred times a day. A system that carries the work inside the channel they already live in has a chance. A system that asks them to leave that channel and log in somewhere else is fighting a habit it will lose. We build our AI automation work on this same placement logic: inside the work, not beside it.
And test the pricing against your growth, not your headcount today. If every hire is a new seat at full price, the tool taxes the thing you want most. Look for the flat option. Look for the plan where adding your sixteenth person does not cost you a second thought.
The test that matters is ninety days, not the demo. Tell the vendor: if half my team is not in this daily by week six, we are out. You will learn more from their reaction to that line than from any feature tour. This is the same adoption thinking behind BaseEngine. The guarantee is not on features. It is on the team actually living inside the system.
Will one more tool fix the tools you already abandoned?
No. A new tool on top of abandoned tools is just a new bill on top of old bills. It also teaches your team the worst lesson: that every tool is temporary, so none of them deserve the effort.
Kill first. One system with one daily habit beats five subscriptions and a WhatsApp group. When the dead tools are gone, your team finally has room for one thing that works. That is when a new system has a chance, and not before.
That is the conversation I want this piece to start. Open your card statement tonight. Count the seats nobody sits in. Then ask whether your next purchase is software, or the team actually using it.
Want to think it through for your business? Start with the BaseEngine overview and ask one question: which of your tools would survive if every seat had to earn its renewal this month.
Frequently Asked Questions
How do I know if my team has abandoned a tool?
Open the seat list and ask who logged in this month. If fewer than half the seats were used, the team has quietly left. The other sign is double entry: work discussed in WhatsApp and copied into the tool for the record. When the tool becomes a filing cabinet, it has been abandoned.
What percentage of SaaS licences go unused?
Zylo's 2026 index puts about 36 percent of licences unused against recommended use. Vertice's Q2 2026 data puts 65 percent as unused or underused. BetterCloud reports 53 percent of licences going a full year without a login. The exact number varies by firm, but a large share of every stack is idle.
Why does per-seat pricing hurt small firms?
Per-seat pricing charges you for headcount, not for use. Every hire adds a bill, and every seat that goes unused still renews. At half adoption, each seat that matters costs you double. For a growing firm, the pricing taxes exactly the thing you want more of: people.
Should I cancel a tool my team half uses?
Cut it to the seats that actually log in first. If that leaves two or three seats, the tool is not your system, it is someone's habit. Ask whether the job it does could move into the system your team already opens daily. Half used and fully billed is the worst of both worlds.
How often should a small firm audit software spend?
Quarterly, with one named owner and a date on the calendar. Monthly is better in the first year. The audit is simple: every charge, who uses it, last use date, and what breaks if it goes. The version that works is the one somebody actually runs.
What should I ask before buying new software?
Ask for adoption proof, not features. Who in a firm like yours opens it daily? What does week three look like? Then test it against growth: does the next hire cost you a new seat? And set the bar in writing before you pay: if half the team is not in it daily by week six, you walk.
By Aravind Bhati, Founder, BaseWorks