I help scale human capability with AI systems. Twenty years helping people and companies move through technological change.
Twenty years helping people and companies move through technological change. I build the education that turns AI into new capability.
The tools change every week. The skill worth building is knowing how to direct them across your work.
Model capability and the harnesses around it move fast. New models, new tools, something to relearn most weeks. Keeping up with that is real work, and it wears people out.
Underneath the churn is something steadier: a way of working with machines. Once you have it, the next tool is a new instrument for a craft you already know. That way of working has a name in how I teach it. Orchestration: directing AI across a whole piece of work while keeping your hand on the outcome. The tools will keep changing. The mental model is what carries you from one release to the next without starting over.
That model is a new way to work, and the hard part of it is human before it is technical. Handing your work to a collaborator you cannot fully see raises real questions of trust and control. I spend as much time on that transition as on any feature.
The hardest thing to hand an AI is the judgment you have built but never had to explain. Over the past few decades, professions grew through specialization, and specialists build intuition they can no longer put into words. A banker or a trial lawyer knows things in their hands that never made it onto a page. To work well with AI, you have to get that knowledge out of your head and into language a machine can use. My frameworks are built to help you do that: surface your own judgment, describe it, and let AI carry it so your experience scales with the work.
Every framework I build, the Orchestrator Method™ and everything after it, is built to augment and scale what a person can do, not to replace them. Replace the person and their judgment stops shaping the real work, and that judgment is what we are trying to scale.
To work well with AI, you have to get that knowledge out of your head and into language a machine can use.
I teach this as The Orchestrator Method™: five principles for delegating real professional work to AI. Say you need a competitive brief. The first time, you run all five in order, and the last one saves the whole workflow as a reusable skill. Next time you need that brief, you run the skill in one step and start where you left off. The first pass takes thirty minutes. Every one after takes two.
Most AI training is a one-off. People learn a few prompts and plateau, because nothing tells them what the next real step is.
A path fixes that. It shows a person where they stand and what changes at the next step, and it shows a company how to move from scattered use to capability it can count on. I built two versions of the same path: one for a person building a career, one for an organization building capability. Each step has its own training and its own outcome you can point to.
Change management runs alongside every step, because capability only counts once people adopt it.
I teach orchestration, and I run my own work on it every day.
My work happens in the terminal, with Claude Code as the orchestrator. I built a production system of skills, agents, and connected tools that drafts curriculum, runs research, and produces content, with me directing and reviewing every step. This site was built the same way. So was the course. When I teach orchestration, I am teaching what I do.
I teach building because I build. Here is some of what I have shipped.
A certification, a company, two products, and a newsletter, all built the way I teach, with Claude in the terminal and me directing every step.
From people I have taught.
ILO Group partners with K-12 education agencies across the country, and we wanted our consulting team to use AI consistently and well. Three sessions with Sash leveled up our team. He taught the orchestrator mindset, the task decomposition framework, and showed us how to build our own custom Claude skills. The skillset has allowed our consultants to focus more time on our important work - the research, synthesis, and strategy that moves our clients forward.
Just completed Sash's course on AI for knowledge work, and it took my AI knowledge to the next level. It is an incredibly useful, hands-on deep dive into building actual skills and autonomous agents with Claude. What really sets this course apart is the balance between practice and theory. Whether you are an industry professional looking to scale your workflows or a curious beginner just starting out, this course is absolutely for you.
This seminal and well structured course helped me spruce up my (outdated) AI knowledge, now at par with a fairly well versed AI practitioner of today. As a new joiner at an AI ready firm, I was anxious about my gaps in knowledge. This course got me right back up with its generous and thorough exploration of concepts, especially systems thinking, agentic orchestration and data organisation, along with toolage and frameworks. Shashwat brings the energy and excitement as a tutor, fused with well curated materials, and as a well developed communicator, making it easy to engage.
Really glad I took this one. Sash did a great job breaking down AI in a way that's actually practical and useful to your personal life and work right away. You start with prompt writing, then you move into orchestration, and eventually you're building agents. Since the class size is small, he is able to give personal attention. Would definitely recommend this to anyone who wants to go beyond just chatting with AI and actually make it work for them.
I came up as an enterprise support engineer, resolving critical failures for large IT organizations. Fixing the same problems repeatedly, I moved into teaching the teams to run their own systems, and that became my work. Over a decade I built technical curriculum and trained more than a thousand IT professionals across Southeast Asia and the United States, writing every hands-on lab myself. The training measurably reduced outages and improved IT health.
Then I spent a decade helping enterprises adopt what came next: first the cloud, then data and AI. My work was enablement, which meant teaching every group in the room. On one major bank's $200M move to the cloud, I taught the IT admins the migration and data-privacy details and walked the executives through banking use cases. I brought the legal team up to speed on eDiscovery in the new tools and worked with the bank's security team to clear compliance. Getting a change that large to land means bringing every one of those people with you.
When AI arrived, I built the education for it. I founded Rift Lab to teach AI-native work, developed the Orchestrator Method™, and now run cohorts and advise leaders on adoption.
Across every one of those shifts, the job has been the same. I help people move through change, and I build the learning that gets them there.
Leading a team or a company through AI adoption? I help leaders and their people build the skilling and the change that makes it real.