Fractional CTO / CPTO
I help you set priorities, design your software architecture and oversee its evolution, without bringing on a full-time CTO. The scope can include product strategy, team support and hands-on development when needed.
When I can help
You are launching or growing a product and need someone to set technical direction, without bringing on a full-time CTO yet.
There is a team building, but key decisions pile up: how to structure the system, what to do with technical debt, what comes first.
An agency or freelancers build for you, and you want someone on your side to review proposals, estimates and deliveries.
Decisions I support
My job is to bring judgment where decisions are made, put priorities in order and make sure execution follows. These are the kinds of decisions I help with.
Align technology with where the business wants to go.
For example
Design a system that holds up today and can grow tomorrow.
For example
Put order into what to do now, what next and what not at all.
For example
When the scope requires it: what to build, for whom and why.
For example
Make sure what was decided gets built, and built well.
For example
When the scope requires it, I support product as well as technology. That is what CPTO means: one person connecting what to build with how to build it.
How we collaborate
Two ways of working together. Dedication, duration and conditions are agreed for each engagement: there are no closed packages, we start from what you need.
One-off
For a specific decision or a defined stretch of work, with a clear start and finish.
It can include
What you get
You finish with the decision made and documented: what to do, why, and the next steps.
Recurring
For ongoing direction with continuity. I join as part of the team, with an agreed dedication.
It can include
What you get
Decisions made at the right time, and a team that moves forward with clear direction.
Relevant experience
I connect technology, product and business because I have worked on all three sides: building software, shaping products and starting companies.
Today I also work with artificial intelligence and mentor in technical training programmes. I don’t just recommend technologies: I understand what it takes to build, run and maintain them.
Software engineer. I have designed architectures and led engineering teams.
I have built digital products from scratch, from the first decisions to their evolution.
I have founded technology products, so I know business decisions from the inside.
Way of working
I use the DARE Method as a framework, applying only the phases each situation needs. A one-off intervention may be just a diagnosis; recurring direction usually moves between realization and evolution.
See the full DARE MethodUnderstand the context: business, product, team and technology. Where you are and what matters first.
Design the plan: what to build, how, with what and in which order.
Supervise execution with your team or vendors, and build directly when it helps.
Keep direction over time: review, adjust priorities and plan what comes next.
Evidence
I prefer not to publish testimonials out of context. If you want to talk to people I have worked with, tell me about your situation and I will put you in touch with relevant references.
FAQ
It means part-time, shared direction: I am not on your team full-time. Dedication is agreed for each engagement, from a few sessions for a specific decision to a regular weekly presence, and we review it as your needs change.
As a Fractional CTO I focus on technology: architecture, technical decisions, team and quality. When the scope requires it, I also take on product (CPTO): what to build, for whom and in which order. Many companies need both connected; we define it at the start.
Yes, when it helps. My main role is direction: deciding, designing and supervising. I can build a proof of concept, unblock a critical piece or review code, but I do not replace your development team. If hands-on work is part of the scope, we agree on it explicitly.
AI is a capability, not the starting point. I help you assess where it brings real value to your product or processes, which approach fits, from a simple integration to more complex systems, and what it costs and risks. I also use AI tools in my own work to speed up analysis and prototyping, always with human review.
I add to what is already there; I do not replace it. With a CTO or tech lead, I act as senior support for the decisions they own. With a team, I help set priorities and processes. With a vendor, I bring independent judgment on your side to review proposals, estimates and deliveries.
Contact
To understand your context and see whether I am the right fit. No commitment.
Scope, format and dedication, agreed together.
A one-off intervention or recurring direction, depending on what you need.