# Blitzify Is Generally Available, And What That Actually Means
As of August 2026, Blitzify is generally available. This announcement covers what that means in practical terms, what is production-stable, what we are actively developing, and the commitments we are prepared to make about the platform's direction over the next twelve months.
We are not going to use this announcement to describe a finished product. Blitzify is a platform in active development. What GA means is that the core workforce, ZED, KAI, BEN, SAL, JOY, MAX, IAN, VAL, LEX, and IVY, is production-stable and supported for production deployments. It does not mean the platform is feature-complete, and we would not claim it is.
What Is Production-Stable
The following are in production and supported:
The core AI workforce (nine specialists + ZED on Workforce). ZED, KAI, BEN, SAL, JOY, MAX, IAN, VAL, LEX, and IVY are available for production deployment. Entitlement includes all nine specialists; customer-operational depth varies by specialist and is documented honestly in product updates.
The IAN integration layer. The following integration categories are production-stable: CRM (HubSpot, Salesforce, Pipedrive), accounting (QuickBooks, Xero), project management (Asana, Monday, ClickUp), email (Google Workspace, Microsoft 365), payment processing (Stripe, Square), and document storage (Google Drive, Dropbox, SharePoint). Additional integrations are in development and will be added through the Product Update release cycle.
ZED's command interface. The morning briefing, escalation management, on-demand agent requests, and Mission Replay are all production-stable. The interface is available on desktop and mobile web.
Operating brief configuration. The quarterly brief system for entitled specialists is production-stable and documented. Initial configuration support is included with every onboarding.
What Is In Active Development
The following are being actively developed and will be released through the Product Update cycle over the next twelve months:
Expanded integration coverage. The primary integration gaps currently: e-commerce platforms (Shopify, WooCommerce), payroll and HR systems (Gusto, Rippling), dedicated support platforms (Zendesk, Intercom), and additional accounting systems (FreshBooks, Wave). Each of these is in development. We will announce each integration at GA through the Product Updates series.
Mobile command interface. The current mobile web experience is functional but not optimized for mobile-first use. A dedicated mobile application is in development. We expect to release a beta in Q4 2026.
Agent collaboration features. The current architecture allows agents to share context through IAN but does not expose multi-agent collaboration as a visible operator experience. The next major platform version will surface agent collaboration, how KAI and SAL share pipeline intelligence, how JOY and SAL coordinate on account handoffs, as a visible, configurable operator experience.
Brief versioning and rollback. Operating briefs currently do not support formal versioning, if an operator changes a brief and wants to revert to a previous configuration, they do it manually. Brief versioning is in development and will allow operators to maintain a history of brief configurations and revert to any prior version.
Performance analytics. The current reporting reflects each agent's activity and output. What it does not yet provide is performance attribution, connecting agent activity to business outcomes in a way that makes the ROI of specific agent deployments measurable. This is in development and expected to release in Q1 2027.
The Support Model at GA
With general availability, the support model formalizes:
Onboarding. Every new operator receives an onboarding session with a Blitzify deployment specialist. The session covers operating brief configuration for the agents being deployed, IAN integration setup, and ZED briefing calibration. Onboarding takes approximately three hours across two to three sessions.
Ongoing support. Support is available through the support portal and the in-product chat interface. Response time targets: critical issues (agent not functioning) within four hours; non-critical issues within one business day.
The Intelligence Library. The Library is the primary self-serve resource for operators. It is kept current with platform updates. If an operator cannot find the answer to an operational question in the Library, that is a Library gap we want to know about.
Deployment reviews. Operators who have been live for ninety days are offered a deployment review, a structured session with a deployment specialist to review agent performance, brief calibration, and opportunities to improve output quality.
What We Are Not Doing
A few things this announcement is explicitly not:
Not announcing an enterprise tier. Blitzify is built for SMB operators, businesses with one to fifty employees that do not have the headcount infrastructure of an enterprise. We are not developing enterprise features (SSO, multi-tenant administration, compliance packages for regulated industries) in the near-term roadmap. If you are evaluating Blitzify for an enterprise deployment, that is not who we are building for right now.
Not announcing pricing changes. Current pricing is on the pricing page. We will give operators minimum sixty days notice before any pricing changes that affect existing subscriptions.
Not announcing new agent types. The current nine-specialist roster covers the primary business functions we designed for. We are not developing additional specialist types in the near-term roadmap, the focus is depth and quality in the existing roster, not breadth of specialist types.
A Word on Timing
General availability in August 2026 is a milestone that reflects three years of development. The platform works, operators are using it in production, and the core workforce performs reliably enough that we are prepared to support it without caveats.
It is not an ending. The platform we want to build is more capable, more integrated, and more deeply useful than what we have now. GA is the foundation we are building from, not the destination.
We publish the Product Updates series precisely so that operators can follow the development honestly, not as a PR exercise, but as a practical resource for understanding what changed, what improved, and what is known to still be imperfect. That series will continue to be the most accurate real-time documentation of the platform's state.
What GA Means for Existing Beta Operators
Operators who have been running on the beta have already been using production-grade agents, the GA release does not change their deployments. What changes:
Support SLAs are now formal. The response time commitments described above are now contractual, not best-effort.
Pricing transitions to GA pricing. Beta operators received discounted access during the beta period. GA pricing applies at the next billing cycle after this announcement. Details were communicated directly to each beta operator by email.
Brief configurations are not reset. Every operating brief, threshold configuration, and calibration setting carries over. GA is a billing and support milestone, not a platform reset.
The Operator Experience We Are Designing Toward
It is worth describing what the platform looks like in two years, not as a product roadmap, but as a design vision that shapes how we prioritize.
The briefing as the complete operator interface. Today, the ZED briefing surface covers the most critical daily decisions. In two years, the briefing should be comprehensive enough that an operator can run their entire business through it, every decision that requires attention surfaces there, prepared with the right context, and can be resolved without navigating to a separate system.
Invisible integration. Today, connecting a new integration requires a deliberate setup step. In two years, IAN should be able to identify what systems an operator is using from minimal context and propose connection configurations. The operator reviews and approves; the heavy lifting of integration setup is handled automatically.
Agent collaboration that is visible. Today, agents share context through IAN but the collaboration is invisible to the operator. In two years, the collaboration should be surfaced, the operator should be able to see when SAL is informing JOY's renewal approach, when BEN's financial trend is informing VAL's board update draft, when KAI's supplier analysis is informing LEX's contract monitoring.
Performance attribution. Today, operators understand qualitatively that the workforce is valuable. In two years, performance attribution should make that value quantifiable: the revenue saved through JOY's churn prevention, the hours recovered from monitoring that BEN now handles, the deals accelerated by SAL's systematic follow-up.
This is the product we are building toward. GA is the milestone that says the foundation is solid enough to build from with confidence.
Frequently Asked Questions
Is Blitzify suitable for regulated industries? The core platform is suitable for most SMB deployments across industries. For regulated industries with specific compliance requirements (healthcare, financial services with fiduciary obligations, legal services with confidentiality requirements), operators should review the platform's data architecture documentation and consult with their compliance function before deploying. We do not currently have industry-specific compliance packages.
What is the minimum business size for Blitzify? There is no minimum in terms of employee count. The relevant threshold is whether the business has enough operational complexity that the workforce's monitoring and execution can produce meaningful value. Businesses with active client relationships, regular marketing and content needs, and financial monitoring requirements benefit from the workforce even at early stages. We typically see the most value in businesses with five to fifty employees, but solo operators running complex businesses are also strong deployment candidates.
Can Blitzify connect to custom or proprietary systems? IAN currently supports connections to the documented integration catalog. Custom integrations are not self-serve, they require custom development work that we handle through a professional services engagement. If your business runs on a platform that is not in the current catalog and that is critical to your deployment, contact the support team to discuss options.
How does Blitzify handle data if the business is based outside the United States? Blitzify is currently operated from United States infrastructure. Data residency and transfer considerations apply for operators subject to GDPR, PDPA, and other data localization regulations. We are actively developing regional infrastructure options; operators with specific data residency requirements should contact the support team before deploying.
[Read: Introducing Blitzify Intelligence →](/intelligence/blitzify-intelligence-launch) | [Read: Platform Update v1.4 →](/intelligence/platform-update-v1-4) | [Read: A Note on Building in Public →](/intelligence/founder-note-on-building-in-public) | [Browse all articles →](/intelligence)