# How to outsource system development using subsidies: the complete guide for buyers

> A complete guide for owners and IT managers who want to outsource system development using subsidies. Covering how to choose among Japan's four major schemes — Digitalization & AI Adoption (formerly IT Introduction), Sustainability, Monozukuri, and Labor-Saving Investment — plus eligible expenses, the ban on starting work before the grant decision, scheduling by back-calculation, and the trap of 'subsidy-first' investment. A neutral guide focused on the buyer's decision-making.

- Published: 2026-07-07
- Author: 友田 陽大
- Tags: 補助金, DX, 中小企業, システム開発, IT導入補助金, 発注, 受託開発
- URL: https://tomodahinata.com/en/blog/subsidy-system-development-outsourcing-complete-guide
- Category: DX with government subsidies

## Key points

- There are four main schemes usable for outsourcing system development. SaaS/package adoption fits the 'Digitalization & AI Adoption Subsidy (formerly IT Introduction Subsidy),' while bespoke scratch development is best served by the 'Labor-Saving Investment Subsidy (General Type)' or the 'Monozukuri Subsidy.'
- The Digitalization & AI Adoption Subsidy assumes you adopt a registered IT tool through a registered IT-introduction-support vendor. Fully bespoke full-scratch development is, in principle, out of scope.
- The single most important rule common to every scheme is that 'work started before the grant decision is not eligible.' Sign the contract, start development, or pay before the grant-decision date, and not one yen of that expense will be subsidized.
- Subsidies are paid in arrears (reimbursement), and even at a subsidy rate of 1/2–2/3 there is always a self-funded portion. 'We build it because we can get a subsidy' is backwards; the correct order is to layer a subsidy onto an investment that already earns its ROI.
- Subsidy rates, caps, category names, and schedules are revised every year. The figures in this article are based on the official public solicitation guidelines at the time of writing — always confirm against the latest guidelines before you place an order.

---

Let me state the conclusion first. **When you outsource system development using a subsidy, the first thing to do is not to hunt for a scheme, but to determine "which scheme's eligible-expense category the thing you want to build falls into."** And there are two pitfalls common to almost every scheme. The first is that **"work started before the grant decision is not eligible"** — sign or start work first, and not one yen comes out. The second is that **"subsidies are paid in arrears (reimbursement)"** — you have to advance the full development cost once. Miss these two, and a subsidy turns from "a weapon you could have wielded" into "a trap that wrecks your cash flow."

This article draws on the "buyer-side decisions" I have seen through projects I actually built — a **B2B SaaS that won the Minister of Economy, Trade and Industry Award** (DX for the lumber-distribution industry), a **payment platform that maintains zero double-charges in production**, an enterprise AI platform for a major domestic broadcaster, and others — to map out how to choose among the four major schemes. The aim is not application techniques for any individual scheme, but **the decision axes a buyer needs to avoid losing money.**

> **On the numbers**: the subsidy rates, caps, and schedules in the body are guideposts based on each scheme's **official public solicitation guidelines and official websites** as confirmed at the time of writing (July 2026). Because subsidy schemes are revised every year, **always confirm against the latest solicitation guidelines before making an ordering decision.** For a few items I could not fix numerically on the official site, I structurally note "confirm in the latest solicitation guidelines." The quantitative values tied to my real projects (221 endpoints, zero double-charges in production, four rounds of security audit, and so on) are measured values verifiable from the repositories; I do not assert business ROI.

---

## 1. The big picture: a map for choosing among the "four major schemes" usable for system development

There are countless subsidies that could relate to outsourcing system development, but the four a buyer should grasp first are these. What matters is to choose by **"which expense category the thing you want to build falls into," not "which scheme is grander."**

| Scheme (common name) | Focus | Fit with system development | Subsidy rate (guide) | Cap (guide) |
|---|---|---|---|---|
| **Digitalization & AI Adoption Subsidy** (formerly IT Introduction Subsidy) | Adoption of registered off-the-shelf IT tools / SaaS | ◎ SaaS/package adoption ／ ✕ full-scratch | 1/2–2/3 | Up to ¥4.5M in the Normal Frame |
| **Small Business Sustainability Subsidy** | Sales-channel development for small businesses | ○ Website production, small-scale outsourced development (commissioning/outsourcing expenses) | 2/3 (partly 3/4) | ¥500K to a maximum of ¥2.5M |
| **Monozukuri Subsidy** | Development of innovative products/services, capital investment | △ System building incidental to capital investment | 1/2–2/3 | Several million to tens of millions of yen depending on the frame |
| **SME Labor-Saving Investment Subsidy (General Type)** | Solving labor shortages / labor saving | ◎ Bespoke labor-saving system development | 1/2–2/3 | ¥7.5M to ¥100M by headcount |

You can narrow the decision down with a simple flow.

```text
作りたいのは「既製のSaaS/ITツールの導入」か「独自開発（スクラッチ）」か？

├─ 既製SaaS/ITツールの導入
│    └─ 事務局に登録済みのツールか？
│          ├─ Yes → デジタル化・AI導入補助金（旧IT導入補助金）が王道
│          └─ No  → 登録ツールに代替がないか確認 or 下記スクラッチ側へ
│
└─ 独自開発（スクラッチ／オーダーメイド）
     ├─ 目的が「人手不足の解消・省力化」→ 省力化投資補助金（一般型）
     ├─ 目的が「革新的な製品・サービス開発＋設備投資」→ ものづくり補助金
     └─ 小規模事業者のHP・小規模開発 → 小規模事業者持続化補助金
```

Let me pre-empt a point many buyers get wrong. **"It's the IT Introduction Subsidy, so they'll build my system however I want" is not true.** As the next section explains, this scheme presupposes "registered off-the-shelf tools," and full-scratch development is, in principle, out of scope. If the thing you want to build is proprietary development, you need to shift your gaze toward the labor-saving and Monozukuri side. The build-or-buy decision itself is covered in detail in [the build-vs-buy, SaaS-vs-scratch, in-house-vs-outsource decision framework](/blog/build-vs-buy-saas-vs-scratch-inhouse-vs-outsource-guide), so settle your policy there before you pick a scheme.

---

## 2. Digitalization & AI Adoption Subsidy (formerly IT Introduction Subsidy) — the royal road for SaaS/package adoption

The former "IT Introduction Subsidy" was renamed to the **"Digitalization & AI Adoption Subsidy 2026"** from FY2026. The name changed, but the essence is the same: the basic form is to **adopt an off-the-shelf IT tool registered with the secretariat (accounting, ordering, inventory, CRM, reservations, and so on) through a registered IT-introduction-support vendor.**

### 2-1. Subsidy rate and amount (Normal Frame)

According to the official solicitation guidelines (Normal Frame), the subsidy rate and amount for the Normal Frame are as follows.

| Item | Detail |
|---|---|
| Subsidy rate | **Up to 1/2** (**up to 2/3** if certain low-wage-employment requirements are met) |
| Amount (1 or more processes) | **¥50,000 or more to under ¥1.5M** |
| Amount (4 or more processes) | **¥1.5M or more to ¥4.5M** |

### 2-2. Eligible expenses, and why scratch development "doesn't fit"

The eligible expenses **require software purchase costs and cloud usage fees (up to 2 years)**, to which are added options such as feature extensions, data-integration tools, and security measures, plus services such as introduction consulting, configuration, training, and maintenance support.

Turned around, this means that **the full-scratch development where a buyer says "build it from zero to match our operations" is not a natural fit for this scheme.** Understand that what is subsidized are "registered off-the-shelf tools," and you cannot simply put fully bespoke outsourced development on it. If a package-plus-customization hybrid can meet the requirements, it's the top choice; but if you want to build a lump of proprietary logic, you should look at another scheme.

### 2-3. Schedule and the "ban on starting work before the grant decision"

The official project schedule shows, for the Normal Frame, the Invoice Frame, and the Security Measures Promotion Frame, for example, a 1st deadline of **July 21, 2026**, a grant decision of **September 2, 2026 (planned)**, and a project-implementation period of **from grant decision to February 26, 2027 (planned).** The decisively important point here is that **the project-implementation period begins "from the grant decision."** In other words, **if you order, start work, or pay before the grant decision, it becomes ineligible.** The accident of looking only at the deadline and ordering early is the most common, so I dig into it again in Section 6.

Note that because this scheme works **through an IT-introduction-support vendor and a registered IT tool,** the buyer starts from "which support vendor's, which registered tool, do I choose." The risk that the tool constraint here distorts the optimal solution is discussed in the "traps" of Section 8.

---

## 3. Small Business Sustainability Subsidy — the "first step" for small businesses

For **small businesses with few employees** (a guide of roughly 5 or fewer in commerce and services, roughly 20 or fewer in manufacturing and others), the Small Business Sustainability Subsidy is easy to use as an entry point to DX. It is structured so that you **formulate your own management plan** with support from the Chamber of Commerce and Industry or the Society of Commerce and Industry, and have your sales-channel-development efforts subsidized.

| Item | Detail (guide; confirm the latest) |
|---|---|
| Subsidy rate | 2/3 (3/4 for deficit businesses eligible for the wage-increase special provision) |
| Cap | Normal Frame ¥500K / up to around ¥2.5M using various special provisions (invoice, wage increase, etc.) |
| Main eligible expenses | Machinery/equipment costs, publicity costs, **website-related costs**, exhibition costs, travel costs, new-product-development costs, rental fees, **commissioning/outsourcing costs** |

What matters in the context of system development are **"website-related costs"** and **"commissioning/outsourcing costs."** A corporate site, a reservation form, or outsourcing a small business web app may be covered under this frame. That said, the cap is small, and website-related costs often have **an upper limit on the proportion they can occupy of the whole subsidy,** so it is not suited to "building a large core system." It is accurate to regard it as a small business's "first step into DX." Because amounts, frames, and deadlines are revised frequently, **always confirm against the latest solicitation guidelines.**

---

## 4. Monozukuri Subsidy — for development incidental to capital investment

Its official name is the **"Monozukuri, Commerce and Service Productivity Improvement Subsidy."** Its focus is developing innovative products/services and **capital investment** that raises productivity, and its cap is among the largest of the four major schemes (on the order of several million to tens of millions of yen depending on the frame and headcount; **always confirm the specific amounts in the latest solicitation guidelines**). From a system-development standpoint, the point to grasp is that **"machinery/equipment and system-building costs" are the core required expenses.** High-unit-cost capital investment (machines, dedicated equipment, and the system building that controls/integrates them) is the lead, and **pure software development "on its own" tends not to pass.** Therefore, the split is:

- A case where system development to run / integrate data with a production facility, inspection device, etc. is **incidental** to its introduction → good fit
- Scratch development of only a business web app, with no accompanying capital investment → not a natural fit (consider labor-saving / sustainability)

Because the solicitation guidelines are updated for each round (Nth deadline) and wage-increase requirements and the like change year to year, it is safest to firm up "the substance of the investment" — as in [the technology-selection framework for legacy-industry DX](/blog/legacy-industry-dx-technology-selection-framework) — and then aim at the latest solicitation guidelines.

---

## 5. SME Labor-Saving Investment Subsidy (General Type) — if you want to save labor with bespoke development

The **SME Labor-Saving Investment Subsidy** has drawn a lot of attention recently. Its purpose is to solve labor shortages and save labor, and it splits into a **"catalog-order type," where you choose from a catalog,** and a **"General Type," where you build equipment/systems bespoke to the individual site.** **It is the latter (General Type) that fits outsourcing proprietary development well.**

The subsidy rates and caps confirmable on the official site (General Type) are as follows.

| Headcount | Cap (normal) | Cap with large wage increase |
|---|---|---|
| 5 or fewer | ¥7.5M | ¥10M |
| 6–20 | ¥15M | ¥20M |
| 21–50 | ¥30M | ¥40M |
| 51–100 | ¥50M | ¥65M |
| 101 or more | ¥80M | ¥100M |

The subsidy rate is **1/2 for SMEs (2/3 in the case of a large wage increase) / 2/3 for small enterprises, small businesses, and rehabilitation businesses.** Because it can cover "equipment introduction and system building tailored to the individual site's equipment and business," it becomes a strong option when outsourcing **bespoke system development for operational automation and labor saving** (e.g., an in-house system that automates manual aggregation, transcription, and reconciliation). The solicitation is held over multiple rounds, so **always confirm the latest round, application period, and requirements on the official site.** The hybrid strategy I took in the lumber-distribution DX — "use off-the-shelf foundations to the maximum, such as Cognito for authentication and Stripe Connect for payments, and limit what we build ourselves to industry-specific logic alone" — is effective in this labor-saving frame too. **The more you concentrate the subsidized scope on "the part directly tied to labor saving,"** the easier it is to explain in the review as well.

---

## 6. The iron rule common to every scheme — never "start work before the grant decision"

I'll pull out and emphasize the **most accident-prone rule** common to the four schemes so far.

> **Any expense for which you sign a contract, start development, or pay the vendor before the grant-decision date is, in principle, entirely ineligible.**

Lay out the life of a subsidy in chronological order, and the "zone you must not touch" becomes obvious at a glance.

```text
①公募締切  ②審査  ③交付決定 ────────── ④事業実施 ── ⑤実績報告 ── ⑥確定 ── ⑦入金
                      ▲                     └── ここで初めて発注・開発・支払いOK
                      │
        ここより前に契約・着手・支払い＝補助対象外（全額アウトのリスク）
```

"Adopted, so order with confidence" is also dangerous. **"Adoption" and "grant decision" are different things,** and it is on the safe side to wait until the grant-decision notice is issued. You will be tempted to start development early under deadline pressure, but whether you can hold back there determines the success or failure of the subsidy. Always **build the schedule forward and backward from the "grant-decision date"** — this is the iron rule.

Another shared iron rule is **"payment in arrears (reimbursement)."** Because a subsidy is paid in only after project completion, through the performance report and confirmation inspection, you have to **advance the full development cost once.** The gap from grant decision to payout can run from several months to about a year, and overlook this and you reach the worst ending: "we won the subsidy, but ran out of cash."

---

## 7. Back-calculate the schedule — a realistic timeline from solicitation to payout

What a buyer should do is **back-calculate from the grant-decision date, not calculate forward from the deadline.** Here is one example of a rough timeline (it varies greatly by scheme and round, so always confirm against the latest solicitation guidelines).

```text
[公募締切] ── 約1〜2ヶ月 ──▶ [交付決定]
     ▲                              │
     │ ここまでに: 事業計画・見積り     ├─ ここから発注・要件定義・開発着手
     │ 相見積り・申請書類を準備          │
     │                              ▼
     └──────────── [事業実施：数ヶ月] ──▶ [実績報告] ──▶ [確定] ──▶ [入金]
```

Realistically, it is safe to allow **half a year to over a year** "from the moment you decide to the payout." That is exactly why **raising the precision of your requirements definition and estimate** while you wait for the subsidy pays off. If the requirements definition is loose, the spec swells after the grant decision, the eligible amount and the actual cost diverge, and your self-funded portion balloons. I summarize the importance of pre-order preparation in [the complete guide to outsourcing system development](/blog/system-development-outsourcing-guide-vendor-selection-cost), and a feel for cost ranges and how to see through an estimate in [the development-cost / estimate market-rate guide](/blog/system-development-cost-estimate-market-rate-guide). With or without a subsidy, the structure is unchanged: **this preparation decides 80% of the success or failure of the order.**

---

## 8. The four traps of "subsidy-first" investment

Used correctly, a subsidy is powerful, but get the order of decisions wrong and you lose. Here are four "traps" I have seen again and again in buyer-side consultations.

### Trap 1: Justifying an investment that doesn't earn its ROI with a subsidy

**"We build it because we can get a subsidy" is backwards.** Even at a 1/2 subsidy rate, the other 1/2 is self-funded, and if there is no prospect of recouping the investment in the first place, **you're in the red even with the subsidy.** The correct order is "first judge whether the investment earns its ROI, then choose the scheme the investment most naturally fits." A subsidy is not "a reason to create an investment"; it is "a tailwind that pushes a good investment forward."

### Trap 2: Being lured by the subsidy rate and underrating the self-funded portion

Even at a subsidy rate of 1/2–2/3, **there is always a self-funded portion.** And because it is paid in arrears (reimbursement), you need the cash flow to **advance the full amount once.** Do not judge by the "effectively half price" figure alone — always confirm "whether you have the funds to pay the full amount up front."

### Trap 3: Choosing a suboptimal tool/vendor because of the registered-tool constraint

The Digitalization & AI Adoption Subsidy **presupposes registered IT tools and IT-introduction-support vendors.** Prioritize the subsidy too much and "choose from among the registered ones when there is really a tool that fits your business better," and you may end up paying an "unfit cost" over the long term that exceeds the subsidy amount. **Choose the tool by business fit, then aim at the scheme usable for it** — do not break that order.

### Trap 4: The schedule bending to the subsidy's convenience, and missing the business's timing

A subsidy is bound by the deadlines of the solicitation round, grant decision, and performance report. **Letting an investment you should start right now lie dormant for several months until the next solicitation** is a cost — an opportunity loss. Weigh the "cannot start work before the grant decision" constraint against your business's demand for speed, and keep **the decision not to use a subsidy when you're in a hurry** among your options.

---

## 9. A checklist for buyers

Before you outsource system development using a subsidy, confirm the following.

- [ ] Is what you want to build "off-the-shelf SaaS/tool adoption" or "proprietary development" — the entry point to the scheme changes
- [ ] Does the investment earn its ROI **without** the subsidy (Trap 1)
- [ ] Do you have the funds to **advance the full development cost once** (arrears premise / Trap 2)
- [ ] Can you keep the operation of **not contracting, starting work, or paying before the grant-decision date** (Section 6)
- [ ] Have you **back-calculated the schedule from the grant-decision date** (Section 7)
- [ ] Can you firm up requirements definition and comparative estimates while you wait for the grant decision (Section 7)
- [ ] Have you confirmed the subsidy rate, cap, eligible expenses, frame, and deadline in the **latest solicitation guidelines** (revised annually)
- [ ] Can you articulate your quality and security requirements (idempotency, tests, audits, type safety) to the vendor

With or without a subsidy, the final check — **whether you can articulate and demand quality and security** — ultimately determines the quality of the order. "Fast and cheap" alone is not value. Even when you accelerate development with one person × generative AI (Claude Code), it becomes a buyer's asset only when you **guarantee "safety" through human verification gates** — that has been my consistent position.

---

## 10. Conclusion — a scheme is nothing more than a "vehicle for a purpose"

- There are four main schemes usable for outsourcing system development. **SaaS/package adoption = Digitalization & AI Adoption Subsidy**, **bespoke labor saving = Labor-Saving Investment Subsidy (General Type)**, **incidental to capital investment = Monozukuri Subsidy**, **small business website / small-scale development = Sustainability Subsidy.**
- The Digitalization & AI Adoption Subsidy **presupposes registered tools plus an IT-introduction-support vendor,** and full-scratch is, in principle, out of scope.
- The iron rules common to every scheme are **"work started before the grant decision is not eligible"** and **"payment in arrears."** Miss these, and a subsidy wrecks your cash flow.
- **An investment that earns its ROI first, the scheme second.** Do not let the subsidy rate, cap, or schedule distort your investment decision.

A subsidy is "a tailwind that pushes a good investment forward"; it is not the reason for the investment itself. First firm up what you should build, then aim at the scheme it most naturally fits — keep that order and a subsidy becomes a powerful weapon for the buyer.

---

**The author is not an IT-introduction-support vendor and does not act as a subsidy-application agent.** This article is a neutral explanation to support the buyer's decision-making. Always confirm the scheme details, the latest subsidy rates, caps, and schedules in the official solicitation guidelines. As for the stage before choosing a scheme — the DX policy-making of "should we even build it" and "where and how much should we spend" — I can help, in the form of free DX consultation and diagnosis, based on the knowledge cultivated in a B2B SaaS that won the Minister of Economy, Trade and Industry Award and a payment platform with zero double-charges in production.