To cut software costs in a small business, first build one complete list of every subscription with its cost, owner, renewal date and what depends on it. Then cancel what nobody uses, choose one tool where two do the same job, move plans to the right tier, and put every renewal date in a calendar with enough notice to act. In Japan, annual contracts and vendor relationships make timing more important than in most markets, so the renewal calendar is often where the real savings come from.

The hard part is rarely the cancellation. It is that nobody in the company can see the whole bill.

Why do small companies end up paying for tools they don’t use?

Software gets bought in pieces. A manager signs up for a tool to solve an urgent problem. A vendor pitches someone senior and a contract gets signed. A project ends, a staff member leaves, a free trial turns into a paid plan. Each purchase makes sense at the time. Years later, the company is paying for a stack nobody chose as a whole.

When I review a company’s systems in a Diagnostics engagement, the subscription inventory usually prompts the same reaction: surprise at the total, then recognition of two or three tools people had forgotten about.

What kinds of software waste should you look for?

Duplicate tools

Two products doing the same job, bought at different times and now running side by side. Common pairs are two task tools (Backlog and Notion, or Notion and a paid Trello board), two chat tools (Chatwork and Slack, often plus LINE), two file stores (Google Drive and Dropbox, or Drive and OneDrive), and a CRM alongside a separate pipeline spreadsheet or tool. Nobody wants to migrate off the older one, so both keep billing.

Forgotten subscriptions

Tools bought for a finished project, a former employee, or a trial that renewed automatically. They are usually small line items, which is exactly why nobody cancels them.

The wrong plan

A company upgraded to a higher tier during a busy period and never came back down. Or seats are still assigned to people who left. Or the opposite: the team hit plan limits and started working around them with personal accounts.

Automations that quietly stopped

A Zapier or Make workflow that synced two tools, set up by someone who has since left. One side changed and the automation stopped working months ago. You may still be paying for all three pieces while the work they were meant to do happens by hand, or not at all.

Tools used for a fraction of what they cost

This is the hardest to spot from a bank statement. An expensive project platform used only for simple task lists. A full CRM used as an address book. A paid integration tool doing a job one of your existing products already supports natively. Finding these means looking at how each tool is actually used, not just whether anyone logs in. It is also worth checking what the tools you already pay for can do before adding another.

Why is SaaS sprawl harder to fix in Japan?

A few local habits make overlapping software more persistent.

Annual contracts. Japanese vendors, and the Japanese sales teams of international vendors, often push annual terms. That leaves a short window each year to cancel or renegotiate, and if you miss it you are committed for another year.

No single owner. In many small Japanese companies, the accounting tools belong to the admin team, the email platform to sales, and the booking system to whoever set it up. Nobody sees the complete picture, so nobody notices the overlap.

Vendor relationships. Canceling a contract with a Japanese vendor you have worked with for years can feel like a confrontation, especially if the vendor or the SIer that installed the system has been helpful. So renewals happen by default.

Compliance nerves. Since the invoice system (インボイス制度) began in October 2023 and the electronic bookkeeping rules (電子帳簿保存法) tightened, companies are rightly careful about changing anything that issues or stores invoices. That caution sometimes spreads to tools that have nothing to do with tax, and nothing gets reviewed at all.

Payment methods scattered across cards. Subscriptions paid on several corporate cards, a founder’s personal card and a few by bank transfer are hard to add up. Some tools are billed in dollars, and some are invoiced through a reseller under a different name.

How do you run a subscription review yourself?

You can do a useful first pass in an afternoon.

Collect three to twelve months of statements from every card and bank account that pays for software, including personal cards that are reimbursed. Annual contracts only appear once a year, so a longer window catches more.
List every tool with its monthly or annual cost, the account email it is registered to, who has administrator access and the next renewal date.
Ask two questions for each one. Who actually used it this month? What would stop working if it disappeared tomorrow?
Mark the candidates. Anything used by nobody or one person, where nothing obvious would break, goes on the cancellation list.
Group tools by job. Put all messaging tools together, all file storage together, all task tools together. Any job with two or more tools is a consolidation candidate.
Set renewal reminders 60 to 90 days before each date, so the decision happens before the vendor sends the invoice.

What do you do with each finding?

Unused, no data worth keeping: cancel now.
Unused, but holds records: export the data to company-owned storage, check whether any of it must be kept for tax or legal reasons, then cancel.
Two tools doing one job: pick the one the team actually prefers, set a migration date, move people over and make the old one read-only before canceling.
Wrong plan or unused seats: remove leavers’ seats and ask the vendor about a lower tier. Most would rather keep you on a smaller plan than lose you.
Broken automation: fix it or switch it off. A broken automation that looks active gives false confidence that work is being done.

For Japanese vendors, give notice politely and in good time, explain the reason in business terms, and keep the relationship intact. You may want them back later.

How do you stop the sprawl coming back?

Give one person responsibility for the software list and the renewal calendar. Agree a simple rule that new paid tools need a named owner and a stated job before anyone signs up. Remove access and seats as part of every staff departure. Review the list twice a year.

This is also where decisions about which tool to keep need a view of the whole stack. The Japan SME tech stack guide sets out one tool per job and covers ownership and exit plans for each system. If you are choosing between two overlapping task tools, Notion vs Backlog vs Linear may help.

When to get help

A first pass you can do yourself. The harder calls are which duplicate to keep, what depends on an old integration, and how to migrate without disrupting customers. A Diagnostics review gives you the full inventory, the dependencies between tools and a prioritized list of what to cut or consolidate. If renewals and vendor proposals keep arriving and you want continuing help deciding, that is what Ongoing Stewardship covers.

Further reading: what belongs in a Japan SME tech stack · the real Japanese SME stack · shared systems need shared rules · using the tools you already own