A founder asks whether it is time to bring in a CTO. You can answer the affordability question before lunch: fully loaded salary, equity dilution, recruiting fee, and the carrying cost of a search that runs longer than anyone plans for. You can build the model.
You cannot tell them whether the seat should exist yet. Nobody can, from a P&L.
So you say what every capable fractional CFO says in that moment, which is some version of “that one is outside my lane,” and the decision proceeds without the only person in the room who reads the spend, the runway, and the hiring plan together.
Here is what makes that galling. You were already looking at the evidence. Engineering payroll climbing faster than engineering output. A cloud bill on a curve nobody has tied to revenue. Three roadmap dates in a row that moved, each with a reason, and the reasons never repeat. A founder whose calendar has quietly become a queue.
Those are not technical signals. They are structural ones, and they are readable from data you already have.
Five stages, from a company where one person holds the whole architecture in their head to a company that needs a CTO with a leadership layer underneath. Each stage names what it costs, what it buys, and the specific signals that a company has outgrown it. You take two readings: where the money says they are, and where the practices actually are. Two companies at identical revenue can sit at different points on this curve. The gap between those two readings is the finding, and it is a cost-structure finding, which puts it inside your lane rather than outside it.
Three of the five stages do not end with hiring anyone fractional. A company at the first stage should stop shopping, and should be told so plainly. A company at the fourth has outgrown fractional help and should run a search. A guide that always concludes its author should be hired is one you would never hand to a client, and you would be right not to.
What you get:
I am a Structural CTO™. More than thirty years in technology, most recently on a platform carrying more than a hundred million transactions a month, where I moved fixed cloud spend to variable and drove per-transaction cost to $0.00035 and falling. I named this curve, and I wrote the book that defines it.
No fee is attached to any of this, and no arrangement sits behind it.
Take it, run it on one client, and tell me where the instrument breaks.
The Load Curve™ and Structural CTO™ are terms coined by Anthony S. Jackson. What a Structural CTO™ is, and why the role exists, is explained at structuralcto.com. Current market ranges for all five stages are at theloadcurve.com/bands. Management Coaching of Wyoming, LLC.