The 2027 Agentic Advantage
Co-presented a session where each attendee left with a first AI agent mapped out.
The part of AI work that begins after the demo: helping people understand what a system can do, build against real work, and keep using it when the novelty wears off.
PRACTICAL AI EDUCATION
Since January 2025, I have led or co-led 90+ workshops, talks and multi-week courses for executive, operator and technical audiences. Thousands of professionals trained. 50+ organizations worked with directly since January 2025.
I teach business owners, operators and professional-service teams, including people using AI for the first time. We work on tasks they recognize, so they can try the approach again after the session.
Co-presented a session where each attendee left with a first AI agent mapped out.
Led both sessions on personalizing Claude and putting it to work.
Trained the 20-person Business Transformation team, plus a four-week series reaching up to 200 employees.
Completed a live AI security and platform exercise in 18 minutes, first among about 75 developers and engineers in a session allotted up to five hours. Used Gemini to find rogue shadow agents, remediate vulnerabilities and improve the system. Selected as one of five to present, briefing in role as the startup’s AI security lead.
A recurring series for business owners and operators on AI agents, practical follow-up, and systems that give teams time back.
A practical session on Claude and applied-AI workflow education for business operators and AI adopters.
A session on practical tool selection and the work of deciding where AI is actually useful.
A speaker session on applied AI and business AI for a mixed operator and professional audience.
A conference session on AI and technology for more efficient note and loan-management work.
The problem. Turning a capable model into a reliable business role takes clear ownership, scoped access, approval rules and evidence of readiness.
The approach. Structural checks, live authorization with read-back, and client acceptance are three separate gates before an agent goes live.
The rule. I verify access and results before asking the client to accept the agent for its role.
The problem. A connector list can make a system look more capable than it is. A useful integration has to run under the correct identity, with the right account, clear permissions, and an understandable approval moment.
The approach. I design for scoped access, named account selection where ambiguity matters, safe read-back verification, and a deliberate distinction between learning about a workspace and taking action inside it.
The rule. Verify the account and read back the result. Escalate when an action falls outside the approved scope.
THESE NOTES DESCRIBE ARCHITECTURE, GATES AND DESIGN TRADE-OFFS. DEPLOYMENT WORK, CUSTOMER CONFIGURATION AND CONNECTED ACCOUNTS ARE PRIVATE.
Based in the Seattle area. I build agent systems that run in production, and I teach teams to use them.