Why Japan's "3% SaaS churn" benchmark misleads your HQ (read the median)

Published Jul 24, 2026

If you are setting a churn target for your Japan operation from a benchmark that says “Japanese SaaS churns at about 3% a month,” you are likely setting it against the wrong number.

That 3% is a mean, and it is pulled up by a small number of high-churn companies.

The median company in the same dataset sits near 1%. Read the mean as the market, and your Japan team looks like it is failing when it is roughly at par.

The number that circulates

The figure comes from CloudCircus’s Fullstar “Customer Success Survey 2025” (fielded August 2025, n=200, customer success and support staff at B2B information and communications companies in Japan; note that this is a vendor survey). The headline is a mean monthly churn of 3.01%.

But the same survey publishes the distribution, and it is heavily skewed: 45% of companies report 1% or lower, while about 9% report 10% or higher.

Those few high-churn companies drag the average up.

The median lands in the 1% range, more than double away from the 3.01% mean.

So “Japan churns at 3%” describes almost none of the companies in the data. It describes the gap between the typical company and a handful of struggling ones.

Why this matters when you report to HQ

Two failures follow from using the mean as if it were typical.

First, you set the wrong target.

If HQ benchmarks your Japan team against a 3% “market rate,” a team performing at the 1% median looks mediocre, and a team genuinely at 3% looks acceptable when it is actually in the worst tier.

The averaged number hides both the good and the bad.

Second, you lose HQ’s trust in the whole report.

The moment a headline number stops matching what people see on the ground, they stop trusting the dashboard it came from.

After that, even your accurate numbers get discounted in decisions.

A dashboard exists to surface what needs intervention, not to produce a tidy single figure; a distrusted figure cannot do that job.

What to report instead

Report the median and the spread, not the mean alone. “Median monthly churn 1.0%; top decile above 8%” tells HQ both where the typical account sits and where the risk is concentrated.
Show the outliers as a separate list, not blended in. The high-churn accounts are exactly what your customer success team should act on. Averaging them into one number hides the intervention target.
Name the source, year, and sample every time. When you cite the Japan benchmark, say “Fullstar 2025, n=200, vendor survey.” HQ can weigh a vendor survey of 200 companies appropriately, and a sourced number survives scrutiny that an unsourced one does not.
Do not compare Japan and home-market retention as if the numbers are equivalent. US benchmarks such as Benchmarkit 2025 report a median net revenue retention around 101%, and Japan’s Fullstar reports a mean NRR of 102.1%, but the samples, methods, and mean-versus-median basis all differ. They look close; they are not directly comparable. Present each with its own definition and let HQ draw the line.

When a distribution is skewed, report the median, not the mean. A single averaged number, misread across a market, sets the wrong target for the whole Japan operation.

Common mistakes

Treating every metric as skewed. Symmetric metrics are fine to average. Churn, deal size, and stage duration are the ones that reliably skew; check the distribution per metric.
Reporting the median but hiding the distribution. The median is a representative value, not a tool for making the high-churn accounts disappear.
Trusting the dashboard’s default. Most tools aggregate with a mean by default. For skewed metrics, do not ship that default to HQ.

Reading the median is the first half; attaching a decision rule to it is the second. See write the threshold before adding another dashboard.

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