Retainer Asset Reuse and Refresh Cadence (Retention)

Retainer Asset Reuse and Refresh Cadence (Retention)

1. 01

   Pull the last 90 days of delivered assets from the client's shared drive and tag each file by campaign, channel, and format

   Tagging by channel exposes which crops and sizes are actually being reused versus rebuilt from scratch every month.

2. 02

   Flag every asset that can be re-cut rather than re-shot, then route the flagged set to a layer separation pass

   Magic Layers converts flat PNG or JPEG files into named transparent layers, so a finished banner can be repurposed without the original source file.

3. 03

   Rebuild the top five performing assets at the new campaign dimensions before the next creative brief opens

   Reusing proven visuals cuts production hours on retainer work and keeps brand consistency across placements.

4. 04

   Re-export every refreshed file through the compression and format pipeline, confirming WebP or AVIF output for web placements

   MageCDN serves images through a dual Cloudflare and BunnyCDN stack with automatic AVIF and WebP compression, which keeps page speed stable as the asset library grows.

5. 05

   Log the refresh in the client-facing asset index with the original publish date and the new version date

   A dated index gives the account lead something concrete to show at the quarterly retainer review instead of a vague claim about ongoing optimization.

6. 06

   Schedule the next refresh window against the client's campaign calendar and confirm it in writing

   A standing 90-day cadence prevents the scramble that happens when a client asks for a seasonal variant two days before launch.