BhuvaneshSelvaraj
← All courses
Cohort 01Applications open· 4 weekends · live · 12 seats

Stop pasting your business into the chatbot. Build a system that knows it.

A four-weekend intensive for owner-operators who are tired of re-explaining their business to a chatbot that forgets everything by Tuesday. You leave with a working AI OS on your machine, the workflows that recover your week, and the maintenance habits that keep it useful for years.

Request your application90 seconds · reviewed within 48 hours

Format

Live cohort · 4 weekends

Built for

Owner-operators

Outcome

A working AI OS

Status

Applications open

// what you are losing right now

36%

of an entrepreneur's work week is admin: invoicing, research, scheduling, follow-ups, data entry.

Source: Time etc. survey

2 hrs

lost every day to context-switching between chat windows, email, docs, and your CRM. The cost compounds across the week.

Source: Microsoft Work Trend Index

16 hrs

a week, two full workdays, lost to manual operational work even by senior leaders.

Source: ServiceNow State of Work

§ 01Diagnosis

You don't have an AI problem. You have a memory problem.

Every ChatGPT or Claude conversation starts from zero. You re-explain your clients, your tone, your offer, your last meeting, for the fifteenth time this week. The output is generic because the input had to be.

So you copy-paste it into Gmail, Notion, your CRM, and call it productivity. It isn't. It's a more articulate version of the same admin treadmill.

§ 02The shift

From a chatbot you talk to, to a system that operates your business.

Before

The chatbot model

  • 01Resets every conversation
  • 02You re-paste context constantly
  • 03Can't update files or send anything
  • 04Output lives in chat, then gets lost
  • 05Generic answers to specific problems

After your AI OS

The operator model

  • 01Reads your client wikis, decisions, drafts
  • 02Specialists on call: researcher, writer, editor
  • 03Drafts directly into Gmail, ready to send
  • 04Updates your knowledge as it works
  • 05Hard rules enforced by hooks, not hope
§ 03Curriculum

Four weekends. Eight live sessions. One system that runs.

01

Foundations: the vault, the manifest, the first workflow

By Sunday night, your most painful daily admin task is being drafted for you before you sit down.

Saturday · 2 hrs

Why current AI workflows fail, and what replaces them

  • ·The three structural failures of chatbot-style AI
  • ·Live demo: an email becomes a drafted reply, an updated record, and a logged decision in 90 seconds
  • ·The three-layer memory model (raw, wiki, outputs)
  • ·You set up your vault, on your machine, with your real files

Sunday · 2 hrs

Your manifest, and your first working command

  • ·Write CLAUDE.md, the runbook every session reads first
  • ·Your first slash command: /triage-inbox
  • ·Run it live on your real inbox
  • ·Three peers demo theirs; we debug together

Takeaway

A fully structured vault, your personal AI manifest, and a working morning triage running on your real email, by 7pm Sunday.

02

Workflows: the four moves that recover real hours

The four workflows where small business owners hemorrhage time. You implement two for your specific business, running on Monday.

Saturday · 2 hrs

Research → proposal · Meeting → follow-up

  • ·Prospect research that ends in a drafted proposal, not a spreadsheet
  • ·Meeting notes that update the client wiki and draft the follow-up automatically
  • ·Variants demoed for realtors, advisors, agencies, coaches
  • ·You build both for a real (or simulated) client of your own

Sunday · 2 hrs

Lead qualification · Weekly operating review

  • ·/qualify-lead: every inbound gets researched, scored, and answered appropriately
  • ·/weekly-review: the document that compounds into your most valuable record
  • ·You pick the two highest-ROI workflows for your business
  • ·Cohort sanity-checks each other's choices

Takeaway

Two complete, tested workflows wired to your real work, typically saving 4 to 6 hours in the first week alone.

03

Specialists & integrations: connect what you already use

The system stops being a clever toy. It runs real operations: in your Gmail, on your Calendar, against your Drive.

Saturday · 2 hrs

Build your five-agent team

  • ·Researcher (web access, no shell)
  • ·Writer (no web, can't hallucinate sources)
  • ·Editor (read-only on source, write-only on drafts)
  • ·Librarian (read-only, the vault's memory)
  • ·Optional bookkeeper (financial files, never anything else)

Sunday · 2 hrs

Connect Gmail, Calendar, Drive · ship one custom skill

  • ·Authenticate the three core MCPs
  • ·Upgrade your existing workflows to draft directly in Gmail
  • ·Build one packaged Skill specific to your business
  • ·Templates for service, e-comm, professional services, creator

Takeaway

A specialist agent team and live integrations. Drafts now appear in Gmail, not in chat windows you forget to check.

04

Hardening & the long run: make it bulletproof, make it last

The difference between a cool demo and a system you trust with client work. Guardrails, scheduled runs, and the maintenance habits that compound for years.

Saturday · 2 hrs

The 70/100 problem · guardrails that don't depend on hope

  • ·Why CLAUDE.md rules are about 70% reliable and hooks are 100%
  • ·Build four essential hooks: immutability, confirmation, summary, cost
  • ·Industry guardrails: redaction for lawyers, financial-data rules for accountants
  • ·Workshop your own industry-specific guardrail

Sunday · 2 hrs

Scheduled runs · maintenance · demo day

  • ·Two scheduled automations: morning draft, weekly review
  • ·The 20-min/day, 1-hr/week maintenance contract
  • ·Your written 90-day rollout plan
  • ·Demo day: every student presents their best workflow

Takeaway

A system with safety rails, scheduled drafts ready for your morning review, and a written plan for how this grows over the next year.

“The owners who shape their context layer nowwill look back on this moment the way early operators look back on the first cloud tools.”

— The premise of Cohort 01

§ 04What you walk out with

Not theory. Not a notion of what you could build. A working system.

→ 01

A private AI OS on your machine

Tailored to your business, your voice, your clients. Yours forever, regardless of what model you point it at next year.

→ 02

8 to 12 custom commands

For your real daily operations: triage, research, drafting, follow-ups, weekly review. Built around how you actually work.

→ 03

Five specialist subagents

Researcher, writer, editor, librarian, bookkeeper. Each with their own tool boundaries, so they can't do what they shouldn't.

→ 04

Live integrations with what you use

Gmail, Calendar, Drive, plus a packaged Skill specific to your industry. Your AI works inside your real tools, not parallel to them.

→ 05

Industry-specific cheatsheets

Realtor, advisor, agency, coach, e-comm, professional services. CLAUDE.md additions and workflow mappings for your category.

→ 06

A written 90-day plan

How this grows from the cohort into your operating reality. Daily habits, weekly cadence, quarterly review checkpoints.

§ 05Apply

By application only. 12 seats.

Cohort 01 is small, deliberately. We accept owner-operators serious about building this, not the AI-curious. The application takes 90 seconds.

Accepted applicants receive the full curriculum brief, instructor introduction, and pricing within 48 hours.

Cohort

01

Seats

12

Format

Live

// application · 90 seconds

Tell us about your business.

Five fields. Twelve seats. Reviewed within 48 hours.

Hours per week you'd most like to recover
no payment · read personally
§ 06Honest answers

What you're probably thinking.

I'm not technical. Won't this be over my head?+
You won't write code. You'll write markdown and plain English. If you can write a clear brief for a new hire, you can build this. The terminal looks intimidating for the first two hours; by the end of Saturday you've forgotten you were ever scared of it.
Why can't I just keep using ChatGPT? It has memory now.+
Vendor memory is one flat bucket, in someone else's cloud, that you can't audit, restructure, or take with you. Your AI OS is your files, on your machine, queryable and version-controlled. When the next better model ships, you point your system at it. Your knowledge doesn't move.
Why apply? Why not just buy?+
Twelve seats. Live cohort. The energy of the room only works if everyone's actually shipping. We accept owner-operators with real businesses and real workflows to build against, not AI-curious tire-kickers. The application is how we keep that bar.
Won't AI just do all this automatically in a year anyway?+
Maybe. But generic tools can never know your voice, your clients, your history. The owners who shape their context layer now will be ten times ahead of those waiting for a one-size product, because they'll have built the taste, the wiki, the decisions. That moat compounds. Starting now is the move.
What's the time commitment outside of live sessions?+
Roughly 2 hours of homework per weekend, plus 20 minutes a day during the cohort to keep your vault current. We're not here to add work to your week. By Weekend 2, the system is already saving more time than it costs you.
What if I miss a session?+
Every session is recorded and available within 24 hours. Office hours run weekly for the duration of the cohort, plus 30 days after. You won't fall behind unless you check out entirely, and the recordings are yours forever.
I've taken courses before and never finished. What's different?+
Every session ends with your vault looking more useful than it did when the session began. You're not learning a topic, you're building a thing. The cohort sees your work each week. The accountability is structural, not a willpower exercise.