How about when supporting both use cases? A multinational company might need the former for people making decisions across the whole company, and a country spec

How about when supporting both use cases? A multinational company might need the former for people making decisions across the whole company, and a country specific department doesn't need anything but what's relevant to that country. You could make two tools, but now you're duplicating implementation. Factor out a shared library/service/modularization-approach-de-jour? Good idea, but we're back to the question of how to structure things. You don't always get to enforce that "OR"