Why we report in your currency, not ours

It's a small operational detail that turns out to matter more than it sounds like it should. A client in Toronto shouldn't have to mentally convert INR figures every time they review a report, and an agency that defaults to its own home currency for every client, adjusting only when asked, is quietly making its own life easier at the client's expense.

Every proposal specifies the currency the engagement is priced and invoiced in before signing, whether that's USD, CAD, AUD, NZD, or GBP. This isn't just a courtesy; it removes an entire category of confusion from every later conversation about budget, and it means nobody has to do mental exchange-rate math to understand what they're actually paying.

Ad spend, cost per acquisition, revenue figures, anything with a dollar sign in a client report is denominated in that client's currency, pulled directly from ad platforms that already report in local currency when the account is set up correctly. We don't hand a Toronto client a report full of numbers they have to convert themselves before they mean anything.

For longer engagements, we agree upfront on how currency fluctuation is handled, whether the price is fixed in the client's currency regardless of rate movement, or reviewed at defined intervals. Settling this before it becomes a live issue avoids an awkward conversation later when a rate has moved meaningfully in either direction.

Our own internal accounting happens in INR, since that's the currency our costs are actually denominated in. That's an internal detail that shouldn't leak into how a client experiences the engagement, and keeping the two cleanly separated is just part of running an international studio properly, rather than something we expect a client to accommodate.

Beyond the obvious convenience, currency-matched reporting avoids a subtler problem: a client's own finance team reconciling marketing spend against results is much easier when the numbers in a report already match the currency in their accounting system, rather than requiring a manual conversion step every reporting cycle that introduces its own error risk.

For clients selling into several countries, we report each market's results in that market's currency alongside a consolidated view in the client's primary reporting currency, so a Canadian dollar figure isn't silently blended into an unlabeled aggregate that obscures market-level performance.

Early in the studio's history we sometimes defaulted to INR reporting out of habit and adjusted only when a client specifically asked. Making currency-matched reporting the automatic default, rather than an opt-in request, was a small internal process change that removed an entire category of friction from client relationships.

Currency reporting is a small thing on its own, but it's representative of a broader principle: operational details that are trivial for us to get right and genuinely helpful for the client should default to the client's convenience, not ours, even when nobody would necessarily notice or complain if we didn't bother.

For a client with, say, a US-based CEO and a Canadian CFO, we've had to decide on a single primary reporting currency for the official report while providing the same figures converted into a second currency as a supplementary reference, so neither stakeholder has to do their own mental math to make sense of the numbers.

USD might feel like a safe universal default, but it's not actually neutral, it just shifts the conversion burden onto every non-US client instead of onto us. We'd rather do the small extra work of matching each client's actual currency than default to whichever currency happens to be most convenient for the broadest audience in the abstract.

A Melbourne-based client once told us directly that a previous agency's habit of reporting ad spend in USD, despite the client being invoiced in AUD, had created a running, low-grade confusion that took months to even notice as a pattern rather than isolated one-off mistakes. Nobody on either side had deliberately decided to cause this confusion, it was simply the default the agency's reporting tools shipped with, left unchanged.

That client specifically cited our currency-matched reporting, unprompted, as one of the concrete reasons they switched agencies, which reinforced for us that this kind of operational detail, while genuinely small in isolation, accumulates into a real, felt difference in how professional and attentive an international engagement feels to the client actually living with the reports every month.

We also apply this same underlying principle, defaulting to the client's convenience rather than our own, to smaller operational choices beyond just currency: meeting times scheduled in the client's working hours by default, documents formatted using the client's regional date and number conventions rather than ours, and support responses written in the specific English variant, US or British spelling and phrasing, the client's own team actually uses day to day in their own communication.

Even with an invoice denominated correctly in the client's currency, some banks apply their own conversion or handling fees on international wire transfers that have nothing to do with our pricing at all. We flag this possibility upfront during contracting, and we're happy to help a client's finance team find a lower-fee payment route when one exists, since an unexpected bank fee showing up on an otherwise clean invoice creates exactly the kind of confusion currency-matched reporting is meant to avoid in the first place.

Occasionally a client's local currency is prone to sharp swings against major currencies, and pegging an entire engagement's price to it introduces real financial risk for both sides over a multi-month project. We're upfront in these cases about recommending a more stable invoicing currency for the contract itself, while still reporting day-to-day performance metrics in whatever currency is most useful for the client's own internal review, keeping the stability concern and the reporting convenience concern cleanly separated rather than solving both with the same single decision.

This distinction has occasionally surprised clients who assumed invoicing currency and reporting currency had to be the same thing by default. Once we walk through the reasoning, most clients agree it's a sensible way to protect both sides from currency risk neither of us actually wants to bear, while still keeping the reporting experience as clear and locally relevant as it would otherwise be.