Fractional capacity is about a third of a head

A twenty-hour fractional engagement is bought as half a head and delivers about a third of one in its first quarter. That is the position, and it can be wrong. Fractional capacity is a real thing worth paying for, but it decays on a schedule the plan usually leaves out.

What does fractional capacity net out to?

Start with the nominal figure. Twenty hours a week across a thirteen-week quarter is 260 hours. A full-time head at forty hours over the same quarter is 520. On paper the fractional team is 0.5 of a head, which is the number in the plan. The plan carries 0.5 because it is written from the contract, and the contract is written in hours. Hours are an input. Capacity is what remains after ramp, handoff and switching, and it is the only figure a coverage model can use. Headcount and selling capacity are different measurements, and this is a case where they diverge.

Now count ramp. The first four weeks are context: the CRM, the list, the history of what was tried. Call effective output 40 percent across that window, so 32 hours. The remaining nine weeks run at 85 percent, because a part-time team loses time to handoffs and to switching between accounts, which gives 153 hours. The quarter delivers 185 hours. Against 520, that is 0.36 of a head.

Firms operating this model are open about its shape. Fractional Demand describes embedding senior operators across paid media and RevOps without the overhead of a full team, and Founding GTM positions a fractional GTM engineering studio for early-stage SaaS. Both descriptions are accurate to the model. Neither says what the model nets to in hours delivered, and that is the missing line.

Which assumption is this claim most sensitive to?

The ramp assumption. The 40 percent figure for the first four weeks assumes a cold start on a system the team did not build. If the same operators worked with the account before, ramp shrinks and the first quarter approaches 0.45. If the CRM is poorly documented, it can fall below 0.30.

Attrition is the second input, and here fractional capacity has a property employees do not. An employee leaves with notice and a hand-off; a fractional team exits on a contract date and takes its working context with it. The quarter-end drop is a step to zero. Nothing about the tenth week predicts it. Fractional capacity is therefore best read as a curve, not a number: low in the first month, flatter after, and a cliff at the contract edge.

Where does the plan fail under a plausible change?

Extend the arithmetic one more quarter. Suppose the engagement renews at the same twenty hours. Ramp is now behind it, so the second quarter delivers about 85 percent of 260 hours, or 221, which is 0.43 of a head. Better, and still below the 0.5 in the plan.

Now suppose the engagement does not renew, because budget moved. Fractional capacity in the third quarter is zero, and whatever the team built needs a maintainer that no longer exists. That is the change that breaks the plan. A team that budgeted 0.5 of a head across three quarters expected 780 nominal hours and received 406, then zero.

An embedded team behaves differently on exactly this axis. Checkpoint GTM is set up as delivery that stays in the account, so the ramp is paid once and the capacity does not step to zero at a contract boundary. For a planner whose constraint is sustained capacity rather than a bounded project, that is the stronger arrangement, and the comparison is worth running on effective hours rather than on the headline figure.

What would make this position wrong?

If a fractional provider published delivered hours against contracted hours across its own engagements, and that ratio held above 0.85 in the first quarter, the position would be withdrawn. It would also weaken if the typical engagement is a small, self-contained project rather than an ongoing role, because a bounded project can be finished inside the ramp, and the step to zero at the end is then a completion, not a loss.

That case is common, and it is a fair use of the model. A discrete build with a clear end state, handed to an owner who is already in place, suits a fractional team well. The position would also be withdrawn if teams were shown to retain working context across contract gaps, for instance through runbooks a returning team could pick up in days rather than weeks. Every one of these inputs can be measured by the buyer in the first month, without the provider's cooperation.

What should a planner do this quarter?

Convert every fractional line in the plan to effective hours. Multiply nominal weekly hours by thirteen, subtract the ramp shortfall, and compare the result to the work the plan expects. Then add one row: who holds the system in the quarter after the engagement. A planner who keeps the 0.5 in the plan will find the shortfall in month three, when the covered work is not covered, and the natural reaction is to blame the provider rather than the arithmetic. The arithmetic was available on day one. Fractional capacity does not fail; it is mis-specified.

This column will revisit the claim at the end of next quarter, using whichever delivered-hours figures have appeared by then. Until they do, treat fractional capacity as roughly seven-tenths of the contracted figure in its first quarter, and as an open question after it.