ciao, hello, hallo

I'm Alex, currently CTO at reev. I started in R&D — now I run AI strategy for every department, helping teams scale output without growing headcount.

I've scaled engineering teams at Limehome and Conichi (acquired by HRS), and shipped products at Blinkist, ProSieben, and Joyn.

For engineers and leaders dealing with AI adoption, I run Talon — a packaged quarterly report.

I write about scaling teams, AI adoption, and engineering leadership here, and I post regular thoughts on LinkedIn.

Book a free 20-min call

how i help

Advice from someone who's scaled it before

What started as an R&D problem turned out to be a company-wide one. Most departments were built to run a process, not redesign it — that's the real reason some companies get value from AI and others don't.

The work falls between the people who own the process and the engineers who own the systems. In my current role, we built a two-person team for exactly this: each department has an AI champion who spots the pointless steps, and when they hit something they can't build themselves, we turn it into a working solution.

That technical depth is what makes the redesign work, not just theory. I get close enough to the work to see where the process breaks, then rebuild the system underneath it.

The goal isn't another dashboard nobody opens. It's a workflow that keeps running the same way whether or not I'm still in the room.

guides

  1. 01 How do I fix my AI-generated codebase? →
  2. 02 When should I hire my first engineer? →
  3. 03 Do you need someone to lead AI strategy? →
  4. 04 What do VCs look for in technical due diligence? →
  5. 05 How do I scale from 5 to 50 engineers? →
  6. 06 How do I know if AI is actually working? →

faq

What does an engagement look like?

Engagements start with a diagnostic phase to understand your current state, team dynamics, and goals. From there, we co-create a roadmap covering priorities like workflow redesign, hiring plans, or technical debt. I work async with your team and join 1-2 calls per week for alignment and unblocking.

Can you help if we built our MVP with AI tools?

Yes. Many founders ship v1 with Lovable or Claude, then hit walls on architecture, testing, or scaling. I help you assess what's worth keeping, what needs rewriting, and how to structure the codebase for the next phase.

We already bought AI tools. Why aren't we seeing results?

Because buying tools isn't the same as redesigning work. Process owners defend the process. Engineers optimize the systems they own. Redesign falls between the two, and most companies never assign it to anyone. I sit with a team, find the steps that only exist because they've always existed, cut them, then rebuild what's left around the new tools.

How long do engagements typically last?

Most engagements run 3-6 months, enough time to implement lasting changes and build internal capability. Some clients continue with lighter advisory relationships afterward. The goal is always to make myself unnecessary.

What types of companies do you work with?

I started with engineering teams. Today the same approach runs across finance, ops, and support, wherever a department has AI tools but no one owning the redesign. I also support VCs and PE firms with technical due diligence.

How does pricing work?

I offer monthly retainers based on time commitment and scope. Rates reflect the senior leadership experience I bring. Let's discuss your specific situation in a call. There's no cost for an initial conversation to explore fit.

Can you help with hiring?

On the engineering side, yes. I help design hiring processes, write job specs, screen candidates, and conduct technical interviews. I can also help you evaluate whether to hire experienced engineers, engineering leads, or a full-time CTO. Building the right team is often the highest-leverage work we do together.