Pre-Order $19.95 • Ships November 2, 2026

The Market Is Not Confused About Fractional CTOs. It Has Never Had a Reason to Tell One From Another.

This book names the pattern you already work inside, and gives you the language your next prospect will actually remember.

Structural CTO™: the field guide for practitioners already doing this work, written by the person who named it.

You already know the conversation. A prospect asks what makes you different from the last three fractional CTOs they talked to. You give a good answer: years of experience, a process, references. It is all true, and it does not land, because the person across the table has heard some version of that answer three times already this month, from three people who sound exactly like you.

Your work is not generic. Your vocabulary is borrowed. Nobody has ever given this category its own language, and that gap is what makes you structurally indistinguishable from every other fractional CTO in your market.

The pattern under the work

Every company that hires you is standing at a specific point on a curve. The need for CTO-level thinking climbs before a company can justify a full-time seat, and climbs again after, at several distinct points most practitioners have never separated out and named individually. You already sense the shape of that curve. You have probably never called it anything.

This book calls it the Load Curve™, names its earliest and most commonly missed point, the First Load Curve Bearing, and gives your role in it a name of its own: Structural CTO™. A title built around a method, where “fractional CTO” only ever described an arrangement.

You have already lived this

You quoted a lower number than you wanted to, at least once, because the prospect could not tell why yours should be higher. You watched a client hire the cheaper option instead, said nothing, and the call came eight months later when the cheaper option turned out to be exactly that: cheaper, and not much else.

You did not say “I told you so.” You just quietly noted it, the way you have noted a dozen versions of the same thing, because you already knew your work was different. What you have not had is a way to say so that does not read like every other fractional CTO’s homepage.

Why I wrote this book

More than a century ago, every brewery in America ran some version of the same process. Bottles washed with live steam, straight from the boiler. Water drawn from artesian wells four thousand feet deep. Beer filtered through white wood pulp. Standard practice. Invisible. Nobody talked about it. Claude Hopkins wrote an ad for Schlitz explaining the process in plain detail. The beer never changed. Schlitz went from fifth place in the market to a dead heat for first on the strength of being the only brewery that ever told the story of a process every brewery already ran.

I have spent over thirty years in technology, doing the actual work of a CTO more times than I have held the title: in my current role right now; earlier, as an outside consultant rebuilding multiple teams for a global services firm; before that, through a healthcare technology company’s final funding round; and in other engagements I still cannot name. I have watched capable practitioners do genuinely differentiated work and describe it in the same three sentences as everyone else. Nobody had named the pattern underneath it. I did. This book is that naming.

Who this is for

This book is written for practitioners already doing fractional, interim, or advisory technical leadership work. It is not written for the companies deciding whether to hire one.

If you are a CEO or founder trying to work out whether you need one, this is not your book. Get the free guide instead.

The Load Curve™ hiring guide →

What you will be able to do

• Name the exact point on the Load Curve™ your next prospect’s company is standing on, before they can describe their own problem to you.
• Answer “what makes you different from the last three fractional CTOs I talked to” in one sentence that does not sound like everyone else’s homepage.
• Replace “Fractional CTO” on your bio, your proposal, and your invoice with a title that describes a method.
• Recognize a First Load Curve Bearing in a discovery call: the earliest, most commonly invisible signal that a company needs you now rather than in six months, before the prospect has any language for it themselves.
• Justify a premium rate with a framework instead of a longer resume.
• Walk into a sales conversation already speaking the vocabulary your prospect did not know existed for their exact problem.
• Stop competing on hourly rate and start competing on diagnosis.
• Tell a prospect the truth when they are not ready for you yet, that they need an in-house hire, and have that honesty become the reason they call you back in eight months.
• Build your own marketing and positioning language on a named, documented framework instead of borrowed consulting-speak every competitor already uses.
• Cite a source for the pattern you have been describing in your own words for years, instead of re-explaining it from scratch every time.

What is inside

• Introduction: The Live Steam Problem. Why doing genuinely different work never explains why you cost more, until someone names the pattern out loud.
• The Load Curve™. Why company size was never the right way to describe what you actually sell.
• The First Load Curve Bearing. The earliest point on the curve, the one every practitioner has felt and nobody has named.
• Reading the Rest of the Curve. The points where a company graduates past you, and how to see it coming before the client does.
• Structural CTO™. Why “Fractional CTO” describes an employment arrangement, and this describes a method.
• Bearing Capacity and Design Load. The diagnostic set for whether the right person is in the right seat, what that seat was aimed at in the first place, and how to read all three in someone else’s org before they can.
• The Primary Span. Where the real load transfers in a leadership structure, and why it is rarely where the org chart says it is.
• Camber Architecture™. Building the shape the next band needs before the load that justifies it arrives, and funding it out of work already approved.
• The Floor and the Gate. The minimum a client is owed, the line past which you are accountable for an outcome, and what insurance actually covers.
• Speaking the Language. Using this vocabulary in a discovery call, a proposal, and a pricing conversation without it sounding rehearsed.
• Qualifying and Scoping the Engagement. What goes in writing before work starts, what to say about attrition before it happens, and the signals that should make you walk away regardless of how well a prospect reads on the Load Curve™.
• What the Work Actually Looks Like. Delivery cadence for an ongoing engagement.
• Conclusion: Washed With Live Steam. Owning a category you did not invent, only named, closing on the practitioner’s own Primary Span and Bearing Capacity across a portfolio of clients.
• Appendix. The Load Curve™ quick-reference, one composite engagement walked through every concept, plus discovery call script starters.
• The Structural CTO™ Lexicon. Every term in the book, defined. Read it online.

The book