A retainer is how software that lives keeps living: the project ends, but the product needs updates, fixes, small features, monitoring and the occasional urgent call. The model reserves a block of time per month — the client keeps an engineer who knows the codebase and stops paying recruitment and re-onboarding every time something is needed.
It pays off when work is steady and unpredictable in shape — the honest test is whether you would otherwise write a new quote every month. The alternative that works for stable systems is a maintenance agreement: monitoring, updates, SLA on response, no feature time. Paying retainer prices for a site that needs four hours a year is the wrong shape.
Related terms
MVP
Minimum Viable Product — the smallest version that tests the real hypothesis, not a cheap version of the whole thing.
Discovery call
The first conversation before any proposal — where scope, budget reality and fit get established instead of guessed.
Social proof
Evidence that others already trusted you — reviews, named clients, numbers — the shortest path past a stranger's scepticism.
The bench this belongs to
Full-stackIf you can describe it, we can build it. React and Next.js on the front, Python or Node behind, Postgres underneath, shipped to somewhere you can afford to run.
