INSIGHTS FOR REVENUE LEADERSPublished by Consilegy ↗

Sales & pipeline

“No budget” in Japan: check the amount and the timing

“No budget” in Japan: check the amount and the timing

A Japan deal that looked healthy comes back with “no budget.” The rep marks it closed-lost.

HQ sees a pattern across the quarter, decides Japanese buyers are price-sensitive, and hands the region discount authority for next quarter.

Two of those three moves are wrong, and the discount is the expensive one.

Japanese IT budgets are going up, not down

JUAS, the Japan Users Association of Information Systems, has run an annual survey of corporate IT spending since 1994 under the supervision of the Ministry of Economy, Trade and Industry’s Commerce and Information Policy Bureau.

The 2026 edition (preliminary figures published 6 February 2026; fieldwork 6 September to 22 October 2025; sent to IT department heads at 4,500 listed and comparable companies; 957 responses) found that 52.6% of companies increased their FY2025 IT budget over the prior year.

The diffusion index, increases minus decreases, was 43.3 points, its fifth consecutive annual rise. The forward-looking figure for FY2026 is 39.9 points.

This is a survey of large listed companies, so do not stretch it to small and mid-sized firms.

It also asked IT department heads about IT budgets. A sales tool is often paid from a business unit’s budget instead, so read the figure as a sign that companies are not cutting IT spend, not as a measure of your buyer’s own envelope.

Directionally it is still clear. The IT wallet, at least, is not shrinking.

The increase is already spoken for, and a weak yen makes your product part of it

The same survey asked why budgets rose. Top reason: replacing, updating, or reinforcing existing systems and infrastructure, 66.3%. Second: the impact of the weak yen, rising labour costs, and vendor price increases, 46.6%. Third: growing cloud spend, 45.0%.

Read the second one again, because it is about you.

For a Japanese buyer paying for a USD-priced SaaS product, foreign exchange movement has already made your line item bigger without anyone deciding anything.

Your product is not sitting in the column marked “investments we chose.” It is sitting in the column marked “costs that went up.”

That column does not compete for budget. It gets absorbed, resented, and reviewed at renewal.

So when a buyer says there is no budget, the accurate translation is: the increase for this year is allocated, and this purchase is not in the allocation.

The fiscal year is the part HQ keeps missing

Most large Japanese companies close their fiscal year on 31 March: 68% of companies listed on the Tokyo Stock Exchange’s Prime Market close their books in March (Nomura Securities, published March 2023).

Budget requests for the following year are drafted through autumn and winter, and the envelope hardens well before April.

Put a global sales calendar on top of that and the mismatch is structural.

A US-headquartered vendor pushing hard through its own Q4 in December or January is arriving after the Japanese buyer’s envelope is essentially set.

A deal that hits “no budget” in September is not a lost deal. It is an early one.

The uncomfortable version: your Japan pipeline probably has deals that were killed for being three months ahead of schedule.

The room where the envelope is decided does not contain your rep

IDEATECH and Hiroyasu Kitagawa of Demagen Research published a second-wave study of large B2B purchases in Japan on 9 June 2026 (fieldwork 25 to 26 May 2026, 330 valid responses; respondents had been one of two or more people involved in buying B2B business software, SaaS, or IT infrastructure and security products with annual contract value above 5 million yen).

IDEATECH runs survey-based PR as a business and this is a panel survey, so read the figures for order of magnitude rather than precision.

The second most common source of internal friction was coordinating budget size and allocation, 51.7%.

Among those whose evaluation ran long (n=239), 63.6% pointed to waiting on an executive decision and 31.0% to budget approval itself. Finance and accounting appeared in 38.2% of evaluations as an involved function.

Your rep usually meets none of those people. A large existing customer may invite a vendor in before the budget is set, but a new deal rarely gets that.

“No budget” is a message relayed out of a room the rep has not entered. Persuading the messenger does not change what happened in the room.

Ask for a date, an envelope, and a name

Three things, in this order, before any conversation about price.

When is the next budget set? A contact who can answer with a month is at least adjacent to the process. A contact who cannot is outside it, which is a different problem and a more useful one to know about.

Which envelope does this come out of? Given that system replacement and reinforcement was the top reason for budget increases, cited by 66.3% of companies that raised budgets, a proposal framed as a new initiative competes for the scarcest money in the company.

The same product framed as replacing an existing arrangement, the spreadsheet, the legacy order-management workflow, the third-party contract nobody wants to renew, competes against a cost that is already approved.

The comparison stops being you versus a competitor and becomes you versus the current run rate.

Who drafts the request? Not who approves it. Who writes it. That person is doing unpaid work on your behalf inside a company you cannot see.

Then hold the deal properly. Do not mark it closed-lost with reason “price.”

Put it on hold, record the month the next budget is set, set the restart date two months before it, and associate the drafter to the deal as a contact with a “drafter” role rather than typed as free text, so the name survives a transfer.

If your loss reasons already include “budget,” keep it but define it as “budget timing does not fit (move to on hold),” so choosing it parks the deal instead of losing it.

Take on-hold deals out of this period’s forecast. Left open, they keep counting in pipeline value and forecast, and inflate end-of-quarter coverage.

In Salesforce, set the forecast category to Omitted. In HubSpot, use an on-hold stage at 0% probability or a separate pipeline. What you can configure depends on the tool and your subscription.

When the restart date arrives and the buyer’s budget conversation is live again, move the deal back to a normal stage and weight it by approval stage.

A follow-up task three months out with no basis behind the date produces a call on a day when nothing has changed inside the buyer. A call two months before the budget month lands while they are actively looking for material to build the request with. Same call, different room.

The wider view of designing revenue around the buyer’s internal process sits in Japan Market GTM and Messaging.

In Japan, “no budget” rarely means the money does not exist. It means this purchase is not in the current envelope. Before approving a discount, get the month the next budget is set, the envelope it comes from, and the name of the person who drafts the request.

Common mistakes

  • Granting Japan discount authority after a run of budget losses. A price cut moves the number, not the envelope. It also becomes the reference price in next year’s request, so the deal does not close this year and closes cheaper next year.
  • Treating the Japanese fiscal year as a scheduling detail. It sets when the answer is possible. A global push timed to your Q4 can land squarely after the buyer’s envelope has closed.
  • Reading a rising exchange rate as neutral. In yen terms your USD price rose without a decision, which files your product under unavoidable cost increases rather than chosen investment, and that classification follows you to renewal.

The third question, who drafts the request, does not end when your champion says they will. In Japan the material that has to go in the request is usually not in their hands, which is covered in in Japan, your champion cannot write the business case.

Other notes on the same problem are collected under Sales process.