Development retainer: what to agree

A development retainer is an agreement in which the client pays a software agency a fixed amount every month for the team's availability and an agreed volume of work, without a separate quote for each task. The payment recurs even in a quiet month, so the value of a retainer depends almost entirely on what it defines and on what gets reported.

What a retainer usually covers

A good retainer defines four things, not only an amount:

Volume: hours per month, or a list of included kinds of work, such as maintenance, bug fixes and small changes;
Availability: how fast a request gets a response, and in which hours;
What is not included: for example, large new features, which get a separate quote;
What happens on overrun: billing at an agreed hourly rate, or notice in advance and approval.

Retainer versus hour bank versus project

With an hour bank the client buys a quantity of hours and uses it until it runs out. With a project the client pays for a defined deliverable. With a retainer the client pays for capacity: a team that knows the system and is available to work on it every month.

The advantage of a retainer is continuity: the same people and the same knowledge, without looking for a contractor each time. The downside is that in a month with little need, the client paid for availability that went unused.

Where retainers break

"Everything is included". Sounds generous on signing day, and by the third month each side reads it differently.
A report without tasks. A fixed amount with a one-line report eventually raises the question "what are we paying for".
Quiet months that go unreported. Even in a quiet month it is worth showing what was done: updates, checks, error monitoring.
An overrun discovered on the invoice. If there were hours beyond the agreed volume, the client should hear about it when it happens.
No review point. A retainer that is not revisited every quarter or half year continues out of habit.

How to track a retainer

Tracking is really the monthly report, and it should compare what was agreed with what happened:

how many hours were worked, and on which tasks;
what closed this month and what is still open;
whether there was use beyond the agreed volume, and how much;
what is stuck on the client's side: an approval, content or access that did not arrive.

When the same structure repeats each month, trends are easy to see: a volume that keeps growing is a sign the retainer needs updating, not necessarily that the contractor is overrunning.

What SLAtech Vantage does for a retainer

SLAtech Vantage has no agreement type called retainer. It has what tracking a retainer needs:

hours logged against tasks, with the rate in force at the moment of logging;
recurring payments, such as hosting or subscriptions, recorded separately from hours;
a monthly report by department, which the client sees in the portal and exports to Excel and PDF;
an "awaiting client" status on a task, so what is stuck on the client's side is visible without asking;
on a project where month handover is switched on, the contractor submits the month and the client accepts it or returns it for correction. From submission on, that month's hours are locked for both sides.

Frequently asked questions

What is the difference between a retainer and an hour bank?

With a retainer you pay a fixed amount each month for availability and an agreed volume of work, and the payment recurs even in a quiet month. With an hour bank you buy a quantity of hours in advance and use them until they run out, regardless of the calendar. A retainer suits ongoing, continuous work with the same team; an hour bank suits irregular needs where you want to pay only for what was used.

What should a development retainer agreement say?

At least four things: the monthly volume in hours or kinds of work, availability and how fast requests get a response, what is explicitly excluded and gets a separate quote, and what happens on overrun. It is worth adding what the monthly report contains, on which date it arrives, and when both sides review the agreement again.

Do unused retainer hours roll over to the next month?

It depends on the agreement. In some retainers you pay for availability, so unused hours do not roll over; in others part of them carries over for a limited period. There is no single right answer, but there must be a written answer before work starts, because the question usually comes up in exactly the month when there was little work.

How do you know a development retainer is worth the money?

Compare each month what was agreed with what happened: how many hours were worked, on which tasks, what closed and what stayed open. After a few months in the same structure a trend appears. If actual volume is consistently low, the retainer can be reduced; if it is consistently high, it is better to update the agreement than to pay overruns every month.