Available now · worldwide on Amazon
The Agent Dream Team
Build Your Autonomous Specialist Roster for a One-Person Company
Stop prompting one chatbot. Coach a roster of specialists.
ROSTER shows solo operators how to create named specialist agents with charters, triggers, handoffs, and review gates instead of one overloaded chatbot.
Get the book
Reading from another country?Pick your own Amazon marketplace — same edition, your store.
Amazon links may include affiliate tags. That does not change the price you pay. Bol.com listings are third-party.
English & Dutch editions · Kindle, Paperback, Hardcover · free on Kindle Unlimited · Nederlandse editie →
- pages
- 484
- chapters
- 14
- hours of reading
- ± 8
- editions
- EN · NL
The editions
Choose your format
Same book, your format. You buy on Amazon, not on this site.
-
Kindle
Read now. Kindle Unlimited members get it at no extra cost.
Buy on Amazon -
Paperback
The working copy. Mark it up. Take it into the meeting.
Buy on Amazon -
Hardcover
The shelf edition. Dark full-art jacket, built to stay in the room.
Buy on Amazon
Available now
Build Your Autonomous Specialist Roster for a One-Person Company
Elena ran her consultancy from one chatbot session, open at eight, decayed after lunch. Her proposal came out polished, for the wrong client: another client's research had drifted in. Three days later the client noticed. She had not, and the deal went with it.
A sharper prompt does not repair a week in which research, writing, operations, and review share one thread. Nothing separates the tasks; they inherit each other's context. The bill is rework, misfires, and output you cannot trust unread: one generalist that cannot specialise and answers to no mandate. If one thread still serves you, keep it. This book is for when it stops.
The Agent Dream Team replaces that generalist with a specialist roster you coach. ROSTER names six skills per agent: Roles, Objectives, Skills and tools, Triggers, Evaluation, Rotation. You start with three roles, Research Specialist, Draft Editor, Ops Coordinator, on one-page charters stating what each owns and never touches.
Role by role, you:
What you can do
What this book puts in your hands
- Write a six-field charter, including the line the role may not cross.
- Wire a trigger map so detectable recurring events route themselves; judgment calls stay yours.
- Grant tools as permissions, least privilege per role.
- Score output on a rubric; the Agent Trust Ladder turns scores into autonomy, L1 to L5. Anything that reaches another person, or is irreversible, public, financial, or legally binding, passes through you first.
- Retire, merge, or upgrade a role on evidence, before a vendor retires its model.
The framework
ROSTER: the system behind the book
Roles, Objectives, Skills, Triggers, Evaluation, Rotation
-
Roles
Give each agent a charter so one job has an owner instead of a shared thread.
-
Objectives
Make the charter measurable. A role without an objective is a job title.
-
Skills and tools
Bound what the agent may use, and cut the access it does not need.
-
Triggers
Decide once, at your clearest, which event starts which agent.
-
Evaluation
Score output with a scorecard. Judgment by vibe is hope, not management.
-
Rotation
Retire, merge, upgrade, or migrate a role on scorecard evidence, before last quarter's design quietly fails this quarter's work.
From the book
Figure 5.1: Least-privilege: each role gets only the tools it needs
The Agent Dream Team, printed page: Figure 5.1: Least-privilege: each role gets only the tools it needs
Inspect more pagesLook inside
Pages from the print edition.
Practice: Draft Three Role Charters 3 12 99
Figure 5.1: Least-privilege: each role gets only the tools it needs
Worksheet: Tool Audit, Current Setup vs Least- … 5 12 157
The attack surface is documented. Malicious instructions
Letta Filesystem with LoCoMo’). The same post states that Letta could
2026, Figure 1 caption, p. 2). Nine lines of code, a perfect score, nothing
Practice: Your first role diagnosis
Follow this order when building a roster from scratch. Skipping ahead
Purchase takes place on Amazon, not on this website.
Buy the paperback on AmazonFrom the book
Read a page
Introduction
Company of One, Team of Many
The solo founder's real problem has never been capability. It has been configuration.
What you get
What you get
- The ROSTER protocol: Roles, Objectives, Skills, Triggers, Evaluation, Rotation
- Named specialist agents with charters and review gates
- Run a company of one like a real team
Who it's for
- Split one chatbot into a specialist roster with clear mandates
- Wire triggers so the right agent runs at the right event
- Run a weekly operating ritual without team-sync overhead
- Evaluate agent output with scorecards, not vibes
- Adopt dream-team templates for GTM, research, or ops
Who it's for
Who this book was written for
The roster runs on a 30-minute weekly ritual: Monday charters, midweek triggers, Friday scorecards. One Field Card per role, and a capacity budget saying when to stop.
Elena is a composite. The frameworks are the author's operating design, and the book never dresses them as research. The multi-agent research carries its token bill and limits; Chapter 12 names six ways rosters degrade. Agents are hires, not prompts. You are the coach, not the only worker. Your morning starts in the team's output, not your own.
The reader it was written for
The solo founder-operator, bootstrapped or early-stage, a company of one, using AI daily but stuck in one endless chat. Wants named specialist agents with charters, not a generic assistant.
Also a fit for
The creator-consultant scaling a newsletter, course, or advisory practice through agents while keeping quality and voice consistent across roles.
What you will use it on
- Split one chatbot into a specialist roster with clear mandates
- Wire triggers so the right agent runs at the right event
- Run a weekly operating ritual without team-sync overhead
- Evaluate agent output with scorecards, not vibes
- Adopt dream-team templates for GTM, research, or ops
Probably not for you if
- Teams of five or more humans needing org design (see The Multi-Agent Organization)
- Readers seeking repository architecture only (see The Agentic Codebase)
The contents
Chapter by chapter
Every chapter of The Agent Dream Team with its printed epigraph, what you can do afterwards, and the moment it is built for.
Introduction
Company of One, Team of Many
The solo founder's real problem has never been capability. It has been configuration.
Chapter 1
Why One Chatbot Fails
The problem with one smart assistant is not a shortage of intelligence but the four jobs you have given it, a shared memory with no boundaries, a full set of admin keys, and no rubric for what good work looks like.
Chapter 2
ROSTER Overview
A company of one can run like a managed team. The six skills that make it possible fit on a single page.
Chapter 3
Design Roles (R)
A job description is the document that makes accountability possible, which is why it survives every attempt to file it under bureaucracy.
Chapter 4
Set Objectives (O)
A role without a measurable objective is a title. The title collects no receipts.
Chapter 5
Assign Skills and Tools (S)
Every tool you connect to a role is a permission you granted. Most founders never see the grant until it fires.
Chapter 6
Wire Triggers (T)
A trigger map records a standing decision, made once and deliberately when you had the most clarity, then applied automatically every time the event recurs.
Chapter 7
Handoffs and Memory
Work that is implicit in a thread stays trapped there. Work that is explicit in a packet can travel anywhere.
Chapter 8
Evaluate Outputs (E)
The founder who reviews by feel is hoping, not reviewing. A scorecard is the minimum equipment for a manager who wants to improve something. And a score that never changes what a role is allowed to do is a number you paid for and then filed.
Chapter 9
Rotate and Retire Agents (R)
A roster that never changes is a roster that never improves. The agent you designed six months ago was built for the work you had then, the work has changed, and so has the model running underneath it.
Chapter 10
Dream Team Archetypes
The fastest way to build something usable is to start from a known pattern and then cut it down to your work.
Chapter 11
Weekly Operating Ritual
The founder who never pauses to look at the roster is running a hope, not a team.
Chapter 12
Failure Modes
Every system designed by one person, for one person, contains the seeds of its own failure, usually planted in the moment of its greatest apparent success.
Conclusion
Coach Your Dream Team
The founder who builds the roster does not automate themselves out of a job. They automate themselves out of the bottleneck.
Editions
Editions and specifications
| Edition | Formats | Chapters | Pages | Reading time | ISBN (paperback) |
|---|---|---|---|---|---|
| English The Agent Dream Team | Kindle, Paperback, Hardcover | 14 | 484 | ± 8 hours | 9798173121790 |
| Dutch Het agent-droomteam | Kindle, Paperback, Hardcover | 14 | 522 | ± 8 hours | 9798173122698 |
Both editions are written natively. The Dutch text is not a machine translation of the English. · Trim size: 6.14x9.21″
Get the book
One title, every Amazon marketplace. Pick your format and your store.
Get the book
Reading from another country?Pick your own Amazon marketplace — same edition, your store.
Amazon links may include affiliate tags. That does not change the price you pay. Bol.com listings are third-party.
Frequently asked
What readers usually want to know
What is The Agent Dream Team about?
ROSTER shows solo operators how to create named specialist agents with charters, triggers, handoffs, and review gates instead of one overloaded chatbot. The subtitle is: Build Your Autonomous Specialist Roster for a One-Person Company.
What is the ROSTER framework?
ROSTER: Roles, Objectives, Skills and tools, Triggers, Evaluation and Rotation. Roles, Objectives, Skills, Triggers, Evaluation, Rotation
In which formats is The Agent Dream Team available?
The Agent Dream Team ships as Kindle, Paperback and Hardcover, on every Amazon marketplace worldwide. The Kindle edition is enrolled in Kindle Unlimited, so KU members read it free.
Is there a Dutch edition?
Yes. The Dutch edition is Het agent-droomteam, written as a native edition rather than a machine translation. It is available on Amazon too.
How long is The Agent Dream Team?
This edition runs 14 chapters, 484 pages in print and roughly 8 hours of reading.
Who is The Agent Dream Team for?
Elena is a composite. The frameworks are the author's operating design, and the book never dresses them as research. The multi-agent research carries its token bill and limits; Chapter 12 names six ways rosters degrade. Agents are hires, not prompts. You are the coach, not the only worker. Your morning starts in the team's output, not your own.
This is overkill for a solo founder.
One chatbot doing four jobs is already a team, just an unnamed one. ROSTER makes the charters explicit so you stop being the bottleneck in every thread.
Maintaining multiple agents sounds like more work.
You already maintain them: prompts, memory, and follow-ups, mixed in one window. Rotation and evaluation are how you stop rebuilding the same assistant every Monday.
My use case is too unique for templates.
The roster is unique. The six skills are not. Roles, objectives, tools, triggers, evaluation, and rotation are the same moves whether the specialist is research, ops, or GTM.
Isn't this just fancy prompting?
A prompt is not a charter, a trigger, or a scorecard. ROSTER is how a company of one coaches a roster instead of doing every job in one chat.
Is this the same as CHORUS?
No. CHORUS coordinates a human team of 2 to 15 with agents in the mix. ROSTER coaches named specialists for a one-person company. Paperback, hardcover, and Kindle are live in English and Dutch.
The production system
How this book was made
Every title moves through the same gated production line: sourced research, a claim-level evidence ledger, structural review, fact-checking, red-team critique, and a bilingual final edit. AI agents do specialist work inside those gates; judgment, voice, and accountability stay human.
- Claims enter an evidence ledger with a source and a confidence grade before they reach the page
- English and Dutch are two native editions, not a translation of one another
- Every chapter clears readability, rhythm, and style gates before it is typeset
Terminology
Books
