How to Build AI-first Business OS using Claude
Most leaders experiment with AI. You'll leave with the Decision OS your team runs on, populated with your real reports, OKRs, and decisions.
Most leaders use AI like a search engine. AI-native leaders use it as an operating layer — for decisions, weekly reviews, hiring, customer conversations, and strategy.
The difference isn't the tool. It's the system. AI-native leaders have built a personal Decision OS — the prompts, agents, and recurring workflows that take their judgment and turn it into something repeatable.
This 2-day cohort walks you through designing and deploying yours. You'll map where your decisions and time leak today, then build a Decision OS in Claude Code that captures your judgment in workflows you'll actually run weekly.
By the end of day two you'll have a working Decision OS, the templates to extend it, and a coaching session with peer leaders to refine it.
This is for leaders who want to operate with AI as infrastructure, not as a toy.
Day 1 — Module 1: What an AI-Native Leader Actually Does
- Beyond chat: the operating-layer mindset
- Examples of leaders running real Decision OS workflows
- Why most exec AI usage stays shallow
- The hierarchy: prompts → workflows → agents → OS
- What a good Decision OS looks like
Day 1 — Module 2: Map Your Decisions
- Where your time and judgment leak today
- Decision categories: strategic, operational, people, customer
- Identifying the repeatable vs. the truly novel
- Prioritizing the highest-leverage 3-5 workflows to build
- Drafting your OS architecture
Day 2 — Module 3: Build Your Decision OS
- Setting up Claude Code as your operating layer
- Structuring context: company, team, customers, your style
- Building reusable prompts for recurring decisions
- Designing weekly review and reflection workflows
- Wiring agents for ongoing tasks (research, drafting, summarization)
Day 2 — Module 4: Coaching Round
- Each leader presents their Decision OS to the cohort
- Live feedback and iteration
- Patterns to copy across leaders
- Where Decision OS thinking breaks down (and what to do)
- Your 30-day operating plan
Live Q&A — Adapting to Your Leadership Context
- Real questions from founders, execs, and team leads
- Recommendations for different team and company sizes
- How to evolve the OS as the company grows
- Common adoption blockers and how to work around them
For the people who ship, not the ones who pontificate.
- You're operating in a leadership role (founder, exec, team lead, ops leader)
- Basic comfort with AI tools (Claude, ChatGPT, etc.)
- Willingness to share real (anonymized) decisions during the coaching round
- A laptop and 2 days of focused time
- A laptop
- Claude Code installed and signed in
- Access to relevant company context (team, customers, current bets)
- A note-taking tool
- Your most recent strategic memo or quarterly plan
- A list of recurring decisions you make weekly
- A peer leader to enroll alongside you (cohort works well in pairs)
This is a small-group cohort. Expect to share real (anonymized) decisions and get coached.
He helps teams at ICICI Bank, Deloitte, and others adopt AI in ways that compound, building durable systems instead of chasing prompt tricks.
As founder of Agentiwise, he designs agent systems, automation platforms, and production-grade AI apps that move teams from prototype to real business impact, currently advising brands like ICICI Bank and Deloitte. He's also founder of glued.me, a marketing SaaS that automates the full performance marketing stack end-to-end, agent-driven. Beyond building, he teaches AI globally through LinkedIn Learning, O'Reilly, and YouTube, turning dense concepts into plain, example-driven walkthroughs.
Is this only for founders?
Do I need a technical background?
Can my co-founder or partner join with me?
Refund policy: Refund requests are eligible only if submitted at least 24 hours before the start time of the first workshop of the cohort. For example, if the first workshop begins on the 24th at 7:00 PM, refund requests must be submitted by the 23rd at 7:00 PM. No refunds will be issued after this deadline.