Activation Sessions

The easiest place to start. One session, just you and me -- we start building a real project of yours together, and you leave with a working prototype in hand. Not a class, not a demo you watch. We see how it feels, then talk about what's next.

It started organically.

I was an extremely early adopter of Claude Code -- a solo founder building an AI-native startup, in it every single day. It honestly felt like a secret I was in on: I could see what it did to what one person could make, and I couldn't not show people. So I started sitting down with friends who felt behind and building something real with them, right there.

Before each one, I'd put together a highly personalized playbook -- what I knew about them, why they'd reached out, the thing they wanted to build -- so we could skip the setup and get straight to building. That's where the name comes from: every activation starts from a playbook made for you.

What actually happens in a session

Every session starts the same way. I ask, "how are you feeling about AI?" And almost everyone says some version of the same thing... overwhelmed, behind, like the train left and they're on the platform. Here's what I tell them, and it's true: even the best engineers I know feel that way right now. This isn't a gap you fell into. It's a moment you get to leapfrog.

That's the first thing we do, before we touch a single tool. We get the weight off.

1. First, I get to know you -- not just the work.
Before we touch a single tool, we talk about you: what you do, sure, but also how you're feeling about all this and how you're thinking about it. Overwhelmed, skeptical, fired up... all of it's useful. The magic isn't the tool. It's the thing you know that the AI doesn't, and finding it starts with understanding where you really are.
2. We start building your project.
Usually the one already scoped in your playbook -- something real from your actual work, not a toy or an "imagine if." We bring your real stuff into it... your data, your docs, your mess. That's what makes it land.
3. We build a prototype, and line up what's next.
By the end, there's a real prototype on your screen that you built yourself. Not a finished product -- a working start. We spend the last stretch mapping your next steps, so you leave knowing exactly how to keep going.

Why I call it activation

Here's what makes this moment different. Most people are still only using AI's brain -- they chat with it, ask a question, close the tab. The leap is using its hands too. That's what Claude Code is: not a smarter AI, the same intelligence with hands. The simpler tools get you in the door, but this is where the ceiling actually is -- the fullest expression of what one person can do, at least for now. One person can now do what used to take a team. That's not a threat. It's liberation.

And here's the part that matters most to me. These tools can make people feel smaller, more replaceable, more behind. This work is the opposite of that. Done right, it's a deeply human thing... it gives you back a sense of agency, the feeling that what you want to build is actually yours to build. That's not a skill I'm teaching you. It's a change in what you believe is possible for you. That's the activation.

When you want to go further: Expansion Sessions

A lot of people finish an activation session and immediately want to keep going. The prototype is real, but now they want to make it really real... wire up the backend, get it live, or just learn how to apply this to the next ten things on their list.

That's an Expansion Session. Same setup, you and me, picking up right where we left off. We take the thing you built and push it toward something you actually use. Most people don't book this in advance. They book it after the first session, once they've felt what's possible and want more of it.

Building your command center.
Set up the context, memory, and tools so AI works the way you think, across everything you do.
Making it real.
Wire up the backend, get it live, and turn the prototype into something you actually use -- and learn how to keep it running and improving on your own, long after the session. See how it works →
Automating the busywork.
Take something you do by hand every week and build an agent -- or a Claude Code skill -- that just handles it for you.

Ways to do this

It started one-on-one, and that's still where the magic is most concentrated. But the same thing works in a few shapes, depending on what you need.

1:1 (where most people start).
Just you and me. The most personal version. We go at exactly your pace and build exactly your thing.
Small groups.
A handful of people, often a founding team or a few friends learning together. You get the personal attention, plus the bonus of watching what everyone else builds, which sparks ideas you wouldn't have had alone.
Workshops.
For teams and organizations who want to move a whole group at once. Same heart, same "build something real today" promise, scaled up. (These grew out of the 1:1 work, so they keep its soul... nobody leaves having only watched.)

Who this is for

This is for you if you've felt that quiet "I'm falling behind on AI" thing and you're tired of it. You don't need any technical background. You don't need a perfect idea. You just need one real thing you've been wanting to make, and a willingness to be a beginner for a session.

Founders, operators, creatives, academics, people mid-career-change, people who are great at their craft and brand-new to this... that's exactly who walks in. The common thread isn't a resume. It's the feeling that your reach should be bigger than your tools currently allow. We fix that.

Who I am

Colton Hess

I'm Colton. I just finished my MBA at Berkeley Haas and am now finishing my MPH at the UC Berkeley School of Public Health. I was in the inaugural cohort of Berkeley's AI for Business certificate, one of the first AI-focused MBA programs in the country. I have experience as a founder myself, and a deep respect for what it takes to lead an organization in a rapidly changing world.

More on the about page →  ·  LinkedIn →

Questions people ask

What actually happens in an activation session?
We start with how you're feeling about AI (honestly, usually "behind" -- that's normal). Then I get a sense for you and your work, we pick one real project you've been wanting to make, and we build it together. By the end you're holding a working prototype you made yourself. Most people take a photo of it.
Do I need a technical background?
No. None at all. If you can describe what you want in plain English, you can do this. The thing that makes a session land isn't coding ability, it's the stuff you already know about your own work that the AI doesn't. That's the part you bring.
Can you do this for my team?
Yes. It started one-on-one, but it works beautifully in small groups and full workshops too. The promise stays the same: everyone leaves having built something real, not just watched a demo. Send me a note about your team and we'll shape it.

Let's build your thing.

Bring one real project, and we'll start with how you're feeling about all this, find the thing only you know, and get something built before you leave. That's the whole promise.

Not sure if it's a fit? Send me a note and we'll figure it out together.