Hey, I'm Rico.

I coach startup CEOs and build tools for coaching agencies and developers.

Rico Trevisan

Coaching

I help startup CEOs build high-performing organizations.

I'm a coach at Mochary Method — the coaching framework used by top Silicon Valley CEOs. My approach comes from 12+ years of building software and leading teams: I treat organizational challenges like engineering problems.

Most founders I work with are going through the same transition — from building the product to building the company. They're great at shipping code but haven't yet designed the systems that let an organization scale: decision-making frameworks, feedback loops, accountability structures.

That's what I help with. Not abstract leadership advice, but concrete communication architecture. The operating system for your company.

From builder to leader

You built the product. Now you need to build the organization. I help founders make that transition without losing what made them effective.

Structured, systematic coaching

Identifying patterns, designing solutions, iterating on measurable outcomes. Concrete frameworks, not abstract advice.

Communication architecture

The bottleneck is rarely the code. I help you design the decision-making, feedback, and accountability systems that let your company scale.

$1,000–$5,000/month

Depending on company size and stage. 2–4 sessions per month plus async access via email, Slack, and text between sessions.

Projects

Things I've built.

If any of these have been useful to you, consider buying me a coffee.

About

I'm Belgian, based in Brussels. My father once brought home a smuggled i486sx computer. My brothers and I promptly took it apart to see how it worked. We fiddled and tweaked and taught ourselves everything we could.

That curiosity led me through IT support, Agile coaching, and a decade of helping teams ship products — until I started building the tools myself. Today I split my time between coaching startup CEOs through Mochary Method and writing software in Elixir. The biggest leverage I've found isn't in the code itself, but in the communication architecture around it.

Outside of work, I cook, bake bread, take photographs, and lift heavy things.