Home / Toolkit / The Builder Factory
THE BUILDER FACTORY.
Two Pioneers. One Pizza Eng. One Owner. The new lifecycle of a feature in the agentic era — and what it means for how product leaders run their orgs.
By Yannic Desch · Last updated June 2026
The Old Org Chart, the New One
A single new feature used to require twelve people. A PM, a PMM, a designer, three engineers, a data scientist, a researcher, a tech lead, a designer's manager, the PM's manager — plus the meetings that come with them. Six standing meetings a week. A status doc nobody reads. Six months minimum.
The same feature today takes two human crews and a pack of agents. Two Pioneers validate the wedge. One Pizza Eng scales what the pioneers proved. One Owner plus Agents maintains and enhances it for the rest of its life — the agents run ops, the Owner ships 80% of enhancements directly. AI absorbs everything between.
This is what an AI-native product organization actually looks like at the unit level. Not a roadmap. Not a headcount plan. A lifecycle.
The Factory Line
The whole lifecycle, on one page.
The Factory Line
Idea
2 Pioneers
Alpha
2 domain owners · validate · 5–20 design partners
1 Pizza Eng
Scale
3–4 eng + AI · hardens alpha for production
1 Owner + Agents
Revenue
Owner ships 80% direct · Agents run ops
AI absorbs everything between · Cycle time: days from idea to revenue
The Three Crews
Three crews. Three jobs. Same feature, moving from validated to scaled to maintained. The headcount actually shrinks as the feature matures — that is the AI-native shape.
Crew 01 · Validate
2 Pioneers
Two domain owners — PM, designer, engineer, data person, business owner. Whoever's closest to the problem. Owns the wedge, the customer evidence, the kill criteria. Runs interviews, drafts the thesis, ships a 30-day MVP with pre-committed design partners.
Output
An alpha 5–20 partners actually use.
Tools
Claude Code, Cursor, prep doc per call, thesis with explicit kill criteria.
Crew 02 · Scale
1 Pizza Eng
3–4 engineers with AI in the loop. Takes the alpha and hardens it for production. Integration, infra, observability, security review, rollout plan. This is craft, not more building.
Output
A production-ready feature with metrics instrumentation wired up.
Tools
Agentic coding, AGENTS.md committed, CI with eval gates, on-call from day one.
Crew 03 · Maintain & Enhance
1 Owner + Agents
Often a Pioneer staying on. Agents watch usage, catch regressions, draft the health report, file routine PRs. The Owner ships 80% of enhancements directly with Cursor or Claude Code. The hard 20% routes back to engineering.
Output
A feature that improves without a standing team.
Tools
Observability with eval gates, agents with scoped write access, published runbook, Owner with repo access.
The CPO Job at Each Waypoint
Six waypoints. Six jobs. None of them are "review the deck."
Idea
Green-light or kill. Set the kill criteria up front. No kill criteria, no green light — otherwise it turns into a roadmap item nobody can close.
2 Pioneers
Protect the wedge. The pioneers will be pulled into status meetings and OKR rituals if you let them. Don't.
Alpha
Enforce the merge gate. Alpha means 5–20 design partners actively using it. Not two demo viewers nodding politely. Not one champion at one logo.
1 Pizza Eng
Hold the team to scale, not build. The build was the alpha. The work now is integration, hardening, observability, and the rollout plan. Resist re-litigating alpha decisions.
1 Owner + Agents
Stand up the agents before the engineers leave. The agents inherit the eval suite, runbook, and customer-language glossary. The Owner stays on for the hard 20%.
Revenue
Measure cycle time. Days from idea (greenlit) to revenue is the accountability metric the whole line is judged by. Publish it. Track it. Hold yourself to it.
What AI Absorbs
"AI absorbs everything between" is the load-bearing claim. Here is what that actually means.
Coordination work
- —Status updates
- —Standing-meeting prep
- —Cross-functional translation docs
- —OKR rollups
Research & synthesis
- —Call-note summarization
- —Cross-call divergence tables
- —Competitive teardowns
- —First-draft PRDs
Production overhead
- —Boilerplate code
- —Schema migrations
- —Test scaffolding
- —Documentation
Communication output
- —Slack drafts
- —Customer follow-ups
- —Release notes
- —Internal announcements
That is the twelve-person org chart. Each of those roles existed because each of those workstreams was a human-shaped job. They are not human-shaped jobs anymore.
What Survives
The work that survives is the work AI can't do yet. It clusters in three places — one per crew.
The wedge worth validating
Taste. Hypothesis. The judgment call about whether a customer pain is real, urgent, and worth twenty days of pioneer time. AI can analyze the data. It cannot feel the urgency.
The system worth scaling
Craft. Engineering judgment about what fails under load, what breaks under partnership, what compounds versus what creates debt. AI can write the code. It cannot feel the fragility.
The customer worth keeping
Relationship plus enhancement. The long-haul work of listening to a real customer use the feature for two years and shipping the small changes that keep them. The Owner holds the relationship and ships the enhancements. The agents hold the ops.
The Punchline
Most product leaders ship features.
The Builder Factory product leader ships the line that ships features.
The metric that matters is cycle time: days from a greenlit idea to the first euro of revenue. That single number is what the whole line is judged by, and the only way to drive it down is to instrument every gate, every handoff, every crew. If you can't see it, you can't shorten it.
Two Pioneers validate. One Pizza Eng scales. A pack of Agents plus one Owner maintain and enhance. AI absorbs everything between. The product leader's job is to enforce the gates, instrument the line, and protect the crews at every waypoint.
The old org chart was a list of twelve people.
The new one is two pioneers, four engineers, then an Owner and a pack of agents.