Failure PatternDecision layer
Why Image Generators Collapse Under Client Brand Review in Month 2
Symptom: Client sends back 40 percent of a 300-asset banner batch for text overflow, wrong logo lockup, or off-brand color, and the agency re-renders the whole set by hand. Root cause: Templates get built for the demo, not for the client's real content extremes: longest headline, smallest screen, and every locale variant are tested after launch instead of before.
By InnovaAI ResearchPublished
How do you recognize it?
- •Client sends back 40 percent of a 300-asset banner batch for text overflow, wrong logo lockup, or off-brand color, and the agency re-renders the whole set by hand
- •Template edits made in the editor drift from the API payload, so the same campaign produces two visual versions depending on who triggered the render
- •Retainer hours shift from strategy to pixel triage, and the account lead cannot explain why a 10x faster render pipeline still takes five days to ship
- •A single font or asset swap requested by the client breaks every downstream template because the dependency was never mapped
- •Usage-based render costs spike in the same week revision rounds triple, and nobody can attribute the overage to a specific client
Why does it happen?
- •Templates get built for the demo, not for the client's real content extremes: longest headline, smallest screen, and every locale variant are tested after launch instead of before
- •Brand rules live in a PDF style guide rather than in the template's constraints, so the API will happily render a 9-word headline into a 4-word box
- •No versioning or approval gate sits between template change and bulk render, letting an unreviewed edit propagate across hundreds of client assets
- •Agency scopes the retainer on asset count while the client buys on revision cycles, so every extra round is unpaid delivery labor
How do you fix it?
- •Rebuild the three highest-volume templates with hard character limits, locked layers, and a test payload containing the client's longest and shortest copy before the next batch
- •Add a 10-asset proof render and written client sign-off as a gate before any bulk run above 50 assets
- •Log every template revision with a timestamp and owner, and freeze templates 48 hours before a scheduled campaign drop
- •Reprice the retainer line to bill revision rounds separately from render volume so margin survives the second review cycle