The build team, humans plus AI

A team is always humans plus AI. Never AI alone, which ships things nobody asked for. Never humans alone, which is a bet against the leverage curve. The trap most companies fall into is hiring humans for roles that are now agent work: a junior PM, a junior developer, a junior QA. Keep humans for what only humans can do, let agents hold everything else.

This protocol is about the team that builds. You will meet the go-to-market side later; for the next two days the only team that matters is the one that gets your system live.

Humans plus AI, always

A team is never AI alone and never humans alone. AI alone ships things nobody asked for and nobody checked. Humans alone is a bet against the leverage curve: hiring a junior PM, a junior developer, a junior QA in 2026 is paying for work an agent does in an afternoon.

The Infinite Leverage bet: keep humans for what only humans can do, let agents hold everything else. This protocol is about the smallest version of that team, the one that builds.

The humans: you, and an engineer when you are stuck

Two human seats. One is always filled. The other is on call.

• You
  The founder. You know the business, hold the vision, run the interview that becomes the plan, and make every call the agents put in front of you. Anything that reaches a customer goes through you. The one job no agent should ever do for you.
• An engineer, when you are stuck
  A catalyst, not crew. They unblock you; they do not work for you. Call when the same error has not changed in 30 minutes, when you are about to bypass a security rule to make something work, when production is down, or when you are not sure the next command is safe.
• The four-item brief
  Exact error message (screenshot, not paraphrase). Last commit. What you already tried. What you think is going on. That brief turns a 90-minute call into a five-minute one, and half the time writing it surfaces the answer before you send it.

The four agents that help you build

Each one is a folder (Protocol 03) with a role, skills, context, routines, guardrails, and a Definition of Done. You direct them, review their output, and own the judgment calls. They hold the execution volume.

• PM
  Runs the interview, writes the product plan and the build plan, holds the Definition of Done, and stages tomorrow. It plans the work; it does not do it.
• Developer
  Builds from the plan, one step at a time, on a branch. Stops when a check fails. Reports what changed in plain English.
• QA
  Tests every line of the Definition of Done against the live site, prints PASS or FAIL with evidence, and never marks something passing it did not observe.
• DevOps
  Owns the pipeline: env vars, deploys, the preview URL, the cron, the domain. When it works locally and breaks in production, this is the agent that finds out why.

The agents you add once the CRM is live

The build team gets the system live. The next agents work off the data it collects, and each is the same folder with a different job (Protocol 15). Start with lead triage. Then, for the ones moving fast:

• Writer
  Reads the last month of inquiries, finds the question leads ask most, and drafts a blog post that answers it in your voice. You approve, it publishes.
• Email
  When a contact reaches a stage, reads everything the CRM knows about them and drafts one personalized email instead of a broadcast. You approve before it sends.
• Customer support
  When a support request lands, reads the person's history and orders, drafts the reply, and flags what it is not sure about. Drafts only, always.

The reach-for-an-agent-first instinct

Every time you feel the urge to hire someone for the build, ask: can an agent hold this seat for the first 12 months? For PM, Developer, QA, and DevOps the answer is usually yes. For you, and for the engineer who unblocks you, the answer is no.

If the answer for a seat is yes, you have just found leverage your competitors are paying salaries for.

A team map showing humans, agents, and gaps, and a practiced four-item brief you can run cold. A starting list for the next hire conversation, and the next not-hire conversation.