The Operator's Map — Cohort 01

Your route through the eight weeks

Everything Cohort 01 covers, in the order we build it. If you are enrolled, there is nothing left to pay, enter, or redeem — a code you were given has already been applied and will read as invalid if you try it again. That is what a secured seat looks like. If someone forwarded you this, you are looking at the whole program — Cohort 01 sold out, but the bottom of this page shows you the way into Cohort 02. Either way this page is public to anyone holding the link; the Zoom room, the recordings, and the class materials live behind one password at Base Camp.

Start here — before anything else

Put the eight weeks on your calendar

Subscribe once and every session and homework deadline lands on your own calendar — and stays correct if a date ever moves. This program competes with your job for the same hours. Give it a defended slot now, not in week three. One note before you look: Build 5 meets on a Thursday rather than a Wednesday, because the Badass Business Summit takes the usual slot that week. That is deliberate, not a mistake.

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. One session has already moved once, so subscribe if you can.

Subscribing beats downloading — a download is a snapshot, a subscription updates itself. On iPhone or Mac the first button just works. On Google Calendar, use “Other calendars → From URL” and paste the .ics address.

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 — one exception, Build 5 meets Thursday, September 17, because the Badass Business Summit takes the usual slot. Office hours are Fridays, 12:00 – 1:00 pm Central.

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

  1. Build 1Governance

    Wednesday, August 19

    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, August 25

  2. Build 2Communication Triage

    Wednesday, August 26

    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, September 1
    Needs
    Your Data Map

  3. Build 3The Map

    Wednesday, September 2

    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, September 8
    Needs
    Your Data Map · A working inbox agent

  4. Build 4The Code Node and the Agent

    Wednesday, September 9

    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 Wednesday, September 16
    Needs
    A trigger connected to your inbox

  5. Build 5Billing and CRM

    Thursday, September 17

    You ship: A CRM that logs itself from the work you already do

    Before
    Where your client history lives today, honestly.
    Homework
    Wire one real relationship end to end. Watch it log for a week. · due Tuesday, September 22
    Needs
    A working inbox agent
    Next up

  6. Build 6Lead Generation and Content

    Wednesday, September 23

    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
    Load the twenty in. Act on the first three signals. Publish twice without hand-writing either one. · due Tuesday, September 29
    Needs
    A self-logging CRM

  7. Build 7The Capstone Build

    Wednesday, September 30

    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 it. Let it run live — client delivery, pipeline, and reporting wired together. · due Tuesday, October 6
    Needs
    A nurture engine · A self-logging CRM

  8. Build 8Graduation

    Wednesday, October 7

    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, October 9
    Needs
    Your capstone system

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 twenty-four 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 this cohort work under client NDAs. That is normal, and it is designed for.

What 75 minutes actually looks 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 August 19 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.

Base Camp

The Zoom room, the recordings, every week's materials, the catch-up kits, the WhatsApp group, and who else is in the room. One password for the whole cohort — it reaches you by email before launch week.

Go to Base Camp

Something unclear or broken?

That is a finding, not a bother. Email waziri@harlemlabs.com and say what you tried and what you saw. The whole point of a pilot is that you tell me before twenty-five other operators hit the same wall.

Not in this cohort

This room filled. The next one is forming.

If you got here from someone already in the room, you have just read the whole program — no second page, no discovery call. Cohort 01 was capped at 25 operators and sold out. The founding seat was $247 for all eight weeks — priced that low exactly once, traded for honest feedback from the first group, and retired with the cohort. The program opens publicly at $1,997, and the waitlist hears about Cohort 02 before anyone else.

Get first access to Cohort 02Ask me something first

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. Join the list separately; there is nothing to coordinate.