Monthly retainer or annual prepay, the lock-in frame.

There are three ways to run a fractional department engagement, and they sit on a continuum from maximum flexibility to maximum savings. Monthly is the default. The retainer bills monthly, the notice period is thirty days after the first sixty, and the engagement can wind down at any month boundary without penalty. No discount applies, but the optionality is total. Annual prepay is the middle option. You pay twelve months upfront, the retainer drops ten percent, and the engagement is locked for the prepaid term. Twelve-month commit is the maximum savings option. You sign a twelve-month term, you can still pay monthly, and the retainer drops fifteen percent in exchange for the commitment.

The discount curve is real. Ten percent off a Sales sprint at eight thousand a month is nine thousand six hundred a year in savings. Fifteen percent is fourteen thousand four hundred. On a four-function bundle at twenty-five thousand a month, the savings stack to thirty thousand on annual prepay and forty-five thousand on the twelve-month commit. Across multiple years and multiple functions, the difference between paying flat monthly and paying on a discounted term is meaningful runway. The question is when the savings are worth the commitment, and the honest answer changes depending on where you are in the engagement.

We covered the underlying retainer structure in What is a Fractional AI Department. This page is the term-selection decision. The framing is straightforward once you accept that the first ninety days of any engagement is a proof window, and the right term for the first ninety days is almost always different from the right term for the rest of the year.

The first ninety days of a fractional engagement is a proof window. The agents are being tuned against your data, the senior team is learning how to review the output, the operator is calibrating against your voice and your ICP, and the cadence is stabilizing against your weekly rhythm. The proof on whether the model fits your specific shape of company is earned during this window. Until the proof is in place, the right term is the one that preserves the option to wind down without penalty. That is monthly.

The cost of staying monthly through the proof window is the discount you do not get during those three months. On a single Sales sprint at eight thousand a month, three months at monthly versus annual prepay costs twenty-four hundred dollars across the quarter, or about eight hundred a month in foregone savings. That is real money, but it is small money against the cost of being locked into a twelve-month prepay on an engagement that has not yet proven fit. The optionality is worth more than the discount during the proof window.

There is no situation we have seen where a team should commit to annual prepay or twelve-month terms in week one of a first engagement. Even teams with prior conviction on the model, where the bundle commitment is the right move from day one, should run the first three months on monthly billing. The annual prepay decision is correctly made in month three or month four, not in week one. The savings are still available at that point. The optionality is what is no longer available if you committed too early.

Annual prepay is the right conversion at the end of the proof window. By month three or month four, the engagement either fits or it does not. If it fits, the next nine to twelve months are predictable in terms of operating value. The function is producing the output, the senior team is comfortable with the review cadence, and the cash flow model is comfortable with the spend. The ten percent prepay discount becomes free money at that point, because the engagement was going to run for the year regardless and the savings are real.

The honest case for annual prepay is cash flow. The full year of retainer comes out of the bank in one transaction, which is cash that is not available for other uses across the next twelve months. For some teams that is fine because the cash position is comfortable and the year-one plan is locked. For other teams, even a strong engagement is not worth pulling a year of retainer out of the bank in a single transaction, especially in the months leading into a fundraise where preserving optionality on the cash position matters more than the discount. In those situations the twelve-month commit is the better fit because the billing stays monthly while the term locks in the same discount tier.

The structural answer is that annual prepay works for teams with comfortable cash positions, locked year-one plans, and high conviction on the engagement after the proof window. That is most teams by month four if the engagement is going well. The conversion is usually triggered by a calendar event on the founder side, like the end of a quarter or the start of a new fiscal year, rather than by us asking for it. The savings are the same regardless of when in the year the conversion happens.

The twelve-month commit is the right fit for a specific shape of team. High conviction on the engagement after the proof window, but a cash flow model that prefers monthly billing over the lump-sum prepay. Pre-fundraise teams, teams burning through runway against a deliberate growth plan, teams where the CFO has explicit preferences about how cash leaves the business. In these shapes the fifteen percent discount on the run-rate is worth the term commitment, but the billing has to stay monthly to fit the cash flow shape.

The honest filter for twelve-month commit is whether the engagement would have run for twelve months regardless. If yes, the commit is free money on the discount side. If the engagement has any meaningful probability of winding down before twelve months for reasons that have nothing to do with the function fit, the commit is a hedge against a wind-down that should not be on the table. Most engagements past the proof window run for at least twelve months because the function is producing and the senior team has built the operating rhythm around it. But not all do, and the right time to think about the commitment is when the proof is fully in place, not when the savings spreadsheet looks attractive.

The other case for the twelve-month commit is when the team is running multiple functions on the bundle and the cumulative annual savings are meaningful. Forty-five thousand a year on the four-function bundle is a senior engineer salary. At that scale the commitment is usually a clean decision once the proof is in place across at least two of the four functions. The math is real and the conviction is earned.

For teams running multiple functions on the bundle, the term discount stacks against the bundle pricing rather than against the single-sprint rate. The four-function bundle at twenty-five thousand a month becomes twenty-two and a half thousand on annual prepay and twenty-one and a quarter on the twelve-month commit. Annual savings against the cold-monthly bundle rate land at thirty thousand on prepay and forty-five thousand on the commit. Against the cold separate-retainer rate of thirty-one and a half thousand a month, the twelve-month commit lands the full year at two hundred and fifty-five thousand instead of three hundred and seventy-eight thousand. That is a hundred and twenty-three thousand in annual savings against the worst-case starting structure.

The stacking math is the reason most teams converge on the twelve-month commit on the bundle by month six or month eight of the engagement. The savings at that scale are meaningful runway, the engagement has proven fit across multiple functions, and the operating cadence is stable enough that the year-out commitment is a clean decision. The conversion usually happens after the second sprint stabilizes, because by then the founder has seen the model run end to end on two functions and the conviction is broader than a single function would justify.

The honest exception is when the bundle is going to wind down to three functions or fewer during the next year for reasons that have nothing to do with EOI. Maybe one of the functions is going in-house as part of a planned org expansion. Maybe a function is being paused while a different operating shift happens. In those cases the twelve-month commit is the wrong fit because the bundle composition itself is changing, and the term discount is structured against the four-function commitment specifically. We will not push the commit in those situations because it does not fit the operating reality.

A Series A SaaS team running a Sales sprint, conservative on cash but high on conviction by month four. They had three quarters of runway, a clean board update, and an engagement that was producing twenty-five qualified conversations a week. The right term was the twelve-month commit because the cash position favored monthly billing while the discount tier was the meaningful one. Conversion happened in month five. Annual savings of about fourteen and a half thousand landed against the run-rate at the eight thousand a month single-sprint rate.

A bootstrapped fintech team running the four-function bundle, strong cash position, on annual planning. They had a comfortable bank balance, a CFO who preferred to lock annual costs at the start of the fiscal year, and high conviction by month four. The right term was annual prepay against the bundle. Conversion happened in month four. Annual savings of thirty thousand landed against the bundle rate, and the cash flow model absorbed the lump sum cleanly because the team had planned for the spend at the start of the year.

A pre-fundraise growth-stage team running Sales and Content, cash flow under pressure during the run-up to the round. They were on the monthly retainer through the proof window and were considering the discounted terms in month four. The honest recommendation was to stay monthly through the close of the round, even though the proof was in place and the savings were meaningful. The optionality on the cash position during a fundraise is worth more than the discount. They converted to twelve-month commit immediately after the round closed, which was the right sequence for their specific situation.