
What happened
ITR principal analyst Hiroaki Koumoto said Japanese firms' efforts in harness engineering are 'almost nonexistent.' Only some leading IT vendors and startups use AI agents in software development, he said, while typical companies and SIers are still stuck at an earlier stage.
Why it matters
Without an integrated agent development process, building a harness has little meaning, so many Japanese firms may keep treating AI as a tool for cutting coding hours rather than a path to better competitiveness.
What to watch
Handling AI agents safely and securely company-wide, not individual tools like MCP, is the definition Koumoto uses — and he sees a roughly five-year window before the gap with global firms becomes hard to close.
WHO IT HITSThis lands hardest on Japanese business leaders and SIer (system integrator) managers deciding how to spend development budgets and hire engineers. It also matters to IT recruiters and engineering managers who must compete for scarce AI talent against leading IT vendors and startups.
Summaries like this, in your inbox every morning.
Koumoto frames the shift as a change in what the industry argues about. Model performance debates have run their course, and the focus is moving to how AI agents are given autonomy — in other words, to harness engineering. Japanese firms, he says, are largely still at the earlier stage of applying AI piecemeal: upstream design, coding, and testing handled as separate tasks, with no integrated agent-driven development process in place.
The deeper cause he cites is structural. Years of 'dependence on major SIers and outsourcing' left many Japanese companies without their own application development know-how or in-house engineers. Business leaders, he says, have started to realize this over the past two to three years, but awareness alone does not create skilled people, and some had hoped AI would let them build applications without them — a hope he describes as an illusion.
His practical advice is to treat application development as the core of business competitiveness and innovation, rather than a cost to be outsourced, and to accept that the first three years may bring no direct return. Koumoto's own comparison is with the shift to agile development after 2015, which took two to three years to take hold in Japan once companies committed. Whether Japanese firms genuinely change course within five years, he suggests, will decide which ones remain competitive.
For example, today's edition would include:
AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
1Password CTO Nancy Wang said at Okta's Oktane event that agents need just-in-time, task-based access, and the…
Bhakti Pitre, ServiceNow's VP of AI platform security product, said at Okta's Oktane event that agent "kill sw…
Futurum's report, sponsored by QumulusAI Inc., finds agentic AI can drive token consumption per task 10 to 100…
Claude Code's creator Boris Cherny answered a developer's question on September 11, 2026, saying throwaway pro…

Stagwell CEO Mark Penn told Power Players most digital ads "are not very good" and said AI's payoff is doing t…

AMD agreed to an $8.2 billion all-stock buyout of World Labs, the San Francisco startup led by Dr
