Built different.
Teaching different.
I'm not a trainer. I'm an engineer with 30 years in the field (Staff Engineer, Founder, CTO, VP of Engineering) who left to build with AI full-time. I started teaching it because I kept having the same honest conversation with executive friends who needed someone without an agenda.
I've spent the last decade building software products at scale: the kind that have to work when they can't afford not to. I lead engineering teams, make architectural decisions, evaluate tooling every week, and ship AI-powered features to production.
For the past two years, AI has been central to how I work and what my team builds. Not as an observer. As a builder. I know what's real, what's performative, and what's genuinely transformative, because I've used it all.
I started The AI Briefing because I kept having the same conversation with executive friends outside of tech. They knew AI was important. They were surrounded by vendors selling products, consultants selling engagements, and conference talks that ended with a slide about "transformation." Nobody was just sitting down with them and being honest.
That's what I do.
Built with AI, not just around it
My team ships AI features. I'm in the tooling every day, not once a quarter.
Executive fluent
I've presented to boards. I understand your context, your constraints, and your calendar.
No agenda
I'm not affiliated with any AI vendor. I don't have a product to sell you after the session.
"The most valuable thing I can do in three hours is give you the judgment to navigate AI on your own, with enough of a network around you that you're never alone when the hard questions come."
Why I charge. Why I limit it.
The structure isn't arbitrary. It's designed to make sure that when you're in the room, it actually matters.
-
The format filters for seriousness.Private, by introduction only. The people in the room want to be there.
-
Four sessions a month keeps quality high.This isn't a business I'm scaling. It's a practice I'm maintaining. Four sessions means full preparation, full presence.
-
The money isn't the point.The introduction you make at the end is worth more to me than the fee. I'm building a network of people who've seen what I can do. That's the real currency.
-
I want you to leave capable.The session succeeds when you don't need me anymore, except as a peer you trust.
Where I come from.
Thirty years building software as a Staff Engineer, Founder, CTO, and VP of Engineering across early-stage startups and large-scale organizations. I've been close to AI tooling since before it was mainstream, close enough to know what to trust and what to avoid.
Jason Wolfe · LinkedIn →
Let's have a conversation.
If someone pointed you here, I'd like to hear from you. No pitch. No pressure.
Request an Introduction →