The real Japanese SME stack: LINE, Excel, fax and one person

Most small businesses in Japan run on a different stack from the one on the software invoice. Alongside the official tools sit LINE groups, Excel files copied from last year, a fax machine a few suppliers still rely on, shared passwords in a browser, and one long-serving person who knows how it all fits together. That real stack usually works, which is why nobody fixes it. The risk shows up when that person leaves, a vendor changes, or the business tries to grow, automate or sell.

This post is about the stack you actually have. If you want the other half of the question, what a sensible stack should contain, read what belongs in a Japan SME technology stack.

What does a typical Japanese SME actually run on?

Ask management and you will hear the official list: Google Workspace or Microsoft 365, Chatwork or LINE WORKS, freee or Money Forward, perhaps kintone, a booking system, a payment provider and a website CMS.

Watch the work for a day and a second list appears.

• LINE for anything urgent, including customer photos, supplier confirmations and staff shift swaps, often on personal phones.
• Excel for quotes, price lists, customer lists and the monthly numbers, usually copied forward from last year’s file.
• Fax for orders from a handful of long-standing suppliers or customers who never moved off it.
• Paper for approvals, delivery slips and anything that still needs a hanko.
• Personal inboxes holding vendor invoices, contracts and customer history that should belong to the company.
• Shared logins for the bank, the tax portal, social accounts and vendor systems, sometimes tied to a founder’s old email address.
• One person who remembers which customer pays late, which supplier needs a call before Golden Week, which folder holds the real template and which official procedure you should not follow too literally.

Nobody designed this. It accumulated, one reasonable decision at a time.

Why do LINE, Excel and fax survive?

Each piece survived because it solved a real problem better than the official tool did.

LINE survives because people answer it within minutes and customers already have it. Excel survives because anyone can change it without asking a vendor. Fax survives because a supplier’s ordering process depends on it, and replacing it means asking a valued partner to change. Paper survives because it is trusted and never changes its interface. A manual approval survives because one expensive mistake made everyone nervous about removing it.

That is why telling staff to stop using the workaround rarely works. The better question is what job the workaround does that the official system fails to do. A shadow spreadsheet often exists because the CRM was set up badly. A private LINE thread exists because the official channel is too slow for field staff. A paper checklist exists because the software cannot handle a Japanese customer’s edge case. Each workaround is evidence of a gap, and it tells you what the replacement has to handle.

What goes wrong with an unofficial stack?

A patched-together stack can run for years without trouble. Then something changes.

Someone leaves. If one person knows where everything is, that person is part of your infrastructure. When they retire or resign, the business finds out which passwords, suppliers and procedures lived only in their head.

A customer relationship sits in private messages. If the history with a key customer exists only in one employee’s LINE account, the company does not fully own that relationship.

Compliance catches up. The invoice system (インボイス制度) and the electronic bookkeeping law (電子帳簿保存法) both assume invoices and transaction records are issued, received and stored in an orderly way. Invoices scattered across personal inboxes, fax trays and LINE photos make that much harder.

The business wants to automate or use AI. Automation needs stable records and clear handoffs. When the real process lives in chat threads and memory, there is nothing reliable to automate.

An owner wants to sell or hand over. A buyer or successor needs to see how the business runs. Accidental infrastructure is hard to value and harder to transfer.

The company may be profitable, with good staff and loyal customers. It is still carrying systems debt that limits what it can do next.

Why is this harder for foreign-owned businesses in Japan?

Foreign-owned and bilingual companies often end up with two stacks that drift apart. Head office imports a global toolset, then the Japanese team keeps a parallel process because the imported system does not fit local suppliers, tax requirements or customer habits. Management reads this as resistance. Staff see a tool that ignores how the work actually happens. Both are partly right.

Other local layers add to it: vendor portals that only work well in Japanese, accounting tools chosen for Japanese tax rules, SIer contracts that nobody on the English side has read, and records kept in two languages that stop matching over time.

Video: Why Japan is a laggard in Digital Transformation | A timeline of Japanese DX 2001 - 2021 from Build+ (formerly Wahl+Case).

The answer is not to pick one side’s habits. It is to make the real workflow visible and agree which system is the record for each kind of information. I cover this for international owners on the foreign-owned SMEs in Japan page.

How do you map the stack you really have?

When I review a company’s systems in a Diagnostics engagement, counting subscriptions is the easy part. The useful work is finding where the official and real stacks diverge. You can start the same exercise yourself.

List every tool, including the unofficial ones

Include LINE groups, personal Gmail accounts used for work, the fax number, shared Excel files and paper forms. For each one, note what it is used for and who relies on it.

Record who owns and who can access each account

Who pays for it, who has administrator access, which email address it is registered to, and what happens if that person is unavailable tomorrow. Shared logins deserve special attention; I cover them in shared systems need shared rules.

Follow information as it changes form

Trace a few ordinary jobs from start to finish: inquiry to quote, quote to invoice, fax order to delivery, Japanese conversation to English report. The points where information is retyped, photographed or forwarded are where it gets lost.

Ask what each workaround is protecting

Before removing anything, find out what would break. Sometimes the answer is nothing. Sometimes it is the only thing keeping a key customer happy.

What should you fix first?

Most messy stacks need a handful of practical moves rather than a new platform.

• Move shared passwords into a company password manager and put critical accounts under company-owned email addresses.
• Cancel the tools nobody uses and choose one tool for each job where two overlap. The SaaS review method covers how.
• Decide which channel is used for which kind of work, so customer decisions do not live only in personal chat.
• Give invoices and contracts one company-owned destination to meet invoice system and bookkeeping rules.
• Plan the move off fax supplier by supplier; see how to migrate off fax.
• Write down what the key person knows, starting with suppliers, renewals and the exceptions in each process.
• Name an owner for each system and keep a simple renewal calendar.

None of this is glamorous, which is partly why it gets postponed.

Normal is not the same as safe

If your company runs on LINE, Excel, fax, shared drives and one person who knows where everything is, you are not unusual. Plenty of well-run, profitable Japanese businesses work this way. The problem is that the arrangement fails suddenly rather than gradually.

A Diagnostics review maps what you actually use, what it costs, who owns it and where the workflow breaks, before you buy another tool. If you already know what needs to change, I can plan and carry out the changes with your team.

---

Further reading: what belongs in a Japan SME technology stack · reviewing the subscriptions your business still needs · fractional IT management for a small business in Japan