Command Network v1.1, General Availability
Released: May 6, 2026 | Type: General availability launch | Breaking changes: N/A (first public release)
The Blitzify Command Network is generally available. This release note documents what is included in the GA release, how to get started, what each agent does at launch, and the near-term development roadmap.
What This Release Is
v1.1 is the general availability release of the Blitzify platform. The entire Command Network, all nine entitled specialists, the ZED coordination engine on Workforce, the IAN integration layer, the Command Center, Mission Replay, and the Morning Brief, is now accessible to operators through the onboarding process.
This is not a soft launch or beta. The platform is production-ready and deployable for live business operations.
What Is Included at GA
The Full Workforce
All nine specialists are included at launch. Workforce adds ZED orchestration:
ZED. Command and Coordination. The intelligence hub of the Blitzify workforce. ZED does not execute domain work, it coordinates. Every morning, ZED compiles a structured briefing for the operator: what happened overnight, what decisions require approval, what agents are working on, and what is due for attention today. ZED also manages cross-agent dependencies, routes escalations to the operator at configured thresholds, and maintains the authority structure that makes autonomous operation responsible. [Read: Why ZED Changes Multi-Agent Coordination →](/intelligence/why-zed-changes-multi-agent-coordination)
SAL. Revenue Operations. SAL operates the pipeline development function: researching prospects against the operator's ICP, preparing outreach at every stage, managing sequence execution, monitoring pipeline health, and surfacing the accounts that most need human attention. SAL's operating brief defines the target customer, outreach approach, and escalation thresholds. [Read: How SAL Operates a Modern Sales Function →](/intelligence/how-sal-operates-a-modern-sales-function)
MAX. Marketing Intelligence. MAX executes the content and distribution function: planning the quarterly content calendar against the operator's strategy brief, producing content for each publication slot, adapting it across connected channels, managing the publishing schedule, and reporting performance back through ZED's weekly briefing. [Read: How MAX Executes a Quarterly Brief →](/intelligence/how-max-executes-a-quarterly-marketing-brief)
BEN. Financial Intelligence. BEN monitors the financial function continuously: tracking revenue, expenses, margins, and cash position against the operator's financial model; detecting variances before they compound; producing weekly and monthly financial summaries for operator review; and flagging financial risk items through ZED's briefing. [Read: Financial Monitoring With BEN →](/intelligence/continuous-financial-monitoring-with-ben)
JOY. Customer Success Intelligence. JOY manages the client relationship function: monitoring account health across the portfolio, managing ongoing client communications, preparing and executing renewal sequences, detecting satisfaction risk signals before they become churn risk, and coordinating with SAL at the sales-to-success boundary. [Read: JOY, The Customer Experience Specialist →](/intelligence/joy-the-customer-experience-specialist)
KAI. Operations Intelligence. KAI monitors operational workflows and surfaces process issues before they affect output quality. For businesses with fulfillment operations, KAI tracks order flow, supplier relationship status, and delivery performance. For service businesses, KAI monitors delivery workflow consistency, project status, and resource allocation. Operational bottlenecks surface in ZED's briefing before they become critical.
IAN. Integration Network. IAN is the integration backbone that connects the workforce to the business's existing software stack. Without IAN, agents operate on limited information. With IAN, agents have real-time access to CRM data, financial accounts, email communication history, calendar context, project management status, and e-commerce data. IAN is configured during onboarding and expanded as additional integration points are identified.
VAL. Executive Strategy. VAL supports executive productivity: briefing preparation, strategic research synthesis, meeting preparation, decision support, and communication drafting for the operator. Where other agents execute domain work, VAL amplifies the operator's own capacity by handling the preparation and synthesis work that consumes executive time without requiring executive judgment.
LEX. Legal and Compliance Intelligence. LEX monitors contracts, agreements, and compliance requirements on behalf of the business. Contract review support, compliance calendar tracking, regulatory monitoring, and legal risk flagging, LEX surfaces legal-adjacent issues for operator attention and professional legal review rather than replacing counsel.
IVY. Research Intelligence. IVY conducts on-demand market research, competitive intelligence, and strategic information synthesis. When the operator needs context on a market, a competitor, an industry development, or a strategic question, IVY prepares a structured research brief. IVY also maintains ongoing research monitoring against configured topics, surfacing relevant developments in ZED's weekly briefing.
Command Center
The Command Center is the operator's primary interface with the workforce. From the Command Center, operators can:
- Review agent status and recent activity
- Access and update operating briefs
- Configure approval thresholds
- Review Mission Replay recordings of agent activity
- Monitor integration status through IAN
The Command Center is designed to be checked alongside the morning briefing, five to fifteen minutes each morning to review what the workforce is doing and what needs operator input. [View the Command Center →](/command-center)
Morning Brief
Every morning, ZED compiles a structured intelligence briefing delivered through the Command Center and (optionally) by email. The briefing covers: decisions requiring immediate operator approval, same-day review items, agent status across the workforce, and any escalations or flags from overnight activity.
The morning brief is the primary governance touchpoint of the operating model. Operators who review the briefing daily and action the items within it get the full value of the workforce. Operators who let briefings accumulate create a backlog of pending approvals that reduces the workforce's operational effectiveness. [Read: How to Lead a Business That Runs on AI →](/intelligence/how-to-lead-a-business-that-runs-on-ai)
Mission Replay
Mission Replay is the audit and review layer. For any completed action by any agent, operators can replay the decision sequence: what information the agent had, what it considered, what it did, and what the result was. This transparency serves both governance (operators can audit any agent action) and calibration (operators can identify where an agent's judgment needs refinement in the operating brief).
IAN Integration Coverage at GA
The following integration categories are supported at launch through IAN:
- CRM: Salesforce, HubSpot, Pipedrive, and others via API
- Accounting: QuickBooks, Xero, and others via API
- Email: Gmail, Outlook/365
- Calendar: Google Calendar, Outlook Calendar
- E-commerce: Shopify, WooCommerce
- Project management: Asana, Monday, ClickUp, Notion
- Communication: Slack (read access for context; Blitzify does not post to Slack channels without explicit configuration)
Additional integration points are added through the IAN settings panel. If your critical business software is not in the current integration library, the IAN configuration process includes a custom integration pathway.
Getting Started
New operators begin with a mission brief session: a structured onboarding process where operating objectives, initial agent configuration, and approval threshold preferences are established. The mission brief session takes approximately two hours for a full workforce deployment and forty-five minutes for a focused single-agent deployment.
Time from onboarding to first agent output: Typically forty-eight hours. This includes brief configuration review, IAN integration setup for the relevant data sources, and initial agent calibration before live execution begins.
Recommended first deployment: For most operators, the recommended starting configuration is ZED + one or two specialist agents rather than the full workforce simultaneously. This allows the operating model and brief configuration to stabilize before adding complexity. [Read: What Business Owners Should Expect from Autonomous Agents →](/intelligence/what-business-owners-should-expect-from-autonomous-agents)
Near-Term Roadmap
The GA release begins the continuous improvement cycle. Planned features in active development at launch:
v1.2 (June 2026): Multi-channel distribution for MAX; expanded variance detection for BEN; automated financial report templates.
v1.3 (July 2026): Intent signal integration for SAL; enhanced prospect research depth; account-level outreach customization; deliverability monitoring.
v1.4 (August 2026): New mission briefing format with tiered priority structure; action-type granularity for approval thresholds; explicit cross-agent dependency declaration.
The development roadmap is maintained in the Command Center and updated with each release.
FAQ
Is the GA release available to all businesses, or is there a waitlist? Onboarding is open. Requests are reviewed to ensure fit with the current platform capabilities. Most requests receive a response within one business day. [Request access →](/request-demo)
What is the minimum viable deployment, can I start with just one agent? Yes. A focused single-agent deployment is a valid starting configuration. Many operators begin with SAL (if pipeline development is the priority), MAX (if content consistency is the priority), or BEN (if financial visibility is the priority). ZED coordinates even single-agent deployments, providing the briefing and approval management structure.
How long does it take to see measurable results? Initial outputs typically appear within the first week. The calibration period, where brief refinements improve output quality, typically runs three to six weeks. By ninety days, most operators have a stable deployment with measurable function-level contributions. [Read: Field Report, Full Workforce Deployment →](/intelligence/field-report-ecommerce-full-workforce)
Key Summary
- Full ten-agent Command Network is generally available
- ZED, SAL, MAX, BEN, JOY, KAI, IAN, VAL, LEX, and IVY are deployed and production-ready
- Command Center, Mission Replay, and Morning Brief are included in the GA release
- IAN supports CRM, accounting, email, calendar, e-commerce, and project management integrations at launch
- Onboarding is open, typical time to first agent output is forty-eight hours
[Request access →](/request-demo) | [See how it works →](/how-it-works/workforce) | [Meet the full workforce →](/agents) | [Next release: v1.2 →](/intelligence/platform-update-v1-2) | [Back to Intelligence →](/intelligence)