This is a presentation layer over the existing catalog, not a separate engine. Every workflow opens a template that already exists in the catalog, so anything you can reach from Templates you can also reach here — grouped by what it produces instead of how it is classified.
Why this exists
Most AI content tools ask you to assemble the output yourself from a pile of general-purpose assistants. That works until the output has to survive review. A specialist workflow starts from the finished artifact — a battlecard, a regulatory memo, an investor memo — and works backwards to the production path that reliably produces it.Outcome-first
Cards are named for the deliverable, not the agent. You pick “Competitive Battlecard,” not a sequence of steps.
Governed production
Every workflow runs the same governed pipeline: structure, research, style enforcement, validation, and a mandatory Quality Gate.
Vertical-aware
Regulated workflows apply the vertical’s controls and mandatory disclaimers rather than general-purpose defaults.
Consistent across the team
The production path is fixed, so output quality does not depend on who initiated the run.
Categories
What a workflow card tells you
Each card answers three questions before you commit to a run.1
What do I need?
The workflow name and category identify the deliverable in the language a buyer uses.
2
What will it produce?
The outputs list names every artifact the run returns — for example a battlecard returns objection handling and value propositions alongside the card itself.
3
Is it meant for me?
The “best for” list names the roles the workflow was shaped around, so a sales workflow is not mistaken for a marketing one.
Running a workflow
Selecting Start opens Studio with the underlying template preloaded and the full parameter schema retrieved. From that point the run behaves exactly like any other Studio execution: you supply the structured inputs, choose a generation tier, and the output lands in your Content Library ready for review, export, or publishing.Workflows and Templates are two entry points to the same catalog. Use Specialist Workflows when you know the outcome you need. Use Templates when you want to browse the full schema-driven catalog, filter by complexity, or inspect a template’s parameter contract directly.