The structural problem with a retainer is that it separates payment from delivery. Once the arrangement is in place, both parties have an interest in it continuing, and the provider's interest is in continuing regardless of whether the remaining work justifies it. That is not a claim about anybody's integrity. It is a description of what the incentive does over time, and it explains why so many retainers persist for years while producing less each quarter.
For a first year business specifically, the arrangement works against what you are trying to build. The objective is a business that runs without external help, with systems you understand and can operate. An ongoing engagement that quietly absorbs the tasks you should be learning produces the opposite, and the dependency is invisible until you try to leave.
The alternative that works is defined projects with a stated outcome and an end date. You know what you are getting, what it costs, and when it finishes. If the result is good and something else needs doing, that is a decision made deliberately rather than a continuation nobody examined.
There is a version of ongoing work that is genuinely appropriate, and it is worth naming so the position does not sound absolute. Anything requiring continuous attention rather than periodic improvement: managing advertising spend that changes weekly, monitoring systems, or handling a volume of requests that genuinely arrives every day. Those are operational rather than developmental, and they suit a different arrangement.
What is not appropriate is a retainer covering advice, availability, or improvements that could be scoped. Those are the arrangements where the monthly invoice arrives whether or not anything happened, and where the honest answer in a given month is frequently that nothing needed doing.
Ask what a retainer is actually buying before agreeing to one anywhere. A specific quantity of work, a stated response time, or a defined set of ongoing tasks is a service. Access, availability, or a general commitment to be there is a subscription to a relationship, and it is worth considerably less than it costs.
Consider what happens when you want to stop, which is the question that reveals the shape of the arrangement. A project ends by finishing. A retainer ends through a conversation nobody wants to have, frequently deferred for months, and the cost of that deferral is the real price of the convenience.
The position here is a preference rather than a rule about the industry. Retainers suit businesses with continuous needs and providers with capacity to fill, and both of those are legitimate. They suit a first year business trying to become self sufficient considerably less well, which is why the work is scoped and finished instead.
Consider what happens to the knowledge when a project ends, since that is the reasonable objection to project work and it has a straightforward answer. Decisions get written down as they are made, accounts are in your name from the start, and the documentation stays with the business rather than with the provider. A project that ends cleanly leaves you able to continue or to bring somebody else in without a handover negotiation.
Ask what happens between projects, since that is the practical question a retainer was answering. The honest arrangement is that questions get answered, small things get looked at, and anything substantial becomes a defined piece of work with a price attached. That covers the genuine need without the standing invoice.