A buyer says "we want to hire a fractional CTO." The title tells you what they want to call you. It tells you almost nothing about what you are being paid to do, how many hours per week the work takes, or which other engagements you can hold alongside it. Two fractional CTOs at identical day rates can be selling radically different products. The structure is the variable that matters, and the structure determines whether the engagement leaves room for the rest of your practice.
This is a pattern library of the four fractional engagement structures I currently sell, indexed against three dimensions that predict whether the engagement is actually sustainable: time consumption per week, revenue stability, and how many you can hold simultaneously without quality dropping.
A shape is not a title
The phrase "fractional CTO" names what the buyer wants on their org chart. The engagement structure is the actual product. Two operators with the same title can be running fundamentally different businesses. One shows up for a 90-minute architecture review every other Tuesday. The other owns the deploy pipeline, runs standup, makes hiring decisions for two open seats, and is on call when the staging environment goes sideways. The title hides what is actually being delivered, and the price tag rarely rescues that confusion.
The rest of this article indexes the four shapes against three dimensions: how many hours per week the structure consumes, how stable the revenue from that structure is, and how many such engagements you can hold at once before quality collapses. Those three are the variables that govern whether a fractional practice is a real business or a long contract with extra meetings.
Sprint structure: fixed scope, fixed end, dense week
The sprint is a 4-to-6 week or 90-day engagement with a named deliverable, a fixed price, and a defined start and end. The buyer is paying for a specific system to exist in their business by a specific date. The engagement ends when the system ships.
Time consumption is roughly 14 to 18 hours per week, packed across two to three working days. The hours are dense because the deliverable date is fixed; if I miss a week I cannot recover it without sliding the date or compressing the next week. Revenue lands as either a lump sum at signature or two staged payments, with no recurring tail after the deliverable ships. Portfolio simultaneity caps at one. Two sprints in parallel is technically possible and almost always degrades both of them, because the daily context for sprint A is incompatible with the daily context for sprint B and the switching tax compounds.
The failure mode is scope creep. A sprint signed at week zero with five deliverables and a sixth quietly added in week three becomes a sprint that misses its deadline by a month. The discipline is naming follow-ons explicitly: "that is a great addition, it is a 30-day follow-on engagement we can scope in week ten." Saying yes inside the sprint is the cheapest way to lose the sprint.
Advisory structure: presence on a recurring cadence
The advisory shape is the opposite. There is no deliverable. The buyer is paying for senior judgment on a recurring cadence: a weekly or biweekly call, plus async access during business hours. One to three scheduled hours per week. The operator stays out of the day-to-day execution: no code commits, no hiring decisions, no standup attendance. The work is review, challenge, and sign-off on the decisions the internal team is already capable of making.
Time consumption is 2 to 3 hours per week of scheduled time, plus the context-switching tax, which is real. Holding the state of four different client businesses in your head between Tuesday calls is itself work, and operators who price advisory purely on the scheduled hour underprice the cognitive load. Revenue is the most predictable of the four shapes: a flat monthly fee that lands on the same date every month. Portfolio simultaneity caps at three or four. Past four advisory engagements, the recall on each client's state degrades and the calls become less useful.
The failure mode is decay. The retainer dies the first month the buyer stops bringing real decisions to the call. Once the meetings become status updates, the engagement has already ended; the buyer just has not canceled yet. The fix is to watch the meeting content. If three weeks pass without a decision needing senior input, the engagement is in the wrong shape and should be reshaped or ended.
I have written separately about why advisory drift is the most common failure mode for fractional CTOs who take this shape by default. Advisory has a narrow legitimate use case. Outside that case, it becomes a slow-bleed engagement that nobody wants to admit ended six months ago.
Ops-lead structure: authority held part-time inside an org chart
The ops-lead seat is the highest-commitment shape. The operator holds a named role inside the buyer's org chart for the engagement window: fractional CTO, fractional head of growth, fractional VP of ops, or the equivalent. The buyer is paying for authority inside a specific function, not for advice and not for a deliverable. The operator runs the team that exists, hires the next seats, owns budget for the function, and reports to the CEO.
Time consumption is 18 to 22 hours per week with high context density. Two and a half working days, but dense ones, because the role is doing the actual work of the function. Revenue is the highest per-month of any shape and usually structured as a quarterly or bi-annual commitment with a defined exit. Portfolio simultaneity caps at two and is often functionally one, because the authority load and the meeting calendar of a real ops-lead seat does not leave space for a second one without compromising the first.
A seat I held in regulated healthcare lived in this band. Effective time on the engagement was around three working days a week, at the high end of the ops-lead range. The role spanned creative direction, marketing technology, cloud operations, and de facto fractional senior operator duties on the technical side. That seat alone was a structural test of how much load this shape can absorb before it becomes a full-time job with extra steps. The honest answer: a single ops-lead engagement at the high end of the time band is roughly 60 to 70 percent of a full-time role, which leaves room for one or two advisory retainers and nothing else.
“A single ops-lead engagement at the high end of the time band is roughly 60 to 70 percent of a full-time role.
”
The failure modes here are dual. The first is authority that is not real: the operator makes a decision in the weekly meeting and watches the full-time team override it the next day. The second is an exit that is never planned. The engagement drifts from "six-month fractional seat" into "permanent fractional seat we keep renewing because the right full-time hire has not appeared yet," and the operator's practice quietly converts back into a full-time role that pays the same as one client. The second failure is softer and more damaging. It looks like success for two quarters and like a structural problem for two years.
Bridge structure: audit first, implementation as a decision
The bridge is a two-phase engagement. Phase one is a fixed-scope, fixed-price diagnostic delivered in two to four weeks. Phase two is implementation, scoped and priced at the end of phase one based on what the audit found. The two phases are sold as separate engagements with a decision point between them, not as a bundled sale that happens to have a checkpoint.
Time consumption during the audit phase is 8 to 12 hours per week. Concentrated, deliverable-shaped, but lighter than a full sprint because the deliverable is a document and a recommendation, not a working system. Revenue is a small audit fee at signature plus a variable follow-on if the buyer continues into implementation. Portfolio simultaneity is the highest of any shape: the audit phase overlaps cleanly with sprints, advisory engagements, and even ops-lead seats, because the audit work is contained and the daily context is the audit subject, not an ongoing operational load.
The failure mode is when the audit and the implementation are pitched as a single sale. At that point the audit stops being a diagnostic and becomes a sales call the buyer paid for. The buyer can feel the slope. The diagnostic loses credibility because the operator is obviously writing toward a continuation. Selling the two phases separately, with a real decision point between them, is what makes this shape work. Either outcome is a clean engagement: continue into the sprint, or stop after the audit and use the document as the buyer sees fit.
I cover the diagnostic-to-sprint transition in detail in the article on scoping the sprint from a single intake call, which is the practical follow-on once the audit lands and the buyer says yes.
How fractional engagement structures consume the week
The four shapes do not compose freely. Some combinations are sustainable for years; others break the operator inside a quarter.
The combinations that work in practice:
- One sprint plus two advisory engagements. Roughly 18-24 hours/week total. The sprint is the active build; the advisory cadence funds the bridge while the sprint runs.
- One ops-lead seat plus one or two advisory engagements. Roughly 22-28 hours/week. This is the high-revenue plateau for most operators, and it leaves zero room for new sprint work, which is a constraint to plan for.
- Bridge plus anything. The audit phase is contained enough to layer onto any of the above without breaking them, which is why bridge is the cheapest entry point for a new buyer relationship.
The combinations that break: sprint plus ops-lead (the dense weeks collide), two ops-lead seats (a full-time role split across two clients, both of whom feel the gaps), and four advisory plus a sprint (the cumulative context-switching tax exceeds the scheduled hours by week six).
The 40-hour assumption embedded in most fractional pricing math is wrong. Nobody actually runs four ten-hour fractional days with the same focus a single ten-hour day on one project would have. Context recovery between client stacks is a real cost: 30 to 60 minutes of warm-up per context switch, depending on how different the daily realities are. A solo operator running three concurrent clients pays that tax six to ten times a week. The math has to absorb it.
I have written about the cost of switching between client stacks in detail, including the practical mitigations. The summary: structure your week so each client gets a contiguous block, not a series of 30-minute slots scattered across days.
Why retainer-as-permanent-revenue is the wrong frame
Both the advisory shape and the ops-lead shape are retainer-shaped: monthly fees, recurring cadence, no specific deliverable contract. It is tempting to treat the retainer column on the spreadsheet as the permanent revenue model and the rest as variable. That framing is structurally wrong for a fractional practice that is trying to scale past the operator's hours.
Inside this practice, retainers (advisory and ops-lead) are bridge instruments. They sunset on 2026-12-31. The decision was made deliberately because the math of an hours-based business caps at the operator's available time, regardless of price. Two ops-lead seats at high rates and three advisory retainers is a 50-hour week of client work that ends the moment the operator stops being able to deliver it. That is the same structural problem a full-time job has, just spread across multiple clients.
The permanent revenue model runs through the productized ladder. Sprints are productized when the pattern has been run enough times to know exactly what ships when. Audits are productized first because the deliverable is contained. The ladder is what you build during the year you still have retainer revenue funding the building of it. The ladder is the bridge's destination, not its alternative.
The article on the retainer trap and why productized work is structurally better is the longer argument. The short version: any shape priced against the operator's time is structurally a job, regardless of how much the buyer pays per hour.
Choosing a fractional engagement structure for the buyer in front of you
The selection logic is one intake question, asked at the start of the discovery call: what does success look like at the end of this engagement?
Buyer names a system that should exist when the engagement ends? The shape is a sprint. Server-side CAPI wired correctly. A new theme architecture shipped. A specific dashboard that did not exist before. The deliverable is the answer to the question.
Buyer names a cadence they want to maintain (a weekly architecture review, a monthly strategy call, a standing Thursday hour)? The shape is advisory. The cadence itself is the deliverable.
Outcome that requires authority? The shape is ops-lead. The marketing function should be hitting these numbers. The engineering team should be shipping at this velocity. The infrastructure should be running below this cost. Outcomes tied to ownership of a function are ops-lead seats, regardless of what the buyer wants to call them.
Buyer cannot name any of those? The shape is a bridge. They know something is broken; they cannot name what; the audit is what produces the answer to the next question. Starting with a bridge is the strongest default for any new buyer relationship that is not already a clear fit for one of the other three shapes.
The fifth shape is the one to decline. The buyer who wants a full-time head of function and cannot afford one and hopes the fractional version will deliver full-time output for 40 percent of the cost is asking for a structure that does not exist. Either the operator delivers 40 percent output and the buyer feels shortchanged, or the operator delivers full-time output and burns out. Fractional is not a cheaper full-time hire is the longer argument. The shorter one: if the buyer came in thinking of fractional as a discount, the engagement is downstream of a bad frame and will end badly regardless of the structure on paper.
The work that has come out of these four shapes is documented in the case study archive. The productized off-ramps from the sprint and audit shapes live in the product suite, which is where the bridge becomes the destination instead of the destination becoming another retainer.
Frequently asked questions
Is a fractional CTO always an ops-lead structure?
No. The title is a label; the structure is the product. A fractional CTO can be sold as advisory (1-2 hours per week, no execution), as a sprint (a specific system shipped in 90 days), or as ops-lead (true seat with authority over the engineering function). The same title can carry any of three structures, and the proposal needs to name which one.
How do I know which structure I am actually selling on a given proposal?
Read your own scope-of-work. If the document names a deliverable and a date, it is a sprint. If it names a cadence and an availability window, it is advisory. If it names a function and an outcome, it is ops-lead. If it names an audit and a follow-on decision, it is bridge. If the document tries to name two of those at once without separating the pricing, the structure is going to break and you are going to be the one paying for it.
Can a single engagement combine structures?
It can, but the combination must be named explicitly with separate pricing for each component. An advisory retainer that includes a contractually-scoped sprint in month two is fine. An advisory retainer that "includes implementation work as needed" is the fifth shape, and it is the one that burns operators out. The rule is: every component of the engagement must have its own structure documented and its own price attached.
What is the realistic maximum for a solo fractional operator running this catalog?
One ops-lead seat plus two advisory retainers is the high-revenue plateau most solo operators can sustain across multiple quarters. Adding a sprint is sustainable only if the sprint is short and the operator clears space by ending one of the advisory engagements first. A practice that wants to scale past those numbers needs the productized ladder, not more retainers.
Why are retainers being sunset if the math works for the operator?
The math works for the operator's current quarter, not for the practice's third year. A retainer-only practice caps at the operator's available hours and cannot scale beyond that without hiring, which converts the practice into an agency and changes the business model entirely. Retainers fund the building of the productized ladder, then sunset when the ladder is producing the revenue retainers used to.
Where does the time-footprint data come from?
From my own scheduling logs across the last two years of fractional engagements, including an ops-lead seat I held in regulated healthcare. The bands are observed averages with quarter-to-quarter variance, not theoretical estimates.
Sources and specifics
- The four engagement structures (sprint, advisory, ops-lead, bridge) are the four products this practice currently sells. Each has a distinct proposal template, scope-of-work skeleton, and close-rate profile.
- Time-per-week footprints are observed averages from operator scheduling logs across 2024-2025: sprint 14-18 hrs, advisory 2-3 hrs (excluding context-switching tax), ops-lead 18-22 hrs, bridge audit 8-12 hrs.
- A fractional senior operator seat I held in regulated healthcare ran in the ops-lead band at roughly three working days per week of effective time.
- Retainer engagements (advisory and ops-lead) inside this practice sunset 2026-12-31. The permanent revenue model runs through the productized ladder.
- Portfolio simultaneity caps come from observed quality drops across multi-engagement quarters, not from theoretical capacity planning. The numbers reflect what actually held up under load.
