Business software and the SME tech stack in Japan
When should a small business stop managing its own IT?
A 10-point checklist for small businesses in Japan to judge when do-it-yourself IT has become a risk, and what kind of outside help fits the problem.
A small business should stop managing its own IT when the work of keeping systems running starts taking senior time every week, when nobody can produce a complete list of accounts and subscriptions, or when the business would stall if one person left. Doing it yourself is sensible early on. It stops being sensible when recurring repairs pull attention from work only you can do, or when the company depends on something nobody else could recover. The checklist below helps you judge where you are.
Why does DIY IT work at first and then stop working?
Most companies start the same way. The founder or an early employee sets up the tools: a Google Workspace or Microsoft 365 account, a chat app, a spreadsheet for customers, freee or Money Forward for the books, a few automations found through a search. That is a reasonable way to start, and for a while it works well.
Somewhere between roughly eight and twenty people, the costs start to pile up out of sight. Five places now hold task lists. An automation fails and nobody notices for weeks. The person who set up the domain and email has left, and the login went with them. Senior people spend evenings answering tool questions and dealing with renewals.
Most businesses keep going anyway, because the costs are spread thinly and something more urgent always comes first. The checklist is meant to make those costs visible.
The 10-point checklist
Answer each one honestly, yes or no.
1. You cannot list what you pay for software each month
Not roughly, exactly. If you cannot produce every subscription with its cost and owner in ten minutes, your stack is unmanaged. The subscription review method is a good first fix.
2. Someone has left and taken system knowledge with them
The integration they built that “just works”. The CRM set up to their preferences. The domain registered to their personal email. This is a dependency on a person, and it has not failed yet only by luck.
3. A broken tool cost real time in the past year
Not a minor annoyance, but lost hours or bad data: an expired card that suspended an account, an integration that duplicated customers, a vendor portal nobody could log in to. One incident is a warning. Two is a pattern.
4. People do the same job in different tools
Some staff log customer notes in the CRM, some in their inbox, some in a personal spreadsheet or LINE. That is a system problem, not a discipline problem. The official tool does not make the right behavior easy enough.
5. New staff take weeks to learn the tools
If a new hire needs two weeks just to learn which tools exist, where files live and who to ask for access, your setup is neither documented nor intuitive. The cost repeats with every hire.
6. A senior person spends two or more hours a week on IT
Managing vendor accounts, fixing integrations, answering tool questions, evaluating software, sorting out billing. If that person is you, an operations manager or an office manager, senior time is going to work that should be organized differently.
7. You don’t know which automations are running
Many companies that have been around a few years have Zapier or Make workflows built by a former employee or contractor, syncing data in ways nobody fully understands. If you cannot name each one, say what it does and confirm it works, your processes depend on faith.
8. You bought a tool and the problem is still there
A CRM nobody logs into. A project tool running alongside the spreadsheet everyone actually uses. A documentation tool with nothing documented in it. Buying the tool did not solve the problem because it was never properly implemented. Often the tools you already pay for can do more than anyone has set up.
9. Vendor pitches arrive and you have no way to judge them
Japanese and international vendors, and SIers, pitch small businesses constantly. Without a clear picture of what you already have and what you need, you keep buying things that overlap or do not fit.
10. Nobody could take over your systems from written notes
Imagine handing the whole stack to a capable new manager. Could they understand the accounts, tools, owners and renewals from documentation, without sitting with you for days? If not, the setup lives in the heads of the people who built it.
What does your score mean?
0 to 2 yes answers. You are in reasonable shape. Keep the subscription list current and run the checklist again in six months.
3 to 5 yes answers. There is real risk. A focused internal clean-up is worthwhile: inventory the accounts, check the automations, name an owner for each tool and document what you find.
6 or more yes answers. Your systems are effectively unmanaged. That is costing time and money now, and the risk will surface at an inconvenient moment, such as a departure, an audit, a busy season or a sale of the business.
If you want a more structured score, the free Technology Risk Self-Check covers similar ground.
What kind of help do you actually need?
“Getting help with IT” covers several different services. Matching the help to the problem saves money and frustration.
A help desk or managed IT provider. If the pain is device problems, printer issues, new PC setup and user support, you need a support provider with response times, not an advisor. Many local IT companies in Japan offer this on a monthly contract.
A one-off review. If you do not know what you have, what it costs or where the risks are, start with an outside review that produces a written picture of the stack and a prioritized fix list. That is what my Diagnostics engagement is for.
A scoped project. If you know what needs to change, such as consolidating tools, moving off fax, setting up proper accounts and recovery, or rebuilding a CRM, you need someone to plan it and do the work with your team. That is Digital Baseline.
Continuing senior judgment. If technology decisions keep coming up, with vendors, renewals, AI proposals and system changes, but you cannot justify a full-time IT manager, a fractional arrangement fits. I explain how that works in fractional IT management for a small business in Japan, and the fractional IT support guide covers how to scope it.
Your own hire. At some point a full-time IT or operations person makes sense. Outside help is still useful for writing the job description, documenting the current systems and handing them over cleanly.
Doing it yourself, but properly
Plenty of businesses should keep managing their own systems. The difference is doing it deliberately: one owner, a written list of accounts and tools, company-owned logins, a renewal calendar and a short document that explains how things fit together. The Japan SME tech stack guide shows what that list should cover.
If you scored three or more and are not sure which kind of help fits, tell me about your situation. A short conversation is often enough to tell whether you need outside help or can handle it internally.
Further reading: fractional IT management for a small business in Japan · the real Japanese SME stack · reviewing the subscriptions your business still needs