I have been on both sides of the retainer agreement more times than I can count cleanly — as the adviser being retained, and as the person inside an organisation arguing the budget line to a sceptical finance director. Each time, I have noticed the same gap: the people buying the retainer imagine one thing, and the people selling it imagine another, and neither party tends to say this out loud until several months have passed and some small resentment has quietly calcified. What I want to do here is say it out loud. Not to talk anyone into or out of the format — retainers are genuinely useful, under the right conditions — but to give you a clearer picture of what you are actually purchasing when you sign one, because the clarity tends to improve the outcome considerably. This is written from the technology advisory context specifically, though I suspect most of it applies to any professional discipline where the engagement is ambient rather than project-shaped.
The retainer is not a project with a monthly payment plan ¶
This sounds obvious but it needs saying, because a surprising number of engagements begin with exactly that misunderstanding on the client side. A project has a defined output — a system audit, a vendor selection, a technical strategy document — and a retainer is not a project sliced into monthly installments. What a retainer actually purchases is availability, accumulated context, and the ability to apply judgment quickly when something unexpected surfaces. The distinction matters practically: if you hire an adviser on retainer and then immediately hand them a defined deliverable with a deadline, you are using the format incorrectly, and you will feel vaguely overcharged because what you actually wanted was a project fee. The adviser, meanwhile, will feel vaguely anxious because deliverable-shaped work and retainer-shaped work require different internal rhythms. Neither of you will quite be able to name the friction, but it will be there, probably in the fourth or fifth month, when the deliverable is done and the calendar still has twelve slots in it.
What the format genuinely does well ¶
The honest answer is that a retainer is very good at one specific thing: lowering the cost of access to judgment at the moment you need it, rather than at the moment you can arrange a procurement process. Technology decisions have a habit of arriving without warning — a vendor calls to say the contract renews in thirty days, a senior engineer resigns and suddenly the build-versus-buy question you deferred is live again, a board member reads something in an airport magazine and now everyone needs an AI strategy by Thursday. In each of these situations, the value of having someone who already knows your infrastructure, your team's capabilities, your budget constraints, and your political landscape is enormous — and it is value that simply cannot be recreated from a standing start in forty-eight hours. The retainer is, at its best, an investment in that already-knowing. It is most obviously worth it in organisations where consequential technology questions arise irregularly but frequently enough that the cold-start cost of a new engagement each time would be prohibitive.
Where it falls short, and why advisers rarely mention this ¶
The retainer format struggles — sometimes badly — when the organisation does not have a culture of using advisory relationships proactively. I have sat on retainers where three months passed and the client contacted me twice, both times apologetically, as though they were interrupting something important. By month five they quietly stopped scheduling check-ins because they felt they had nothing to bring to the table. This is partly a failure of expectation-setting at the start, but it is also a structural feature of the format: retainers work best when the client already has enough internal maturity to know what they do not know and to articulate it into a conversation. Organisations in very early stages of building technology capability, or those in genuine operational crisis mode with no bandwidth for reflective advisory conversations, tend to get poor value from retainers regardless of how good the adviser is. The other failure mode worth naming honestly: some advisers use the retainer as a comfortable revenue line that demands very little of them, showing up to monthly calls without doing any background thinking, offering the same broad observations they offered to the last three clients. This is not universal, but it is common enough that you should ask, before signing, what the adviser does with the retainer hours that are not directly client-facing.
The question of hours, and why that framing is usually wrong ¶
Most retainer agreements specify a number of hours — eight hours a month, sixteen, whatever the number — and then everyone spends some energy worrying about whether those hours are being used. I have come to believe that the hours framing is almost always the wrong unit of measurement for advisory work, even though it is the most practical one to put in a contract. The actual value delivered is rarely proportional to time logged. An adviser who has been thinking about your cloud migration in the background for three weeks, notices a relevant case study, and sends you a four-paragraph email on a Tuesday afternoon may deliver more genuine value than four hours of structured call time. Conversely, an adviser who bills a full hour on a call where you talked mostly about industry gossip has technically fulfilled the contract but has not done much. What you should be tracking instead is whether your decisions are better-informed, whether surprises are arriving with more lead time, and whether your team's thinking about technology problems is getting sharper over time. Those are harder to measure but they are the actual outputs.
How to decide whether a retainer is the right structure for your situation ¶
The question I would ask is this: how frequently do consequential technology questions arise inside your organisation, and how much does it cost you, in time and in quality of decision, to not have immediate access to someone who understands your full context? If the answer is that significant decisions come up two or three times a year and they are reasonably predictable, you are probably better served by commissioning discrete project work when you need it. The overhead of maintaining a retainer relationship — the monthly calls, the onboarding investment, the ongoing communication — may not justify itself against that frequency. But if the answer is that technology questions are surfacing constantly, often urgently, and often at the intersection of technical and organisational factors that an outside specialist would need months to understand before being useful, then the retainer's core value proposition becomes very clear. There is also a threshold question about internal capability: organisations with strong internal technology leadership often use retainers most effectively as a sounding board and a source of outside perspective, rather than as a substitute for expertise they do not have in-house. Both uses are legitimate, but they suggest different things about who you hire and at what fee level.
Making the structure work once you have decided to use it ¶
If you do enter a retainer arrangement, the single most important thing you can do is establish a shared understanding of what good use of the relationship looks like, in a specific and practical way. Not 'we will talk monthly about your technology strategy' — that is so vague as to be nearly meaningless. Better: 'we will hold a ninety-minute call on the third Tuesday of each month, where you will bring the two or three live technology questions that are actually on your mind, and between calls I will monitor relevant developments in the areas we have identified and flag anything that seems directly relevant to you.' That specificity makes it easier to evaluate whether the arrangement is working, easier for the adviser to prepare usefully, and easier for you to show internal stakeholders what the budget line is actually purchasing. I would also suggest building in a formal review — not an awkward performance review, but a structured conversation — at the six-month mark, where both parties say honestly what has been useful and what has not. Most retainers that end badly do so because neither party called this conversation early enough.
A note on the asymmetry of information between buyer and seller ¶
Advisers know much more about how retainers work in practice than the organisations buying them, and this asymmetry deserves acknowledgment. An experienced adviser has seen dozens of these engagements. They know which organisations get good value and which do not, and they often have a reasonable sense of which category a new client is likely to fall into. If you are on the buying side, it is entirely reasonable to ask an adviser you are considering to give you their honest assessment of whether this format is likely to serve you well — and to be mildly suspicious of any adviser who answers that question with unconditional enthusiasm. The honest answer will contain some uncertainty, some conditions, some things that would need to be true for it to work. That honest answer is also, incidentally, your first data point about whether this is someone whose judgment is worth paying a monthly fee to access.
The retainer format is not a product with guaranteed specifications. It is a relationship structure, and like most relationship structures it performs well when both parties understand what they have agreed to and badly when they do not. The clearest thing I can say after years of working inside and alongside these arrangements is that the conversations worth having about them tend to happen before the contract is signed, not after. That is probably true of most things, but it is especially true here, where the deliverable is judgment and the measurement is always slightly uncomfortable.