How to Run a Subsidised System Development Project — Working Backwards From the Grant Decision, and the Practicalities of Writing the Business Plan

The previous article, “Can You Use a Subsidy to Outsource System Development?”, set out which programmes to look at for which purpose.

This article is the follow-up. It deals with what happens after you have chosen a programme: how you actually run the project.

A subsidised system development project differs decisively from an ordinary one in two respects.

• Expenses ordered before the date of the grant decision are ineligible
• The subsidy is paid in arrears (settlement payment), so you front the entire development cost yourself

These two rules govern everything about the plan — how you build the schedule, when you contract, and how you manage cash flow. Put the other way round: plan backwards around these two, and you will avoid any major failure.

Note that the procedural detail differs by programme and by application round. This article sets out the general flow as of July 2026; align your actual plan with the call-for-applications guidelines of the programme you are using.

1. The Bottom Line First

Here are the points to have covered when planning a subsidised system development project.

• Build the schedule not from your preferred delivery date but by working backwards from two dates: the date of the grant decision (when you may order) and the project implementation deadline (when acceptance inspection and payment must be complete). The results report has its own, later deadline
• “Selection” and “the grant decision” are separate procedures. As a rule, you may only order after the grant decision
• Plan your cash flow on the assumption that around a year will pass between starting and receiving the money (with bridge financing if needed)
• The business plan is the client’s responsibility. What you can ask of the vendor extends to supplying factual material about the development
• Supporting documents (contracts, delivery notes, acceptance certificates, payment records) will definitely be used in the results report. Assemble them as each event occurs
• Ask yourself once, before applying, whether the investment would be worth making even without the subsidy

2. Understanding the Overall Flow — Development Is Only One Step

When a subsidy is involved, system development sits inside a sequence of procedures like this.

Check the guidelines / choose a programme
        ↓
Prepare the application (business plan, quotations, gBizID, etc.)    ... 1-2 months
        ↓
Application deadline → review → selection announced                  ... several months
        ↓
Grant application → grant decision                                   ← you may order from here
        ↓
Contract/order → development → acceptance → payment                  ... complete by the project deadline
        ↓
Results report → final review (subsidy amount fixed)
        ↓
Request for settlement payment → subsidy paid                        ... payment in arrears
        ↓
Commercialisation status reports, etc.                               ... continue for years after completion

Note: this is the pattern for programmes that go through two stages — “selection announcement → grant application” — such as the Monozukuri Subsidy and the Labour-Saving Investment Subsidy (general type). Under some programmes, such as the Digitalisation and AI Adoption Subsidy, the initial application is itself the grant application and the grant decision is issued as the outcome of the review (there is no intermediate selection announcement).

Where an ordinary project would run “order → development → acceptance inspection”, the application and reporting stages are bolted on at either end. Three points in particular deserve attention.

Selection and the grant decision are different things. Under the Monozukuri Subsidy, the Labour-Saving Investment Subsidy (general type) and similar programmes, the selection announcement is no more than a notification that your business plan has been chosen; a grant application procedure that scrutinises the expenses follows, and you can only order once the grant decision has been issued. The number of procedural stages varies by programme, but the point that you can only order after the grant decision is common to all of them. The procedural guidance for the Digitalisation and AI Adoption Subsidy likewise states explicitly that the IT tool is ordered, contracted and paid for after the grant decision. Expenditure on a jumped gun is, as a rule, not rescued.

The project implementation period has a deadline. Each programme sets a period from the grant decision to completion of the subsidised project (the project implementation deadline), and development has to be completed, and acceptance inspection and payment finished, by that deadline. The deadline for submitting the results report is set separately, after that — but the only expenses recognised are those paid by the project implementation deadline. If development slips past the project implementation deadline, you risk not receiving the subsidy at all.

The money comes last. No subsidy is paid until confirmation of the results report is complete. And even then it is not transferred automatically: under the Monozukuri Subsidy and others, payment is only made once the applicant submits a request for settlement payment after the subsidy amount has been fixed. That request has its own deadline under each programme, so do not submit the results report and then relax and forget about it. Expect around a year from starting out to receiving the money, and plan to cover the entire development cost over that period out of your own funds or from borrowing.

3. Schedule Backwards From Two Dates

The development schedule for a subsidised project is built by fixing the following two dates first and fitting the development in between them.

• Start point: the (expected) date of the grant decision — you cannot order before this
• End point: the project implementation deadline (the deadline for completing the subsidised project) — acceptance inspection and payment must be finished by this date. Submission of the results report is a separate, later deadline

3.1. A Worked Example

Suppose the grant decision comes in April, the project implementation deadline (for completing acceptance inspection and payment) is the end of November, and the results report is submitted after that.

The crucial thing here is to place acceptance inspection and payment one to two months before the project implementation deadline. In acceptance testing of a business system, problems that only surface once you push real data through it will always appear. Schedule acceptance right up against the deadline and you have no time for fixes, which leads to the self-defeating outcome of “signing off acceptance while it is still inadequate, in order to make the deadline”.

3.2. What You Can and Cannot Do Before the Grant Decision

You cannot contract before the grant decision, but that does not mean nothing can be done.

Indeed, the more you sharpen the requirements and the accuracy of the quotation before applying, the more smoothly development can start once the grant decision arrives. If the quotation at application time diverges substantially from what is actually developed, you lose time in the grant application or in plan-change procedures.

Note also that obtaining a gBizID Prime account, which is needed for electronic submission, involves a review and can take time. It is safer to obtain it when you first start considering a programme, rather than just before you apply.

3.3. Aligning Phases With Contracts

Being a subsidised project does not change how you think about the development contract. If you are using a multi-stage contract — requirements definition under a quasi-mandate, design onwards under a contract for work (see “How Should You Structure a Contract Development or Operations & Maintenance Contract? — Learning the Quasi-Mandate vs. Contract-for-Work Distinction from IPA’s ‘Model Contract’”) — you need to map which expenses under which contract are eligible onto the content of the grant application. If you are splitting the contracts, itemising the quotations along the same lines makes reconciliation at results-report time much easier.

4. Cash Flow — Preparing for Payment in Arrears

A subsidy is not an advance. Development costs are paid entirely up front, and the subsidy arrives after the results report has been confirmed.

Things to check when planning:

• Can you front the entire development cost (including ineligible expenses) for the period until the money arrives?
• If not, can you use bridge financing from a bank (in some cases you can approach them on the basis of the selection notice)?
• At a subsidy rate of 1/2, the remaining 1/2 — at 2/3, the remaining 1/3 — is a permanent cost to you
• Maintenance and running costs after go-live are normally ineligible and become an annual cost to you. There are exceptions: under the Digitalisation and AI Adoption Subsidy, for example, cloud usage fees for a registered IT tool can be eligible for a set period (up to two years under the standard category), and the Monozukuri Subsidy also has an expense category for cloud service usage fees. Which running costs are eligible, and for how long, has to be checked in the guidelines for each programme

The last two points in particular are easy to overlook. Inflate the development scope on the basis that “there’s a subsidy”, and both your own share and the maintenance cost inflate with it, remaining as a burden after the subsidised project has ended. Asking yourself once, before applying, whether the investment stands up as an investment decision even without the subsidy is, in the end, the safest approach.

5. Writing the Business Plan — What the Client Writes, and What the Vendor Can Supply

Subsidy applications are assessed on the business plan. And the plan is the responsibility of the applicant, that is, the client.

5.1. What Only the Client Can Write

• Your own management challenges (what is causing you trouble, and why solve it now)
• Numerical targets (labour productivity, added value, wage increases — whichever indicators the programme requires)
• Implementation structure (who is accountable, who is the point of contact on the business side)
• Funding plan (own funds versus borrowing)

The 中小企業省力化投資補助金 (一般型) (SME Labour-Saving Investment Subsidy, general type), for instance, requires a business plan including targets for improving labour productivity and raising wages (the indicators and figures used differ by application round, and some rounds let you choose from several indicators), with clawback provisions if the targets set at application time are missed. These are commitments about the running of the business itself, and not the kind of thing a vendor can take on in your place.

5.2. Factual Material the Vendor Can Supply

The factual side of the development, on the other hand, is where the vendor can help.

• Documents describing what is being built (what will be created, and how which operations will change)
• System architecture diagrams (current state and post-implementation)
• A quotation itemised to match the expense categories
• The basis for estimating the reduction in effort (how current working time is measured, how the reduction is calculated)

Of these, the one that carries the most weight in assessment is, perhaps surprisingly, the last: the basis for the estimate. A build-up along the lines of “data entry takes an average of X minutes per order, at Y orders a month, so Z hours a month; of that, the Z% moving to automatic import is what will be eliminated” makes for a far more convincing plan than a qualitative statement that “operations will become more efficient”. That build-up can only be produced jointly, from the client’s operational data and the vendor’s design knowledge.

5.3. For Help With the Writing Itself, Go to a Public Support Body

Support with how to write the plan itself is outside a development vendor’s remit. Consult a Chamber of Commerce and Industry or Society of Commerce and Industry, a よろず支援拠点 (Yorozu Support Centre), a support organisation listed on ミラサポplus, or a specialist such as a 中小企業診断士 (SME management consultant). If you use a success-fee application agency, we recommend taking a cool look at the fee rate and the contract terms.

6. Preparing for the Results Report — Assemble Documents as Each Event Occurs

For the results report you submit the whole chain of supporting documents from order to payment. Generally, the following are required.

• Competing quotations (under the Monozukuri Subsidy, the Labour-Saving Investment Subsidy (general type) and similar programmes, procurement above a certain amount requires, as a rule, quotations from more than one supplier. If you can only obtain one, you will be asked for explanatory material such as a statement of reasons for supplier selection)
• The contract, or the purchase order and acknowledgement of order
• The delivery note and acceptance certificate (dated within the project implementation period)
• The invoice and the transfer record (under the Monozukuri Subsidy and the Labour-Saving Investment Subsidy (general type), payment must as a rule be made by bank transfer in the applicant’s own name, and cash payment is not eligible. A receipt does not substitute for a transfer record, so set the payment method to bank transfer from the outset)
• Any variation contract or memorandum covering a change of specification

The way people come unstuck here is always the same: trying to put it all together afterwards. Because the consistency of the dates is checked (was the order placed on or after the date of the grant decision; was payment made within the period), documents cannot be assembled retrospectively — and should not be. At each point — order, delivery, acceptance inspection, payment — finalise the dated document there and then, and file it. That alone dramatically reduces the burden of the results report.

From the development side, this is simply the document management that ought to be happening on any contract development project. On a subsidised project, it is merely spelled out as a condition of receiving the subsidy.

Some programmes also carry several years of reporting obligations after the money arrives, such as the commercialisation status report. The indicators used in those reports (productivity, effort, revenue) are much easier to produce each year if you build the recording mechanism into the system at development time, rather than starting to measure once the system is live.

7. Common Stumbling Blocks and What to Do About Them

Summary

• Planning a subsidy-funded development comes down to working backwards from two dates: the grant decision (when you may order) and the project implementation deadline (when acceptance inspection and payment must be complete). The results report has its own, later deadline
• Selection and the grant decision are different things. As a rule, ordering comes after the grant decision
• The subsidy is paid in arrears. Settle the cash flow for fronting the full amount first
• The business plan is the client’s responsibility. What you draw from the vendor is factual material — what is being built, architecture diagrams, quotations, and the basis for the estimated benefit
• Do not leave supporting documents to the end; assemble them as each event occurs
• Programme details change from one application round to the next, so always check the latest guidelines

For the overall picture of choosing a programme, see the previous article, “Can You Use a Subsidy to Outsource System Development?”; for a concrete example using the Labour-Saving Investment Subsidy, see “Can the Labour-Saving Investment Subsidy Pay for Moving FAX Orders to the Web?”.

If You Are Considering Development on the Basis of a Subsidy

KomuraSoft LLC takes on contract development centred on Windows business applications. For projects premised on using a subsidy, we help with the ballpark quotation, architecture diagrams and the basis for estimating the reduction in effort before you apply, and we plan the development that follows the grant decision on a schedule worked backwards from the project implementation deadline.

We do not act as an agent for applications, and we do not make judgments about whether an application will be selected. Take the application procedure to a public support body or a specialist — and do feel free to talk to us about the substance of the development and how to run it, from the requirements-sorting stage onwards.

Related Articles

Recent articles sharing the same tags. Deepen your understanding with closely related topics.

Related Topics

These topic pages place the article in a broader service and decision context.

Where This Topic Connects

This article connects naturally to the following service pages.

Frequently Asked Questions

Common questions about the topic of this article.

Once I have been selected, can I place the development order straight away?

Under many programmes, such as the Monozukuri Subsidy, the selection announcement is followed by a grant application procedure, and the grant decision is issued after the secretariat's review. Under some programmes, such as the Digitalisation and AI Adoption Subsidy, the initial application is itself the grant application — but either way, what is eligible is, as a rule, expenditure contracted or ordered on or after the date of the grant decision. Ordering immediately after selection may still be premature, so check in the call-for-applications guidelines for your programme when ordering becomes possible, and do not contract before then.

Does a subsidised system development project take longer than an ordinary one?

The development work itself takes no longer, but procedural periods are added at either end. Allow one to two months to prepare the application, several months until the selection announcement, further time until the grant decision — and after development is complete, payment comes only after the results report and its confirmation. It is not unusual for a year or so to pass between starting out and receiving the money. In addition, because acceptance inspection and payment must be completed by the end of the project implementation period, the development period has to be secured by working backwards from that deadline.

Can the vendor write the business plan for me?

The business plan is the responsibility of the applicant, that is, the client. Only you can write about your own management challenges, numerical targets and implementation structure. What a vendor can contribute is material covering the factual side of the development: descriptions of what will be built, system architecture diagrams, quotations, and the basis for estimating the reduction in effort. If you need help with how to write the plan itself, consult a Chamber of Commerce and Industry, a よろず支援拠点 (Yorozu Support Centre) or an SME management consultant.

What documents are needed for the results report?

This varies by programme, but generally you need the full chain of supporting documents from order to payment: the contract (or purchase order and acknowledgement of order), the delivery note, the acceptance certificate, the invoice and the transfer record. Because the consistency of the dates is checked (was the order placed on or after the date of the grant decision; was payment made within the project implementation period), it is important to assemble the documents as each event occurs — including any variation contract where the specification changed during development.

Author Profile

Profile page for the article author.

Go Komura

Representative of KomuraSoft LLC

Focused on Windows software development, technical consulting, and investigations into failures that are difficult to reproduce.