The blueprintPrep beforeDays in the roomBuild support after

The blueprint for a
retreat

One day or five, public cohort or private team, the shape is always the same: confidence rises first, capability catches up. Here is how the room works, and the 18 protocols you walk by doing.

Book a private retreat See 2026 cohorts
One blueprint, any format

Same shape
any length

Every retreat runs the same arc. The prep before and the build support after never change. Only the number of build days in the middle does, and you pick that to fit your team.

Length
1 day2345 days

One focused build day, or a full week. More days means more shipped: lead magnet funnel, payments, a program plan for your business, a one-shot prototype.

Format
Public cohortPrivate team

Join an open cohort and build alongside other founders, or run it private for your own team, your city, your dates, built around your business.

What this is

One shared way to ship
and hand off

The Infinite Leverage team is three humans: the founder, a subject matter expert at the founder's company, and an AI engineer. All the other roles, Product Manager, Developer, QA, Writer, Designer, Web Publisher, Email Marketer, DevOps, are AI agents. The 18 protocols are the operating system the three humans and the eight agents share, so the work moves without stepping on itself.

The retreat is where you walk all 18 protocols by doing them, in the room. The rest of this page is how you get there and what happens after.

Confidence Timeline

Confidence rises first
capability catches up

The retreat is the middle of a longer journey. Two weeks before you arrive, your days in the room, thirty days after with our team building alongside you. The first stretch teaches you the language. The retreat lifts your confidence to the ceiling. The month after lifts your capability to meet it. By the 90-day mark, both run at full strength.

T minus 14 days

Pre-retreat warm-up

A live group learning session, then two weeks to study the 18 protocols on your own time at aiolabz.com. You arrive at the retreat with the vocabulary, the mindset, and a plan, ready to build.

The retreat

Walk all 18 by doing

In the room, wherever you run it, AI engineers on site. You leave with a live web app deployed, a working CRM, and eight agents that run on your real work.

T plus 30 days

Stabilize with human tokens

Optional 40 human tokens retainer: senior engineers and operators on tap while you keep adding agents. Your capability climbs to meet your confidence over the month.

T plus 90 days

Capability meets confidence

By month three, capability has fully caught up. Your eight agents run on real work, your team uses them as default, and the IL system is now just how your company operates. You stopped learning Infinite Leverage; you became an operator.

Curve
ConfidenceCapability
2 WEEKS BEFORETHE RETREAT30 DAYS AFTER90 DAYS LATERHIGHLOW

The pre-work nudges your confidence and barely moves your capability. The retreat sends confidence to the ceiling and starts capability climbing. The 30 days that follow are where capability catches up, with our team building alongside you. By the 90-day mark, both run at full strength.

A day in the room

Every build day
has this rhythm

This is one build day, open to close. A retreat runs one to five of them. Whatever the length, every day follows the same arc: warm up, install, build, ship.

  1. 9:00 AM

    Welcome and the protocols at altitude

    The shape of the day, your pod with an engineer in it, and the 18 protocols at altitude. A relaxed reset before any tools come out.

  2. Late morning

    Install your stack, Hello World live

    Claude, GitHub, Vercel wired. Hello World deployed to your own domain, change it by prompt and watch the new version ship in under two minutes.

  3. Early afternoon

    Build the core system

    Drop in a design system and watch your site re-skin in 30 seconds, build real pages, then wire Supabase data, a contact form, and email. Submit a lead, watch the row appear.

  4. Late afternoon

    Ship something live

    Stand up the admin CRM with customer and admin logins, wired to your live site, all on your own data. Engineers on hand for the gotchas.

  5. End of day

    Close and what you take home

    A quick ceremony to mark what each operator shipped. The live site, the CRM, the agents, all yours, plus what to build next.

See the full agenda, hour by hour →
The operating system

18 protocols
five tracks

This is what you walk out owning. The same system Edge 8 runs on every client build, grouped into five tracks. You learn them hands-on in the room and take them home.

Mindset01 to 04
  • 01CMS is dead, AI is the CMS
  • 02The stack, Claude plus GitHub plus Vercel plus Supabase
  • 03Agents, the folder is the agent
  • 04Cataloguing, folder structures for agentic development
Infrastructure05 to 07
  • 05GitHub hygiene, check-in and check-out
  • 06Vercel hygiene, domains and DNS
  • 07Supabase, data structures basics
Building08 to 11
  • 08Design systems and Claude design
  • 09Workflow design
  • 10Communications, SMS, email, Resend
  • 11Admin interfaces, CRM, dashboards, Supabase access
Product Management12 to 14
  • 12Product planning and epic planning
  • 13Epic status, project status HTML tracking
  • 14Planning your day with a PM agent
Continuity15 to 18
  • 15Working with an engineer to unlock you
  • 16User roles on an Infinite Leverage team
  • 17AI testing vs human testing
  • 18Working with human tokens after you leave
See all 18 protocols
FAQ

Two questions
worth answering

What are the 18 Protocols

The 18 Protocols are the operating system we run on every client build, grouped into five tracks: Mindset, Infrastructure, Building, Product Management, and Continuity. They cover how an AI-native team thinks, what it builds on, how it ships, how it plans, and how the work outlives any one person. You learn them hands-on in the room and take them home.

Why do I need to learn GitHub, Vercel and Supabase

These three tools are the spine of a real, durable stack, and knowing what each one does keeps you in control of your own business. GitHub is the filing cabinet: one safe home for every file with a full history of changes. Vercel is the publisher: it puts your site live on the web with preview and production versions and one-click rollback. Supabase is the memory: your database and your logins. You won't operate them by hand, your agents do, but understanding them means you own the system instead of renting it.

Learn by doing

Pick how
you run it

Same blueprint, two ways in. Join an open cohort on a set date, or run the retreat private for your own team. Either way you leave with the system, not a recording of it.

Join a public cohort

Open dates in 2026. Build alongside other founders in the room, with engineers on site throughout.

See 2026 cohorts

Run it private

Your team, your city, your dates. Pick one to five days, built around your business.

Book a private retreat