Ask a structural engineer what a building can carry and you will not get an answer from the floor count. Floors matter. Floors are load. But two buildings with the same number of floors hold very different things: one has desks and people, the other has compact archive shelving on rollers and a chiller plant on the roof. Same silhouette, and one of those floors fails under a load the other never notices. So the engineer asks what is actually up there, and where that weight travels to reach the ground.
A Structural CTO™ asks the same question about a company's technical leadership. Read the load it is actually carrying. Name the point where that load has outgrown the structure holding it. Build the decisions the situation requires.
The title names a method, not an employment arrangement. Fractional CTO describes how someone is retained: hours, duration, contract structure. It says nothing about what they do once they arrive. Structural CTO™ describes the work itself, and the diagnosis is what sets the hours.
Almost everyone serving this market segments by company size. Headcount, revenue, funding stage. Under that model a company either needs a CTO or it does not, and the line sits somewhere around a number.
The line does not exist.
A company's need for CTO-level structural decision-making climbs continuously as it grows. Two companies at identical revenue can sit at opposite points on that climb, because what climbs is structural entanglement. Revenue is the floor count: real information that leaves the question open. That climb is the Load Curve™, and reading a company's position on it is the whole of the diagnosis.
The most commonly missed point on the curve is the earliest one. The need has outgrown what a working technical lead can absorb alongside their existing job, and it has not yet grown enough to justify a full-time hire. Nobody sells into that point, so it gets absorbed as unpaid overtime by whoever is standing closest to the problem. It has a name now: the First Load Curve Bearing.
It is visible from inside without any framework at all. One person is the last word on every cross-cutting technical decision. Architecture decisions exist only as institutional memory. “We should really document this” has become a running joke nobody owns.
It is visible from outside too, and that is the part people miss. Nobody can get thirty minutes with the founder or the lead engineer that is not about a decision only they can make.
The person absorbing it is usually the most capable person in the room. That is precisely why the work landed on them. They are doing good work under a structure that was never designed to hold what it is now holding, and no amount of additional effort on their part changes the shape of it. Naming the bearing is what lets a company keep what that person is good at without spending them to get it.
A Structural Bearing™ is a permanent tension between two legitimate systems, neither of which can be removed without breaking something the business needs. What the situation demands is legitimate. What the people in the room can absorb is legitimate. Neither side is the error, and neither side goes away.
That is a claim about geometry, not strength.
A bearing is the joint that lets two structures move against each other without either one tearing. Engineers put bearings under bridges for exactly this reason: the deck expands in July and contracts in January, the piers move far less and never in step with it, and that difference has to go somewhere. The bearing is where it goes. It carries the load while permitting the movement, and the bridge stands because the movement was designed for.
The market reads the space between two legitimate systems as a strength problem and answers it with a stronger person, or with more hours from the person already there. The variable is distance, and distance is managed, never closed. Which is why that answer fails on a schedule, and why it keeps being tried.
Read a dozen fractional technology leadership sites in a row and the language is close enough that two competitors are hard to tell apart, even reading on purpose, looking for the differences. Strategic technology leadership. Scalable architecture. Aligning engineering with the business. Every one of those phrases is true, nearly every one of those pages carries it, and not one of them tells you what the person actually does on a Tuesday.
The expertise behind those sites is real and the decades are real. The descriptions are interchangeable because the thing that makes the work valuable had no name.
A buyer given nothing else to compare compares rates. They are doing the only thing the market left them.
What that person does on a Tuesday is take a reading: two measurements from records the company already keeps, and a written finding short enough to act on. Both doors below open onto the worked version.
There are points on the curve where the honest answer is that you do not need a Structural CTO™, and anyone selling you one is selling hours. A team of eight shipping one product, where the founder still carries the whole architecture in their head and it genuinely fits there, does not have a structural problem. It has a founder who is still comfortably inside their own span. Hiring against that buys meetings.
There are points further along where a company has outgrown the role entirely. Three product lines, a compliance regime with an audit calendar, and a board asking every quarter about technical risk: that is a full-time seat with a full-time salary attached. A fractional engagement there postpones the hire while paying for the symptom.
Neither reading ends with an apology. A company told it has outgrown the role leaves with help writing the profile for the person who takes the seat.
Both readings are part of the method. A category that fits everyone describes nothing.
You are already doing fractional, interim, or advisory technical leadership. You have scoped an engagement in hours because hours were the only unit on offer, and watched a client treat your rate as the thing they were deciding about. The book is the full treatment: reading the curve, naming a bearing, qualifying an engagement, and scoping the work that follows.
The vocabulary, defined with sources and chapters →
Start by finding out where you actually are. The guide walks the five stages of the curve and tells you which one your company is standing in, including the stages where the answer is that you do not need this.
The Load Curve™ hiring guide →
If you would rather have the reading run properly on your own company, that is The Load Curve™ Placement. A written placement naming your current stage, the stage you are moving into, and what the crossing costs, short enough that your board reads all of it. Your graduation signals come named specifically enough that you see the next crossing yourself, months before anyone brings it to you.
Then what you recognized is real. You are the person standing closest to the problem, and this is the wrong door: everything above describes the load you are carrying from the outside in, by someone who gets to leave. The work on carrying it from the inside is a different body of work.
Structural CTO™, The Load Curve™, and Structural Bearing™ are terms coined by Anthony S. Jackson, who named the method this page describes. Management Coaching of Wyoming, LLC.