Hi there, I’m Fred. My goal is to share strategic and actionable insights on being a scale-up CTO. I’ve been working in startups and scale-ups for 20 years as a Systems Engineer, VP Engineering and now as a CTO, and been through numerous funding rounds and m&a. A few highlights:

CTO at Data Impact where I played a significant role in the acquisition of the company by NIQ after scaling the engineering team, getting rid of the technical debt and stabilizing the product.

VP Engineering at Ledger and Aircall where I organized the engineering team during and after a 10x people growth period respectively.

Advised CTOs and lead devs of companies like Aircall, Red River West and

Since 2005, I've written on my blog my learnings and insights about managing having ADHD, building top notch infrastructures and scaling teams. After a 4 years hiatus, I'm back with this newsletter which focuses about being a non developer but still hands on CTO in series B to D and post acquisition scale-ups.

Why scale-ups and not startups?

Scale-ups are startups that found their product market fit. A scale-up CTO shares lots of common challenges with a startup CTO, but at a different scale, and they face different issues that I want to cover here. I don't feel confident to write about being a startup CTO, but I know a bit about scale-ups. Also, the startup CTO field is covered by several publications already, I wanted to bring something different.