Fractional CTO: hands-on technical leadership
As a fractional CTO I take on the technical leadership of a product or a team: architecture, how the team is organised, deployments, on-call, and the technical decisions that need to be discussed with the business. I still write code, so I make those decisions knowing the codebase. It is the work I have done as CTO of Blanco Brand since 2024, on a platform with 25 deployed projects.
What is included
- Product architecture and technical decisions explained to the business: what to build, what to buy and what to integrate.
- How the development team is organised and works: code review, continuous integration and quality standards.
- The deployment and operations platform: environments, managed databases, monitoring, alerting and on-call.
- Keeping development and infrastructure spend under control.
- Hands-on development in the critical parts, without becoming the team’s bottleneck.
How I work
- At Blanco Brand I organised development around a stable team of three. Development spend fell 63% and infrastructure spend 55%.
- Deployments went from one hour to five minutes, at 99.95% uptime.
- The platform I run has 25 deployed projects, of different sizes, for healthcare, mining, residential communities and other sectors.
- The team’s rules live in continuous integration, not in my review. At SuiteMedica every change goes through build, type checks, lint, unit tests and end-to-end authorization tests.
Cases and products behind it
Frequently asked questions
What is a fractional CTO?
Someone who takes on the technical leadership of a product or a team for a project, without holding the role full time. It covers architecture, the team, deployments, on-call and the technical decisions made with the business.
Do you still write code?
Yes. On SuiteMedica my part is the architecture, leading the team and development. It works well in small teams; in organisations with many teams, the CTO’s job is mostly coordination.
When does an external CTO make sense?
When a product or a small team needs technical leadership and someone who also builds, and adding a full-time CTO does not make sense. Some call it CTO as a service; I set it up by project, with an agreed scope.
What results can you show as a CTO?
At Blanco Brand, with a stable team of three: development spend down 63%, infrastructure spend down 55%, deployments from one hour to five minutes, and 99.95% uptime.