Cisco reported $15.8 billion in quarterly revenue and announced a plan to give each of its 90,000 employees a personal AI agent by the end of July 2026. In the same earnings call, it announced roughly 4,000 job cuts. California terminations were scheduled to begin July 13, with the agent rollout due two weeks later.
Those announcements put workforce planning and agent deployment on the same management agenda. Their timing does not establish that the agents caused the layoffs or show which roles the company expected them to replace.
The planned agent layer
The proposed agent handles tasks, answers internal questions, and routes requests to the underlying model suited to the job. Cisco described infrastructure built largely on-premises for cost and data control. CFO Mark Patterson described a layer integrated with employees’ existing work.
Cisco’s finance team was already running 80% of its draft work through AI. That figure measures draft work. An implementation review also needs to account for the effort people spend checking the finished output. The company also reported $9 billion in AI orders on its books, a separate measure of customer demand.
For a $60 billion networking company, an employee-wide rollout raises operating questions about permissions, support, and supervision. The announcement describes the intended reach; it does not by itself demonstrate completed deployment or dependable use by every employee.
Plan the division of work
A team considering a similar rollout needs to name the person responsible for workflow design. That person should specify the agent’s assignments, the work people retain, and the points where a human reviews or stops an action. Budget and vendor choices need to support those assignments.
Build an 18-month workforce plan around explicit assumptions about the work. Identify tasks an agent can perform, test the output, and record how much review and exception handling it creates. Use those observations before changing staffing assumptions. Cisco’s 90,000-agent plan and 4,000 job cuts are company-specific announcements; applying them directly as another team’s staffing formula would require additional evidence.
The useful follow-up to this story is evidence from the rollout: which employees use the agents, what work moves to them, and what happens to quality and workload. Until that evidence is available, keep the deployment plan and the explanation for the layoffs separate.