Japan is the world's third-largest economy. It has 1.2 million
software engineers. And most of them spend their workday in Excel.
Not writing code. Writing specs. In spreadsheets.
I spent time researching Japan's IT industry and found five deep,
structural pain points that have no good software solution yet. Each one has a clear product gap. Here they are:
## Pain #1 — Excel Hell
Japanese engineers at large system integrators (called SIers) deliver
Excel files as their primary output. Test case matrices, architecture
diagrams, design specs — all in grid format, never in version control.
76% of Japanese companies have documentation outdated by at least
one version (2026 survey).
Product gap: SpecSync — a CLI that parses Excel spec files and
converts them into versioned, searchable Markdown synced to Git.
Open-source core, paid cloud sync. No competitor targets this workflow.
## Pain #2 — Siloed Knowledge (属人化)
Over 70% of Japanese companies report that critical system
knowledge lives exclusively in one person's head. When they retire,
the knowledge goes with them.
Product gap: TribeMind — indexes Git history, PR comments, and
Slack logs into a queryable knowledge base. Ask why a module was
built a certain way — get an answer from years of commit context.
## Pain #3 — The Language Wall
Japan ranks 92nd globally in English proficiency, yet employs
over 90,000 foreign IT workers. Spec miscommunication between Japanese
clients and offshore English-speaking teams causes real project
failures.
Product gap: BridgeSE — converts Japanese requirements documents
into English, detects unstated cultural assumptions, and generates
bilingual handoff packets. DeepL doesn't do this. Google Translate
doesn't either.
## Pain #4 — Reporting Hell
Japanese engineers have adopted AI for coding. But the administrative
overhead — weekly progress reports, formal meeting minutes — hasn't
dropped.
Product gap: StandupAI — monitors Git commits and Jira activity,
auto-generates formal Japanese progress reports (進捗報告書) in proper
business keigo style. CLI + VS Code extension.
## Pain #5 — The Legacy Cliff
Japan's enterprise infrastructure includes COBOL systems from the
1970s, Java monoliths from the 2000s, and Classic ASP still running
on-premise in 2026. Nobody understands the full picture anymore.
Product gap: LegacyMap — deep-scans a codebase and outputs a
system map, dependency graph, risk heat map, and plain-language
narrative for each component. B2B — sold to banks, manufacturers,
and retailers.
## Watch the full breakdown
I made a short video on this (under 4 minutes, no fluff). It's my
first YouTube video and it's available on youtube.
Which of the five would you build? Drop it in the comments here or on
YouTube.