.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
How to Calculate International Market Performance a Guide for SaaS Executives
A country can post 25% revenue growth and still be a poor place to invest. Foreign exchange may account for part of the gain. Expansion from one global account may account for the rest. The local sales team may be spending twice as much to acquire each new dollar of ARR as the company spends at home.
This problem is becoming more urgent as SaaS companies move beyond opportunistic international demand. A few overseas customers do not create a market. A market exists when a defined buyer segment can be acquired, retained, expanded, and served at a repeatable return. Executives need a way to separate those conditions from currency movements, global-account allocations, and regional reporting labels.
Monetizely's position is clear: international market performance should be calculated in local currency, by customer cohort, and against direct local costs. Reported USD revenue is necessary for financial statements, but it is not the primary measure for deciding where to put the next dollar of growth capital.
Revenue labels often obscure where customer value was actually created
Public SaaS disclosures show why regional revenue is an unreliable proxy for market performance. Companies can use different rules to assign the same customer revenue to a geography. Salesforce, for example, reports geography based on the location of its contracting entity, which it notes may differ from the customer’s location. Bentley Systems attributes revenue to the customer’s location. Both choices can be valid for financial reporting. Neither should be accepted without question in a market-investment review.
The difference matters most for global accounts. A U.S.-headquartered manufacturer may sign a global contract through a U.S. entity, while 600 users sit in Germany, Japan, and Brazil. Booking all revenue to the Americas may be clean for accounting. It says little about whether Germany or Japan can support a local sales motion.
The implication is straightforward: before calculating performance, define the market. For most B2B SaaS companies, the best rule is the location of the economic buyer and the operating team receiving the primary value. Global contracts should sit in a separate global-account ledger until revenue can be assigned using a consistent rule, such as active users, business-unit budget ownership, or contracted deployment.
A regional label such as “EMEA” is too broad for capital allocation. France, Germany, the United Arab Emirates, and South Africa differ in language, procurement, buying power, channel structure, data requirements, and sales cost. A region may be useful for executive oversight. A country or tightly defined subregion is the unit that should earn the next local hire.
Local-currency cohorts separate demand from exchange-rate noise
The central calculation starts with a local-currency ARR bridge. Keep each country’s operating ledger in the currency in which customers are priced and sales teams are paid. Translate it into USD only after the underlying business calculation is complete.
[ \text{Ending ARR} = \text{Beginning ARR} + \text{New ARR} + \text{Expansion ARR} - \text{Contraction ARR} - \text{Churned ARR} ]
The formula looks familiar. Its discipline comes from applying it to a defined market, in native currency, with a stable account-location rule. New ARR should include only customers that were not in the starting cohort. Expansion and contraction should reflect changes within existing accounts. Churn should include both full cancellations and customers that fall to zero recurring revenue.
For group reporting, finance should translate income-statement figures at a consistent historical average exchange rate and ARR balances at a consistent period-end rate. For market management, however, the primary growth rate should be the local-currency rate. Oracle’s fiscal 2026 results show why: EMEA revenue growth was six percentage points higher as reported than on a constant-currency basis.
A country leader should therefore present two numbers every quarter:
- Local-currency ARR growth, which measures customer demand, price realization, retention, and expansion.
- Reported-currency ARR growth, which reconciles the country’s results to the corporate financial statements.
Only the first number should determine whether a market is gaining commercial traction.
A second calculation protects the analysis from a common distortion: a country can grow quickly because a few large customers bought more, even if the company is failing to retain the broader base.
[ \text{Net Revenue Retention} = \frac{\text{Beginning ARR} + \text{Expansion} - \text{Contraction} - \text{Churn}}{\text{Beginning ARR}} ]
[ \text{Gross Revenue Retention} = \frac{\text{Beginning ARR} - \text{Contraction} - \text{Churn}}{\text{Beginning ARR}} ]
Net revenue retention answers whether the starting cohort is worth more or less one year later. Gross revenue retention reveals whether expansion is masking a churn problem. Both measures should be calculated by country and by segment, not only at the regional total.
Four gates prevent fast growth from becoming expensive false progress
Growth, retention, acquisition efficiency, and local contribution should be treated as gates rather than blended into one weighted score. A weighted average lets a market compensate for poor retention with a large one-time deal, or compensate for weak economics with a favorable currency movement. Neither condition deserves more investment.
The following scorecard gives executives a practical operating view.
The table means that a country should not be called successful because it has a favorable top-line growth rate alone.
Consider a €10 million starting ARR base. During the year, the market adds €3.0 million of new ARR and €1.4 million of expansion ARR, while losing €0.4 million to contraction and €0.8 million to churn. Ending ARR reaches €13.2 million, or 32% local-currency growth. Net revenue retention is 102%, while gross revenue retention is 88%.
| Exhibit 3: The same country can look attractive or fragile depending on the calculation | Amount or result |
|---|---|
| Beginning ARR | €10.0M |
| New ARR | €3.0M |
| Expansion ARR | €1.4M |
| Contraction ARR | (€0.4M) |
| Churned ARR | (€0.8M) |
| Ending ARR | €13.2M |
| Local-currency ARR growth | 32% |
| Gross revenue retention | 88% |
| Net revenue retention | 102% |
| Local acquisition spend | €2.1M |
| Gross margin on new ARR | 80% |
| CAC payback | 10.5 months |
The result is a market that deserves attention, but not automatic expansion: new-customer acquisition looks efficient, while 88% gross retention points to a renewal or product-fit problem that expansion is partly concealing.
If the euro weakened 8% against the dollar over the same period, the USD-reported ARR increase would look closer to 21% than 32%. Neither number is wrong. One describes corporate reporting; the other describes market performance.
International performance cannot be separated from pricing. A market may show strong pipeline volume because the company has priced too low for local enterprise buyers. It may show weak conversion because a U.S. package includes features that local mid-market buyers neither need nor understand.
Monetizely's 5-Step Pricing Framework provides the required sequence. As set out in Monetizing Agentic AI, the work begins with business goals and customer segments; then moves to packages that fit those segments; selects the metric customers will be charged on; sets price points; and finally operationalizes the model through product, billing, sales, and finance systems. The sequence matters because a price change made before the company understands the local buyer, package fit, and billing capability usually creates more noise than learning.
International market performance should follow the same logic.
| Exhibit 4: The five pricing decisions define what a country scorecard must measure | Pricing decision | International performance question |
|---|---|---|
| Goals and segmentation | Which buyer segment is the country expected to win, and is the goal penetration, margin, or enterprise expansion? | |
| Packaging | Which package is selling, which features drive upgrades, and where does shelfware appear? | |
| Pricing metric | Does the meter match how local buyers receive value and how they budget for software? | |
| Price points | What is local price realization after discounts, currency conversion, and partner margin? | |
| Operationalization | Can CRM, billing, finance, and customer success assign revenue, usage, renewals, and cost to the same market? |
The table means that an international dashboard should diagnose the economics behind performance, not merely rank countries by revenue.
HubSpot’s 2025 disclosure offers a useful reminder. Customers outside the United States represented roughly 53% of its customer base but generated 48% of revenue. That gap may reflect customer size, product mix, discounting, usage, or regional price levels. An executive team cannot know which explanation applies without segment-level data.
The most useful country pricing measures are therefore:
- Local average contract value by customer segment and package.
- Discount rate relative to the local list price, not the U.S. list price.
- Expansion ARR by package, feature, and pricing metric.
- Gross margin by customer segment after cloud, support, payment, and partner costs.
- Win rate and sales-cycle length by package and buyer type.
A German enterprise package may need stronger governance, local-language enablement, and a different implementation offer than a U.S. mid-market package. That does not mean Germany needs a separate product strategy. It means the company must prove that the local offer produces stronger retention and contribution than a remotely served alternative.
Strong international operators do not review markets through presentation slides built from different systems. They maintain one country ledger with linked account, product, billing, and cost data.
The ledger should record every account’s market assignment, parent account, contract currency, local price list, package, pricing metric, renewal date, ARR movement, sales source, partner involvement, delivery cost, and customer-success cost. Finance owns the translation rules. Revenue operations owns account assignment and pipeline definitions. Product and billing teams own the link between package entitlements, usage, and invoices.
Several errors regularly undermine this work:
- Treating a region such as APAC as a single market despite large differences in buyer behavior and cost.
- Assigning a global contract to the country that signs the paperwork rather than to the buyers who use and fund the product.
- Calculating local revenue at constant currency while leaving sales and customer-success costs at spot exchange rates.
- Counting expansion from existing customers as evidence that new-customer acquisition is working.
- Charging a country with arbitrary corporate overhead before testing whether the local go-to-market motion covers its direct costs.
Bentley’s June 2026 disclosure is a useful benchmark for the level of discipline required. The company reported both actual and constant-currency growth by region, attributed revenue to customer location, and separately described revenue from existing accounts and new accounts. SaaS executives do not need public-company reporting complexity on day one. They do need the same separation between location, currency, customer expansion, and new demand.
A new market rarely begins with a fully loaded local team. Early results should earn additional investment in stages. The first stage can be served remotely, with localized demand testing and a small number of target accounts. The second stage can add local sales coverage after the company sees repeatable conversion and acceptable payback. The third stage can add customer success, partner capacity, or local implementation resources when retention and expansion show that the market can support them.
Monetizely's position is that USD revenue should be a reconciliation line, not a country’s report card. The primary report card should show local-currency ARR growth, cohort retention, acquisition payback, and revenue after direct local costs. A country that misses one of these measures should receive a diagnosis, not a larger budget.
Executives should make five changes before the next planning cycle:
Create a market taxonomy that separates countries, subregions, and global accounts. Make one executive accountable for enforcing the account-assignment rule across CRM, billing, and finance.
Classify every market as scale, build, serve remotely, or exit. Tie each classification to a capital envelope and a specific review date rather than allowing every country to request headcount through the annual budget process.
Set a local-currency hurdle rate for additional investment. Require country leaders to show the expected effect of each new sales or customer-success hire on new ARR, payback, retention, and direct local contribution.
Create a separate global-account review. Global contracts should be judged on total account economics and deployment depth, then allocated to countries only when the allocation improves local operating decisions.
Run quarterly reallocation meetings with finance, sales, product, and customer success in the room. Move resources from markets that cannot clear the four gates to those that can, even when the slower market has a louder internal sponsor.
Footnotes
- Monetizing Agentic AI: https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
- Salesforce, Form 10-K for the fiscal year ended January 31, 2026. (sec.gov)
- HubSpot, Form 10-K and fourth-quarter results for the year ended December 31, 2025. (sec.gov)
- Oracle, Form 10-K for the fiscal year ended May 31, 2026. (sec.gov)
- Bentley Systems, Form 10-Q for the six months ended June 30, 2026. (sec.gov)