Why I invested in Kapso
WhatsApp is the OS of LatAm. Building on top of it as a developer is still painful enough to ruin a weekend. Kapso is the infrastructure layer that fixes that — the way Stripe is for payments and Twilio is (sort of) for SMS, but actually built for the agent + vibe-coder cycle we’re in now.
Why I backed it
Andrés. I’ve been helping him with intros to VCs and angels and advising for a while now, and what he’s built as a solo founder is genuinely impressive — 4,000+ developers organic, full multi-tenant platform, observability, flows, the works. His AI-first bias is the right one for this moment, his founder style is the kind I want to keep working with for a decade, and the references I have from mutual friends are unanimous. I offered him a small angel check.
The vibe-coding stack tailwind. Lovable, Claude, Codex, Cursor — these are becoming the default way internal software gets built across LatAm. Every internal tool that gets vibe-coded into existence eventually wants to talk to a customer, and in this region that means WhatsApp. Kapso is positioned to be the native, drop-in infrastructure layer for every one of those apps. The buyer here is the developer, not the IT director — and the developer is increasingly an AI.
Personal autonomous agents in WhatsApp-first markets. In regions where WhatsApp is the economy’s OS — most of LatAm, India, much of Southeast Asia — autonomous agents (Claude Code, Open Claude, the next generation of personal agents) need an integration layer to act on a user’s behalf inside WhatsApp. Kapso is the obvious place that layer should live. There’s no incumbent here yet.
Tracked the space since Agentmail. I tried to get into Agentmail’s YC round and couldn’t — close-but-no-cigar. The fact that Kapso is the next move in roughly the same vector, with a founder I already know and a region I understand better than email, made the bet much easier the second time around.
The bet
Two stacking tailwinds — vibe-coded apps + WhatsApp-first agent users — both routing through the same infrastructure problem, both addressed by the same product, in regions where the buyer is technical and willing to pay. If Kapso becomes the default import * from kapso for any app that needs a WhatsApp surface, the company prints. Andrés has 4k organic devs already with no marketing engine; the wedge is sharp.