Template Intake and Asset Governance (Onboarding)

Template Intake and Asset Governance (Onboarding)

1. 01

   Inventory every recurring asset the client buys before touching a generator

   List banner sizes, ad formats, store screenshot sets, and social dimensions with monthly volumes. A retainer scoped at 40 static assets per month needs a different pipeline than one at 400.

2. 02

   Lock brand tokens into a single source of truth the API can read

   Fonts, hex values, logo clear-space rules, and legal disclaimers belong in one versioned file. Template editors in tools like Bannerify and Text Logo both break when typefaces or colors are edited per asset instead of at the token layer.

3. 03

   Classify each asset type by structural rigidity

   Screenshot sets for app stores, city or location iconography, and diagram-style figures tolerate templating well; hero photography and campaign concepts usually do not. Route rigid formats to automation and keep the rest with a designer.

4. 04

   Define the variable fields and their validation rules

   Headline character ceilings, price formatting, locale-specific date formats, and required legal lines. Unvalidated text swaps are the most common cause of a rendered batch shipping with truncated copy.

5. 05

   Set a render budget and a per-asset cost ceiling in writing

   Record expected monthly render volume and the unit price at that volume. Usage-based pricing means a client who triples campaign frequency can quietly halve the margin on that retainer.

6. 06

   Name a fallback path for API downtime before the first campaign ships

   Identify which assets can be produced manually and by whom, and how fast. A single vendor outage during a launch week is a delivery failure, not an inconvenience.

7. 07

   Run one pilot batch end to end and have the client sign off on the output

   Produce a representative set across every format, review it against brand rules, and get written approval. This becomes the reference standard for every later batch.