What it does: Swap the hero, rewrite a market's copy, open any stage of the pipeline and change how it composes, then run it. Every millisecond on the chips below is measured on the render happening in front of you — the service reports its own stage timings, and the page replays them. The dwell is capped so the animation stays watchable; the numbers are not.
The most common way an automated creative pipeline embarrasses a brand is text. It is also the part people most often hand to a model, and that is the wrong instinct — so this is worth being precise about, because a Brand Standards director will ask.
The market's line is set from the brand font's own outlines. The engine reads the TrueType file directly — the character map, the advance widths, the quadratic curves in the glyf table — and converts the copy into vector paths before it ever becomes an image.
Three things follow, and each one is a problem that would otherwise show up after launch:
Fifty brands and twenty markets is a thousand brand-market pairs. You cannot sequence a thousand of anything by opinion, and you should not try — the argument in the room is never "is this brand important", it is "whose turn is it". So the sequence comes out of a model the stakeholders can see and argue with. Move the weights and watch Wave 1 change; that is the point. The model is the artefact, not the list it happens to produce today.
A high score does not earn a place in Wave 1. These four are binary, because each one is a way for the wave to fail publicly.
Wave 1 is deliberately small. Every pair added is another brand kit to normalize, another reviewer to train and another way to be wrong in front of the CMO — and the goal of Wave 1 is not volume, it is a defensible answer to "does this transfer".
Readiness is not enthusiasm. It is whether the brand kit is machine-readable, whether the DAM exposes the assets, and whether there is a named owner who can approve. A brand with huge value and no readiness is a Wave 2 problem with a Wave 0 dependency — and saying so early is cheaper than discovering it in month three.
The pilot proved Firefly makes excellent heroes. It did not touch the part that actually costs money. One approved hero has to become an e-commerce tile, a story, a billboard and a shelf card — in six languages, against each market's spec sheet, without breaking brand standards. Today that is a person in a layout file, 500+ times a season. The gap is not generation. It is adaptation. So we build the adaptation engine, and we build it as a bridge the customer's own IT can own.
The legacy DAM stays the system of record. We do not migrate it, mirror it or fork it — it gets a read adapter and a write-back of renditions plus compliance metadata. Firefly Services keeps doing hero generation. The engine is the missing middle, and it is roughly two thousand lines with no runtime dependencies, which is the honest answer to "who maintains this when the pod leaves".
Productivity is the easiest number to produce and the easiest for a board to discount, because "we saved hours" invites the question "so where are they". The metrics below are the ones that survive that question: they measure whether the company can now reach markets it could not afford to serve properly, whether it can commit to dates, and whether the risk of a brand or legal defect reaching the public has gone down. Cost avoidance is the floor, not the case.
Every input is an assumption the CMO's finance partner will challenge, so they are all exposed rather than baked in. The defensible version of this slide is the one where they change a number and the conclusion holds.
The claim is not headcount reduction. It is that adaptation stops consuming the people you hired to originate — which is the version the Creative directors will accept and the board can still bank.
A transformation dashboard that can only go up is a marketing asset, not an instrument. These are the leading indicators I would put in front of the same board, and I would rather name them now than be asked for them in month five.
Five people with five different reasons to say no. Each concern below is legitimate, and each one is answered by something that is already running rather than by a promise on a slide — click a stakeholder to see the answer and the proof.
All of it, served by the thing it builds. No runtime dependencies — the YAML reader, the PNG codec, the TrueType parser and the compositor are in this repository, on top of primitives the Workers runtime already has. That is the honest answer to "who maintains this after the pod leaves".