About

The person behind the plumbing

Co-founder · revenue systems & agentic interfaces · based in Portugal

I run revenue and ecosystem at Playbook — the agentic-first media backend, 2.5M+ users — and I write the code for both. Two jobs, one person: the money and the machines.

The money: making sure what a company brings in is real, predictable and built to scale, and that the systems underneath hold when everything else shakes. Financial analytics and strategy, payments end to end, dunning, trials and discounts, churn — and getting money reported to match money collected. That last one is where the real work is: the layer under the dashboard, where the number everyone trusts turns out to have a defect behind it.

The machines: making Playbook usable by agents, not just people. Agents generate the media; Playbook stores it, versions it, gets a human to approve it, and serves it. I design the programmatic and agentic interfaces and the observability that shows what agents actually do. Not whether the tool responded, but whether the agent got its job done.

Before Playbook: a CS background, my own travel-tech startup (a Booking Booster Labs 2018 finalist), five years as an engineering manager at Evil Martians shipping with eBay, Tines, HTTPie and LOEWE; YC Startup School 2018.

I'm not a visionary founder, and I've made peace with that — what I'm actually good at is taking something that works, just barely, and making it scale.

Advisory

I advise growth-stage startups, sparingly, on two things I've actually done. The layer under the dashboard — billing, reconciliation, the numbers the board sees; if yours don't agree with each other, that's the conversation. And making a product usable by agents — API/MCP design and observability of what agents actually do with it, so it does the job, not just returns 200.

Write to hello@.

Why write

Because this layer is under-documented. The people who do it well rarely write it down, and the people who write about revenue usually aren't the ones holding the wrench. These notes are my attempt to close that gap — field notes from the systems that scale and survive.

If you're wrestling with revenue ops, billing migrations, or numbers you no longer trust, say hello.