AI agents that actually shipFintech with real marginsCustom software, not off-the-shelfResearch that reaches productionBacking people first, slides secondReal estate with a tech lensFairways over pitch decksSkin in the game — alwaysSignal over noiseBerlin-rooted. Worldwide reach.
André Beyer

Operating

Interim CTO Berlin

Sometimes a company doesn't need advice. It needs someone in the seat. I step in as interim CTO — selectively, with skin in the game, and only where I'd want to own the outcome.

When an interim CTO makes sense

There are a handful of situations where it does:

  • The technical co-founder has left, and the product, the team, and the roadmap have nobody who owns them.
  • A non-technical founding team has a product built by an agency or by freelancers and now needs to turn it into a company's technology.
  • The company is moving to AI-native products and the existing leadership has not built such systems before.
  • A funding round or due diligence is coming up and the technical story has to hold up under questions.
  • The team has grown past what the first technical lead can manage, and the search for a permanent CTO will take months.

What these have in common is that decisions are piling up and nobody has the mandate to make them. An advisor can tell you what they'd do. An interim CTO does it and is accountable for what happens next.

What I actually do

The first weeks are for finding out what is true. I read the code, look at the infrastructure and the bills, sit in on the team's meetings, and talk to every engineer one-on-one. I talk to customers if the company lets me. By the end I want to be able to say what works, what is fragile, and what the team already knows but hasn't said out loud.

Then I make the decisions that have been waiting. Which parts of the system get rebuilt and which are left alone. What gets cut from the roadmap. Who is in the wrong role. Where AI belongs in the product and where it doesn't — including how you'll know whether it works, which most teams skip.

After that it's operating: running the team, hiring, representing technology to the board and to investors, and being the counterweight a founding team needs when product, sales, and engineering pull in different directions. This is the day-to-day job, and I do it as a member of the leadership team, not as a visitor.

AI-native companies in particular

Most of the companies I talk to about this role are building with AI, or are being pushed to. That changes the CTO job in a few ways.

  • The architecture has a component that isn't deterministic. Testing, monitoring, and release processes have to account for that, and most inherited setups don't.
  • Costs scale with usage in a way classic software doesn't. Someone has to own the model bill and the unit economics behind it.
  • The team needs different skills than it did two years ago, and not every good engineer wants to make that move.
  • Vendors and models change every few months. The system has to be built so that a switch is a project, not a rewrite.

If testing is the open point in your company, I've written more about it under AI agent evaluation. If you're raising, agentic systems investing explains how I look at companies from the other side of the table.

Equity over fees

I prefer equity over fees. I'm invested in the outcome, not the invoice. That's a deliberate filter on both sides: I only take a seat in a company I'd want to own part of, and you get someone whose incentives match yours.

It also means this isn't a service you can book. There's no day-rate card and no bench of associates. If you need a few focused conversations about architecture or strategy, paid advisory is the better format — that's described on Work with me, together with the other ways I work with companies.

How long I stay

As long as the story needs me. Sometimes that's until a permanent CTO is hired and settled in, and part of my job is to help find that person and hand over properly. Sometimes the interim turns into a permanent role. I don't decide that up front, and I'd be suspicious of anyone who does.

What I do agree on at the start is what done looks like for the first phase: the state the team, the system, and the roadmap should be in, so that both of us can tell whether it's working.

Where it doesn't fit

  • You're looking for a senior engineer to write features. That's a hire, not an interim CTO.
  • You want a CTO title on the pitch deck without giving that person real authority.
  • The founders disagree about whether they want this role filled at all. Sort that out first.
  • I don't believe in the product or the market. If I wouldn't own the outcome, I don't take the seat.

And the chemistry has to be right. I only do this where the vision, the team, and the chemistry genuinely click. An interim CTO who doesn't get along with the CEO makes things worse faster than no CTO at all.

Why Berlin

I was born and raised in Berlin, and I've built and led tech companies here for a decade — as CTO, as CEO, and as an investor. My network is here: engineers, founders, investors, and the people you'd want to hire next. For an interim role that matters, because much of the work happens in the room, with the team.

I also work with companies outside Berlin. But being present is part of the job, and I'm honest about how much of that I can offer at a distance.

Also as interim CEO

The same applies to the CEO seat. I've held both roles, and in some companies the gap is on the business side. The principles don't change: skin in the game, real authority, and a mutual fit.

How to start

Write me a few lines about the company, the situation, and why now. No deck needed. If it sounds like a fit, we talk — and if it isn't, I'll say so quickly. No polite maybe.

The FAQ has a short answer on what interim CEO and CTO work looks like, alongside the other questions I get asked. The note form is on Work with me. And if you want to know who you'd be dealing with, the homepage is the place to start.

Related