The argument in one line.
Boris Cherny argues AI-era teams and solo builders alike should organize around five function-based archetypes rather than job titles, and a Slack-embedded Claude agent is now filling the unnamed sixth role that decides which archetype to deploy and when.
Read if. Skip if.
- You run a one-person or small-team business and want a mental model for which AI-agent role to hand off next.
- You're already running multiple Claude Code sessions and want a framework for organizing them beyond ad hoc terminal windows.
- You want to understand what Anthropic's 'Claude Tag' / 'Claude everywhere' rollout actually does before it shows up in your own team's Slack.
- You want a step-by-step Claude Code build tutorial — this is a business-model reaction to one tweet, not a build-along.
- You already follow Boris Cherny's original thread closely and run a Claude-in-Slack setup yourself.
The full version, fast.
Boris Cherny, creator of Claude Code, argues every AI-era product needs five function-based roles rather than job titles: Prototyper (idea generation), Builder (production build), Sweeper (refine/simplify), Grower (product-market fit), and Maintainer (scale/reliability). Which 2-3 matter depends on your product's stage. Boris himself runs 10-15 concurrent Claude Code sessions, each spinning up sub-agents toward one goal, which is how he technically manages 'thousands of agents' without prompting each one directly. A reply named the missing sixth role — the orchestrator, who decides which archetype to deploy when — and Anthropic's new Slack-native Claude Tag, already writing 65% of the company's own new product code, is being positioned to fill exactly that gap.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open
Promise: Boris Cherny's viral blueprint for the businesses that will dominate the next decade.

02 · Boris's viral tweet
The tweet has reached 3M+ views. Archetypes apply regardless of team size, product, or job title — at Anthropic, designers/engineers/PMs/DS all map onto the same five buckets.

03 · The five archetypes
Prototyper (many raw ideas, most never ship), Builder (production-grade build), Sweeper (clean up UI/code, unship what's not working), Grower (iterate for PMF), Maintainer (secure/reliable/fast at scale).

04 · Real-world example: weight-loss niche
Walks the five archetypes through a hypothetical weight-loss product (the '6-Week Kettlebell Shred'): idea, build, sweep unused features, target the 3-week retention drop, maintain coaching/security/content.

05 · Which archetypes to focus on right now
Pre-PMF needs 1+2+3. Growing-with-PMF needs 2+3+4(+5). Strong-PMF, like Claude Code itself, needs 3+4+5(+2).

06 · Silicon-based agents: running thousands at once
Boris runs ~10-15 concurrent Claude Code sessions, each on a different project, each spinning up as many sub-agents as needed toward one goal — explaining how 'thousands of agents' is literally true while he tracks roughly 20 goals, not thousands of prompts.

07 · The sixth archetype: the orchestrator
A reply names the missing role: the person who knows which of the five to deploy, when, and how to transition between them. Boris: ideally people self-organize via incentives, but a central coordinator works less well as pace increases — Claude can fill part of that gap.

08 · Claude Tag and Claude everywhere
Anthropic's Slack-native Claude Code bot: shared instance per channel, own identity and memory, proactive not just reactive. 65% of Anthropic's own new product code is now written by their internal version.

09 · Dream Labs' own version + close
Dream Labs claims to have built their own 'omnipresent Claude' setup and just released it inside their paid community.
Lines worth screenshotting.
- A tweet from Anthropic's Boris Cherny proposing five business archetypes — Prototyper, Builder, Sweeper, Grower, Maintainer — reached over 3 million views.
- The five archetypes aren't job titles: one person can span two or three of them, and the same role can be filled by an AI agent instead of a human.
- A product that's pre-product-market-fit needs people strong in archetypes 1, 2, and 3 — ideation, building, and refining.
- A product with strong product-market fit, like Claude Code itself, needs archetypes 3, 4, and 5 — refine, grow, maintain — not fresh ideation.
- Two and a half years ago most builders ran a single Claude Code session in one terminal window; now one session spins up sub-agents that are themselves other Claude instances.
- One person's Claude Code setup can now run roughly 10 to 15 concurrent sessions, each overseeing hundreds to thousands of sub-agents working toward a single stated goal.
- The operator isn't prompting the agents directly anymore — their Claude prompts other Claudes, turning one person into the manager of a goal rather than the author of every task.
- A reply to Boris's thread named a missing sixth archetype: the orchestrator, the person who decides which of the five roles to deploy and when to transition between them.
- Boris's own answer to who fills the orchestrator role: ideally people self-organize through incentives, but a central human coordinator works less well as project pace increases — and Claude can increasingly do that job instead.
- Claude Tag drops one shared Claude Code bot into a Slack channel with its own identity and memory, replacing the pattern of everyone running separate sessions and passing files between them.
- 65% of Anthropic's own product teams' new code is now written by their internal, Slack-embedded version of Claude Tag.
- The pitch for this kind of AI integration is that it disappears into daily use the way phones replaced telephone booths — proactive enough that you stop noticing you're using it.
Five archetypes, one orchestrator, and a stage-based rule for which role needs you next.
Boris Cherny's framework says every AI-era product needs five functions — Prototyper, Builder, Sweeper, Grower, Maintainer — and your product's current stage tells you which two or three actually need your attention.
- Archetypes are workflows and roles, not job titles or specific individuals — one person, or one AI agent, can span two or three of them at once.
- At Anthropic, designers, engineers, PMs, and data scientists all map onto the same five archetypes regardless of their actual job function.
- The Prototyper generates many raw ideas knowing most will never ship; the Builder turns the one that sticks into production-grade infrastructure.
- The Sweeper cleans up the UI and simplifies the code after launch; the Grower iterates on the shipped product to improve product-market fit; the Maintainer keeps a mature system secure, reliable, and fast as it scales.
- In a hypothetical weight-loss business, the Prototyper tests several concepts (postpartum reset, protein challenge, kettlebell program) before picking one to build.
- After launch, the Sweeper cuts unused features, the Grower targets the exact point retention drops (three weeks in) with a specific save tactic, and the Maintainer keeps coaching, security, and content running.
- A pre-product-market-fit product needs people strong in archetypes 1, 2, and 3 — ideation, building, and refining — not growth or maintenance yet.
- A product with strong product-market fit, like Claude Code itself, needs archetypes 3, 4, and 5 — refine, grow, maintain — because the idea stage is behind it.
- Two and a half years ago most people ran a single Claude Code session in one terminal window; today one session spins up sub-agent Claudes that do the work below it.
- Running 10 to 15 Claude Code sessions at once, each in charge of a different project and empowered to spin up as many sub-agents as needed toward one stated goal, is how 'thousands of agents' becomes literally true while tracking only about 20 actual goals.
- A reply to Boris's thread named the missing sixth archetype: the orchestrator, the person who knows which of the five roles to deploy, when, and how to transition between them as the product matures.
- Boris's answer: ideally people self-organize into the five archetypes through incentives and team design, but a central human coordinator works less well as project cadence speeds up — which is exactly the gap Claude is being positioned to fill.
- Claude Tag drops one shared Claude Code bot into a Slack channel with its own identity and memory, replacing the old pattern of everyone running separate sessions and passing files between them.
- The goal is for the agent to disappear into daily use the way a phone replaced the telephone booth — proactive enough that you stop noticing you're using it, working across every channel, app, and platform the team already uses.
Terms worth knowing.
- Archetype
- A functional role in a business (not a job title or specific person) — Boris Cherny's framework names five: Prototyper, Builder, Sweeper, Grower, Maintainer.
- Product-market fit (PMF)
- The point at which a product has found genuine, sustained demand from its audience, as opposed to an unproven early-stage idea.
- Sub-agent
- A separate Claude Code instance spun up by another Claude Code session to handle one narrow task, allowing one operator's session to fan out into many parallel workers.
- Orchestrator
- The proposed sixth archetype — the role that decides which of the five archetypes a business needs right now and manages the handoffs between them as the product matures.
- Claude Tag
- Anthropic's Slack-native Claude Code integration: one shared bot instance per channel with persistent identity and memory, able to act proactively instead of only responding to direct prompts.
Things they pointed at.
Lines you could clip.
“The creator of Claude Co just revealed the exact blueprint of the businesses he thinks will dominate the next decade.”
“It's not meant to be an app by itself. It's meant to integrate into your life so you don't even realize that you're using it.”
“It's almost like having to go to a telephone booth to make a call, and that's the technology of a telephone versus having a phone in your pocket at all times.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Boris Cherny — the creator of Claude Code — posted a tweet that quietly reframed what a modern business org chart should look like, and Dream Labs AI opens by promising to decode it: the five archetypes, the thousands of agents Boris is personally running, and the Slack tool Anthropic just shipped to manage all of it.
Named ideas worth stealing.
The Five Archetypes
- Prototyper
- Builder
- Sweeper
- Grower
- Maintainer
A function-based org model for AI-era businesses: generate ideas, build the winner, refine/simplify it, grow it toward product-market fit, then maintain it at scale. Not tied to job titles — one person or one AI agent can span multiple archetypes.
PMF-Stage Archetype Mix
Which archetypes matter shifts with product maturity: pre-PMF needs 1+2+3 (idea/build/refine), growing-with-PMF needs 2+3+4 and some 5, strong-PMF needs 3+4+5 and some 2.
The Missing Sixth Archetype: The Orchestrator
The role that decides which of the five archetypes to deploy, when, and how to transition between them as the product matures — named in a reply to Boris's thread, and framed as rarer than all five combined.
How they asked for the click.
“We set this up from scratch after a lot of trial and error, and today, we've actually just released it inside our Dreamlabs community. So come and join us. We have a massive discount at the moment. The link is in the description below.”
Soft, credibility-first pitch — leads with 'we already built this ourselves' before naming the community, using the video's own subject (Claude everywhere) as the proof of the product.







































































