"Fractional" is a word that covers four different products. Most of the confusion inside the practice, and most of the blown engagements, come from selling one shape and delivering another. Here are the four shapes I actually sell, the commitment each one carries, and the failure mode each one creates when you get it wrong.
This article is part of the running-a-fractional-practice cluster. The hub covers the full architecture; this piece goes deep on the shape question.
Why the shape matters more than the title
When a buyer says "we want to hire a fractional CTO," they are naming a title. The title tells you almost nothing about the shape of the engagement. Two fractional CTOs at the same hourly rate can be selling radically different products. One shows up for a 60-minute advisory call each week and reviews architecture docs. The other runs the engineering team's standup, owns the deploy pipeline, and makes hiring decisions.
Same title. Different product. Different price. Different failure mode.
The shape question is: what am I on the hook for between my touchpoints? The four shapes below answer that question four different ways. Every engagement I run is one of these, and the proposal names the shape so the buyer cannot confuse it later.
Shape 1: The 90-day installation sprint
The installation sprint is the cleanest product in the practice. It has a fixed start, a fixed end, a named deliverable, and a fixed price. The buyer is paying for a specific system to exist in their business 90 days from the signature date. The engagement ends when the system ships.
The closing argument in the sales conversation is straightforward. "In 90 days, you will have a working server-side tracking implementation with GA4, Meta CAPI, and Klaviyo reconciled against Shopify order data. Here is what ships in weeks 1-4, 5-8, and 9-12. Here is what you are responsible for. Here is the fixed price." The buyer either says yes or no. There is no hourly negotiation.
The sprint works because the scope is known before the engagement starts. That means the sprint cannot be the first engagement of a pattern. It has to be pattern number three or four, after you have run the work enough times to know exactly what ships when. The first time you try to sprint a new capability, you almost certainly underestimate one phase and the 90-day clock punishes you for it.
The failure mode is scope creep. If the buyer asks for a fifth dashboard in week 6, and you say yes without moving the delivery date, you lose the sprint. The sprint survives by being ruthless about the line between "what's in scope" and "what's the follow-on engagement." The phrase I use is: "That's a great addition. It's a 30-day follow-on we can scope in week 10."
Shape 2: The weekly advisory retainer
The advisory retainer is the opposite shape. There is no deliverable. The buyer is paying for access to senior judgment on a recurring cadence. Usually one or two hours per week, plus async responsiveness during the engagement window.
The closing argument is: "You have a senior team that knows what they're doing. You don't have someone at the table who has seen 20 versions of the decision you're about to make. For $X/month, I am that person. I do not ship code. I do not manage people. I review, challenge, and sign off." The buyer hires advisory retainers when they have execution capacity but lack senior pattern-matching.
The retainer works because the cadence is light enough that the operator can hold three or four simultaneously without conflict. The failure mode is severe. The retainer decays when the buyer stops bringing real decisions to the weekly call. Once the calls become status updates, the engagement has already ended; the buyer just hasn't canceled yet.
I have written separately about why retainers are a trap and productized work is structurally better. Advisory retainers have a narrow legitimate use case. Outside that case, they become the retainer trap.
Shape 3: The fractional ops-lead seat
The ops-lead seat is a category-specific leadership seat held part-time. The operator holds a named role inside the org chart for the engagement window. Fractional head of growth. Fractional director of platform. Fractional VP of marketing ops. The buyer is paying for authority inside a specific function, not for advice and not for a deliverable.
The closing argument is: "Your company needs a senior head of [function] but you cannot justify the full-time hire yet. For the next two quarters, I own the function. I run the team that exists. I hire the next seats. I report to the CEO. I sign off on budget. I am accountable for the outcome." The buyer is trading authority for time.
The seat is the highest-commitment shape in the practice. Usually 2 or 2.5 days a week. The cadence is dense enough that the operator can only hold two of these seats simultaneously without quality dropping. Sometimes only one.
The failure mode is dual: either the authority is not real, or the exit is not planned. When authority is not real, the operator can make decisions in the weekly meeting and watch the full-time team override them the next day. When the exit is not planned, the engagement drifts from "six-month fractional seat" to "permanent fractional seat that we keep renewing because finding the right full-time hire is hard." The second failure is softer than the first but more damaging long-term, because it converts the operator's practice into a de facto full-time role.
Shape 4: The audit-to-implementation bridge
The bridge is a two-phase engagement. Phase one is an audit: a fixed-scope, fixed-price diagnostic of the buyer's current state, delivered in 2 to 4 weeks. Phase two is implementation, priced and scoped at the end of phase one based on what the audit found.
The closing argument is: "You don't know what's actually broken. An hourly consultant will tell you they need to explore before they can scope. I'll give you a fixed-price diagnostic in three weeks that tells you exactly what's broken and what it costs to fix. Then you decide whether to implement, and whether to hire me or someone else for the implementation." The buyer is paying a small fixed amount for clarity before committing larger amounts to a direction.
The bridge works because the audit phase is itself a productized deliverable (it is the sprint shape compressed into 3 weeks with a scoped deliverable). The transition to phase two is a decision point, not a continuation. The buyer chooses to continue or to stop. Either outcome is a clean engagement.
The failure mode is when the audit and the implementation are priced and pitched as a single sale. At that point, the audit stops being a diagnostic and becomes a sales call that the buyer pays for. The buyer can feel it. The diagnostic loses credibility because the operator is obviously writing toward a continuation. Separating the two sales is what makes the bridge work.
How to tell which shape you are actually selling
| Dimension | Sprint | Advisory | Ops-Lead | Bridge |
|---|---|---|---|---|
| Deliverable | Named system ships | None | Function outcome | Audit, then decision |
| Commitment | Fixed price, fixed end | Monthly, open-ended | Quarterly, authority | Two-phase, checkpointed |
| Cadence | 2 days/week | 1-2 hours/week | 2+ days/week | Batched, then sprint |
| Primary failure | Scope creep | Decay to status-reporting | Authority not real | Bundling sales into audit |
| Portfolio math | One sprint at a time | 3-4 simultaneous | 1-2 simultaneous | Overlaps with anything |
The shape is usually clear from the first intake question: what does success look like at the end of this engagement? If the buyer names a system, it's a sprint. If the buyer names a cadence, it's advisory. If the buyer names an outcome tied to authority, it's an ops-lead seat. If the buyer can't name any of them, it's a bridge.
The mistake of selling one shape and delivering another
The most expensive mistake in a fractional practice is selling an advisory retainer and then delivering ops-lead work because the buyer keeps asking for it. The hourly rate that was reasonable for advisory becomes terrible for ops-lead. The operator burns out filling the gap. The buyer is happy in the short term because they're getting more for less. The engagement ends badly in month four when the operator realizes they've been running a 2-day-a-week seat at advisory pricing and raises the rate, at which point the buyer feels the rate change as a betrayal rather than a correction.
The prevention is simple. Name the shape at proposal time. Write the inclusions and exclusions against the shape. When the buyer asks for something outside the shape, name it as a follow-on or a change in shape, priced accordingly.
“The most expensive mistake in a fractional practice is selling one shape and delivering another.
”
The shape also dictates who you can take on simultaneously. The cost of switching between client stacks changes dramatically based on shape mix. Four advisory retainers is a sustainable portfolio. One ops-lead seat plus three advisory retainers is sustainable. Two ops-lead seats plus a sprint will break most operators in a month.
How pricing tracks shape
Each shape has a different pricing logic.
The sprint prices against the outcome. "What is this system worth to your business in the first year?" Typically a number between $25K and $80K for a 90-day sprint, depending on the buyer's size and the system's leverage.
The advisory retainer prices against the operator's hourly anchor plus a premium for access. Usually $4K to $10K/month for 1 to 2 hours a week of scheduled time plus async access.
The ops-lead seat prices against the full-time equivalent salary of the role, discounted for the fractional nature. A role that would cost $250K/year full-time runs $10K to $18K/month fractional, usually structured as a 2-quarter commitment.
The bridge prices the audit phase as a fixed diagnostic ($5K to $15K) and the implementation phase separately, usually as a follow-on sprint. The bridge's total is not quoted upfront because the implementation scope is unknown until the audit finishes.
All four of these are different products. Trying to put them on a single price sheet flattens the distinctions that matter. The work page shows which of these shapes the practice has delivered recently; the products page shows the productized off-ramps for the sprint pattern.
When to take no engagement at all
Sometimes the right answer is to decline. A buyer whose request doesn't match any of the four shapes is usually asking for a full-time hire with an undersized budget. Taking that engagement means delivering a fifth shape, which is the one that burns you out.
The fifth shape is "fractional as discount." The buyer wants a full-time head of function, cannot afford one, and hopes the fractional version will deliver full-time output for 40% of the cost. It will not. Either the operator delivers 40% output (and the buyer feels shortchanged) or the operator delivers full-time output (and burns out trying). Fractional is not a cheaper full-time hire goes deeper on why the framing is structurally broken. The short version: if the buyer came in thinking of fractional as a discount, the engagement is downstream of a bad frame and will end badly.
Frequently asked questions
Can a single engagement mix shapes?
It can, but only if the mix is named upfront. An advisory retainer that includes a contractually-scoped mini-sprint in month one is fine if both pieces are priced and documented. An advisory retainer that "includes implementation work as needed" is the fifth shape, and it will eat you alive.
Which shape makes the most money?
Per engagement, the ops-lead seat. Per year, usually a mix of one ops-lead seat plus two advisory retainers and a sprint-and-bridge stream. The single-shape practice caps lower than the portfolio.
How do I transition a retainer client into a sprint?
Name the transition explicitly. "Our current retainer is scheduled to end on [date]. I want to propose a 90-day sprint to ship [system] as the follow-on. Here's the scope and price." The key is that the retainer has an end date. Without one, the transition is a sales conversation the client did not ask for.
What if the buyer insists on hourly billing?
Decline or reshape. Hourly billing collapses all four shapes into a fifth one that pays the operator for time instead of for the product. Scoping without hours covers how to reshape the intake. If the buyer insists on hourly after that conversation, they're a bad fit for a fractional practice.
Which shape should I start with?
The bridge. The audit phase is the smallest commitment, produces real output the buyer can act on, and creates a natural transition to a sprint or retainer based on what the audit finds. Starting every new engagement with a bridge is a strong default for a practice still developing its sprint patterns.
Sources and specifics
- The four shapes are the four products I currently sell. Each has a distinct proposal template, SOW skeleton, and close rate.
- Sprint price band ($25K to $80K) comes from the sprints I've run over the last two years. The range reflects buyer size and system leverage, not hours.
- Advisory retainer price band ($4K to $10K/month) is the range for 1 to 2 hours/week plus async access. Above $10K the buyer is usually better served by a different shape.
- Ops-lead pricing (40% to 50% of FTE cost per day/week) mirrors what senior operators in DTC and martech charge across the practices I've seen.
- The bridge pattern is documented in detail in the sprint scoping article and the productized sprint article. Both are in this cluster.