Retainer

A retainer is a subscription to a vendor’s time. You pay every month; in return you get a defined number of days or a defined team capacity. The exact scope shifts; the availability does not.

Retainers work well when the work is ongoing and the priorities change too fast for a Statement of Work to keep up. Product teams use retainers for design partners, engineering teams use them for fractional senior roles, and almost every legal counsel arrangement is a retainer. In Austria a retainer is usually structured as a Dienstvertrag or freier Dienstvertrag, since what you are buying is reserved availability and judgement rather than a fixed work product.

The risk is the inverse of T&M: the vendor gets paid even when there is no work. Smart customers attach a “reasonable use” clause and review the retainer quarterly to confirm capacity is being used. If utilisation is below 60%, the retainer is the wrong shape and you want a per-engagement SoW instead.

Worked example: a startup puts a senior advisor on a 10-day-a-month retainer “to be safe”. For two months it is fully used; then the launch ships and the work drops to two days a month, but the invoice does not. They are now paying for eight idle days. The fix is not to cancel the relationship, it is to right-size it: drop to a smaller retainer plus the option to scope a fixed-price build when a real deliverable appears. Healthy retainers sit at 70 to 85% utilisation; below that you are buying insurance, above 95% you are running the vendor as staff with no slack for the work that matters.

The honest trade-off is predictability versus efficiency. A retainer buys you a known monthly cost and a reserved senior brain, at the price of paying for capacity in the quiet months. Related: Fractional CTO Austria runs a weekly retainer you can cancel any week, which removes most of the lock-in that makes traditional retainers risky.