By the 12th, the included bank was empty. The client still expected retainer turnaround on the next drop — fifty more SKUs, same brand tone, same Friday habit.
Nothing in the agreement was dishonest. The month simply had no remaining capacity left to spend, and nobody had written what happens when that happens.
A product photography retainer only works when the studio treats it as a capacity bank with a calendar — not as a loyalty discount that somehow makes infinite work feel cheap.
A retainer is a capacity bank with a calendar, not a discount for loyalty
A product photography retainer is an ongoing agreement where the studio reserves a defined amount of production capacity for a client over a period — usually a month or a quarter — and runs recurring drops against that bank.
That is different from "they send us work every so often and we invoice each job." Repeat clients are common. A retainer is specific: included capacity, a period, a cadence, and rules for unused capacity and overage written before the first drop ships.
If you are still choosing the commercial unit itself — project fee vs ongoing agreement, what unused capacity means on paper — start with the pricing guide. This post assumes you already know a retainer might fit and need the operating rules that keep month two from becoming a scramble.
When a retainer fits — and when it doesn't
A retainer fits when the studio can measure recurring volume and the client can commit to a period. Monthly Amazon replenishment, Shopify launch drops, catalog refreshes that arrive on a known rhythm — those are retainer shapes. One campaign every other quarter with a new creative brief each time is usually still a project fee.
Use the studio's own production capacity evidence before selling a bank. If you cannot estimate how many shot rows a reserved week can honestly clear, you cannot sell that week as included capacity. Guessing a round number because the client asked for a retainer is how the 12th-of-the-month problem starts.
Skip the retainer shape when volume is sporadic, when the client will not name a decision maker for each drop, or when the brand's visual rules change every cycle. In those cases a clean project proposal per job is safer than a bank nobody can steward.
Define the included bank in outputs the studio can count
"Hours of shooting" sounds precise and usually isn't. Ecommerce work burns capacity in shot rows, setups, retouch level, and review rounds — not camera time alone.
Write the included bank in units the floor and the edit queue both understand:
- Included products or SKUs for the period, with a clear rule for variants
- Included shot-list rows or views per product (packshot only vs packshot plus detail)
- Included setup or look count, if lighting changes drive the work
- Retouching treatment level that applies to included rows
- Included proofing rounds and who consolidates feedback
- What is explicitly outside the bank (new lifestyle sets, rush inside 48 hours, model days)
Present that bank in the proposal template the same way you would present a project scope — countable, with exclusions — then keep a running tally against it as drops land. A retainer without a tally is a mood.
Cadence beats vibes
The calendar is half the product. Decide when drops are accepted, when the shot list freezes for a given cycle, and when proofs go out — then protect those windows the way you protect call time.
A practical monthly pattern for a 3–10 person studio:
- Drop window: client submits the SKU list and samples by a named date (for example, the 3rd).
- Freeze: brief and shot rows lock within a short window after intake — no silent adds in Slack.
- Production block: reserved floor and edit capacity for that client's bank.
- Proof and release: a named review window so approvals do not spill into the next drop.
Each cycle still needs a thin intake form pass — new SKUs, discontinued variants, changed Amazon crop rules, a new approver. The retainer does not replace intake; it replaces reinventing the commercial relationship every time. The underlying product photography workflow still runs. The retainer is the wrapper that keeps capacity and cadence honest across cycles.
Style continuity is the whole point
Clients buy retainers when they want the catalog to look like one studio made it across months. That only happens if the visual standard travels with every drop.
Keep the current style guide version on the account — background, crop, retouch boundaries, color-critical rules — and attach a recent approved set as the reference for the next cycle. When a new producer or second shooter touches the account in month four, they should not be guessing from memory of month one.
Findability matters as much as the guide itself. If last month's approved heroes live in a random Drive folder, the next drop will drift. Use the same file system habits you would for reorders — organize product photography files so the baseline set is one path away, not a scavenger hunt.
Unused capacity and overage are ops decisions, not afterthoughts
Write two rules before month one starts. Not after the client asks why Friday feels slow.
Unused capacity. Does unused bank expire at period end, roll a limited amount, or convert to a defined credit? Pick one and say it in the agreement. Studios that leave this vague end up either giving away free work to "be nice" or arguing about leftovers while the next period's drop is already in the tray.
Overage. When a drop blows the bank mid-period, the studio needs a pre-agreed path: quote the extra rows at a stated unit, split delivery, push part of the drop to the next period, or decline the excess for this cycle. If the honest fix is outside help, the overflow work rules apply the same as they would on a one-off job — style guide, sample custody, QC, and margin math still have to travel.
Track the bank in the same place the team already looks — a simple running count of included rows used vs remaining is enough. The number does not need to be fancy. It needs to be current before anyone promises Friday.
One account record across months
The operational advantage of a retainer is continuity of context: who approves, how samples usually arrive, which delivery names the client expects, which colorways are chronic problems. That context dies when every drop is a new email thread with a new folder name.
Keep each drop attached to the same account lineage — brief answers, style guide version, sample habits, proof decisions, released sets. The producer should be able to open month three and see what month two already settled.
That is the job Lenso for studios is built for: keeping briefs, capacity-facing shot rows, approvals, and delivery context on the same record across recurring work. Lenso does not invent your retainer terms or calculate the bank. It makes the missing tally and the missing style baseline harder to lose between drops.
Copy-ready retainer ops checklist
Run this before you sell the first period, then again at the start of each cycle:
- Confirm recurring volume is measurable from the studio's own capacity evidence — not a hopeful round number.
- Define the included bank in countable units: SKUs, shot rows, setups, retouch level, proofing rounds.
- Write exclusions and the overage unit in the same document as the bank.
- Write the unused-capacity rule (expire, limited roll, or defined credit) before month one.
- Set drop, freeze, production, and proof windows on the calendar both sides can see.
- Require a thin intake for every drop even when the commercial relationship is ongoing.
- Attach the current style guide version and a recent approved reference set to the account.
- Keep a running tally of bank used vs remaining where the producer already looks.
- Name the client decision maker and the studio owner for schedule calls.
- At period end, review actual vs included capacity and adjust the next period's bank before promising it.
FAQ
What is a photography retainer?
A photography retainer is an ongoing agreement that reserves a defined amount of the studio's capacity for a client over a period — typically a month or quarter — instead of pricing every drop as a brand-new project. For ecommerce product studios, the useful definition includes a countable included bank, a cadence for drops, and written rules for unused capacity and overage.
How much is a photographer retainer?
There is no universal number. The fee should come from the studio's own scope, labor, operating costs, capacity evidence, and risk — the same method as any other pricing unit. Use the pricing guide to build the commercial model; do not copy someone else's monthly fee from a forum thread.
How much is a monthly retainer fee?
Same answer with a calendar attached: price the included bank for that month, then decide unused and overage rules. Two studios can reserve "forty SKUs a month" and still need different fees because setup load, retouch level, review process, and overhead differ. Build from the studio's records, not from a published average.
What should be included in a product photography retainer?
At minimum: the period, the countable included bank (products, shot rows, setups, retouch treatment), proofing expectations, drop and freeze cadence, unused-capacity policy, overage process, and what is excluded. Style-guide continuity and a named decision maker on both sides belong in the operating rules even if they are not line items on the invoice.
What happens if a client exceeds the included capacity mid-month?
Follow the overage path you wrote before the period started: quote the excess at the stated unit, split delivery, roll part of the drop into the next period, or decline the excess for this cycle. Do not silently absorb fifty extra SKUs because the relationship is "on retainer." If covering the excess needs outside help, treat that handoff with the same rigor you would for any overflow work.