Retainers vs. projects

A project has a defined start, a defined end, and (usually) a fixed scope agreed before any work begins; it suits a clear, bounded piece of work like a new website, a redesign, or a specific feature with well-understood requirements. A retainer has none of that structure by design: it's ongoing capacity, used flexibly on whatever comes up, for as long as the arrangement continues.

The practical difference shows up most clearly once a business already has a working site or product and needs a steady trickle of changes, fixes, and small features rather than one big, bounded piece of work. Scoping and quoting a brand-new project for every individual change (a new form field here, a small integration there) adds overhead that often costs more in admin time than the work itself. A retainer removes that overhead: the capacity already exists, so smaller pieces of work simply get picked up without a fresh proposal each time.

That said, a retainer isn't the right tool for everything. A substantial new feature, a major redesign, or a genuinely large piece of net-new work usually benefits from being scoped and quoted as its own project, with its own timeline and a fixed price, even for a business that also holds a retainer for everything else. We'll say so plainly if something on a retainer's plate has grown into project-sized work, rather than quietly absorbing it into ongoing hours and stretching the arrangement past what it was meant to cover.

Cost comparison depends heavily on volume and predictability. A business with occasional, unpredictable small changes is usually better served by ad hoc hourly work or a smaller retainer block; a business with a steady, ongoing stream of changes gets a lower effective hourly rate from a larger fixed monthly block. Neither is inherently better; it comes down to how much ongoing development work a business actually generates, which is exactly what the initial call is for.

In short: a project is the right tool for a single, bounded piece of work with a clear end point; a retainer is the right tool for ongoing, open-ended development needs that don't have a natural stopping point. Many clients use both: a project to build something new, then a retainer afterwards to keep extending and maintaining it without starting a new proposal every time.