Retainer vs. project-based pricing: which should you choose?

Every freelancer eventually asks a long-term client: "should this be a retainer?" The honest answer depends on how predictable the work is, not on which model sounds more professional.

Project-based pricing works when

• The scope has a clear start and end (a website build, a brand identity, a one-off campaign)
• You can estimate effort accurately enough to quote a fixed price without losing money on scope creep
• The client relationship is new and neither side is ready to commit to an ongoing arrangement

A retainer works when

• The work is ongoing with no defined end date (maintenance, monthly content, continuous support)
• You want predictable revenue instead of re-selling the relationship every few weeks
• The client wants priority access to your time without negotiating a new scope each time

The revenue-predictability argument

A handful of retainer clients gives you a predictable revenue floor each month, generally described as MRR (Monthly Recurring Revenue). That floor makes it much easier to plan hiring, take a slow month in stride, or simply sleep better. Project work alone means every month starts at zero.

Making the switch

If a project client keeps coming back with small, similar requests, that is usually the sign to propose a retainer instead of quoting each request separately. In practice this just means setting up a recurring invoice for a fixed monthly scope and letting it bill automatically instead of re-invoicing by hand every time.