Can Japan's Digitalization And AI Implementation Subsidy Cover A Custom PoC?
Japan's 2026 Digitalization and AI Implementation Subsidy is relevant for teams thinking about AI workflow automation, SaaS adoption, document automation, and DX tooling. It is also easy to misunderstand.
The short version: the subsidy is designed around the implementation of registered IT tools. A custom-built PoC, prototype, or bespoke workflow app may not qualify unless it fits the program rules through a registered IT tool and registered IT support provider.
That distinction matters for buyers planning an AI or software sprint. A subsidy can help with tool adoption, but it should not be treated as guaranteed funding for custom product development.
What changed in 2026
The Small and Medium Enterprise Agency announced that the program name changed from the former IT Implementation Subsidy to the Digitalization and AI Implementation Subsidy from the FY2025 supplementary budget program. The stated purpose is to support small and medium-sized businesses adopting IT tools, including AI, for digitalization and productivity improvement.
Official sources:
SME Agency announcement, March 10, 2026
Digitalization and AI Implementation Subsidy overview
Under the normal category, the 2026 official program page lists subsidy rates of 1/2 or 2/3 and subsidy amounts up to 4.5 million yen when four or more business processes are covered. The page also states that eligible software should hold at least one business process, and that a generic process alone is not sufficient.
Official details:
Normal category: subsidy rate, amount, and IT tool requirements
The registered IT tool rule
The practical constraint is the registered-tool model.
The subsidy secretariat explains that eligible IT tools are reviewed in advance and published/registered on the subsidy website. It also states that applicants generally need to work in partnership with a registered IT support provider. On the IT vendor side, the secretariat explains that IT tools must be registered and approved before they can be used for subsidy applications.
Official details:
Program overview: registered IT tools and IT support providers
IT tool registration for vendors
This means the buyer should ask a very specific question:
> Is the thing we want to buy a registered IT tool, or are we commissioning custom software development?
Those are not the same procurement shape.
Why a custom PoC may not fit
A custom PoC often starts with a problem, not a pre-registered tool:
"Can we extract fields from our supplier PDFs and review low-confidence cases?"
"Can we build a natural-language search interface for our internal database?"
"Can we connect support email triage to our CRM and dashboard?"
"Can we prove whether an LLM workflow is safe enough for a real team?"
That work can produce software, but it is not automatically a registered IT tool. It may include design, discovery, data handling, custom implementation, API integration, and human review UX. Those activities are often exactly what makes a good PoC useful, but subsidy eligibility depends on the program category and the registered tool structure.
So the safe planning assumption is:
Registered SaaS or packaged tools: potentially subsidy-friendly.
Implementation support around a registered tool: potentially subsidy-friendly, depending on category and registration.
Fully custom PoC or bespoke software sprint: do not assume coverage.
Custom development around an unregistered tool: verify before budgeting.
What buyers should check before relying on the subsidy
Before treating the subsidy as part of the budget, confirm these points:
1. Is the vendor an approved IT support provider for the program?
2. Is the specific software or service registered as an eligible IT tool?
3. Which category applies: normal, invoice-related, security, or multi-company?
4. Does the tool cover the required business processes?
5. Which costs are software, cloud usage, support, setup, training, or consulting?
6. Which costs are custom development, experimental PoC work, or bespoke integration?
7. Does the company already have G Biz ID Prime and SECURITY ACTION?
The official applicant preparation page says G Biz ID Prime and SECURITY ACTION are required before applying, so teams should not leave those steps until the final week.
Official details:
Required preparation before application
How to use the subsidy conversation wisely
For an AI workflow project, separate the work into two tracks.
The first track is subsidy-friendly tool adoption. This is where the team evaluates registered SaaS, accounting tools, invoice tools, security services, or other registered software that clearly fits the program.
The second track is decision proof. This is where the team asks whether a custom workflow, API, LLM feature, document automation step, or natural-language search experience is worth building. That may be better handled as a paid PoC or sprint with a clear scope, even if it is not subsidy-covered.
Trying to force every experimental workflow into a subsidy program can slow the project down. The better question is not "Can we make this subsidized?" It is:
> Which part is registered-tool implementation, and which part is custom proof that helps us decide what to build next?
Where Urbano DX fits
Urbano DX is most useful when the buyer needs working proof before a larger software or AI investment:
AI workflow PoC
Custom web app or internal tool
API-connected workflow
Document automation with human review
Natural-language search with editable filters
Sprint scope and handover material
Some clients may also be evaluating registered tools in parallel. That is fine. The important thing is to keep the funding logic clear. A subsidy-eligible tool rollout and a custom PoC are different work packages, and they should be scoped separately.
For buyers in Japan, a clean first step is to prepare a short decision memo:
The workflow to improve
The users and business owner
The data or API access available
Whether a registered IT tool already exists
What proof is needed before larger budget
What must be checked with the subsidy office or a registered IT support provider
That memo prevents the subsidy conversation from swallowing the product conversation. The goal is still the same: working evidence that lets the team decide whether to integrate, expand, change scope, or stop.