Nobody trains you for this job. One day you're the best engineer in the room, the next you're explaining a budget to a board. I help CTOs with both halves: the architecture calls that have to age well, and the people who have to live with them.
The job changed
You became CTO because you were good at technology.
Funny, that.
Because the job you got is something else. It's the 1:1 you've been postponing for three weeks. The board that wants a date, not an explanation. The engineer who was there from day one and hasn't grown along with the company. The founder who sold a feature on Thursday that you heard about on Friday.
Nobody put that in the job description. (I checked.)
And now there's AI on top. Every architecture choice has become an AI choice, every vendor has a demo, and everyone at the table has an opinion they picked up over the weekend.
So you do what good engineers do. You work harder. You fix it yourself, at night, because explaining it takes longer.
It doesn't scale. And neither do you.
What does work is a lot less heroic. Guardrails instead of firefighting. Decisions made once, on purpose, and written down. A team that doesn't need you in the middle of everything.
It's a craft. It can be learned.
Mostly the hard way. Or with someone who has already paid for the lessons.
A demo is not a product. I help you tell the difference before it ends up in your roadmap.
The smaller half. The stack does what you tell it. People don't, and that is where companies are won.
You can't think out loud with your team, your CEO or your board. You can with me.
Sound familiar?
“I'll just fix it myself tonight.”
You're still the best engineer in the company, so everything passes through you. The reviews, the decisions, the incident at 2am. It feels like dedication. It's a queue, and you're at the front of it. We work on letting go without letting things slide.
“The board wants a date.”
You explain the why. They ask for the when. You leave feeling nobody listened, and so do they. A board doesn't need less detail, it needs a different story: risk, money, options. We build that story before the meeting. Not during.
“They were here before we had an office.”
Loyal, liked, and no longer right for the role. You know it. The team knows it. They probably know it too. Every month you wait, your best people are watching what you tolerate. We prepare that conversation properly, so it's fair to them and to everyone else.
“Sales promised it for Q3.”
Your founder sells the future. You have to build it. Somewhere in between, a date was mentioned. That's not a planning problem, it's a relationship. We work on how you and your CEO disagree, so it happens in the room and not in the roadmap.
“I thought we had agreed on this.”
Three time zones, five nationalities, one standup. Half the team heard a decision. The other half heard a suggestion. Nobody is wrong, which is the annoying part. I replace assumptions with structure, so people can work together without you translating.
“I miss building things.”
You were promoted for what you loved doing, into a job where you hardly do it. Some CTOs grow into leading people and wouldn't go back. Others find out they would rather lead the technology. Neither is failure. Finding out which one you are, that's the work.
What I help with
Build or buy. Rewrite or repair. Wait or jump. Big calls, usually made under pressure and regretted at leisure. I pressure-test them with your team, so they still make sense in three years (and in the next board meeting).
A confidential place to think out loud. About how to lead, and about which seat to lead from. The board, the growth, the hard personnel calls. And sometimes the quieter question: is leading people the job you actually want? Some leaders I coach grow into it. Others move to Principal or Staff+ and do their best work there. Both count as wins.
An org chart is architecture too. Who owns what, who decides what, who gets hired for what. When the team is shaped differently than the system, the system loses. Every time.
How I work
I don't sell hours. Hours are easy to sell and hard to stop. A decision sprint takes one to three weeks and is aimed at one hard call. You know the scope, the timeline and the price before I start.
At the end you get a recommendation you can act on. Not a slide deck. Not a proposal for the next phase. (Well, maybe one slide.)
What a sprint delivers
Prefer something ongoing? I also work as:
For when the questions keep coming. A fixed rhythm each month, and a phone that gets answered when a big decision can't wait.
Regular, confidential coaching for your engineering leaders: their hardest calls, their growth, and the people challenges no org chart prepares them for.
About
I'm Paul van Eijden.
I've co-founded two companies and exited both. One of them for €34 million, eighteen months after launch. I also built an agency from zero to forty people, which teaches you things an exit never will.
Mostly about people.
Somewhere along the way I noticed I'm at my best with teams of ten to thirty. And that my favourite moment in any assignment is the one where they no longer need me. So that's how I work. I design the framework, I train the team, and then I make myself redundant. On purpose.
(It's a terrible business model. It works very well.)
I'm not a slide-deck consultant and I don't do hustle. I work with a few leaders at a time, in the room where the real decisions get made. Half technology, half people.
The second half is harder.
What I've built
I've co-founded and exited two ventures, grown an engineering agency to 40+ people, and led platforms serving millions. A selection:
Built and ran a 20+ platforms team across 3 time zones, and laid the foundation for a spin-off.
Took the product through compliance, unlocking enterprise clients and the Belgian Army, then handed the CTO role to an internal hire.
Architected the tech stack from inception and led the strategy through growth to a successful exit.
Co-founded the platform and scaled its early infrastructure. Exited to Recruit Holdings for €34M.
Built a startup engineering agency to 40+ people, owning delivery and engineering culture.
Led 20+ engineers building lottery platforms that served millions of participants, and made the department fully independent of external consultants.
Let's talk
You're still good at technology. Let's talk about the rest. Tell me what you're wrestling with: the decision, the person, the board. If I can help, we'll scope it together. If I can't, I'll tell you who can.
Send me a DM on LinkedInIf you have an outsourcing agency wanting to sell me something, please don't.