Stalled deals in Japan: is the deal dead or just queued?

Published Nov 3, 2026

December pipeline review. Japan has a line that reads: Negotiation, 95 days, next touch April.

HQ asks what it takes to close this quarter. The country lead says the customer is still interested. Someone moves the close date out a month, the stage stays put, and the same line comes back in January.

That line can mean two very different things. In the CRM, a deal the buyer has walked away from and a deal waiting its turn look exactly the same.

A quiet deal is either stalled or queued, and the responses are opposite

A stalled deal has no one moving it inside the buyer. It got pushed aside, it never reached the meeting where it would be decided, or the buyer has quietly dropped out.

A queued deal has support inside the buyer and is waiting for something on the buyer’s calendar: a budget being set, or an approval slot with someone senior.

Both show no activity, no stage change and a close date that keeps moving. But the right move differs.

Chasing a queued deal does not move it up the queue. It uses up the time of the person walking it through their own company. Pressing for a December signature with a discount has the same problem if the money sits in a budget that starts in April: a lower price does not create the slot.

Waiting on a stalled deal gets you the same explanation next quarter.

The calendars are part of why this shows up in Japan reviews. Many HQs are pushing for a December year end, while most large Japanese companies run April to March: of companies listed on the Tokyo Stock Exchange’s Prime Market, 68% close their books in March (Nomura Securities Investment Information Department, published March 2023, based on company filings). At companies on an April start, next year’s budget often firms up between January and the end of March, and the timing varies by company.

That is not a reason to call every quiet Japan deal queued. It is a reason to check.

The published numbers do not separate the two

In a May 2026 survey by IDEATECH and Hiroyasu Kitagawa of Demagen Research Institute (330 people who took part, with at least one colleague, in a B2B software or IT infrastructure purchase of ¥5 million or more a year), 73.5% said the evaluation ran longer than planned (n=325).

The top cause was waiting for senior management’s decision, at 63.6%, and budget approval came in at 31.0% (n=239, multiple answers). IDEATECH sells survey-based PR and this was an online panel, so read the ranking and the rough scale. These answers alone do not show whether those deals were waiting or stalled.

Ebsta and Pavilion’s 2025 GTM Benchmarks (655,000 deals across 387 companies, not Japan-specific) point the other way. Deals that slipped one month closed at 13%, and deals that slipped three months at 8%. Read alone, that says cut.

Neither tells you which of your deals is which. The survey did not track outcomes, and the slip data is sorted by how long the deal moved, not by what the buyer was doing. You need your own split.

Ask who decides next, on what date, and whether it is on the agenda

“When do you expect a decision?” gets you “early next year,” which a stalled deal can say just as easily.

Have the Japan rep ask for three things:

Who decides next: a department head, an executive, or the department that holds the budget
The date: a scheduled budget meeting, an approval deadline or a board meeting
The agenda: whether this deal is confirmed to come up, and what goes in front of them

If all three come back in the buyer’s words, the deal is queued. Anyone can name the budget meeting date, even for a deal nobody is carrying, which is why the agenda question matters.

If any of the three is missing, handle it as stalled. The rep’s feel for the account does not make a deal queued.

Frame the question as preparation rather than a chase: “When does this next come up internally? We would like to get you what you need ahead of it.” The country lead should word this in Japanese, because the tone is what makes it work.

““No budget” in Japan: check the amount and the timing” covers the moment a buyer raises budget. This sort applies to every quiet deal, whatever the stated reason.

Stop making the close date carry the reason

Today the close date does three jobs: expected landing, the reason for waiting, and a reminder to call. So “budget timing” is recorded only as a date change, and the reason is lost. In Salesforce the Close Date is a required standard field, so it cannot be left blank either.

Split the jobs:

Stage: how far your sales process has got. No change
Approval progress: which approval level the buyer has reached, as in “Forecast your Japan pipeline on approval progress”
Close date: the expected signature date, and nothing else
Next decision date (new): a date the buyer named on their internal calendar
Budget year (new): which fiscal year’s money this deal depends on

Neither new field is required. Forcing a field people cannot know yet gets you plausible dates.

Do not reuse the restart or check date on deals on hold. That is when you go back to look, not when the buyer decides. Deals on hold stay out of the forecast as they do now, on their own line.

Apply the sort only to deals with more than 30 days since the last activity. A moving deal with a blank field is unaffected.

Among those deals, a deal is queued only if its next decision date is in the future. Blank or past means stalled. When the date goes in, add who decides and what is on the agenda to the deal notes in one line. A date without that line does not count.

This gives the CRO something better than “Japan is slow.” The review can say how much of the slipped amount has a named decision date in April, and how much has none.

Prepare queued deals, and check stalled ones beyond your contact

For a queued deal, work back from the decision date. Get the material into the contact’s hands about two weeks ahead: one page they can paste into the approval document, the cost breakdown finance will ask about, the reasoning behind the comparison.

If the budget year is next year, check now, while there is still time to be on the agenda.

On the stalled side, your contact may simply not know. Check with the person drafting the proposal or the department holding the budget, through your contact. If nothing shows, ask plainly: “Would it be easier internally to carry this into next fiscal year, or to close it for now?”

Offering to close matters. A contact who found it awkward to say no can now answer.

If they carry it over, put the deal on hold with a check date. If they close it, mark it lost with the reason and a restart condition. If the reason is budget amount or timing, keep it on hold even when they say close. After two unanswered attempts, the rep and sales manager decide whether to close it.

Check passed dates weekly, or “queued” becomes the next excuse

“Queued” is a convenient word. Left alone, it becomes a nicer way of saying “budget timing.”

In the weekly Japan pipeline meeting, start with deals whose next decision date has passed. Ask one thing: what was decided? This is a check, not a blame exercise.

If the date moves, add the reason in the buyer’s words to the notes. If it moves twice in a row, clear the date. Blank means stalled, so the deal stays there until someone confirms a new date.

The view is open deals with more than 30 days since last activity, with no upper limit, whether or not a next step is scheduled. It differs from the view in “AI time saved by your Japan sales team needs a destination,” which finds deals to contact. Take queued deals out of that list and its ratio.

Stage the rollout. The CRM admin adds the fields, and the Japan sales manager and RevOps agree the definitions. Sorting and exports can start this week.

Forecast changes wait for the start of next quarter, with the CRO’s agreement. If the date falls outside the quarter, move the close date past it. Stalled deals stay out of commit until confirmed. Forecast categories can reset on stage changes (check your setup), so adjust by hand from the exported list for the first quarter.

Moving deals to lost or on hold can also trigger automation. Check marketing sync, loss surveys and lifecycle updates first, and try a few deals before doing more.

Each week, save the deal IDs, count and amount on each side. Field history can show past dates, but not the split as the team saw it that week, and queued deals leave the view once you send material.

When a decision date passes, mark the deal decided, moved or gone. The main measure is how many queued deals actually reached the agenda on that date. If that share is low, the questions are not sorting deals. Look at win rate as well, but only as a reference, because the two sides get different treatment.

What we decided against

A “Queued” stage was rejected. It mixes your sales progress with the buyer’s state in one field, and stage conversion and time-in-stage stop being comparable with past quarters, across regions too.

Auto-classifying from activity logs was also rejected. Logs record contact with you, not what happens inside the buyer. On the log, stalled and queued are the same silence.

Sort quiet Japan deals by whether the buyer can name who decides next, on what date and whether the deal is on the agenda. If they can, the deal is queued, so prepare that decision. If they cannot, treat it as stalled and find out. Once the date passes, a queued deal goes back to stalled.

This week, open ten Japan deals with more than 30 days since last activity and see how many have those three answers. You will walk into December’s review knowing which lines are waiting and which ones are gone.

Whether a queued deal counts this quarter is an approval-level call. The rule is in “Forecast your Japan pipeline on approval progress, not rep confidence.”

Other notes on the same problem are collected under Sales & pipeline.