You have probably already begun. A few chats with an AI assistant. A tutorial half watched on a Sunday. A folder of links called “AI stuff” that you rarely reopen.

And still the real question has not moved an inch: where does any of this actually go?

Every week drops ten new tools on you, and a hundred voices insisting you are already behind.

Not one of them hands you an order to do things in.

What You’re Missing Is A Map

AI advice reaches you as a pile. A clever trick here. An app you simply must try there. A thread of fifty tips with no first step and no last one.

A pile is not a path. You can stand in front of one for a year and climb nothing.

I spent seventeen years building software systems, and I still walked straight into that pile when AI agents arrived. Three weeks comparing frameworks, with nothing built at the end of them.

The fix came from admitting I had no order to work in, and then building one.

This ladder is that order. It is the map I wish someone had handed me on day one.

It Works Like A Ladder, Rung By Rung

Here is the one idea this whole publication runs on: structure beats prompting.

A result that holds up does not come from cleverer words. It comes from architecture. A clear role. The right context. A fixed shape for the answer.

That is true for a single AI task. You can feel it in ten minutes.

It is just as true for the whole journey. Getting good at this works like a ladder, and every rung is a real skill you did not hold before.

Subscribe now

Seven Levels, Seven Real Skills

1. The Chatter. You get specific, usable answers instead of generic ones.

2. The Prompter. You turn your best asks into instructions you keep and reuse.

3. The Context Engineer. The AI knows who you are without being told again every time.

4. The Operator. The AI works on your real files, not only inside a chat window.

5. The Systemizer. Your repeated work gets packaged into named skills you can call.

6. The Orchestrator. Work runs scheduled and delegated, with you reviewing instead of watching.

7. The Director. You hand over an outcome, keep the judgment, and run your one-person business from the director’s seat.

That last move, handing over an outcome and trusting the system you built, is the agentic leap itself. The six rungs beneath it are how you earn it honestly.

Find Your Rung

You start where you actually are. Where Level 1 sits on the page has no claim on you.

Read down this list. The first line that names a wall you keep hitting is your level. Begin there.

• Level 1, The Chatter. You use AI like a search box. The answers come back bland, and when one misses you open a fresh chat and try again.

• Level 2, The Prompter. You have found a few asks that work, and you retype them from memory every single time.

• Level 3, The Context Engineer. You save your good instructions, yet you still re-explain who you are at the top of every new chat.

• Level 4, The Operator. The AI knows you, but it is stuck in a chat window. It cannot touch the files where your work lives.

• Level 5, The Systemizer. The AI works on your real files, and you still re-instruct the same job by hand each time.

• Level 6, The Orchestrator. You have packaged work into skills, and everything still runs one at a time with you watching.

• Level 7, The Director. Work runs scheduled and delegated, and you still carry every outcome from start to finish.

Most people land at one or two. That includes people who have used AI every day for a year.

Landing low is simply the rung where the ground turns shaky under you. That is the honest place to start.

Bring One Idea

This is a build, not a course you watch from the back row. Every level uses your own work as its raw material.

So come with one idea: a service you could plausibly sell, drawn from something you already know how to do.

Bookkeeping cleanup for tradespeople. Welcome emails for independent coffee roasters. Untangling spreadsheets for founders who are drowning in them.

Bring whichever idea is most truly yours. Whether it is the right one is a question for later.

No idea yet? Pick the dullest, most obvious skill you have, and use that.

By the end of the season you will hold the systems that run it: an instructions file in your voice, a core context file that knows your business, a small library of skills, and a weekly routine that runs while you are elsewhere.

You will also hold the materials to go and find a first client.

I will be straight with you about that line every week. I can hand you the systems and the structure. The client is yours to win.

How The Climb Works

One level a week. One step a day.

Each weekday post is a three to seven minute read with a single small action at the end. Something you do once and keep.

Saturday is a one-page recap, so a missed Tuesday never hardens into a missed week. Sunday is a short exercise, and Monday opens with the answer.

Season 1 starts Monday, the fifteenth of June. Seven weeks, seven levels, the first rung through to the leap.

The early levels run on whatever assistant you already have open, whether that is Claude, ChatGPT, or Gemini. You will not need a new account or a budget to begin.

A more capable tool joins at Level 4, where the work moves onto your real files. Even then, the lesson is the structure underneath, never the brand on the box.

One Honest Thing First

You will not “finish” AI at the top of this ladder, and I am never going to tell you that you have. The tools shift under all of us, constantly.

What the ladder gives you is footing. A way to always know which rung you are on, and what the next one asks of you.

When Season 2 arrives, the same seven rungs begin again, deeper this time, built on what you made in Season 1.

Two Things To Do Right Now

First, find your level in the list above.

Second, reply to this email with the level you landed on and the one idea you are bringing. I read every reply, and the patterns inside them shape what I write next.

The first issue, The 10-Minute Win, is already published and pinned to the top of this page.

If you want to feel structure beats prompting in your own hands before the climb begins, start there. Ten minutes, one working agent, a real brief on a real business by the end of it.

Subscribe, and meet me on the first rung.

Arsenios

The Agentic Leap. One real build, every week.

P.S. If you skimmed to the bottom first (I do that too), here is the whole thing in three lines:

1. The Agentic Leap is a seven-level ladder, from chatting with AI to running a small AI back office for your own service business.

2. Find the rung you are on, bring one business idea, and climb one level a week, starting Monday the fifteenth of June.

3. Start with the pinned issue, The 10-Minute Win, to feel how it works in ten minutes.

I know that loop from the inside. Seventeen years of building software systems did not make me immune to it. When agents arrived, I spent three weeks comparing frameworks before noticing I had built nothing at all.

Here is what the comparison time costs, and I will say it once: every week spent evaluating tools is a week your first real prospect goes unresearched and unapproached.

So today we skip the preparation. In the next ten minutes you will stand up a working agent that researches a prospect for you, and you will finish holding a structured one-page brief about a business you might actually serve. You need nothing new. The chat assistant you already use is the whole toolkit.

The principle before the build

An agent sounds like something that needs an engineering team. Strip the jargon away and a working agent is three sections of text:

1. A role. Who the model is supposed to be.

2. Context. Who you are and who the work is for.

3. A fixed output shape. The exact structure the answer must arrive in.

That third section does the heavy lifting. When you chat loosely with an AI tool, you get a different answer every time, so you never trust it with real work. When you fix the output shape, the same block of text produces the same kind of result on every run. Repeatability is what turns a tool you tried once into a system you use every Tuesday. The result comes from the structure you hand the model, not from finding cleverer words to decorate the request.

You will feel this yourself at minute eight, because we are going to run the same agent twice.

Subscribe now

The build

1. Minute 0 to 1: pick one real prospect.

   A business you could plausibly serve. The local roastery, the consultant whose newsletter you read, the design studio down the street. Have their website or main social profile open in a tab. Skip the famous companies; pick one you could actually email on Monday.

2. Minute 1 to 2: open the assistant you already use.

   Claude, ChatGPT, or Gemini. Any of the major assistants runs this build. Start a brand new conversation so nothing from an old chat leaks in.

3. Minute 2 to 4: paste the agent block.

   This is the whole agent. Copy it as one piece, exactly as written:

   

   You are a prospect research analyst working for me.
   
   WHO I AM
   [One sentence: what you do and who you do it for. Example: “I run a
   one-person studio building email welcome sequences for independent
   coffee roasters.”]
   
   YOUR JOB
   Research the prospect below using only publicly available information,
   then produce a Prospect Brief in the exact structure defined under
   OUTPUT SHAPE. Do not skip a section. Do not add sections.
   
   THE PROSPECT
   [Business name, their website or main social link, and one line on why
   you noticed them.]
   
   RULES
   1. Public information only. Never guess at private data. No contact
      details.
   2. Prefix anything you cannot verify with “Unverified:”.
   3. Plain language. No marketing fluff.
   4. Keep the whole brief under 400 words.
   
   OUTPUT SHAPE
   ## Prospect Brief: [business name]
   **What they do:** two sentences.
   **Who they serve:** one sentence.
   **How they show up:** website, social presence, tone of voice. Three
   bullets maximum.
   **Three signals worth knowing:** publicly observable changes, gaps, or
   opportunities. One line each.
   **One likely problem I could help with:** a single specific sentence,
   tied to what I do.
   **One natural opening line:** a first sentence for an outreach message
   that references something real about them.

4. Minute 4 to 6: fill the three brackets.

   One sentence about you. The prospect’s name and link. One line on why you noticed them. That is the entire configuration. If a sentence feels rough, leave it rough; the structure will carry it.

5. Minute 6 to 8: run it and read what comes back.

   A one-page brief, in the exact six-section shape you defined. Read the “three signals” section closely. This is usually where you learn something about the prospect you did not know, and it took the agent seconds to surface it.

   Notice the agent flagged that this prospect is not actually a roaster, that is the kind of signal you want.

   

6. Minute 8 to 10: the proof run.

   Open a second fresh conversation. Paste the same block. Swap in a different prospect. Run it.

Watch what comes back: a different business, the same shape, the same depth, the same six sections in the same order. That consistency came from the shape you fixed, on its own. This is the quiet lesson of the whole build. Hold onto it, because everything we do together in the coming weeks stands on it.

What you are holding now

A repeatable research agent and a real brief: what the prospect does, who they serve, how they show up, three observable signals, one likely problem you could help with, and one opening line grounded in something true about them. Work that used to swallow an afternoon of tab-hopping and second-guessing now has a ten-minute shape you can run on any prospect, any week.

Where this breaks

I want you trusting this agent for the right reasons, so here are its real failure modes.

• Thin web presence invites invention. If your prospect barely exists online, the model may fill gaps with plausible fiction. The “Unverified:” rule catches a good share of this. It does not catch everything. Before you use any fact in real outreach, check it yourself.

• Same name, wrong business. A bakery in Lisbon can share a name with a bakery in Leeds. If the brief feels slightly off, confirm it describes the company at the link you gave, then rerun.

• The opening line is a draft. It will be serviceable and slightly generic. Rewrite it in your own voice before it goes anywhere near an inbox. The agent’s job was the research underneath it.

• Deleting the shape brings the chaos back. Trim the RULES if you like, but the moment you remove OUTPUT SHAPE you are back to loose chat and different answers every run. The shape is the agent.

What this sets up

You typed who you are into a bracket today, by hand. Next week we fix that permanently: one file, the Core Context File, that carries who you are and how you sound into every agent you run from now on. Today you built a structure. Next week you give it your identity.

If you ran the build, reply to this email with the opening line your agent wrote. I read every reply.

Arsenios

The Agentic Leap. One real build, every week.