Console launches 'Assistant': the AI that reads API docs, builds its own integrations, and deploys CrowdStrike in 40 minutes
Mar 30, 2026 with Andrei Serban
Key Points
- Console's Assistant agent reads API docs and deploys software autonomously, executing a CrowdStrike rollout in 40 minutes that would have taken a day or two manually.
- Console positions itself as an AI replacement for legacy ITSM platforms like ServiceNow, claiming to push IT headcount ratios from one per 100-150 employees to one per 400-500.
- The startup targets both ITSM displacement and a larger market of workflow automation work that IT teams never attempted due to capacity constraints, expanding beyond IT into HR, legal, and finance.
Summary
Console is pitching itself as an AI-native replacement for the IT service management stack — think ServiceNow, Jira Service Desk, and Freshservice — built around a context graph that tracks employees, their devices, and their software access.
The core product argument is a force-multiplier play on IT headcount. Most companies run roughly one IT person per 100 to 150 employees. Console says it pushes that ratio to one per 400 or 500, letting fast-growing customers — Databricks, Cursor, Figma, and Chime are named — keep their IT teams flat through hyper-growth.
Assistant: the agentic layer
The segment centers on a newer capability Console calls Assistant. Rather than routing tickets to a human, Assistant reads API documentation, builds its own integrations on the fly, and executes multi-step deployments autonomously. The clearest example: Console's own head of security used Assistant to roll out CrowdStrike across company devices in roughly 40 minutes, a task he estimated would otherwise have taken a day or two. Assistant identified the required binaries for the relevant macOS versions, generated the deployment script, confirmed with the user, and pushed it.
A lower-stakes but telling example: Console's office manager is building a weekly dinner-ordering workflow through Assistant that connects to eCater — an integration Console says it never would have built manually.
TAM framing
The market framing has two components. The first is displacement: Console is going after the installed base of legacy ITSM tools. The second, arguably larger, is expansion into work that IT teams never got to because they were buried in support queues. The pitch is that IT was an enablement function in the 1980s and 1990s — deploying computers, internet, email — and became a pure cost center as SaaS sprawl turned it into a ticket-management operation. Console's argument is that automating the reactive layer frees IT staff to do strategic work, and that the addressable market is everything companies would have done if they had the headcount.
The workflow automation use cases are also spreading beyond IT into HR, legal, and finance, where agents with elevated system permissions handle employee requests and take actions directly inside enterprise software.
Console is early-stage, and the TAM math is more directional than modeled at this point. But the combination of headcount-ratio economics and legacy ITSM displacement gives it two distinct levers to argue against.