What you can use retainer hours for

Retainer hours are deliberately broad in scope; they're not tied to a specific feature list agreed up front, because the whole point of a retainer is flexibility to work on whatever matters most as priorities shift. In practice, most retainer work falls into a handful of recognisable categories.

Small features and enhancements are the most common use: a new page or section, an improved form, a small workflow change that makes day-to-day use of a site or product easier. These are typically well-suited to a retainer because they're bounded enough to estimate and deliver within a normal monthly cycle, without needing the overhead of a separate project quote.

Integrations with other systems (connecting a website or app to a CRM, a stock system, an accounting tool, or a booking platform) are another common category. These vary a lot in complexity depending on the other system's own API and documentation, so larger integrations sometimes get scoped as a dedicated chunk of a month's hours rather than squeezed in alongside everything else.

Bug fixes and small technical debt clean-up also fit naturally into a retainer: fixing something that's behaving unexpectedly, improving a slow page, or tidying up a part of the codebase that's become awkward to extend. This kind of work rarely justifies its own project but matters over time, and a retainer is a natural place for it to happen steadily rather than being deferred indefinitely.

What generally doesn't fit inside a retainer: a large net-new product or a major redesign, which usually needs dedicated scoping, its own timeline, and often more capacity than a single month's block provides. As a hypothetical illustration only (not a real client, figures are estimates): a business on our 20-hours-a-month tier might typically see a mix of two or three small features, one small integration, and ongoing bug fixes across a month; the actual mix always depends on what that specific business needs that month, and we'll tell you plainly if something looks like it needs a separate project instead.