> ## Documentation Index
> Fetch the complete documentation index at: https://www.plungeai.com/guide/llms.txt
> Use this file to discover all available pages before exploring further.

# Production

> The pipeline moves a request from brief to internal review without anyone pressing a button. When it cannot go on by itself, it stops and opens an exception (see When something stops).


The pipeline moves a request from brief to internal review without anyone pressing a button. When it cannot go on by itself, it stops and opens an exception (see [When something stops](/agency/for-the-agency-team/when-something-stops)).

*Diagram 3. An ad set from brief to client review. Landing pages and lifecycle email follow the same shape with one page or 1–4 email variants and no images.* Brief, quote, start the client's workflow, concepts, concepts as data, validators with two copies per rule, judge, images per format, a new version whose pieces are being checked, the QA settle, internal review by a person, and client review.

1. **Brief.** A client's brief enters Intake and the pipeline takes it on at once. It names an owner (the client's account lead when there is one) and moves it to Queued.
2. **Quote.** The pipeline prices the run from the agency's rates. The quote is the agency's internal estimate; the client never sees it. Above the agency's maximum quote (default $25) the pipeline stops and a strategist confirms on the request page.
3. **Checks.** Before any run: an active, paid plan with a unit left, an activated client with a saved workflow and an approved brand, consents for any named person, a domain pack for a regulated industry. A refusal opens an exception.
4. **The run.** The client's own workflow runs on the platform with the brand card attached. It writes 3 to 6 concepts, turns them into data, has every QA rule judged twice by identical copies, writes a judge's summary that never decides anything, and renders one image per concept for each format the brief asked for.
5. **A new version.** Every piece lands as “Checking” and the request stays In production. Clients do not see pieces until they pass.
6. **QA settle.** The scheduled QA job decides each concept (see [The QA gate](/agency/how-it-works/the-qa-gate)), up to four versions per pass.
7. **Internal review.** If anything passed or was held for a person, the request goes to the Review queue; if nothing passed, to QA failed.
8. **Send.** When a reviewer has decided every piece of the version, the version goes to the client's approvers at once, each with their own magic links.

If a run fails, the request goes back to Queued and is retried once. If the retry fails as well, an exception opens, and a per-piece fee is credited back.
