Most small businesses run well on a core of roughly 7 to 12 software tools, even though the average small company actually pays for far more. The gap between what you need and what you own is where money leaks. Studies of software spending find that around half of all licenses go unused within a month of purchase.
What Does the Data Actually Say?
Software usage has become a measurable problem, and the numbers are eye-opening. Reports on SaaS usage and spending converge on a few themes.
| Metric | Typical finding |
|---|---|
| Apps used by companies under ~200 staff | Roughly 25 to 55 on average |
| Company-wide average (all sizes) | Around 106 to 130, and falling |
| Licenses unused within 30 days | Close to half |
| Pure “shelfware” apps | Around 15% |
| Organizations reporting tool overlap | About 7 in 10 |
| SaaS spend per employee, per year | Often $1,000 to $5,000+ |
Two things stand out. First, waste is enormous, roughly half of what many companies buy goes unused. Second, the trend has reversed. After years of piling on apps, businesses are actively cutting back and consolidating. The peak is behind us. Deliberate is the new direction.
What Are the Core Functions Every Small Business Must Cover?
Forget the app names for a moment. Every small business has to cover the same short list of jobs. Cover each one once.
- Money in and out. Accounting, invoicing, payments.
- Customer records. A CRM or contact system so relationships do not live in one person’s inbox.
- Communication. Email, plus one team chat channel.
- Getting work done. A project or task tracker, and file storage.
- Marketing and presence. Website, and the one or two channels your customers actually use.
- Payroll and people. Once you have employees.
- Security basics. A password manager, and backups.
That is seven functions. Most small businesses can run on one strong tool per function, plus a couple of niche extras. Everything beyond that should earn its place.
What Does a Lean Small-Business Stack Look Like?
Here is a reference stack by function. The point is not the specific category but the discipline of one tool per job.
| Function | What you need | Common trap |
|---|---|---|
| Accounting and invoicing | One bookkeeping platform | Running spreadsheets alongside it |
| CRM | One shared contact system | Sales data trapped in inboxes |
| Communication | Email plus one chat app | Three chat apps, no single source |
| Work and files | One task tracker, one storage drive | A tracker, a doc app, and a separate spreadsheet all holding the same work |
| Marketing | Website plus one or two channels | Paying for tools on channels you never post to |
| Payroll and HR | One payroll tool | Manual payroll plus a half-used HR app |
| Security | Password manager plus backups | No password manager, shared logins |
For small teams, one of the biggest sources of sprawl is coordination overhead: a chat app, a docs app, a tracker, and a spreadsheet all holding pieces of the same work. Keeping the work and the conversation about it in one place removes several tools at once.
How Do You Know You Have Too Many Tools?
Watch for these signals. They map directly to the waste stats above.
- You are unsure what you are paying for each month.
- Two or more tools do roughly the same job.
- A tool nobody has logged into for 30 days is still billing you.
- Data lives in several places and never quite matches.
- Onboarding a new hire means handing them a long login list.
- New tools get added faster than old ones get removed.
If three or more of these ring true, you have sprawl, not a stack.
The Tool Audit: A 5-Step Cleanup
Owners on Reddit’s entrepreneur and small-business communities describe the same fix: an honest subscription audit, done on a schedule.
- List every subscription. Pull your card and bank statements. Include the ones you forgot.
- Tag each by function. Which of the seven core jobs does it do?
- Flag duplicates. Any function with two tools is a decision waiting to happen.
- Check last-login dates. Anything unused for 30 days is a cancel candidate.
- Cut, then recheck quarterly. Sprawl is not a one-time clean. It creeps back.
A single pass usually removes several tools and a meaningful chunk of monthly spend.
A Unique Insight: Count Integrations, Not Apps
The real cost of a tool is not just its subscription. It is the integration and attention it demands. Every app you add needs data flowing in and out, someone to own it, and a place in everyone’s mental map of “where does this live?”
A better metric than “how many apps” is “how many places does the same piece of information live?” If a single customer’s details sit in your CRM, your invoicing tool, a spreadsheet, and someone’s inbox, you do not have four tools helping you. You have one job scattered across four places, each able to fall out of sync.
The strongest small-business stacks are not the ones with the most features. They are the ones where each piece of information has exactly one home.
The AI Wrinkle
One trend worth naming: AI-native tools are the fastest-growing line in software spending, and much of it arrives as unmanaged “shadow” software that individual staff sign up for. Before adding another AI subscription, ask whether a tool you already pay for now includes the same capability. Increasingly, it does.
Frequently Asked Questions
How many software tools should a startup begin with?
Start with the bare core: accounting, email, one communication tool, one place to store work, and a website. Add tools only when a specific, repeated pain justifies one. Five to seven is plenty at the start.
Is it cheaper to use one all-in-one platform or several specialized tools?
All-in-one platforms reduce sprawl and integration headaches but may be weaker at any single job. Specialized tools do one thing better but multiply cost and overlap. For most small businesses, fewer, broader tools win on total cost and simplicity.
How much should a small business spend on software?
Spending varies widely, but many businesses run in the range of $1,000 to a few thousand dollars per employee per year. The better test is not the total but whether every tool is actively used.
How often should I audit my software stack?
Quarterly. Sprawl creeps back through free trials, per-seat creep, and shadow signups. A short quarterly review keeps the stack lean.