I Lost Access to My AI and My First Thought Was “I Guess I’m on Vacation”

At the end of 2025, I was working like most of you probably do right now. Take on a project, have some chats with ChatGPT or Claude along the way, get help brainstorming ideas or drafting a section of a report. Use image generation for visuals in a deck. Maybe let AI help outline a workshop.

It was useful. It saved time here and there. But the work was still fundamentally mine to do. AI was an assistant — a smart search engine with better manners.

I was the one doing the industry research. Writing the analysis. Building the workshop in Mural. Structuring the JTBD map. AI handed me ingredients. I did the cooking.

If you’d taken away my AI access back then, I would have been annoyed. But I would have kept working. Losing it would have been like losing a good calculator — inconvenient, not debilitating.

That’s not where I am anymore.

In early 2026, I stopped chatting with AI and started working with agents.

The difference sounds subtle. It’s not.

Chatting with AI means you’re the worker and AI is your research assistant. You ask questions. You get answers. You do the work.

Working with agents means you’re the director and they’re your production team. You set the vision. You define the quality standards. You review and refine what they produce. But the actual production — the research, the drafting, the data gathering, the formatting, the iteration — that’s happening around you, often in parallel.

Here’s what my workflow actually looks like now. I work in innovation — Jobs to Be Done mapping, client workshops, industry research, identifying unmet needs, ideating new solution concepts, rigorous theory testing, proof of concept, prototyping. The kind of work that used to mean weeks of solo research, synthesis, and deliverable production.

Now I have agents for it. I run them through Claude Code — a command-line interface where I can orchestrate agents, define their roles, and build structured workflows. When I need to map a competitive landscape, a research agent digs through industry data, identifies patterns, and surfaces insights I’d have spent days finding manually. When I’m building a JTBD analysis, an agent structures the framework while I focus on the strategic judgment — which jobs matter, which are underserved, where the real opportunity sits. When I need to pressure-test a concept, an agent runs it through evaluation criteria while I decide what questions to ask next.

I direct the process, make decisions at each stage, and apply my judgment to the output. I’m not copy-pasting from a chatbot. I’m running a production operation.

It extends to everything. Presentations, visual assets, written deliverables, workshop preparation — all of it runs through agents with context about my work, my standards, and my preferences. They aren’t generic. They know what “good” looks like for my specific work because I’ve given them the rules, the templates, and the constraints.

This is the part people miss when they hear “AI-generated content” and picture slop. Output quality isn’t a function of AI capability alone — it’s a function of the *system* you build around it. Context, rules, guardrails, and human judgment at the right moments. When that system is well-designed, the output is frequently better than what I’d produce solo. Not because the AI is smarter than me, but because it can explore more options, maintain more consistency, and execute more thoroughly than one person working alone.

I’ve been tracking my output this month. Conservatively, I’m producing 10x what I could do manually. On the projects where agents handle the most production work — deep industry research, multi-layered analysis, concept development — it’s closer to 27x. Those numbers aren’t precise, but the direction is unmistakable. This isn’t a marginal improvement. It’s a different category of work.

The best metaphor I’ve found for this is filmmaking.

A film director doesn’t hold the camera. They don’t build the sets. They don’t edit the footage frame by frame. But the movie is unquestionably theirs. Their vision, their decisions, their quality bar.

That’s what agentic co-work feels like. I act as director, editor-in-chief, CEO of my own projects. I am frequently not the doer, but the leader. The agents are my cinematographer, my production designer, my sound editor — specialists who execute at a level I couldn’t match individually, but who need my direction to produce something coherent and intentional.

Sam Altman described this exact dynamic at the Snowflake Summit: “You hear people that talk about their job now is to assign work to a bunch of [AI] agents, look at the quality, figure out how it fits together, give feedback.” He’s describing me. He’s describing a growing number of people. And soon, he’ll be describing the baseline expectation for knowledge work.

Here’s what people get wrong, though: they assume this means less work. It doesn’t. Directing is harder than doing, in some ways. You have to know what good looks like before you see it. You have to articulate standards you used to keep in your head. You have to make dozens of judgment calls per hour instead of just executing a task.

The skill set shifts from production to curation. From creation to orchestration. The effort doesn’t disappear — it concentrates on the parts that only a human can do.

But the leverage? The leverage is something else entirely.

My experience isn’t an outlier. The data tells the same story at scale — with a split ending.

According to Gallup’s Q4 2025 workplace survey, 49% of U.S. workers have never used AI at work. Nearly half. Meanwhile, daily AI use has climbed to 12%, and in tech, 57% are frequent users.

This isn’t a bell curve. It’s a bimodal distribution. People are either in or they’re out.

Among leaders, frequent AI use has risen from 17% to 44% since mid-2023. Among individual contributors? From 9% to 23%. Leaders are pulling ahead — not just in adoption, but in the kind of work AI makes possible.

Gartner predicts 40% of enterprise applications will feature task-specific AI agents by the end of 2026. In 2025, that number was less than 5%. An eight-fold increase in a single year.

Here’s the number that should stop you: according to OpenAI’s State of Enterprise AI report, frontier workers send 6x more messages than the median employee — and in coding and data analysis, that gap widens to 16–17x. Workers who save more than 10 hours per week aren’t just using AI more often. They’re using it across more tasks, with more tools, in more integrated ways. The gap isn’t between people who use AI and people who don’t. It’s between people who’ve restructured their work around AI and people who treat it like a fancier Google.

Yet according to Deloitte’s Tech Trends 2026 research, only 11% of organizations have AI agents in active production — despite 38% piloting them. Most are still experimenting. Still writing strategy decks about whether to try.

And the tools are catching up to the ambition. Anthropic just launched Claude with co-work — a visual, user-friendly platform for running agents without touching a terminal. The creator of popular open-source agent tools has been hired by OpenAI, signaling accessible agent interfaces coming from every major player. The barrier to entry is dropping fast.

The gap isn’t just between individuals. It’s between people like me who’ve already built these systems and organizations that haven’t started. And soon, they won’t even have the “it’s too technical” excuse.

Let’s be honest about what this means.

If you’re still in the “chat with AI sometimes” phase, you’re not behind — but the ground is moving under you. The people who’ve made the shift to agentic work aren’t a little more productive. They’re operating in a fundamentally different mode. It’s the difference between emailing your team and *having* a team.

I know this lands differently depending on who you are.

If this makes you skeptical — fair. “AI changed everything” is a tired headline. But I’m not making a prediction. I’m reporting what happened to me, with the data to back it up.

If this makes you uncomfortable — sit with that. Not because AI is coming for your job tomorrow, but because the people who figure this out will operate at a level that redefines what “productive” means. That changes what employers expect and what clients demand.

If this excites you — you’re the right audience for what comes next.

I know what you’re thinking, because I had the same thought staring at that API limit screen: Isn’t this dangerous? Haven’t you made yourself completely dependent on a tool?

Yes. And I’m fine with that.

We’re already dependent on electricity. On the internet. On cloud services. On our phones. Nobody calls those dependencies “dangerous” anymore — they’re infrastructure. The question was never whether to depend on powerful tools. It was always about whether to be the last person doing it the old way while everyone else compounds their advantage.

My “vacation until March” moment wasn’t a failure. It was confirmation that the system I’d built was working so well I couldn’t imagine going back. That’s not weakness. That’s what leverage feels like from the inside.

The risk isn’t dependency. The risk is irrelevance.

If you’ve read this far, you’re probably wondering how to make this shift. There’s no quick playbook, but here’s what I’ve learned:

Stop chatting, start building. The difference between using AI and working with AI is structure. Give it a role. Give it context about your work. Give it quality standards. Turn a conversation into a workflow.

Think in systems, not sessions. A single AI chat is useful. A set of agents with defined roles, shared context, and quality rules is transformative. The magic isn’t in any one interaction — it’s in the architecture you build around them.

Embrace the role shift. You’re not being replaced. You’re being promoted. The skills that matter now are judgment, direction, quality control, and taste. Those are human skills. They’re leadership skills. And they’re suddenly the bottleneck.

Start before you’re ready. I went from chatting with Claude to directing a team of agents in about two months. You don’t need to be a developer. You need to be willing to experiment. The tools are meeting you where you are — and they’re getting easier by the month.

The window is open right now. Not next quarter. Not when your organization rolls out an AI strategy. Now.

Here’s the thing about exponential shifts: by the time they’re obvious to everyone, the advantage belongs to the people who moved first.

I learned that staring at an API limit screen, realizing my entire working life had been quietly, fundamentally transformed — and I’d barely noticed it happening.

Don’t wait for your own “vacation until March” moment to see what’s changed.

— -

If this resonated, share it with someone who’s still in the “chat with AI sometimes” phase. They need to hear this more than you did.