Read it as an argument you will have to make
An operator reads this to understand their week. You are reading it to decide whether you believe it, and to be able to defend it.
Get the operating-model argument in a form you can put in front of a board, and identify the claim you would be challenged on first.
This is the same page the Launchpad track opens with, and the reason to read it is different. An operator reads it to make sense of their week. You are reading it to decide whether the argument holds, because you are the person who will have to make it to a board, a CFO or a skeptical sales leader.
So read adversarially. The claim is that agents carry the repeatable work while people manage the last mile, which is a capacity argument, the same team covering more, with judgment concentrated where it changes outcomes. Note where you think that claim is strongest and where you would push back, because both will come up when you present it.
The distinction the track is built on is worth being deliberate about, because it is easy to blur and expensive to blur. A capacity argument says the same people cover more ground and spend a larger share of their time on work that requires them. A headcount argument says you need fewer people.
They lead to different implementations and different outcomes. The capacity framing is also the one that survives contact with what actually happens, which is why the module is named for it, and the ROI lesson that follows models it that way rather than as a cost-reduction case.

Now read the concept
This lesson is the orientation. The material itself lives on its own page, kept in one place so it stays current everywhere it is referenced.
You should be able to answer each of these from memory before opening it. Recalling the answer is what makes it stick; recognizing it when you read it does not.
Capacity says the same people cover more ground and spend more of their time on work that requires them. Headcount says you need fewer people. They lead to different implementations, and the capacity framing is the one that survives contact with what actually happens.
The claim you most want to test, in a form a number could answer. You are reading the concept page adversarially because you will have to defend it.
An operator reads this to understand their week. You are reading it to decide whether you believe it, and to be able to defend it.
Agents carry repeatable work; people manage the last mile. That is a capacity argument, not a headcount one, and the distinction is the whole case.
The next lesson models this with your own figures. Arrive with the claim you most want to test.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo