Log why a Japan deal was forecast, or misses go unexplained
The same Japan deal appears in “closing this month” for the third month running. The rep says the customer is positive. At HQ the question becomes whether the local team is too optimistic.
That question is usually the wrong one. The more useful one is whether anyone can show why the deal was counted.
In one engagement we supported, the account owner knew the buyer was waiting for next fiscal year’s budget, and she had said so in meetings. But the CRM kept only a stage and an expected close date.
She pushed the date back a month at a time by hand. The deal was counted as “closing this month” every month and missed every month.
At the next month’s meeting, nobody could look up what the deal had been counted on the month before. The basis had been said out loud and recorded nowhere.
A miss is only explainable if the day-of basis was kept
Forecasts miss for several reasons. The buyer’s budget changes. A competitor enters. An internal decision slips. The rep misreads the situation.
All of these happen in Japan as anywhere.
The trouble starts after the miss.
To tell the reasons apart, you need the basis that existed on the day the deal was counted: how far the approval had climbed, when the budget was expected to be set, and who held the ball (your team, the buyer’s contact, or the buyer’s approver). Then you set that next to what changed afterwards.
A CRM normally shows you the latest state. When the forecast meeting adjusts a deal, the previous values are overwritten.
Some tools keep field history, but few companies keep the reason a deal was counted in one place and pull it up in the meeting after the miss.
Without it you cannot separate “the buyer changed course” from “the first read was wrong.” When you cannot separate them, the blame lands on the most visible person, the local rep.
Adding fields does not fix this either.
If no meeting uses the fields, people stop filling them in. The rep has no reason to enter information nobody reads.
Treat record, forecast, review and fix as one loop
Revenue architecture, as set out by Jacco van der Kooij of Winning by Design in his 2023 book, treats revenue as one customer process in which recording, forecasting, deciding, verifying and improving have to run together. The company’s Bowtie model tracks conversion and time at each stage.
For a Japan forecast, five things need an owner.
| What to decide | What it means |
|---|---|
| Record | Approval progress, expected budget timing, who holds the ball, and the date each one changed |
| Count | Which conditions put a deal into this month’s number |
| Review | Check the basis in the forecast meeting, adjust, and keep the basis as it stood that day |
| Compare | For missed deals, put the day-of basis next to what happened since |
| Fix | Change the counting rule or the sales action based on the comparison |
Approval progress lives in one deal field. Do not add new fields for each rung; take the date a rung changed from that field’s history.
The rep updates it on the same screen when moving the stage, and the manager checks it in the weekly forecast meeting.
“Expected budget timing” in the table is the same field as the “month the next budget is set” that we record for deals on hold, described below.
None of these is new. Having them as one loop is what matters. If one is missing, the others stall.
Once the dates of approval changes accumulate, you can see time by approval stage across deals, which is what the Bowtie’s stage-by-stage timing is meant to show.
On forecast day, save the list as it stood
What you keep is the list of deals counted in this month’s number at the weekly forecast meeting, with these columns: approval progress, budget timing, who holds the ball, expected close date, and forecast category.
Save it with the values as adjusted in that meeting, dated. The manager who runs the meeting owns this.
Look for a standard feature first. Salesforce has reporting snapshots, which save report results to a separate object on a schedule, and field history tracking. HubSpot keeps property history.
Whether you can report on past point-in-time values in bulk, and what limits apply to how much is kept and for how long, depends on the tool and its settings.
If neither works for you, export the list on the day of the meeting and save it in a fixed place. Why reports rewrite past numbers, and how to keep them, is in Japan’s conversion rate changed after you reported it to HQ.
For Japan, put the buyer’s budget and approval calendar into the count
A joint survey by IDEATECH and Hiroyasu Kitagawa (published April 2026, n=307, limited to buyers who took part with at least one colleague in purchases of 3 million yen or more; a vendor-run survey skewed toward large, multi-stakeholder deals) found that 60.9% of the purchases surveyed went through two approval layers.
Our reading: with two or more layers, internal steps continue after your contact agrees, and your own activity log cannot show how far they have gone.
Budget timing differs by company too, so confirm per account when and at which meeting the budget is decided, where the approval sits now, and as of what date each of these was true, and feed that into the count.
A deal known to wait for next year’s budget comes out of this month’s number and goes on hold.
Record the month the next budget is set and a restart date, and put the deal back in the forecast when the restart date arrives. How to hold it is in “No budget” in Japan: check the amount and the timing.
The axis that decides which approval rung a deal sits on is covered in Forecast your Japan pipeline on approval progress, not rep confidence.
For a miss, set the saved values next to today’s
Do not create a new meeting to review misses. Put it on the agenda of an existing forecast meeting once a month.
Set the values saved on the day the deal was counted next to the current ones: approval progress, budget timing, who holds the ball, expected close date. Then sort each miss into one of two groups.
- Buyer-side change: the deal met the counting conditions that day, and the values changed afterwards. The budget timing moved back, approval progress went backwards, or the ball has not come back from the approver.
- Wrong first read: the deal missed with the values unchanged, or the values never met the counting conditions in the first place.
If most misses are buyer-side changes, work on catching buyer-side movement earlier. If most are wrong first reads, the counting rule is what needs fixing.
What changes when a deal misses
We cannot promise this makes the forecast accurate.
Whether a count built on budget timing and approval stage predicts better only shows after you compare forecasts with outcomes a few times.
What changes is the miss itself.
| Without the day-of basis | With the day-of basis | |
|---|---|---|
| The review after a miss | Question the rep’s judgment | Lay the day-of basis next to what changed |
| Sales action | Activity targets, manager ride-alongs | Find the approval stage where deals stall and act there |
| Headcount | Long cycles read as too few reps | Check how much of the time is buyer-side approval and budget waiting |
If most of the delay is on the buyer’s side, material for the approver and proposals timed before budget setting will do more than another hire.
Sort misses early.
In the 2025 benchmark by Ebsta and Pavilion (n=655,000 deals across 387 companies; non-Japan data), a deal that slipped one month won 13% of the time, and one that slipped three months won 8%. Deals that slip win less often.
A deal you keep carrying with “next month, for sure” is likely already weak, so sort it before you carry it again.
At each forecast meeting, save the approval progress, budget timing and next owner of every counted deal as they stood that day. For a miss, compare those values with today’s to separate a buyer-side change from a wrong first read.
Before your next forecast meeting, open three deals
Open three deals currently “in negotiation” and try to write two things for each:
- Who holds the ball now: your team, the buyer’s contact, or the buyer’s approver?
- Why is the deal counted this month, and as of what date was that information true?
Write “unknown” for anything the record cannot show.
Many unknowns mean the fields are missing, the entry has stopped, or no meeting uses the information. Ask whether the basis was kept before you ask about the rep.
The wider design of this loop is part of our Japan market GTM and messaging work.
Related reading
If your forecast counts deals on rep confidence rather than on how far the approval has climbed, start with Forecast your Japan pipeline on approval progress, not rep confidence. This note picks up from there: keeping the basis you counted on.
Other notes on the same problem are collected under Sales process.