What a monthly technology retainer should actually cover

The two get sold under the same word and they are different purchases. A support contract is insurance: something breaks, somebody fixes it, and in a good year you use almost none of it. A retainer is capacity: somebody who knows your business is looking at it every month whether or not anything has broken.

That distinction decides what you should expect to see. If the only thing arriving each month is a ticket queue that stayed empty, you are paying for insurance and should price it as insurance. If what arrives is work you did not have to ask for, the fee is buying something else.

The practical test is whether the provider brings you things. A month with no incident and no proposal is a month where nobody looked.

Nearly every provider needs software to deliver the work: something to run automations on a schedule, something to answer questions from your documents, something to hold your compliance record, something to keep your reporting. There are three ways that gets charged, and they are not equally good for you.

The first is that you buy the subscriptions and they configure them. You end up with four vendor relationships, four renewal dates and four sets of terms, and the provider's fee is genuinely just their time. This is honest and it is the most work for you.

The second is that they resell you the same subscriptions with a margin. Ask what the margin is. A firm that earns more when you run more software is being paid to recommend more software, and you will not be able to tell the good advice from the profitable advice.

The third is that the software is theirs and it is inside the fee. That removes the incentive problem entirely, and it introduces a different question worth asking directly: what happens to the record if you leave. Our own retainer is the third kind, and the honest answer to that question is the one you should insist on from anybody.

Compliance is the part that gets left out, because it is the part nobody enjoys and it does not demo well. It is also the part with dates attached.

Article 4 of the EU AI Act has applied since 2 February 2025 and asks you to take measures supporting AI literacy among the staff who use AI on your behalf. There is no prescribed course, no certificate and nothing to buy, which is exactly why it gets forgotten: it is cheap to satisfy and invisible until somebody asks. Any policy drafted before late July 2026 overstates it, because the Digital Omnibus reworded it from a duty to ensure a level into a duty of effort.

The European Accessibility Act has applied in Ireland since 28 June 2025 through S.I. No. 636 of 2023. If consumers can buy from you online you are inside it, and the penalties at Regulation 32(6) run to €60,000 or eighteen months on indictment, with Regulation 33 reaching a director who consented to the offence.

The high-risk parts of the AI Act moved out to 2 December 2027 and 2 August 2028. That is the one worth knowing about precisely, because most advice written before August 2026 still carries a date that has passed, and a provider quoting you an urgent 2026 deadline for high-risk obligations is reading something out of date. Whether the Act reaches you at all takes about two minutes to establish.

A named person who has met your team, rather than a queue. The value of a retainer is somebody carrying context between months, and a rotating pool of engineers cannot do that whatever the response time says.

Something written down. A month that produced no artefact (no procedure, no record, no measured figure) is a month you have no evidence of, and the first time that matters is when a customer's procurement questionnaire arrives and you have to answer forty questions about how you operate.

A number you did not have before. Reporting is the part clients most often already own and cannot reach: the figures are in the ad account, the accounts package and the inbox, and the work is assembling them reliably rather than discovering them.

And a standing invitation to stop. A provider unwilling to tell you when a piece of work is not worth doing has an incentive problem, whatever the contract says.

If you have somebody internal whose job this already is, you do not have the problem a retainer solves. You may have a capacity problem, which is a different purchase and usually a project.

If what you need is one thing built and then left alone, a site or an integration or a dashboard, buy that, take the handover, and do not sign a monthly fee to maintain something that does not change. A good provider will say so.

And if the fee is a large share of what the work is worth, the arithmetic does not survive. That applies to ad management below a certain spend, and it applies to us: it is the reason we turn that work down rather than take it and hope.

There is also money available for the first piece of work. The grants that are actually open will cover part of a discovery engagement, which changes the decision from your own money to a co-payment.