What a Retainer is
A Retainer is a monthly engagement for teams that keep shipping after launch. It gives you a senior frontend lead and agent-assisted delivery for a defined number of days each month. The spec stays current as the product changes, so every change remains checkable months later.
It suits teams whose roadmap brings a steady stream of new features, brands, markets or rules, where a fresh project for each change would cost more in setup than in work.
What is included
| Included | What it means in practice |
|---|---|
| Senior frontend lead | One accountable engineer who knows your codebase and your spec |
| Agent-assisted delivery | Supervised coding agents building from approved tasks, each change reviewed before merge |
| Spec upkeep | Every change written as a delta against the living spec: ADDED, MODIFIED or REMOVED |
| Rule-change watch | We track changes in the rules that affect your interface, for the markets you name, and propose deltas for your compliance team to confirm |
| Monthly releases | Releases with trace reports, so you can see what changed and that it was checked |
| Quality gates | Tests, security, privacy, accessibility and performance checks on every change |
How a month runs
Each month starts with a short written plan and ends with a release report. Between the two, work moves in small, approved deltas.
- Plan. At the start of the month we agree priorities with your decision-maker: which deltas, in which order, within the month’s capacity.
- Deltas. Each change is written as a proposal against the current spec, priced in days and approved in writing before work starts.
- Build and check. Agents and engineers build from the delta’s tasks. Every change passes the quality gates and a senior review.
- Weekly update. Done, next, blocked, and anything that threatens the month’s plan.
- Release. Changes ship with a trace report covering the criteria they touch.
Why deltas instead of tickets
A delta changes the spec first and the code second, so the spec never falls behind the product. Tickets describe work. Deltas describe what the product must now do, and that description outlives the work.
After a year of tickets, nobody can say with confidence what the product is supposed to do. After a year of deltas, the spec still answers that question, and every answer has a test. This is the OpenSpec way of working on an existing codebase.
Who it is for
The Retainer fits a product team with a continuous frontend roadmap that doesn’t need a full in-house frontend team. Common examples:
- A platform adding brands or markets on a shared multi-brand design system.
- A product whose rules change often, where each change needs to reach the interface quickly and provably.
- A team that finished a Build with us and wants the same standard to continue.
Capacity and terms
Capacity is a fixed number of days per month, agreed in the Statement of Work and invoiced in advance. The minimum term and notice period are set in the contract. Whether unused capacity rolls over is agreed up front, so there are no surprises at month end. Prices are quoted after a first conversation.
What stays the same as a Build
The standards don’t relax because the work is ongoing. A mutual NDA, a company messenger, a reply within one business day, ownership of all work on payment, no training on your code, and only tools you approve in writing: all of it applies to a Retainer exactly as it does to a Build.
Starting a Retainer
Most retainers start after a Build, when the spec and codebase are already ours to maintain. If you come to us with an existing frontend, we usually start with an Audit or a short Spec Sprint to write the current behaviour down as a baseline spec. Every delta after that has something to change.