Slide 1 of 4
From the model to your calendar
The previous lesson explained the division of labor. This one is what it looks like on a Tuesday.
RevTech Launchpad
ReadLesson 2 of 6Understand the model
Working with AI agents day to day
Turn the model into the shape of your actual week, and take away the one habit that decides whether any of this sticks.
12 minBeginner
Part 1 of 2
The practical half of the model
The concept page told you what changes structurally. This guide tells you what changes in a working week: where prepared work shows up, what you do with it, and which habits separate teams who get value from this from teams who conclude it is noise.
It is placed second in the track deliberately. Read in the other order, the habits look like arbitrary process advice; read after the model, they are obviously the consequences of it.
Part 2 of 2
Read for the two habits, and commit to one of them
Two things in the guide do most of the work. The first is the rhythm (working the queue at set points rather than whenever a notification arrives) and the second is rejecting properly rather than silently. Both sound minor. Both are the difference between the system improving and the system staying exactly as good as it was on day one.
Do not finish this lesson without picking your two times. A pass at the start of the day and one before you finish is enough for most roles, and the specific times matter less than that they exist. The next lesson asks you to work your own queue for a week, and it is a materially different exercise if you have decided when.
- Pick the two points in your day now, and put them in the calendar
- Note what "rejecting properly" involves — you will need it in the practice week
- Notice which parts of your week the guide implies should get quieter
Now read the guide
Working with AI agents day to day
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.
Key questions
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.
What are the two habits that decide whether this sticks?
Working the queue on a rhythm rather than reactively, and rejecting properly rather than silently. Both sound minor and both are the difference between the system improving and staying as good as it was on day one.
What should you have decided by the end of this lesson?
The two specific times of day you will work your queue, in the calendar. The practice week that follows is a materially different exercise if you have not.
What to take away
- Read this before the practice week, not after. The week is where the two habits get tested.
- You are looking for one habit to commit to. Choose it before you close the guide.
Teach this lesson
The argument in 4 slides, for presenting it to your team
Slide 2 of 4
What to look for
- Why the queue is the interface, not a notification list
- The rhythm that makes it work — a pass at each end of the day
- What rejecting properly means, and why it matters more than approving
Slide 3 of 4
The habit is the whole thing
Teams that work the queue on a rhythm get value from this. Teams that work it reactively get an inbox they resent. The difference is not effort.
Slide 4 of 4
Decide before you move on
When your two passes will happen. Actually pick the times — the next lesson assumes you have.
Demo
Try the demo.
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