Workflows: structured movement
A workflow describes steps and handoffs, often linear, sometimes branching. Workflows excel when the path is known and triggers are clear (form submitted → route → notify). They struggle when each case needs different research depth, documents, or policy checks.
Agents: functional ownership
Agents in Blitzify are role-based workers: Sal on revenue motion, Ben on finance signals, Kai on operational flow. They maintain context across days, not just a single zap. Agents use tools, respect permissions, and surface approvals.
Tradecrafts: packaged specialization
A Tradecraft encodes how to perform a class of work, including estimating, competitive briefs, AR follow-up cadences, so agents execute consistently. Multiple agents may participate; the Tradecraft supplies the method.
How they compose
Typical pattern: an Operation sets the business objective → a Mission sequences work → agents invoke Tradecrafts for specialized steps → C10 meters capacity → humans approve outbound or contractual actions. See Tradecrafts for the public model diagram.
Limitations
Workflows alone rarely capture tacit expertise. Agents without Tradecrafts may improvise inconsistently. Tradecrafts without governance can automate the wrong thing faster; visibility tiers and approvals matter.
Frequently asked questions
Can a Tradecraft include workflow steps? Yes. Tradecrafts often orchestrate sub-steps, checks, and templates; they are capability packages, not a competing automation product.
Tradecrafts overview → | Intelligence library → | Missions →