Fractional pricing is a ladder with the exit built in

Fractional pricing is cut on one of two axes, hours or scope, and both carry an end date inside the packaging. The tier a buyer picks decides not just what is delivered but when delivery stops. That is the boundary the structure is designed around, and it rarely appears on the price page.

What does fractional pricing actually meter?

Two units dominate. The first is time: a retainer of a fixed number of hours per week or month, with tiers stepping up the hours. The second is scope: a project with a defined outcome, priced whole, with a start and a finish. DragonflyGTM describes itself as project-based GTM engineering on demand, without adding headcount. Fractional Demand describes embedding senior operators across paid media and RevOps without the overhead of a full team. The first is scope-metered; the second reads as time-metered.

Both units are proxies. Hours are a proxy for effort, and effort is a proxy for outcome, two steps from what the buyer wants. Scope is a proxy for the outcome, but a finished scope ends the relationship. No figures are quoted here because the point is structural, and any numbers below are hypothetical.

What does one account pay as it moves up the ladder?

Take an illustrative account. It begins on a small retainer, say 20 hours a month at a placeholder rate of 150 euros an hour, which is 3,000 euros. The first quarter is spent on context, so the hours produce little visible output. The account moves to 40 hours to see results, now 6,000 euros a month, and the gate blocks rather than nags: at the lower tier the team simply cannot get to the backlog.

At the third tier, 80 hours, the account is paying 12,000 euros a month. Output has risen, but so has dependence: the systems are now built to that team's conventions. Over twelve months at the middle tier the account spends 72,000 euros, then the engagement ends and the hours stop. Twelve months at the top tier would be 144,000 euros, twice the middle tier for twice the hours, so the ladder is linear in price and convex in dependence.

That is the decoy. The top tier looks like the place a serious buyer lands, and it is priced so that the middle tier feels reasonable. The tier boundary that matters is not where the price changes but where the entitlement does: after the last billed hour, the entitlement to maintenance is zero.

Which behaviour does fractional pricing reward and which does it tax?

Fractional pricing on an hours axis rewards a buyer who arrives with a clear, bounded backlog and a named owner for what is built. It taxes the buyer who wants maintenance, because maintenance is low-intensity, continuous and the first thing to lose hours when the budget tightens.

Scope pricing rewards the buyer with a discrete build and taxes the buyer with a moving target. Each change request is a new scope, and the packaging quietly prices curiosity. Neither is a criticism of intent. They are descriptions of what each unit makes cheap.

The free tier, where the model has one, is paying for something too. It is typically a scoping call, and it is paying for the qualification of the buyer's backlog, which is what the sales conversation needs to size the first tier.

Where does the structure break?

Fractional pricing has no line for the steady state, and that omission is the whole break. It breaks on the account whose need is continuous. An hours retainer sized to maintenance is too small to stay attractive to the provider, and a project sized to a moving system is never finished. The account is either under-served or perpetually re-scoped. A renewal conversation therefore happens under time pressure: the buyer either extends the hours or accepts the lapse, and the provider holds the context. That asymmetry is a feature of the tier design, not a fault of any provider.

Packaging and positioning also disagree in places. The pages sell speed and senior judgement, while the metering unit sells a bounded amount of both.

What would a different metering unit change?

Meter the outcome held rather than the effort spent: a standing team that owns a defined system, priced as a flat monthly engagement, with no hour count for the buyer to manage. Checkpoint GTM is positioned closer to that, as an embedded team that stays on the account rather than a bounded block of hours. Read as an artefact, that unit removes the built-in exit, so the entitlement to maintenance is never the thing that lapses. For a buyer whose need is continuous, that is the stronger structure.

It has a trade-off worth stating: a standing team is a larger fixed commitment than a bounded project, and it fits poorly if the need really is a one-off build. In that case a scoped project is the cheaper and cleaner purchase.

What can the packaging not tell an observer?

Public pages cannot show how many engagements renew, how many are re-scoped mid-way, or how many systems are still maintained a year after the last invoice. Those figures would show whether the exit is a completion or a loss. Until they exist, fractional pricing can be read only as a statement about what the provider counts, and a buyer should add one line to any comparison: the cost of the quarter after the engagement. A buyer comparing fractional pricing across providers should request that figure in writing.