Training
Certification Leadership Frameworks Agentic for Business
Community Keynotes Retreat Blog Book A Consultation
Protocol 16 of 18 · Track, Continuity · How it lasts

User roles on an Infinite Leverage team

Three humans, eight agents, one team. The founder, a subject matter expert at the founder's company, and an AI engineer. PM, developer, QA, writer, designer, web publisher, email marketer, and DevOps are all AI agents.

Protocol 15 Working with an engineer to unlock you All 18 Protocol 17 AI testing vs human testing
Why this matters

The pain it
solves

The trap most companies fall into is hiring humans for roles that are now agent work. Hiring a junior PM, a junior developer, a junior QA in 2026 is a bet against the leverage curve. The Infinite Leverage team takes the opposite bet: keep humans for what only humans can do, let agents hold everything else.

Get this wrong and the agents on your Mac Mini sit unused while you keep hiring expensive humans to do work an agent could do in an afternoon.

The teaching

What this
actually is

Three humans, eight agents, one team

The trap most companies fall into is hiring humans for roles that are now agent work. Hiring a junior PM, a junior developer, a junior QA in 2026 is a bet against the leverage curve. The Infinite Leverage team takes the opposite bet: keep humans for what only humans can do, let agents hold everything else.

Get this wrong and the agents on your Mac Mini sit unused while you keep hiring expensive humans to do work an agent could do in an afternoon.

The three humans

Each one holds something an agent cannot fake. Each one is irreplaceable. Three roles, three reasons.

  • The Founder
    Holds vision, stakeholder relationships, and the final call. Talks to customers. Owns the why. The one job no agent should ever do for you.
  • The Subject Matter Expert
    A senior person at the founder's company who holds the domain knowledge AI cannot fake: the legal nuance, the manufacturing reality, the industry vocabulary, the regulatory shape. The expert who keeps the agents accurate.
  • The AI Engineer
    Builds with AI. Owns the agent architecture. Handles the harder code that requires judgment. Unblocks the team when the infrastructure misbehaves (Protocol 15).

The eight agents

Two teams of four. Each agent is a folder (Protocol 03). The three humans direct them, review their output, and own the judgment calls. The humans hold what cannot be agented yet. The agents hold the execution volume.

  • Build team
    PM plans the work. Developer ships the code. QA tests the change. DevOps owns the pipeline.
  • Go-to-market team
    Writer drafts. Designer creates visuals. Web Publisher publishes. Email Marketer runs campaigns.

The reach-for-an-agent-first instinct

Every time you feel the urge to hire someone, ask: can an agent hold this role for the first 12 months? Usually the answer is yes for PM, Developer, QA, DevOps, Writer, Designer, Web Publisher, Email Marketer. Usually the answer is no for Founder, SME, AI Engineer.

If the answer for a role outside the three humans is yes (an agent could do it), you have just found leverage your competitors are paying for.

Try it yourself 20 minutes

Map your team to the 11 roles in 20 minutes

Open a doc. List every person on your team and every paid contractor. You will map each to one of the 11 IL roles, then mark the gaps.

  1. Step 01
    List your real headcount

    Every full-time person, part-time, contractor, freelancer. Names and current job title.

  2. Step 02
    Map each to an IL role

    Founder, SME, AI Engineer, PM, Developer, QA, DevOps, Writer, Designer, Web Publisher, Email Marketer. Some people fill more than one. That is fine; note it.

  3. Step 03
    Mark the duplicates

    Two writers? One human PM and the PM agent? Two QAs? Where you have human + agent in the same role, ask: does the human still need to be there, or has the agent absorbed the work?

  4. Step 04
    Mark the gaps

    Any of the 11 roles with no one? That is a gap. For roles outside the three humans (Founder, SME, AI Engineer), the first move is to install the agent, not hire.

  5. Step 05
    Run one real handoff

    Pick any work in flight. Walk it from PM agent to Developer agent. Watch the seam. The first handoff feels novel; by the tenth, it is invisible.

Outcome

A team map showing humans, agents, and gaps. A first-hand sense of which seams are tight and which are loose. A starting list for the next hire conversation (and the next not-hire conversation).

Official resources

Straight from
the source

What you walk out with

By the end of this
protocol

At the retreat

You learn it by
doing it

You map your team to the three human roles plus eight agent roles. Gaps become visible. Then you run a real PM-to-Developer handoff and see exactly how the seams work.

Connects to

Other protocols this
compounds with

← Previous, Protocol 15 Next, Protocol 17 →