The Operator's Map — Cohort 02

The route through the eight weeks

Everything Cohort 02 covers, in the order we build it: eight Wednesdays, January 6 to February 24, 2027. If someone forwarded you this, you are looking at the whole program. There is no second page and no discovery call. The Zoom room, the recordings and the class materials live behind one password at Base Camp, which reaches you with your welcome email.

Cohort 02

Doors are open

Dates
January 6 to February 24, 2027
Live
Wednesdays, 12:00 – 1:15 pm Central
Office hours
Fridays, 12:00 – 1:30 pm Central, optional
Seats
30, capped
Enrollment closes
December 31, 2026

$2,000for all eight weeks

Enroll in Cohort 02Ask me something first

Full refund any time before Week 3 begins. Prefer installments, or a company invoice? Email me and we will set it up.

Bringing someone from your own team is the version of this that works best — mapping how work actually moves needs two people who can disagree about it. Each of you enrolls separately; there is nothing to coordinate.

Eight builds, eight things you keep

This is not eight weeks of lectures. Each week you ship one named thing into your own business, and each build stands on the one before it. Sessions run 12:00 – 1:15 pm Central. Office hours are Fridays, 12:00 – 1:30 pm Central. Your welcome email carries a calendar file with all of it.

What it asks of you: about three hours a week. Seventy-five minutes live, plus about two hours building inside your own business. The Friday office hour is there if you want it and skippable if you do not. If you have three hours a week, you can finish this.

  1. Build 1Governance

    Wednesday, January 6

    You ship: Your Data Map and a written Shadow AI Policy

    Before
    Where your legal and financial documents actually live right now.
    Homework
    Classify your drive. Archive or wall off anything AI should never see. · due Tuesday, January 12
    Next up

  2. Build 2Communication Triage

    Wednesday, January 13

    You ship: A working inbox agent that classifies and drafts

    Before
    Who in your inbox always deserves a reply, and who never does.
    Homework
    Ship the agent. Let it run a week. Log every reply it got wrong. · due Tuesday, January 19
    Needs
    Your Data Map

  3. Build 3The Map

    Wednesday, January 20

    You ship: A named leak, measured in minutes per week

    Before
    A week of the agent running, and every reply it got wrong.
    Homework
    Time the leak for one week. Real numbers off the miss log, not estimates. · due Tuesday, January 26
    Needs
    Your Data Map · A working inbox agent

  4. Build 4The Code Node and the Agent

    Wednesday, January 27

    You ship: One code node that filters your inbox for one thing

    Before
    The one thing you most wish your inbox would sort on its own.
    Homework
    One code node, filtering for one thing. Get it working before you build the second. · due Tuesday, February 2
    Needs
    A trigger connected to your inbox

  5. Build 5The CRM That Logs Itself

    Wednesday, February 3

    You ship: A CRM that logs itself from the work you already do, and a task list that briefs you

    Before
    Where your client history lives today, honestly.
    Homework
    Copy the sheet and make the columns yours. Point Task Rabbit at it. Let one real relationship log itself for a week. · due Tuesday, February 9
    Needs
    A working inbox agent

  6. Build 6Lead Generation and Content

    Wednesday, February 10

    You ship: A nurture engine that tells you when to reach out, and a content system that feeds it

    Before
    Twenty people who already know and trust you — and the thing you know that your market does not.
    Homework
    Bring the one automation you will run for a week without touching it. Know what database it reads from, and what it has to remember so it never does the same thing twice. · due Tuesday, February 16
    Needs
    A self-logging CRM

  7. Build 7The Capstone Build

    Wednesday, February 17

    You ship: One autonomous system running a revenue-facing part of your business

    Before
    Which single function, if it ran without you, would change your week most.
    Homework
    Build the one thing you named on Wednesday. Thirty minutes back a week is the bar, and it has to run without you pressing the button. · due Tuesday, February 23
    Needs
    A nurture engine · A self-logging CRM

  8. Build 8Graduation

    Wednesday, February 24

    You ship: Proof it runs without you — the handoff test, passed

    Before
    Which of your builds still needs you to press the button.
    Homework
    Hand it to someone else and see if it survives a week without you. · due Friday, February 26
    Needs
    Your capstone system

Put every date on your calendar

All eight sessions, every office hour and every homework due date, starting January 6. Subscribe once and the calendar keeps itself current if anything moves.

Google CalendarOpens Google and asks you to confirm. Say yes. On a computer — see the note below about phones.Outlook / Microsoft 365Work or school account. This is also the calendar Teams reads.Outlook.comPersonal Microsoft account.Apple CalendarMac and iPhone.

Any other calendar

https://www.theoperatorsmap.com/api/calendar

Look for “Add calendar” then “From URL” and paste it.

On a phone? A calendar you add to Google by URL shows up on the Google Calendar website but does not appear in the Google Calendar phone app — that is a Google limitation, not something on your end. If you live in your phone calendar, use the Apple Calendar option instead: it subscribes at the device level and syncs everywhere, including on an iPhone signed in to Gmail.

All of the above subscribe, which means the schedule corrects itself on your calendar if a date ever moves. Downloading the .ics file works too, but it is a snapshot taken the moment you download it — it will not update, so subscribe if you can.

Whether this is meant for you

One profile at two scale points. A solo consultant billing a few hundred thousand belongs here, and so does an executive running a fifty-million operation. Headcount is not the qualifier — decision-making authority over a working business is, plus a real operational problem you personally own. A solo operator brings the whole business. Someone at a two-hundred-person company brings the part they control. Both work.

What does not work is attending on behalf of someone else who makes the decisions.

One thing about the room

You will be working on your real business in front of other operators, so it is worth saying how that is handled. What is said in the room may be used by anyone in it, and attributed to no one outside it. Nobody is asked to disclose anything a client agreement does not permit — and Build 1 covers how to work on a real problem without putting confidential material anywhere it should not go. Several people in the first cohort worked under client NDAs. That is normal, and it is designed for.

What the 75 minutes actually look like

The live block does the one thing a recording cannot: take a real business apart while everyone watches. Concepts and demos come to you as material you can pause and replay. Eight weeks, eight operators in the chair — and you will learn as much from someone else's teardown as from your own.

  • 0 – 10The frameWhat this week protects or unlocks, and what you are shipping by Friday.
  • 10 – 50The hot seatOne operator’s real business, taken apart live. Eight weeks, eight operators in the chair.
  • 50 – 65Your turnYou apply the same diagnosis to your own business, in the room, while I am still here.
  • 65 – 75The handoffExactly what to build, what you already have to build it with, and when it is due.

Yours right now

You do not have to wait until January to get something out of this.

  • Pre-work diagnostic

    Open

    Ten questions that tune the sessions to your real business. Do this first — Week 1 starts from your answers.

  • Shadow AI Policy template

    Open

    Yours now, before the program starts. Fill it in and you have a written AI policy most companies do not have.

  • Tool stack and what it costs

    Open

    Everything you need for the eight weeks, and what you will actually spend. No surprises in week three.

If you fall behind

You will, at some point. Work gets loud. The thing that ends people in a program like this is not missing a session — it is that week five needs what week three built, so one missed week quietly locks you out of the next three.

So every build ships with a catch-up kit— a pre-made version of that week's artifact you can adopt in about ten minutes. Falling behind means downloading two files and rejoining on Wednesday, not redoing three weeks. The kits live at Base Camp, and they do not expire when the program ends.

Cohort 02

Take a seat

Dates
January 6 to February 24, 2027
Live
Wednesdays, 12:00 – 1:15 pm Central
Office hours
Fridays, 12:00 – 1:30 pm Central, optional
Seats
30, capped
Enrollment closes
December 31, 2026

$2,000for all eight weeks

Enroll in Cohort 02Ask me something first

Full refund any time before Week 3 begins. Prefer installments, or a company invoice? Email me and we will set it up.

Bringing someone from your own team is the version of this that works best — mapping how work actually moves needs two people who can disagree about it. Each of you enrolls separately; there is nothing to coordinate.