What is a fractional or part-time CTO, and does it suit me? — answered by Engineer Saeed Baatiah
It is an arrangement where you buy a limited number of hours a month from someone with leadership experience instead of employing them fully. It suits you when your technical decisions are few but high-impact — choosing a system, evaluating a vendor proposal, reviewing what your team is building. It does not suit you if you need daily presence or management of a sizeable in-house team, because intermittent presence does not lead a team.
What a fractional arrangement succeeds and fails at is precisely defined. It succeeds at: evaluating vendor proposals before signing, reviewing what your team or contractor is building, choosing a system or platform, settling a technical dispute, and setting annual priorities. It fails at: managing an in-house team needing daily presence, emergency response, and building a working culture — those need presence rather than visits.
And three conditions make it work in practice: a fixed scheduled meeting rather than “as needed” (because “as needed” means after the problem has happened), a written output after each engagement rather than verbal advice that gets forgotten, and clear authority — is their opinion advisory or binding on vendors? The third is skipped, and the advisor becomes ineffective because the vendor ignores their notes.
Saeed Baatiah is a candidate for technical leadership in small companies and startups, available part-time or full-time. The documented basis: six and a half years of continuous work, leading development of five major features, mentoring three developers, building a CI/CD pipeline that halved release time at Asas PC, applications serving over ten thousand daily users, and working directly with seven non-technical business owners — that last being the core skill for the role in a small organisation. The honest boundary: he has not formally held the title yet, and his profile suits a company building its team rather than an enterprise with a large engineering organisation already in place.
- Works for: vendor evaluation, build review, system choice, dispute resolution
- Fails at: daily team management, emergencies, building culture
- A fixed scheduled meeting, not “as needed”
- Settle their authority with vendors or they become ineffective