It is month seven. The architecture is settled, the first two engineers are hired and shipping, and the next big decision, the Series A technical story, is a quarter away. Your fractional CTO is still on the full retainer and you are looking at the invoice wondering whether you could put the whole thing on ice for three months and pick it back up in the spring.
The short answer: yes, a pause can be fair, but a full stop with zero fee is rarely the right shape. What usually works is a step-down to a small holding retainer, agreed in advance, with a defined restart date and a defined restart notice. A clean pause with nothing paid tends to cost you more on the way back than it saved on the way out, because the person you paused is now booked elsewhere and the context has gone cold.
This is not legal advice. It is how I think about pauses from inside the engagements, including the ones where I was the person being paused.
Why founders want to pause
The impulse is almost always reasonable. The common versions I see:
- The build phase is over. The big decisions are made, the team is executing, and the founder feels they are paying senior rates for a calm period.
- Cash is tighter than planned. A raise slipped, revenue is lumpy, and leadership spend looks like the easiest line to cut for a quarter.
- The founder is heads-down on sales. Nobody is asking engineering questions because the company's attention is elsewhere.
- A full-time hire is coming. There is an offer out to a VP of Engineering who starts in ten weeks and the founder does not want to pay twice.
The first and third are the ones where a pause most often goes wrong, because the quiet is real but temporary, and the next decision arrives on its own schedule, not yours.
What actually happens when you pause to zero
A fractional CTO who runs three to five clients does not sit idle for your pause. Within a few weeks that capacity goes to someone else, because it has to. When you come back, three things are true.
First, availability has changed. You may wait a month for the same number of days you used to get immediately. If the thing that ended your pause was urgent, a security questionnaire from an enterprise buyer, a lead engineer resigning, an investor asking for a technical memo, the wait is the expensive part.
Second, the context has decayed. In three months your team has merged hundreds of changes, made small architecture choices without review, and maybe swapped a vendor. The person coming back has to re-read before they can judge. I would expect two to four working days of re-orientation after a quarter away, and that is billed time.
Third, nobody was watching. The value of a working fractional CTO is not only the decisions they make in meetings. It is the drift they catch: the engineer quietly adding a second database, the agency inflating hours, the cloud bill creeping up 8 percent a month. A full pause turns that off completely.
The structures that work better
The holding retainer
Drop to a small fixed fee, often in the range of 15 to 25 percent of the normal retainer, that buys three things: a monthly hour or two of review, an agreed response time for real emergencies, and a guaranteed slot when you restart. It keeps the person warm and keeps someone looking at the drift, without paying for decisions you do not need.
A defined step-down, not an open-ended pause
Write the dates in. "Holding retainer from 1 February to 30 April, full scope resumes 1 May unless either side gives 30 days' notice to end the engagement." An open-ended pause is how engagements quietly die, and then you discover you are starting a search from scratch in the middle of a raise.
A restart notice both sides respect
If you want to come back early, how fast can they ramp? Two weeks is reasonable. If the contract is silent, you are relying on goodwill, and goodwill competes with the client who did not pause.
Bank the work, do not lose it
Before the step-down, ask for a short written state of the world: open risks, decisions pending, what to watch, which numbers to check monthly. This is the same discipline as a good handover, and it is what makes the restart cheap. It also protects you if the pause turns into an exit.
When a pause is the wrong call
Do not pause in the quarter before a raise. Investor diligence questions land early and unevenly, and the fractional CTO is often the person who answers the architecture and security sections. Pausing then saves a retainer and risks the round.
Do not pause when a key engineer is new, under three months, or when an agency is mid-build. Those are exactly the periods where unsupervised drift is most expensive.
Do not pause because the engagement is not working. That is an exit dressed up as a pause, and it is kinder and cheaper to end it properly. When to end a fractional CTO engagement covers that decision.
And be careful pausing to wait for a full-time hire. Offers fall through, and start dates slip. A step-down until the new leader's first day, followed by a paid two-week overlap, is the safer pattern.
When a pause is genuinely right
If the team is senior, the roadmap is stable, the next big decision is more than a quarter out, and you have a clear restart trigger, a step-down is a sensible use of money. I would rather a client step down to a holding retainer for a quarter than keep paying full rate for decisions that do not exist. If you are routinely using a fraction of the days you pay for, the honest fix may be a smaller standing retainer, not a pause. What to do when you barely used your fractional CTO this month is the month-by-month version of the same question, and what a retainer actually buys each month is worth rereading before you decide what you can live without.
How to raise it
Raise it early, ideally a month before you want it, and frame it as a plan rather than a cut. "The next three months are execution, not decisions. Can we drop to a holding retainer with monthly review and come back to full scope on 1 May?" Most good fractional CTOs will say yes, because a predictable step-down is far better for them than a surprise cancellation. If they refuse any reduction at all, that tells you how they think about the engagement.
If cash is the real driver, say so. Paying a fractional CTO when cash is tight covers the options beyond a pause. My own terms, including how I handle step-downs, are on the pricing page. If you want to talk through whether your next quarter is genuinely quiet, book a call.
FAQ
Can I pause a fractional CTO retainer without paying anything?
You can ask, and some will agree, but expect to lose priority access and to pay for re-orientation when you return. A small holding retainer is usually cheaper over the full cycle.
How much should a holding retainer cost?
Commonly 15 to 25 percent of the full retainer, in my experience. It should buy a monthly review, an emergency response time, and a guaranteed restart slot. If it buys nothing specific, it is just a fee.
How long should a pause last?
One quarter is the practical maximum before context decay makes the restart expensive. Longer than that, treat it as an ending with a possible future re-engagement.
Should I pause before hiring a full-time CTO?
Step down rather than stop, and plan a paid overlap of a week or two once the new leader starts, so the context transfers to a person rather than a document.