From the Cisco edition of October 31, 2026
Fortune: Cisco gives a two-person team unlimited AI tokens and a four-week proof period toward refactoring 98% of its legacy code in 24 months
Cisco (reported by Fortune) · Network, security and collaboration software vendor (indirect SLED relevance through installed Cisco software) · Global (Cisco engineering); United States reporting
- Publisher
- Fortune
- Original publication
- Fortune, Oct. 30, 2026, 3:00 AM ET
- Source retrieved
- 2026-11-01
What happened
Fortune reports Cisco president and chief product officer Jeetu Patel’s account, given at a roundtable dinner, that he gave Padmanabhan “Paddy” Krishnamurthy, a 27-year-old former EzDubs co-founder, unlimited AI tokens to refactor code. Krishnamurthy believed a two-person team could rewrite Cisco’s legacy code; there is a four-week window to prove the approach and an end goal of refactoring 98% of Cisco’s legacy code within 24 months. The piece is mainly about hiring early-career staff. Every figure is a goal stated by a Cisco executive. No results, tools, codebases, test methods or products in scope are reported.
Why it matters
Limited and indirect. SLED agencies, campuses and school districts run Cisco routers, switches, firewalls, ISE and collaboration software. A large AI-assisted rewrite of Cisco’s code would eventually show up in the software releases those teams patch and certify. Nothing here changes current SLED products, contracts or support terms.
Evidence and measured results
News reporting of an executive’s on-record remarks at a small roundtable. There is no Cisco press release, no technical description, no baseline or measure of what counts as “refactored,” and no independent assessment in the article.
Limitations and uncertainty
Executive remarks to the press. 98% and 24 months are targets, not results. The four-week proof had not reported. Scope (which products, which languages) is undefined. Large parts of the article cover hiring philosophy, not engineering.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-01; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- SLED IT teams depend on stable Cisco software releases and may soon face releases containing large AI-assisted rewrites, with no public detail yet on how those are tested.
- Stakeholders
- Network operations manager
- CISO / security operations lead
- IT change advisory board
- Procurement / vendor management
- Discovery questions
- How do you test Cisco software releases before production upgrades today?
- Which Cisco platforms are most critical to keep stable (core, firewall, ISE, voice)?
- Would you want release-level disclosure of AI-generated or rewritten components?
- Value hypothesis
- Bounded: helping a customer strengthen upgrade validation now reduces the risk of disruption from any future large code changes, whatever their cause.
- Potential engagement
- A short release-readiness review of the customer’s Cisco upgrade testing, rollback and change approval process.
- Unsupported claims
- That AI refactoring has improved Cisco software quality or security
- That the 98% target will be met or on any timeline
- Any cost or feature-velocity benefit for SLED customers
Pre-sales engineering
Role takeaway
- Fit
- Watch item only; no product or architecture change follows from this report.
- Architecture and integration
- Affects how customers test future Cisco OS and application releases within existing upgrade pipelines.
- Prerequisites
- Lab or staging environment for critical Cisco platforms
- Baseline configurations and regression test cases
- Constraints
- No product scope disclosed
- Public-sector change windows and certification cycles limit upgrade frequency
- Security
- No security data in the source; treat any security claim as unverified until Cisco publishes release-level evidence.
- Proof of value
- Track Cisco release notes for statements about rewritten components
- Run existing regression suites on the first releases that cite AI-refactored code
Delivery
Role takeaway
- Work
- Add a roadmap watch item and review upgrade test coverage for Cisco platforms.
- Dependencies
- Cisco release disclosures
- Customer lab capacity
- Ownership
- Customer network/security operations owns upgrade validation; partner supports.
- Skills and adoption
- Engineers need regression-testing and rollback skills more than AI skills for this item.
- Governance checkpoints
- Change advisory board review of first releases citing AI-refactored code
- Security review of release notes and advisories
- Acceptance criteria
- Proposed: documented regression test plan for each critical Cisco platform
- Proposed: rollback rehearsed for the next major upgrade
- Risks
- Over-reading an executive target as a product commitment
- Untested large code changes reaching production
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
If the rewrite reaches network operating systems or security appliances, SLED engineering teams should expect larger-than-usual code changes in future releases. Their own regression and lab testing before upgrades becomes more important, not less (interpretation).
Governance
Who approves, reviews and stays accountable for outcomes?
Agencies relying on vendor secure-development attestations may want to ask how AI-generated code is reviewed and tested before release; the article provides no answer (interpretation).
Security and privacy
What data, permissions and controls need testing?
The article does not discuss security. Any security benefit is a later claim by Patel (see the India Today item) and is unverified.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Workforce angle: the article frames AI-assisted refactoring as work for a small, early-career team. SLED IT shops considering similar efforts would need staff able to verify AI-generated changes, not just generate them. No accessibility content.
Procurement
What should contracts, pricing and exit terms secure?
No procurement change. At renewals, agencies may ask Cisco how AI-generated code is reviewed and tested before release (interpretation).
Operating model
Which teams own the service once it runs?
Shows a vendor operating model in which a two-person team catalyzes a large AI-assisted rewrite; SLED operating impact is limited to future upgrade validation.
Publication history
- 2026-10-31Cisco · Issue 035 resources
Stable resource ID: fortune-cisco-ai-refactor-98-percent-legacy-code-24-month-target-20261030