How do ecosystem grant budgets get spent in Latin America?

Most regional grant budgets are approved annually and spent late, on whatever is available in the final quarter. Money and intent are there. What is missing is someone on the ground to convert an approved budget into scheduled activity across a region that behaves as twenty separate markets.

Why an approved budget is not the same as a programme

A foundation approves a regional allocation in January. By March there is no calendar, because building one requires knowing which events are real in each country, which communities actually convene builders, and which universities will engage. By September the budget is unspent and visible. By November it goes to whatever is bookable at short notice.

The result is a familiar pattern: a logo on a banner at an event nobody in the region considers important, and no measurable activity afterwards. The money was not wasted through negligence. It was spent under time pressure with no local information.

The structural cause is that regional grant work is a scheduling and relationships problem disguised as a funding problem. It needs someone who knows, in each market, who convenes people and when.

What actually converts budget into activity

A named counterpart per market. Not a regional agency, a person or organisation in each country who already convenes the audience you want. The region does not have a single builder community; it has many, weakly connected.

A calendar built backwards from the events that already exist. Creating an event from nothing is expensive and slow. Attaching to something with an audience is cheaper and faster, and the first year of a regional programme should lean heavily on what already exists.

A definition of success written before the spend. "Builders engaged" is not measurable. "Forty developers who had never deployed on our chain deployed something, and twelve of them deployed again within ninety days" is.

Follow-up capacity. The gap between a hackathon and a live project is entirely follow-up, and it is the line item that gets cut first because it produces no photographs.

Where regional grant spend tends to evaporate

That last row is uncomfortable and worth saying plainly: a grant process run only in English selects for English fluency, not for engineering quality. In a region where much of the strongest technical talent works primarily in Spanish or Portuguese, that is an expensive filter to apply by accident.

How to structure the year so the budget lands

1. Spend the first quarter on mapping, not activity. Who convenes builders in each of your three or four target markets? What already exists on the calendar? 2. Commit to a small number of markets. A budget spread across eight countries produces eight token presences. The same budget across three produces three real ones. 3. Attach to existing events for the first cycle. Build your own only once you know what draws the audience. 4. Fund the follow-up explicitly, as a named line item, before it is competing with something more photogenic. 5. Report quarterly against the definition written in step zero, not against spend.

What a working programme looks like from the inside

The description above is the shape. This is what the year looks like when it works, because the difference is almost entirely in the routine rather than in the plan.

There is a standing call per market with the local counterpart, short and frequent, where the agenda is what is happening in the next six weeks. Not a quarterly review. Regional calendars move, and a programme that reviews quarterly finds out about a change after the date has passed.

There is one owner for follow-up who is not the person who ran the event. The people who deliver a hackathon are exhausted afterwards and are already booked on the next thing; asking them to also convert forty developers over the following ninety days is how follow-up quietly stops existing. It is a separate role, and naming it is most of the work.

There is a written record of what each market actually produced, in developer behaviour, kept in one place across the year. Foundations run these programmes with people who rotate, and institutional memory that lives in one person's inbox is lost at the first handover. The knowledge that Bogotá converts and São Paulo does not is worth more than the budget line it came from.

And there is a decision, made explicitly at the mid-point, about which markets get the second half of the budget. A programme that allocates evenly in January and refuses to reallocate in June is spending on the plan rather than on the evidence.

What this guide does not cover

It does not name specific events, communities or conveners, which change year to year and would be stale before this page is a season old. It does not cover grant programme legal structuring, which varies by foundation domicile. And it does not give benchmark figures for cost per developer engaged, because we have not seen a dataset across the region we would stand behind.

Frequently asked questions

Why do regional grant budgets underperform in Latin America?

Usually because approval and execution are separated. The budget is approved centrally and there is nobody on the ground to convert it into a scheduled calendar across markets that behave very differently. The money then gets spent late, under time pressure, on whatever is still bookable.

Is it better to sponsor an existing event or create one?

For a first cycle, attach to what exists. Creating an event from nothing carries the full cost of building an audience, and first-year attendance is usually disappointing. Once you know which audiences convert, building your own becomes a reasonable second-year decision rather than a first-year gamble.

How should a foundation measure a regional programme?

Against a definition written before the spend, in terms of developer behaviour rather than activity volume. "Forty developers deployed for the first time and twelve deployed again within ninety days" is measurable and tells you something. "Builders engaged" and "impressions" do not survive contact with a board question.

How many markets should a first-year regional programme cover?

Three at most, and two is defensible. The region behaves as separate markets. Brazil alone moved more than three times Argentina's on-chain volume between mid-2022 and mid-2025, so a budget spread across eight countries buys eight token presences. Concentrating it buys relationships that are still there in year two.

Should grants be reviewed in English?

Not exclusively. A process run only in English selects for English fluency rather than engineering quality, and much of the region's strongest technical talent works primarily in Spanish or Portuguese. Adding local reviewers changes which applications survive, which is the point.

What is the first thing to fix in a programme that underdelivered?

Find out who owned follow-up, and whether it was the same people who ran the events. In almost every underperforming programme we have seen, follow-up was nobody's job in particular and was absorbed by people already committed elsewhere. Naming a separate owner, with time allocated, changes the outcome more than increasing the budget does.

Related guides

• The LATAM crypto conference calendar, and which ones matter
• LATAM crypto adoption by country: the numbers, with sources
• Where LATAM developers actually are, and what they cost