Blog

The market that doesn't exist in the vendor's CRM

You noticed the Brazilian operation of a multinational in your industry runs an enterprise planning platform. The tool clearly works, clearly exists in the country, and clearly solves the problem you have.

You reach out to the vendor. And nothing happens.

It isn't a refusal — it would be easier if it were. It's a form answered by someone in a different time zone, a contact that gets handed to a regional team that gets handed to another one, a proposal that doesn't come, a technical question that goes unanswered. The conversation doesn't heat up on either side.

The natural reading is that your company is too small for the vendor. Almost always it isn't that.

The installed base is misleading

Look at who runs enterprise planning platforms in Latin America and you'll find big names. The obvious conclusion is that the market is served.

Except most of those installations weren't bought here. They're subsidiaries of multinationals: the licence came inside the global contract, the rollout came bundled with a corporate programme decided elsewhere, and support comes through the global account. Nobody in Brazil had to find a salesperson, homologate a foreign vendor, or justify a foreign remittance.

Headquarters bought. The local operation received.

That means the reference you're looking at — the company in your industry, your size, in your country, using the tool — got there through a path that doesn't exist for anyone without a foreign headquarters.

Why nobody answers you

Here's the mechanism, and there's nothing conspiratorial about it.

Regional revenue reaches the vendor either way, through global contracts. Subsidiaries add to the account without anyone needing to sell anything locally. From the vendor's perspective, the region shows up in the numbers as served.

If revenue arrives without a channel, there's no incentive to build a channel. Without a channel, there's no sales team accountable for the country, no pre-sales to run a proof of concept, and the reseller that formally covers the region often doesn't really operate in it.

And without a channel, the locally-owned company stays outside — which keeps local revenue at zero, which confirms it isn't worth building a channel.

The loop closes on its own. Nobody had to make a bad decision for it to exist.

The segment that doesn't show up in any statistic

The most uncomfortable part: the piece that really isn't served — the large, locally-owned company without a foreign parent — doesn't show up anywhere.

Not in the vendor's CRM, because it never became an opportunity. Not in the market report, because market reports count what was sold. Not in the regional team's conversation, because the regional team is evaluated on the accounts it already has.

A market that was never approached doesn't turn into pent-up demand in the numbers. It turns into absence — and absence looks a lot like "there's no market here".

This probably isn't a Latin America problem

Here I have to be honest about what I know and what I'm inferring.

Latin America is where we have direct experience with this. What I described above is what we see happen, repeatedly.

But notice the mechanism doesn't depend on anything specific to the region. It depends on a single ratio: how much revenue arrives via global contracts compared to how much would require local sales effort. Where that ratio is high, the channel doesn't justify itself, and the local market stays out.

By that logic, the same pattern should show up wherever multinational presence arrived before the vendor's commercial operation — Southeast Asia, much of Africa, parts of Eastern Europe and the Middle East. It's not a claim about those markets: it's what the mechanism predicts. If you operate in one of them and recognise the description, it probably isn't a coincidence.

What is safe to say is the opposite: where the vendor has a real local commercial operation, this problem doesn't exist.

The IBM Planning Analytics case in Brazil illustrates the contrast well. IBM has had a local operation for decades — it sells, invoices, and supports here. Buying a Planning Analytics licence in Brazil simply isn't a problem, and we've never seen a case where it was. The tool isn't cheaper or simpler than the others; it's reachable, because there are people on the other side.

The difference, then, isn't market maturity or buyer size. It's vendor presence — and it's why that should weigh in the choice as much as any line in the functional matrix.

What buyers can do

None of this is fate. But it means treating access as part of the project, not as a given.

Find the name. Before investing in functional evaluation, find out who — with a name, a team, a time zone — is accountable for your country on the vendor's side. If there is no name, there is no channel, and that's the most important piece of information you'll get in the whole process.

Come in through the partner, not the front door. Whoever implements the tool often has more access to the vendor than you'll have as a cold prospect, and can register the opportunity somewhere it has an owner. It's the shortest path in most cases.

Ask about deal registration and the partner programme. If there's a formal mechanism, your conversation has an owner. If there isn't, you've just learned something important.

Treat availability as a functional requirement. A tool 15% better on the evaluation matrix and unreachable in practice is worth zero. Worth less than zero, actually, because it consumed months of selection.

Consider who has local presence. Sometimes the right answer is the platform that came second in the evaluation and has people here — selling, implementing, supporting. It isn't lowering the bar; it's recognising that support, response time, and continuity are criteria too.

Buying is only the first obstacle

Once you've found a path to buy, three things still determine whether the tool is usable here — and all three tend to be discovered after signing.

Support in your time zone and language. An incident during your close, answered on the next business day from another continent, is an unavailable tool, whatever the contract says. Read the SLA against the clock of your close, not against the number of hours promised.

What's local and the tool doesn't cover. This isn't interface translation: it's payroll with statutory charges, 13th salary, holidays, provisions, collective agreements; Brazilian taxation, on top of that in transition; statutory chart of accounts and fiscal calendar. A global tool models the generic very well — the specific is always yours to build. And here your situation is worse than the subsidiary's: it can live with the global model plus a few local tweaks, because the corporate model is what governs. For you, the local requirement is the requirement.

Who implements and sustains. Being sold in a market doesn't mean there are people able to implement, sustain, and — above all — be hired by you later. A market with three certified professionals is a market where your project depends on the schedule of three people, and where losing someone from your internal team becomes an existential risk to the model. That's the question almost nobody asks in selection, and the one that most determines whether the model will be alive three years from now.

If you're a subsidiary, none of this is your problem

You have a path to buy — the global contract. Your difficulty is different: figuring out what that contract actually covers in your country, because it rarely covers everything the scope assumes.

And, unintentionally, you're the reference that confuses the market: it's your operation everyone looks at to conclude the tool is available around here.


We're a planning consultancy with a team in Brazil and expertise in Anaplan and IBM Planning Analytics, and we operate on both sides of this line — with subsidiaries inside global programmes and with locally-owned companies trying to reach the same tools. Get in touch if you're trying to access a platform that looks available on the market and isn't available to you.

← All articles