Numbers don't speak for themselves. The way a figure is framed — what it's compared to, what conclusion it's meant to support, how uncertainty around it is acknowledged — determines whether it lands as evidence or noise.
For non-native English speakers presenting financial results, metrics, or business performance, the language conventions are specific and worth knowing. Getting them right makes the data more effective. Getting them wrong doesn't affect the underlying numbers, but it affects how they're received — and in high-stakes contexts, that matters.
Leading With the Meaning, Not the Number
The most common error when presenting data: giving the figure before the frame.
"Revenue in Q3 was 2.1 million."
Versus:
"Q3 revenue came in above target — 2.1 million, which is 18% ahead of plan."
Or on a miss:
"Revenue came in below target in Q3 — 2.1 million against a plan of 2.6 million. Here's what drove the shortfall."
The number is the same in all three cases. What differs is the interpretive frame the listener receives before the number. Without that frame, the listener has to supply their own context — and they may supply the wrong one. A board member who heard "2.1 million" without context might have expected 3 million and hear it as a miss; or expected 1.5 million and hear it as good news. The frame removes the ambiguity.
Lead with whether the result is positive, negative, or neutral relative to expectations. Then the number. Then the context that explains it.
The Language of Positive Results
Reporting strong results in English professional contexts has its own conventions. The goal is clarity and confidence — not excessive enthusiasm, which invites scepticism.
Effective:
- "We hit our target on [X]." — direct, clean
- "Revenue grew 34% year-on-year." — uses a benchmark comparison, immediately interpretable
- "[Metric] came in ahead of expectations." — modest, professional
- "We're tracking well on [X] — here's why."
- "Strong quarter: [key metric], [key metric], [key metric]." — headline summary before detail
Avoid:
- Excessive superlatives: "extraordinary results", "phenomenal growth", "record-breaking performance" — these invite scepticism and raise the question of whether the presenter is reliable
- Vague positives: "results were very positive across the board" without a number — tells the audience nothing specific and signals that the speaker is managing their reaction rather than reporting accurately
The Language of Negative Results
Negative results in English business communication are best reported directly, named early, with a brief explanation and a forward-looking response. The structure that works:
"We missed the revenue target this quarter by approximately 20%. The primary driver was [specific factor]. Here's what we're changing."
The order matters: miss, cause, response. Not cause, miss, response — which delays the news and builds anxiety. Not miss, response, cause — which skips the accountability step.
Common errors:
Burying the miss. Surrounding bad news with good news before naming it. "We had strong engagement metrics, customer satisfaction was up, the team executed well — revenue however was below plan." By the time the miss arrives, the audience is already braced for it from the hedging, which makes the news worse to receive, not better.
Over-explaining the cause. Two or three paragraphs on the circumstances before naming what you're doing about it. Extended explanation reads as defensiveness. Investors and boards need to hear the plan; the cause is context, not the story.
False precision. "Revenue was 17.3% below target due to a 4.2% deceleration in SMB combined with a 6.1% underperformance in new logo..." Granular attribution of a miss without a clear narrative or action plan reads as complexity without insight.
Describing Trends
Business communication in English uses a consistent vocabulary for trends. Using it correctly reads as competent; deviating from it without reason sounds off.
Growth:
- "growing steadily / growing strongly / accelerating"
- "up [X]% month-on-month / year-on-year / quarter-on-quarter"
- "tracking ahead of plan"
- "gaining momentum"
Decline:
- "declining / contracting / softening" — register varies: "softening" is gentle, "contracting" is harder
- "down [X]% from [comparison period]"
- "below plan / below target"
- "slowing" — for deceleration without absolute decline
Flat:
- "stable / holding steady / broadly flat"
- "within the expected range"
- "[Metric] is unchanged from [period]"
Reversal:
- "we've turned the corner on [X]"
- "[Metric] reversed in [period] — here's why we believe it's sustained"
- "after [difficult period], [metric] has returned to [X]"
Uncertainty and Projections
Forecasts require explicit framing of confidence. English business communication has conventions for this:
Committed forecast: "We're projecting [X] for Q4. That's based on [assumption]." — Names the forecast and the assumption together; signals you've thought about the basis.
Range with central case: "Our range for Q4 is [X] to [Y], with [midpoint] as our central case." — Appropriate for genuinely uncertain scenarios; signals analytical rigour.
Conditional forecast: "Our current expectation is [X], contingent on [specific variable resolving]." — Names the condition explicitly so the audience can track it.
Honest uncertainty: "We have limited visibility into Q2 at this point. Our best estimate is [X], but I wouldn't want you to plan around that number." — More credible than false precision on a genuinely uncertain figure.
What to avoid: hedging so heavily that the forecast is meaningless. "Results could potentially fall somewhere in the range of X to Y depending on various factors that are difficult to predict at this stage" tells the audience nothing and signals either analytical weakness or a reluctance to be held to anything.
Numbers in Spoken Communication
Spoken presentation of numbers has different conventions from written. The key differences:
Round numbers in conversation. "Approximately two million" is easier to process in a spoken update than "one million nine hundred and forty-seven thousand." Keep precision for written materials; round for spoken updates and then offer to go to the detail if needed.
Contextualize every significant number when you first use it. "Our customer acquisition cost is $47" means nothing without "against an average revenue per customer of $380 over the first year." Give the reference point before or immediately after the number.
Say the comparison explicitly. "Revenue was 2.1 million" requires the listener to remember the target. "Revenue was 2.1 million, against a target of 2.6 million" removes that cognitive burden.
Avoid strings of numbers without narrative. "Revenue 2.1M, gross margin 68%, CAC 47, LTV 380, churn 2.3%" is a data dump. A narrative version — "strong margins at 68%, healthy LTV/CAC at roughly 8x, and churn below target at 2.3%" — gives the audience the interpretation alongside the data.
Frequently Asked Questions
How do I handle it when I don't know a specific number I'm asked about?
"I don't have that figure in front of me — I want to give you the right number, not a guess. I'll send it to you today." Never estimate a number you're uncertain about in a high-stakes context. The cost of a wrong number is significantly higher than the cost of "I'll check."
How precise should numbers be in a board or investor presentation?
As precise as the data warrants — no more. Round numbers are often more honest than precise ones that carry false confidence. "Approximately 40%" is a better representation than "38.7%" if your data quality doesn't support that level of precision.
Should I use percentages or absolute numbers?
Usually both. "Revenue was down 20%" without an absolute number doesn't allow the audience to understand scale. "Revenue was 2.1 million, down 20% from last quarter" gives both the scale and the direction. In general, lead with whatever is more dramatic or relevant, then provide the other.
How do I talk about numbers in a second language without losing track of them?
Write the key numbers down in front of you before any presentation or call. Retrieving numbers from memory under pressure, in a second language, is significantly harder than reading them. There is no professional stigma in having a page of key metrics in front of you during a board meeting.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.