The uncomfortable arithmetic of a fit conversation
A founder books a call about fractional CTO services. They are articulate about the problem, the budget is real, and the engagement would be straightforward to deliver. And the honest answer is that they should hire a lead engineer instead, at roughly half the cost, and call us in eighteen months.
We say so. Not out of nobility — because the alternative is worse business. An engagement sold into the wrong problem underdelivers, and an underdelivering engagement is the most expensive marketing you can buy.
The test is a count, not a feeling
List every genuinely CTO-level decision facing you in the next two quarters. Architecture choices, build-versus-buy, the first engineering hire, vendor selection, security posture ahead of an enterprise deal, diligence preparation, whether to rewrite.
Count them. Fewer than roughly one a week and a fractional CTO will spend a meaningful part of the engagement inventing work — which you will notice, and resent, around month four. More than that and a fractional arrangement becomes a bottleneck: the decisions queue for the days they are available.
| < 1 / week | Fractional is over-specified. You likely need a lead engineer. |
|---|---|
| 1-3 / week | Fractional is the right shape. |
| > 3 / week | Fractional becomes the bottleneck. Consider full-time. |
The three cases where we say no
- You need someone to ship, not to decide. Many founders searching for a CTO are describing a strong senior engineer. That is a cheaper hire, a faster search, and it solves the problem they actually have.
- Your problem is delivery speed. If features are slow, measure change lead time first. Days between commit and production means the constraint is pipeline and process, and no amount of senior technical direction fixes a manual deploy.
- You are past the threshold. Beyond roughly 25 engineers, or raising a round where the CTO is part of the story investors are buying, or fielding enterprise security reviews weekly — hire full-time. Fractional at that scale is a saving that costs you.
Why this is commercially rational, not charitable
Three reasons, in ascending order of importance.
First, the deal was fragile anyway. An engagement that does not fit the problem produces a client who cannot articulate what they got, which produces no renewal and no referral.
Second, disqualification is the fastest qualification. Every founder we turn away sharpens the description of who we are for, and that description is what makes the next conversation shorter.
Third, and most durably: the founder we turned away is the one who remembers. They come back at the right stage, and in the meantime they answer the question 'who should I talk to about this' with our name. We have no way to measure that precisely and we are not going to pretend otherwise — but it is the reason the practice is structured this way.
What we say instead
The conversation does not end at 'no'. It ends with something they can act on:
- The specific role we think they should hire, with the seniority and the two or three things to screen for
- The four DORA measures — deploy frequency, change lead time, change failure rate, time to restore — so they can tell whether engineering is healthy without a technical hire
- A rough marker for when to revisit: the decision count, and the 25-engineer threshold
- An open door with no follow-up sequence attached. If it is useful later, they know where we are.
The claim underneath all of this
Our site says we will tell you if we are not the right partner. That claim is either operationally true or it is decoration, and there is no middle position — a prospect finds out which within one conversation.
Making it true costs real revenue in the short term. It is the only version of the claim worth making.