SaaS sprawl: how to audit your tool stack
SaaS sprawl is the slow pile-up of software subscriptions. SaaS is software you rent online and pay for every month or year. Each tool was added for a good reason, but nobody ever looked at all of them together. The cure is an audit of your tool stack: one list of everything you pay for, who uses it and what it is for, and then a decision for each tool. A company of twenty people can do it in a day.
How sprawl happens
Nobody decides to have thirty tools. It is like subscriptions at home that keep running long after you stopped watching. One team starts a free trial, and the trial turns into a paid plan. A second team picks a different product for the same job. A tool bought for one project keeps renewing after the project ends. Each step is sensible. The sum is not.
Step 1: find everything
- Go through twelve months of bank and card statements. Yearly plans show up only once.
- Check expense claims for tools that someone paid privately.
- Ask every team one question: which tools do you open every week?
Step 2: fill in the list
One row per tool. Five columns are enough.
| Column | What to write |
|---|---|
| Tool and job | The product, and what it is used for in three words |
| Owner | The person who decides about it |
| Users | How many you pay for, and how many really use it |
| Cost per year | Everything included |
| Cancel by | The last day you can cancel before it renews |
A tool without an owner gets one now. Finding out that nobody feels responsible is already a result.
Step 3: group by job
Sort the list by what each tool is used for. Doubles show up at once: two tools for projects, three places for notes, two for surveys. Mark every group with more than one tool.
Step 4: decide for each tool
- Keep. Used every week, one clear job, one owner.
- Reduce. The right tool, but you pay for more users or a bigger plan than you need.
- Merge. Another tool on the list does the same job. Choose one and move the information.
- Cancel. Nobody has opened it for two months, or the project is over.
Decide the merges last. They bring the most, and they need a plan.
Step 5: cancel properly and keep it tidy
- Save your information from the tool first, and check that the saved file opens.
- Tell the users the date and where the work moves to.
- Cancel in writing before the deadline.
- From now on, one person approves every new subscription, however small.
- Repeat the review once a year. The second time is much quicker.
What to expect
A first review usually finds three kinds of money. Users you pay for who have left. Tools nobody opens. And pairs of tools that do the same job. The first two can be saved within the week. The third takes longer, because it changes how the team works.
How Worknano handles this
When the review shows several tools doing neighbouring jobs, Worknano gives you one workspace to merge them into. Tasks, CRM, OKRs, forms and HR work there on the same data. The tools you still need, such as your payment service, stay connected to it.
- What you can usually retire
- How Worknano differs from separate tools
- Integrations: keep the tools you still need connected
Create a free workspace and test it against the "merge" rows of your list.