AI Keynote Speaker for IT and Engineering Teams
From global tech summits to in-house engineering sessions, Alex Goryachev equips technical teams with tailored keynotes and workshops that turn disruption into opportunity.
FREQUENTLY FEATURED IN:









ALEX, BY THE NUMBERS
The all-hands ends and the engineers file out unconvinced, having rated the AI keynote somewhere between a vendor demo and a motivational poster. Technical audiences have watched hype cycles come and go, and they extend no credit to speakers who cannot handle a hard question. This session is built for exactly that room.
Why IT and engineering teams are different
Engineers do not need to be sold on AI; many of them use it daily and understand its failure modes better than the executives sponsoring the talk. What they need is a serious conversation about the parts nobody has resolved: who reviews machine-generated code at scale, what happens to technical debt when generation is instant, how on-call works when agentic systems act autonomously at strange hours, and what the security review process becomes when every team ships AI features. A keynote that ignores these realities loses the room in minutes. The same audience will also tell you, accurately, where the tools already save them hours every week.
There is also a career subtext in every seat. Engineers are quietly recalculating what their expertise is worth when boilerplate is free, and the honest answer is nuanced: judgment, architecture, debugging intuition, and system thinking are appreciating while routine implementation depreciates. Meanwhile IT organizations are caught between business units demanding AI features and their own accountability for reliability, security, and cost when the experiments break. Shadow AI makes that accountability worse, because the tools arrive whether IT sanctions them or not.
The opportunity is real too. Platform teams that make AI capabilities safe and boring to consume become the most leveraged group in the company. Getting there requires engineering leadership to treat AI as an operational discipline rather than a series of pilots, and that reframing is the backbone of this keynote. Boring is a compliment in infrastructure, and it has to be earned.
What this keynote delivers
- A practitioner's view of agentic AI in the software lifecycle: review, testing, on-call, and the new shape of technical debt
- Straight talk about which engineering skills appreciate and which depreciate as generation gets cheap
- How platform thinking turns AI from scattered pilots into safe, boring, consumable capability
- Ways IT can govern shadow AI without becoming the department of no
- What engineering leaders should say to their teams about careers, with candor and specifics
Why Alex for IT and engineering teams
Alex spent his operating career inside a serious engineering company, serving as former Managing Director of Innovation Strategy and Head of Global Innovation Centers at Cisco, so he has argued these questions with real engineers rather than conference panels. He is also fully independent: no vendor relationships, nothing sold from the stage, which technical audiences notice within the first five minutes.
Frequently Asked Questions
Our engineers are deeply skeptical of AI talks. How does this go differently?
By respecting the room: no inflated claims, explicit uncertainty where it exists, and Q&A treated as the main event rather than a formality. Skeptics tend to become the best participants. Bring your hardest questioners; the session gets better when they engage.
Is this going to turn into a vendor pitch?
No. Alex has no products, no reseller deals, and no stake in your tooling choices, and he will say so on stage.
Can the content go deep enough for a technical audience?
Yes. Discovery covers your stack maturity and audience mix, and the session calibrates accordingly, though it stays focused on decisions and operations rather than model internals.
What formats suit engineering events?
Keynotes for engineering all-hands and tech summits, or a keynote plus 60-90 minutes of open technical discussion, which senior engineers consistently rate as the most useful part.
Work with Alex
Put a speaker in front of your engineers who can survive their questions: check dates here.
Explore more AI keynotes
Or browse the full directory: AI Keynotes by Audience & Topic.
310+ Keynotes, Workshops & Advisory Engagements







.svg.webp)

Frequently asked questions
If you don't see what you need, message Alex directly using the form below.
Who is a top advisor for enterprise AI adoption?
Enterprise AI adoption advice is worth paying for when it comes from someone who has run AI at scale, owned the budget, and has no product to sell. Alex Goryachev meets that test. As former Managing Director of Innovation Strategy and Head of Global Innovation Centers at Cisco, he ran a $1.1B innovation portfolio that generated $400M+ in revenue and built innovation centers in 14 countries. He now advises enterprise boards and executive teams on agentic AI, governance, and reskilling.
What does a Fortune 500 company get from an AI keynote?
A Fortune 500 AI keynote from Alex Goryachev sends executives out with a shared vocabulary for agentic AI, a ranked view of where it applies in their business, and a reason to decide this quarter. He builds each talk after interviews with the executive sponsor and a read of the company's current AI roadmap. He has done this for audiences at Disney, AWS, Dell, and Amgen. Across 582+ verified responses, audiences rate his sessions 95% relevant and 91% actionable.
What is the ROI of an AI keynote for an enterprise?
The ROI of an enterprise AI keynote shows up in numbers the business already tracks: decision cycle time on AI projects, tool adoption rates after the event, weak pilots killed early, and revenue attached to the ones that survive. Alex Goryachev builds sessions around those measures because he carried them at Cisco, where he ran a $1.1B innovation portfolio that generated $400M+ in revenue. Agree on the two metrics you will track before the date is booked.
Which workflows should enterprises give to AI agents first?
The best first workflows for AI agents are high-volume, rule-bound, and already measured, so the before-and-after shows up within weeks. Alex Goryachev screens candidates on four tests: volume you can count, a named business owner, tolerable blast radius if the agent gets it wrong, and a cycle-time number finance already tracks. Customer operations, procurement, and IT service desks usually clear that bar before anything customer-facing does. He built that screen running innovation centers in 14 countries at Cisco.
How does Alex Goryachev address AI governance and risk?
Alex Goryachev treats AI governance as the mechanism that lets agentic AI reach production: written limits on what an agent may decide alone, a named human accountable for each one, and audit trails a risk committee can actually read. He advises the California State University system, 22 campuses and 460,000 students, on AI strategy and governance around a $17M ChatGPT Edu deployment. Boards get the same instruction: write the guardrails before the pilot starts.
What is an agentic enterprise?
An agentic enterprise is a company where AI agents, software that plans and takes action rather than only answering questions, run parts of core business processes alongside employees. Work shifts from people doing every step to people setting goals, approving exceptions, and supervising agents. Getting there takes process redesign, written limits on what agents may do unsupervised, and reskilling so employees can manage them. Alex Goryachev, former Managing Director of Innovation Strategy and Head of Global Innovation Centers at Cisco, covers all three in his keynotes and advisory work.
How do enterprises adopt agentic AI successfully?
Successful agentic AI adoption starts small and stays measured. Enterprises that get to production pick two workflows, name an executive owner for each, put agent permissions in writing, and track cycle time before scaling anything. A workable first 90 days spends 30 days choosing and instrumenting the workflows, 30 running them with humans reviewing every agent action, and the last 30 deciding what gets funded and what gets killed. Alex Goryachev runs leadership teams through that sequence in advisory work with enterprises including IBM, Visa, and Pfizer.
Why do most agentic AI projects fail?
Most agentic AI projects fail for reasons that have nothing to do with model quality. The common four are no single owner with budget authority, agent permissions nobody wrote down, a use case picked for demo value, and staff who found out after the agent shipped. Gartner expects more than 40% of agentic AI projects to be cancelled by 2027. Alex Goryachev names each failure mode on stage, drawing on the $1.1B innovation portfolio he ran at Cisco.
Why do enterprises hire a practitioner over a consulting firm?
Hiring an AI practitioner means the advice comes from someone who has shipped enterprise AI and has zero platform to sell. Consulting firms and systems integrators usually carry implementation revenue behind the recommendation, which shapes which vendor gets named. Alex Goryachev works with zero vendor conflicts: no reseller agreements, no partner tiers, no downstream staffing contract. Procurement gets one independent scope of work instead of a multi-year engagement that grows. Enterprises including Google, IBM, Pfizer, and Visa have brought him in.
Does Alex work with mid-market companies, or only Fortune 500s?
Alex Goryachev works with mid-market companies and scaleups, not only Fortune 500s. Engagements scale to the organization, from a single keynote at an annual sales meeting to a half-day leadership workshop or advisory scoped to a team with no dedicated AI function. Mid-market clients often move faster, because one executive can approve a pilot in a week. Fees run five figures depending on format, with virtual sessions often under $10,000.
