
CTO Coaching Without the BULLS?%t*.
Built teams. Scaled companies. Sold a startup. Now I coach technical leaders to lead like founders — not firefighters.

My clients don’t wait to be stuck - they lead ahead of the curve.

This Coaching Is Not for Everyone.
This is for you if…
- You're leading a scaling tech org
- You're facing serious leadership challenges
- You're ready for direct, unfiltered feedback
- You want to operate at a founder level
This is not for you if…
- You want a motivational cheerleader
- You need more productivity hacks
- You’re not ready to be challenged
- You just want to “get by” as CTO
What Happens During A Coaching Session?
In our 90-minute sessions, held every two weeks or monthly, we will work on a wide range of different topics and challenges.
Fire-Fighting
We will discuss all issues and questions that you would collect between sessions, always focussing on the whole company, not only Engineering. The topics could include, but are not limited to:
- Stakeholder Management
- Hiring
- Team Management
- Technology and Architecture
Personal Development
During our first sessions, we will determine where you want to develop yourself. This will become our guiding light. After all, coaching is also a mindset change and it i about you. I will constantly suggest articles and literature for direction. Reaching your personal goals is key to satisfaction and therefore key to high performance.
Team Development
Your team is never static, it grows and has a dynamic of its own. We will work on keeping your team motivated, fostering ownership and accountability among its members. Keep in mind that you are managing developers and they deserve to be developed.
What’s Included
The sessions are the core. These are the parts around them.
Prepared Sessions
Every session is prepared and followed up by me. We start with an assessment of your team, structure and open challenges, so the first sessions already work on the real problems.
A Shared, Confidential Log
One document holds every session. It is the record of what we said and agreed, you write in it between sessions, and it shows your progress over time. Only the two of us see it.
A One-Page Summary per Session
Outcomes and learnings come back as a visual cheat sheet you can keep, pin up or share with your team.
Worksheets When Needed
If a topic calls for a structured exercise, I hand you a worksheet for it during the program.
Support Between Sessions
Questions come up on a Tuesday, not only in session. You can write to me in between.
My Network
If a topic is beyond me, I introduce you to specialists I trust.
No lock-in. You can stop whenever you want.
1:1 Coaching That Drives Real Change
This isn’t a course or a checklist. This is a working relationship that changes how you lead.

Unfiltered Words from the People Who’ve Been There
Trusted by:You don’t need another framework. You need a real challenge.
Why I Coach the Way I Do
I coach CTOs because the chaos I lived through gave me my experience and made me a better leader.
The work of a CTO, and of course the work of engineers, is changing fast. We no longer see all the code that gets written, so we need different processes and different tools to keep up. I’m here to show you solutions and to coach you through this change. I won’t tell you what to do. I’ll help you build the skills you need to create an adaptive process for your team.











