Your Japan team's conversion rates don't match HQ's? Start with the denominator

Your global dashboard says Japan’s lead-to-opportunity rate is far below every other region, and headquarters wants to know why the Japan team is underperforming. Before you accept that read, check the denominator.

When Japan’s conversion numbers won’t reconcile with HQ’s, the cause is rarely the CRM or the team.

The definitions drift in two places: what counts as a lead, and as of which date the numerator and denominator are counted. The second is easy to miss, and it often survives a definitions meeting.

The same “conversion rate” is a different division in each place

A conversion rate is a simple division: opportunities divided by leads. But that denominator, “lead,” often points to different objects in different places.

Marketing counts everyone who downloaded a whitepaper. Inside sales counts only the ones they reached by phone. The account executive counts only deals with a visible budget and decision-maker.

Run the same “conversion rate” over three different denominators and the numbers will never agree.

This is not a Japan-specific failure, but it compounds when a Japanese subsidiary inherits a lifecycle model built at a US headquarters.

Write each stage’s entry condition on one map

Draw the path from lead to closed deal as a single horizontal map, and write, in words, the entry condition for each stage.

• The stage marketing hands over. Fix an attribute condition and a behavior condition together. “High intent” gets judged differently by every person.
• The stage inside sales takes on. Write it as an observable behavior, so a new hire judges it the same way.
• The stage that becomes a registered opportunity. Use only conditions that can be confirmed at that moment. Budget, decision-maker, and timing are often not settled until well into the sales cycle, and in Japan the internal approval route takes longer still. Make them registration conditions and deals get registered late, so the pipeline HQ sees looks thinner than it is. Put them on later stage transitions instead.

Once this one page exists, marketing and the Japan sales team can answer “where is that deal right now” by looking at the same picture.

Written stage conditions also let you split the conversion rate.

Instead of one lead-to-opportunity number, track two: from the marketing handover to the inside sales stage, and from the inside sales stage to a registered opportunity. Once you see which step is leaking, you know which team needs to change.

Fix “as of when” to one method

Even with aligned definitions, the number moves again if people take the cutoff date differently. There are two common ways to count a “June conversion rate.”

By creation month (cohort). The denominator is leads created in June; the numerator is how many of those converted, even if they converted in July or later. Numerator and denominator are the same population, so the ratio is clean.

The catch is that recent months still have leads in progress, so their numbers keep rising after you report them.

By period. The numerator is opportunities created in June; the denominator is leads created in June. It is available at month-end and does not move afterward.

The catch is that the numerator includes conversions from leads created in May or earlier, so the two are different populations. A month that follows heavy lead acquisition will read high.

Neither is more correct. Period counting shows recent movement sooner; cohort counting is better for comparing campaigns. What matters is that Japan and HQ use the same one.

Before you measure, write in a single line “as of when, and which population,” and name the field each date comes from. In HubSpot, the date a record entered each lifecycle stage; in Salesforce, the lead’s converted date or the opportunity’s created date.

If HQ counts by period and Japan by cohort, the regional gap you are escalating may be a difference in arithmetic, not performance.

Cohort numbers that rise after you report them are handled with a close process, covered in Japan’s conversion rate changed after you reported it to HQ.

When a definition changes, mark the break

Definitions get revised, and every revision moves the conversion rate. Decide in advance what happens to the history.

If the old records hold the fields needed to recompute under the new definition, recompute. If they do not, leave them and annotate the report: “before this date, the old definition.”

Join the two periods into one unbroken line and the month the definition changed will look like a result of the Japan team’s work.

There is no public Japan conversion benchmark to anchor to

With no external yardstick, internal consistency is the only reliable standard you have.

Overseas there are large-scale benchmarks such as Ebsta and Pavilion’s “2024 B2B Sales Benchmarks” (n=4.2 million opportunities, non-Japanese companies).

For Japan, no public benchmark discloses the denominator and method behind lead-to-opportunity and opportunity-to-win rates. So a Japan subsidiary cannot look up whether “45%” is high or low for the market.

That makes it doubly important to align your own definitions and cutoff dates first, so you can at least compare Japan to itself over time. This is the foundation for measuring the full revenue path end to end, which is what Japan GTM built on Revenue Architecture depends on.

Before comparing conversion rates, align both the numerator and denominator, the unit of count and the cut-off date. Document any differences that remain.

Common mistakes

• Building the dashboard before agreeing on the definitions. Automate on a misaligned denominator and you produce a clean chart of the wrong number every day. Aligning one page comes first.
• Putting unknowns into the registration condition. Require confirmed budget, decision-maker, and timing to register a deal, and Japan’s conversion rate reads low and its pipeline reads thin.
• Comparing Japan to HQ without a shared cutoff. If the global model counts by period and the Japan team counts by cohort, the gap is in the method before it is in the market.

Related reading

After the denominator is aligned, the numbers still need a rule attached. Write the threshold before adding another dashboard covers that step.

Other notes on the same problem are collected under Revenue data.