The Studio Retainer, Worked: Visual Production as a Subscription
The studio retainer (S6.15) was the article; this is the worked example. The studio (S9 series) produces the visual language of the sovereign stack — editorial covers, infographics, brand assets — and the retainer turns that production into a subscription. The client doesn’t buy images; they buy an ongoing visual operation that keeps their brand coherent. This is what the retainer actually delivers.
The retainer’s scope
The studio retainer has a defined scope with a monthly envelope: a fixed number of editorial assets (heroes, covers, infographics), a fixed number of revisions, and a standing brand system (the style guide, S9.13, configured for the client). The client’s visual language is enforced by the same prompt libraries and style anchors (S9.3) that keep the kingdom’s own work consistent — the client gets the studio’s discipline without the studio’s headcount.
The production pipeline behind it
Every retainer asset runs through the studio pipeline (S9.4): brief, prompt, generation, QA (S9.15), delivery. The pipeline is what makes the retainer economically viable: the marginal cost of an asset is near zero once the pipeline exists, so the retainer’s price is set by value, not cost. The visual QA loop (S9.15) is the quality guarantee — the same editorial threshold the kingdom’s own featured images must clear, applied to the client’s assets (the editorial featured-image directive).
Why a retainer beats a per-asset price
The retainer beats per-asset pricing for both sides. The client gets predictability, priority, and a brand system that compounds — every asset reinforces the last. The studio gets a stable revenue base (S6.15) and a portfolio that feeds the marketplace (EX-4) and the white-label offers (EX-6). The retainer is the skill product (EX-2) in subscription form: the client buys the visual capability, and the capability produces month after month, metered and dashboard-visible (EX-3).
Grounded in the EX worked-example series, the S6.15 studio-retainer article, the S9 studio series, and the S9.15 visual-QA article. Ninth article in the Round D examples track.
